On 07/29/2018 05:38 AM, Anton Aylward wrote:
On 29/07/18 07:33 AM, Carlos E. R. wrote:
Use always the current (new version) browser, and exceptionally use the old version to do the file download only.
I have been faced with that situation for some located RPMs and my approach was to locate them with the browser but download them using FTP or, more likely, WGET. The latter has the advantage of easier restart if interrupted :-) Better debugging, more control over retries, authentication, logging, better visibility as to what is going on. GUIS (aka browsers aka firefox) hide too much, hide the configuration and operation, and as this thread is pointing out, make changes to configurations baseline that are not apparent without investigation of the release changelog, and ore. This is why so many of us favour CLI for many operations.
Yes, the GUI has its place and I wouldn't be without it for reading mail (a visual summary is better than the step-and-repeat one at a time of old terminal based mailx or the hell I go though with telephone voicemail!) or for the 99.8% case of web browsing.
But here we have a fine instance of the CLI being not merely a convenience but pretty much a necessity.
As suggested, I used wget to download the files I needed to get my wifi network running on my new Alienware 13 R3 laptop. I also found a link on the web for the Atheros Killer E2500 Gigabit Ethernet Controller which I works, but I have not taken time to determine why. The really strange, to me, commands are: sudo modprobe alx echo 1969 e0b1 | sudo tee /sys/bus/pci/drivers/alx/new_id
Other posts indicate that the opensuse kernel is just not up to date.
One problem at a time:-) Now for Firefox. Thanks for the inputs.