[opensuse] Upgrading 13.1 > 13.2
I just tried upgrading to 13.2 and I've noticed a couple of worrisome "features". First, when I boot from the installation, there is no longer any option to upgrade an existing system. After passing the licence (twice) and time zone, I'm immediately taken to "Suggested Partitioning". Unless I go into "Expert Partioner", btrfs will be used and the existing Windows partition is ignored and not mounted. Then, once past there, it wants to create a user, even though there already is one. Shouldn't it use the existing user(s)? At this point I decided to cancel the upgrade, as I don't know what damage might result to my existing system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 04:01 PM, lynn wrote:
On 09/11/14 21:55, James Knott wrote:
there is no longer any option to upgrade
It's on the first screen after 'boot from hard disk' and 'installation'.
Sorry, that was my mistake. I was booting from the "Live" pen drive and not the install. However, now that that's straightened out, when I get to the network adapters, there's no mention of network manager. While that may be OK on a desktop system, network manager is essential on an notebook. Or is making a notebook essentially useless when elsewhere now a "feature"? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 01:20 PM, James Knott wrote:
On 11/09/2014 04:01 PM, lynn wrote:
On 09/11/14 21:55, James Knott wrote:
there is no longer any option to upgrade
It's on the first screen after 'boot from hard disk' and 'installation'.
Sorry, that was my mistake. I was booting from the "Live" pen drive and not the install. However, now that that's straightened out, when I get to the network adapters, there's no mention of network manager. While that may be OK on a desktop system, network manager is essential on an notebook. Or is making a notebook essentially useless when elsewhere now a "feature"?
For me, NetworkManager is there, and a utility called connection editor appears in KDE. When you go into yast, it will warn you about network being handled by networkmanager service, which is handled by systemd network.target. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-09 16:20 (UTC-0500):
when I get to the network adapters, there's no mention of network manager. While that may be OK on a desktop system, network manager is essential on an notebook. Or is making a notebook essentially useless when elsewhere now a "feature"?
Did you happen to read the release notes? 13.2 has a new network management system called Wicked. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 05:22 PM, Felix Miata wrote:
Did you happen to read the release notes? 13.2 has a new network management system called Wicked.
Does it work like network manager? What happens to my WiFi settings. I have several connections and passwords configured. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 02:29 PM, James Knott wrote:
On 11/09/2014 05:22 PM, Felix Miata wrote:
Did you happen to read the release notes? 13.2 has a new network management system called Wicked.
Does it work like network manager? What happens to my WiFi settings. I have several connections and passwords configured.
These get handled by connection manager in the kde tray. (looks like a resistor from a motherboard). Don't know if it copies your existing settings or not, because I nuke my machine and started fresh. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 05:40 PM, John Andersen wrote:
These get handled by connection manager in the kde tray. (looks like a resistor from a motherboard). Don't know if it copies your existing settings or not, because I nuke my machine and started fresh.
As mentioned in another note, it's not even getting a network connection during the upgrade. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 05:29 PM, James Knott wrote:
On 11/09/2014 05:22 PM, Felix Miata wrote:
Did you happen to read the release notes? 13.2 has a new network management system called Wicked. Does it work like network manager? What happens to my WiFi settings. I have several connections and passwords configured.
Now, it wants to download the repository info, but claims there's no network configured. I'm connected via Ethernet and DHCP is available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 02:41 PM, James Knott wrote:
On 11/09/2014 05:29 PM, James Knott wrote:
On 11/09/2014 05:22 PM, Felix Miata wrote:
Did you happen to read the release notes? 13.2 has a new network management system called Wicked. Does it work like network manager? What happens to my WiFi settings. I have several connections and passwords configured.
Now, it wants to download the repository info, but claims there's no network configured. I'm connected via Ethernet and DHCP is available.
Has Ruben stopped over for coffee or something? ;-) Seriously, I just don't know why that would be. I'm old school, and burned a dvd and didn't worry about a net connection till it was done. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 05:47 PM, John Andersen wrote:
Seriously, I just don't know why that would be. I'm old school, and burned a dvd and didn't worry about a net connection till it was done.
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-09 18:14 (UTC-0500):
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past.
https://bugzilla.opensuse.org/show_bug.cgi?id=888805 sorta smells like what you're going through. If you'd like to get upgraded today, since it's Sunday and many regulars aren't around, I suggest doing as I do for fresh installs, and put your network configuration on cmdline as https://en.opensuse.org/SDB:Linuxrc explains to install using a fixed IP and wired Ethernet. Alternatively, do what I do for virtually all upgrading since Zypper grew past infancy. I use it to upgrade instead of installation media. First do zypper clean -a, then change the files in /etc/zypp.repos.d/ to point to 13.2, then zypper ref, then zypper dup. It's simple enough, and effective. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 06:42 PM, Felix Miata wrote:
James Knott composed on 2014-11-09 18:14 (UTC-0500):
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past. https://bugzilla.opensuse.org/show_bug.cgi?id=888805 sorta smells like what you're going through.
If you'd like to get upgraded today, since it's Sunday and many regulars aren't around, I suggest doing as I do for fresh installs, and put your network configuration on cmdline as https://en.opensuse.org/SDB:Linuxrc explains to install using a fixed IP and wired Ethernet.
Alternatively, do what I do for virtually all upgrading since Zypper grew past infancy. I use it to upgrade instead of installation media. First do zypper clean -a, then change the files in /etc/zypp.repos.d/ to point to 13.2, then zypper ref, then zypper dup. It's simple enough, and effective.
Well, I've got it installed, but now WiFi won't work. I get an error "Failed to add connection No session found for UUID 1000 (unknown)" With this and the failed networking at install, I have to wonder how much testing this went through. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-09 22:26 (UTC-0500):
Well, I've got it installed, but now WiFi won't work. I get an error "Failed to add connection No session found for UUID 1000 (unknown)"
Is that after trying the instructions in the relnote? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 07:26 PM, James Knott wrote:
On 11/09/2014 06:42 PM, Felix Miata wrote:
James Knott composed on 2014-11-09 18:14 (UTC-0500):
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past. https://bugzilla.opensuse.org/show_bug.cgi?id=888805 sorta smells like what you're going through.
If you'd like to get upgraded today, since it's Sunday and many regulars aren't around, I suggest doing as I do for fresh installs, and put your network configuration on cmdline as https://en.opensuse.org/SDB:Linuxrc explains to install using a fixed IP and wired Ethernet.
Alternatively, do what I do for virtually all upgrading since Zypper grew past infancy. I use it to upgrade instead of installation media. First do zypper clean -a, then change the files in /etc/zypp.repos.d/ to point to 13.2, then zypper ref, then zypper dup. It's simple enough, and effective.
Well, I've got it installed, but now WiFi won't work. I get an error "Failed to add connection No session found for UUID 1000 (unknown)"
With this and the failed networking at install, I have to wonder how much testing this went through.
Also look for messages in the boot log, or just switch to console 1. On my machine I had to run a command to fetch firmware before the wifi came up. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/14 04:45, John Andersen wrote:
Also look for messages in the boot log, or just switch to console 1. On my machine I had to run a command to fetch firmware before the wifi came up.
Exactly. You have to be an expert and know what you are doing. The upgrade is very difficult to do. Not all of us have time to install afresh and start again from nothing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2014 10:45 PM, John Andersen wrote:
Well, I've got it installed, but now WiFi won't work. I get an error
"Failed to add connection No session found for UUID 1000 (unknown)"
With this and the failed networking at install, I have to wonder how much testing this went through.
Also look for messages in the boot log, or just switch to console 1. On my machine I had to run a command to fetch firmware before the wifi came up.
The WiFi is working, but not properly. So far I've got that problem again, it doesn't remember passwords and doesn't get the DNS address via DHCP. It's clear 13.2 was not tested properly. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-10 00:42, Felix Miata wrote:
Alternatively, do what I do for virtually all upgrading since Zypper grew past infancy. I use it to upgrade instead of installation media. First do zypper clean -a, then change the files in /etc/zypp.repos.d/ to point to 13.2, then zypper ref, then zypper dup. It's simple enough, and effective.
Effective as in days, not hours. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2014-11-10 20:11 (UTC+0100):
Felix Miata wrote:
...It's simple enough, and effective.
Effective as in days, not hours.
Not hours here either; roughly 30 minutes here. It's sad that not everyone can have the connectivity they wish they had. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 10 Nov 2014 14:25:21 -0500
Felix Miata
Carlos E. R. composed on 2014-11-10 20:11 (UTC+0100):
Felix Miata wrote:
...It's simple enough, and effective.
Effective as in days, not hours.
Not hours here either; roughly 30 minutes here. It's sad that not everyone can have the connectivity they wish they had.
*Installing* 4500 packages during dup from 13.1 to 13.2 took approximately 17 hours here. Downloading was a breeze. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz Rotational notebook disk 5400 RPM. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-11-11 04:21, Andrei Borzenkov wrote:
В Mon, 10 Nov 2014 14:25:21 -0500
*Installing* 4500 packages during dup from 13.1 to 13.2 took approximately 17 hours here. Downloading was a breeze.
model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
I intend to stay with 13.1 for at least some months, but the offline upgrade from 12.3 to 13.1 was way faster. My system is larger than yours: Telcontar:~ # rpm -qa | wc -l 6160 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz Of course, offline doesn't update all, you have to do an online just after the first boot. With a /usable/ system, and takes ages on 1mbit/s. It makes one consider whether to mirror "oss" somewhere in advance. In my case, inet is the big hurdle. Root, rpm cache, and /usr are on different rotating disks (distributed load). And 8 Gigs of ram. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRiHjYACgkQtTMYHG2NR9VBpwCfc+DA6SgSTzQ21zwptUox64lt QCMAn3Xjx25mcWCvYQ1o9zkyt8S7ChGz =S7Vf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/14 00:14, James Knott wrote:
On 11/09/2014 05:47 PM, John Andersen wrote:
Seriously, I just don't know why that would be. I'm old school, and burned a dvd and didn't worry about a net connection till it was done.
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past.
Unless you're an expert, the only way to do it and keep all your configurations is from the dvd install. Boot and choose upgrade. You can only go online after the upgrade finishes. This really is a pity when you see Ubuntu with a one click upgrade with everything coming from Internet after each new release. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 02:26 AM, lynn wrote:
Unless you're an expert, the only way to do it and keep all your configurations is from the dvd install. Boot and choose upgrade. You can only go online after the upgrade finishes. This really is a pity when you see Ubuntu with a one click upgrade with everything coming from Internet after each new release. Given the USB and DVD install use the same ISO, why should there be a difference? Instead of burning a DVD with the downloaded ISO, I copied it to a USB pen drive. So, all the files that are on the DVD should be on the USB drive.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-10 13:23, James Knott wrote:
On 11/10/2014 02:26 AM, lynn wrote:
Unless you're an expert, the only way to do it and keep all your configurations is from the dvd install. Boot and choose upgrade. You
Given the USB and DVD install use the same ISO, why should there be a difference? Instead of burning a DVD with the downloaded ISO, I copied it to a USB pen drive. So, all the files that are on the DVD should be on the USB drive.
None. The other thing is the CD install, aka "live" install, aka "live kde" or "live gnome" install, the previously was a CD. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
lynn wrote:
Unless you're an expert, the only way to do it and keep all your configurations is from the dvd install. Boot and choose upgrade. You can only go online after the upgrade finishes. This really is a pity when you see Ubuntu with a one click upgrade with everything coming from Internet after each new release.
It is a major advantage to be able to install or upgrade every kind of software independent of the internet. In fact, it is a prerequisite for user control. For user control one cannot be dependent on the presence of external services or repositories in order to install on one's own system - the independence from net-based software subscriptions and services is the greatest advantage of Open Source and Linux. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/14 13:31, Per Inge Oestmoen wrote:
It is a major advantage to be able to install or upgrade every kind of software independent of the internet.
I'm sure it is. With this 13.2, that's all you _can_ do. What we want is a method for those of us who have a lot of machines or not a lot of time or who are not experts to be offered an update as and when it is released. On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated: 1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 10.11.2014 um 18:42 schrieb Felix Miata:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2
This can be done with one command :): sed -i.safe 's|13\.1|13.2|g' *repo This way, you get copies of the old files with .safe suffix, so you can switch them back, if needed (though I recommend disabling the repo, if the 13.2 repo does not yet exist). If you do not want those copies, simply user "sed -i 's..."
5-# zypper ref 6-# zypper dup 7-reboot into 13.2
That's my standard procedure :) Just my 2¢, Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/14 18:42, Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2
Nah, c'mon, please. Modestly? I've got 80 clients. Surely someone can give us a yes/no box to click after a new version is released can't they? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 10.11.2014 um 18:51 schrieb lynn:
On 10/11/14 18:42, Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2
Nah, c'mon, please. Modestly? I've got 80 clients. Surely someone can give us a yes/no box to click after a new version is released can't they?
I can put those commands in a shell script and start it from remote. Or per cron job. I'd use "zypper -n" then, because I don't want questions. Or I do it on a test box and clone the installation to my clients, ig their software is homogenuous enough. It might be not so much slower than 80 clicks on an OK button. Oh, and pssh is my friend :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 10 Nov 2014, Werner Flamme wrote:
I can put those commands in a shell script and start it from remote. Or per cron job. I'd use "zypper -n" then, because I don't want questions. Or I do it on a test box and clone the installation to my clients, ig their software is homogenuous enough.
It might be not so much slower than 80 clicks on an OK button. Oh, and pssh is my friend :)
And use the DVD-ISO as a local (shared) Repo: baseurl=iso:///?iso=openSUSE-<whatever>.iso&url=file:///PATH_TO_ISO I guess, you could use a nfs/cifs mount instead of file://, but it might be better to loop-mount the ISO and share the mountpoint (as in baseurl=nfs://...) -dnh, last time I burned an SUSE ISO was for 8.2, IIRC, zypper dupping (out of the DVD.iso + online) since IIRC 11.2. -- Mary had a little lamb, her father shot it dead. Now she goes to school with it, between two lumps of bread. -- sig of C. Herbig -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn composed on 2014-11-10 18:51 (UTC+0100):
Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2
Nah, c'mon, please. Modestly? I've got 80 clients. Surely someone can
If it takes as much as 3 minutes to set in motion, you're dawdling. To reduce the time for your 80 systems, adapt one of Werner's sed lines for #4, and reduce all the above to a simple script.
give us a yes/no box to click after a new version is released can't they?
Sure, given both motivation and requisite talent, and understanding a checkbox is something one normally finds in a GUI, which is better to not have running during the upgrade. It is after all FOSS. If 2-3 minutes/system is a problem for you, script it, or motivate somebody. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-10 18:51, lynn wrote:
On 10/11/14 18:42, Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2
Nah, c'mon, please. Modestly? I've got 80 clients. Surely someone can give us a yes/no box to click after a new version is released can't they?
Surely you can script the above. Some did. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/10/2014 12:42 PM, Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2
Does this apply for all those repositories outside of the ones in the normal distribution basic set? Well obviously not all the Build service ones! What about "Kernel_Standard" then?
5-# zypper ref 6-# zypper dup 7-reboot into 13.2
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2014-11-10 12:59 (UTC-0500):
Felix Miata wrote:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2
Does this apply for all those repositories outside of the ones in the normal distribution basic set?
It probably does for most 80 system admins, and for others, most if not all eventually. The ref process will notify of any repos that do not exist and ask what you want it to do about it/them. If you're worried any might not, don't rush to upgrade to a less than week old release. Waiting a couple of months or more for updates to show up to fix new release bugs is smart policy.
Well obviously not all the Build service ones!
What about "Kernel_Standard" then?
It includes no version string, correct? You and sed don't "replace" something that doesn't exist.
5-# zypper ref 6-# zypper dup 7-reboot into 13.2 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 01:27 PM, Felix Miata wrote:
Well obviously not all the Build service ones! What about "Kernel_Standard" then? It includes no version string, correct? You and sed don't "replace" something that doesn't exist.
Mine reads (at present) $ grep 13 /etc/zypp/repos.d/Kernel_standard.repo baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-13.1/standard/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2014-11-10 14:46 (UTC-0500):
Felix Miata wrote:
Well obviously not all the Build service ones! What about "Kernel_Standard" then?
It includes no version string, correct? You and sed don't "replace" something that doesn't exist.
Mine reads (at present) $ grep 13 /etc/zypp/repos.d/Kernel_standard.repo baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-13.1/standard/
Why would the procedure be any different for that? http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard/ exists. If you're worried about the kernel, lock it before upgrading, then unlock, and maybe use YaST instead of Zypper to ensure the repo you think you want is valid and suitable. Too many lookalike repos. One I (sometimes) use is: baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/ For 13.1, ever since I discovered it, I've been using: http://download.opensuse.org/repositories/home:/mkubecek:/evergreen-13.1/ope... It I would disable before upgrading to 13.2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Felix Miata
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup
much safer, zypper dup -d zypper dup
7-reboot into 13.2
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 12:42 PM, Felix Miata wrote:
lynn composed on 2014-11-10 18:22 (UTC+0100):
On Ubuntu, after you have logged in, it asks you if you want to upgrade. You click yes or no. There is nothing to configure or isos to burn. We have nothing like that.
We do have something effectively equivalent that is modestly more complicated:
1-login on a vtty as root (vtty recommended but not required) 2-# zypper clean -a 3-navigate to /etc/zypp/repos.d/ 4-edit each file there, replacing each instance of 13.1 with 13.2 5-# zypper ref 6-# zypper dup 7-reboot into 13.2
It occurs to me that unlike a fresh install, this is not going to do anything to your partitions, install a new root file system, alter your configuration in many ways. If you have a working network/wifi it shouldn't alter that. I've done this before, though when I get a new drive I do carry out a 'proper' install. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 18:22, lynn a écrit :
On 10/11/14 13:31, Per Inge Oestmoen wrote:
It is a major advantage to be able to install or upgrade every kind of software independent of the internet.
I'm sure it is. With this 13.2, that's all you _can_ do.
no. I just installed 13.2 (not upgraded) and it asked from the beginning for network and did accept wifi - no problem jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/11/14 19:07, jdd wrote:
Le 10/11/2014 18:22, lynn a écrit :
On 10/11/14 13:31, Per Inge Oestmoen wrote:
It is a major advantage to be able to install or upgrade every kind of software independent of the internet.
I'm sure it is. With this 13.2, that's all you _can_ do.
no.
I just installed 13.2 (not upgraded) and it asked from the beginning for network and did accept wifi - no problem
jdd
No Installing, maybe. But you need to be an expert to set up the wifi. We are upgrading in this thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
On 10/11/14 19:07, jdd wrote:
Le 10/11/2014 18:22, lynn a écrit :
On 10/11/14 13:31, Per Inge Oestmoen wrote:
It is a major advantage to be able to install or upgrade every kind of software independent of the internet. I'm sure it is. With this 13.2, that's all you _can_ do. no. I just installed 13.2 (not upgraded) and it asked from the beginning for network and did accept wifi - no problem
Installing, maybe. But you need to be an expert to set up the wifi. We are upgrading in this thread.
Fylly agree. It should absolutely not be necessary to be an expert to set up the wi-fi. Are these problems still persisting? Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 02:26 AM, lynn wrote:
On 10/11/14 00:14, James Knott wrote:
On 11/09/2014 05:47 PM, John Andersen wrote:
Seriously, I just don't know why that would be. I'm old school, and burned a dvd and didn't worry about a net connection till it was done.
I'm installing from USB pen drive, but that shouldn't make any difference. I also have installed without worrying about a network connection in the past.
Unless you're an expert, the only way to do it and keep all your configurations is from the dvd install. Boot and choose upgrade. You can only go online after the upgrade finishes. This really is a pity when you see Ubuntu with a one click upgrade with everything coming from Internet after each new release.
No argument with that! As laptops are getting thinner one of the losses is a DVD drive. (the plethoa of USB ports is another loss.) Being able to install or update from a USB stick as effortlessly as we used to - or some of us who have the PMA and lap-cat software did) - with the DVD (and memtest and do maintenance) is getting increasingly important. You are right. Suse used to have one of the nicest installers, even the dreaded ZD-Net reviews used to admit that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 15:30, Anton Aylward a écrit :
As laptops are getting thinner one of the losses is a DVD drive. (the
but an external usb drive is around $20 (and dvd's are much cheaper than usb keys)$ notice that in my experience, usb keys are *much* more reliable than dvd's jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 10:59 AM, jdd wrote:
Le 10/11/2014 15:30, Anton Aylward a écrit :
As laptops are getting thinner one of the losses is a DVD drive. (the
but an external usb drive is around $20 (and dvd's are much cheaper than usb keys)$
notice that in my experience, usb keys are *much* more reliable than dvd's
It depends on how you do the accounting. A stack of 50 DVDs costs about the same in my local computer discount stores as a 16G USB stick. Or a little less than an el-cheapo 32G SD card on ebay. Since I've arranged so much of my FS in 5G partitions they map nicely onto the DVDs. Since some are a good deal less than 5G occupied I can often put 3 or 3 on a DVD at present. In a years or so of growth that may change. But then again, I may do some pruning. So for less than $10 I have a year's worth of backup media. BACKUPS ARE NOT ARCHIVES http://www.factorydirect.ca/Canada-Ontario-/Recordable_Media/Dvd/Dvd-R_Rw/HP... or even http://www.factorydirect.ca/Canada-Ontario-/Recordable_Media/Dvd/Dvd-R_Rw/TD... that's C$15 for 500G of storage. if I go for the no-name media it works out even cheaper. Now of you are talking ARCHIVE storage as opposed to backup of last iteration or two for disaster recovery, then that's another matter. Thanks to "the race to zero" archiving to the Cloud makes more sense. Heck, at $50 for a 1T drive its almost worth using rotating rust for archives. Image your drive and put the result in a bank vault ... that's pretty near as cheap as bulk DVD. So the investment in a USB DVD writer makes sense. Among other things. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 18:26, Anton Aylward a écrit :
On 11/10/2014 10:59 AM, jdd wrote:
Le 10/11/2014 15:30, Anton Aylward a écrit :
As laptops are getting thinner one of the losses is a DVD drive. (the
but an external usb drive is around $20 (and dvd's are much cheaper than usb keys)$
So for less than $10 I have a year's worth of backup media.
I know, dvd cost if around cents 20 :-) but are them reliable? in my experience, if they are read on the writer they where written by, peobably no problem, but for *install* dvd, this is not what is used, no reason to install on the computer you used to write :-) on recent time, I see more and more install problem with dvd's and absolutely no with usb (I speak about media problems) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2014-11-10 19:10 (UTC+0100):
I know, dvd cost if around cents 20 :-)
but are them reliable?
They are if you buy good ones instead of junk. http://www.digitalfaq.com/reviews/dvd-media.htm Don't forget, HDs haven't been as reliable media as we would like for many years. Perfection is just a dream. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 19:18, Felix Miata a écrit :
They are if you buy good ones instead of junk. http://www.digitalfaq.com/reviews/dvd-media.htm
no. I buy the bmost expensive available at my dealer. it's not (IMHO) a dvd problem but a reader problem, dvd readers are so cheap nowaday, they are not well aligned and do not like burned dvd - we are back at the dvd beginning era :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2014-11-10 20:15 (UTC+0100):
Felix Miata composed:
They are if you buy good ones instead of junk. http://www.digitalfaq.com/reviews/dvd-media.htm
no.
I buy the bmost expensive available at my dealer.
No local dealers here that offer any quality media. For several years I've only been buying JVC Taiyo Yuden, making bad discs here very rare.
it's not (IMHO) a dvd problem but a reader problem, dvd readers are so cheap nowaday, they are not well aligned and do not like burned dvd - we are back at the dvd beginning era :-(
Futzing with reader upgrades might be OK for those with one or few, not for those with more, or those married to hardware for which upgrading is no option. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 20:31, Felix Miata a écrit :
No local dealers here that offer any quality media. For several years I've only been buying JVC Taiyo Yuden, making bad discs here very rare.
it's the brand I have :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 01:10 PM, jdd wrote:
on recent time, I see more and more install problem with dvd's and absolutely no with usb (I speak about media problems)
I've never had problems with the DVDs[1] but James has just documented problems with USB. [1] except one time on a new machine which, as it turned out, only had a CD reader. That was fixed with a screwdriver. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 01:20 PM, Anton Aylward wrote:
I've never had problems with the DVDs[1] but James has just documented problems with USB.
I didn't experience a problem with USB. I experienced a problem with the software I installed from the USB. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Nov 10, 2014 at 4:36 PM, James Knott
On 11/10/2014 01:20 PM, Anton Aylward wrote:
I've never had problems with the DVDs[1] but James has just documented problems with USB.
I didn't experience a problem with USB. I experienced a problem with the software I installed from the USB. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I am glad I did not have any of these problems. You can also use YaST2 Software Repositories to manually change each of the configured repo's to the 13.2 version, I also create local ios image repos for the DVD installer, Additional Language and non-OSS disk images prior to the zypper dup so I have as much local packages as possible. I place these in /opt/local.repos. I did not have any of the issues you are talking about. If you know you need closed source WiFi drivers I would have them ready ahead of time and make sure that your drivers are supported currently by the kernel that is included with 13.2. What WiFi hardware do you have? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Is there any way to change what appears on the boot menu? On this computer, I have 2 partitions that show up in the menu for Windows. One is the Windows 7 partition and the other is the restore partition, which I most definitely do not want to be available on the boot menu. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 07:30 AM, James Knott wrote:
Is there any way to change what appears on the boot menu? On this computer, I have 2 partitions that show up in the menu for Windows. One is the Windows 7 partition and the other is the restore partition, which I most definitely do not want to be available on the boot menu.
I believe someone mentioned editing grub.cfg. However, that appears to be a complex script, which I have no idea how to modify. Is there no simple way to keep grub2 from including that restore partition in the menu? There's another, mission critical issue with the menu. Next to the Windows partitions, there's the Microsoft flag. Since Linux shouldn't be outdone by Windows, is there any way to put a "Tux" image next to the Linux items? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 14 Nov 2014 16:00:15 -0500
James Knott
On 11/10/2014 07:30 AM, James Knott wrote:
Is there any way to change what appears on the boot menu? On this computer, I have 2 partitions that show up in the menu for Windows. One is the Windows 7 partition and the other is the restore partition, which I most definitely do not want to be available on the boot menu.
I believe someone mentioned editing grub.cfg. However, that appears to be a complex script, which I have no idea how to modify. Is there no simple way to keep grub2 from including that restore partition in the menu?
os-prober tries to avoid restore partitions, but of course it is best efforts heuristic. It is always possible that vendor or newer Windows changed something so it is not detected. Open bug report so it can be investigated.
There's another, mission critical issue with the menu. Next to the Windows partitions, there's the Microsoft flag. Since Linux shouldn't be outdone by Windows,
I almost stopped reading further ...
is there any way to put a "Tux" image next to the Linux items?
For me on 13.2 it shows SUSE icon (I forgot English name for this animal) for openSUSE menu entries. Do you want to replace SUSE icon with something else or you mean something different? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2014 02:04 AM, Andrei Borzenkov wrote:
For me on 13.2 it shows SUSE icon (I forgot English name for this animal) for openSUSE menu entries. Do you want to replace SUSE icon with something else or you mean something different? --
I'm running 13.1 and see nothing next to the openSUSE items. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2014 09:47 PM, James Knott wrote: > On 11/15/2014 02:04 AM, Andrei Borzenkov wrote: >> >For me on 13.2 it shows SUSE icon (I forgot English name for this >> >animal) - Gecko :) .............. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2014 03:09 PM, ellanios82 wrote: >> On 11/15/2014 02:04 AM, Andrei Borzenkov wrote: >>> >For me on 13.2 it shows SUSE icon (I forgot English name for this >>> >animal) > - Gecko :) I thought it was a "Geeko". ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2014-11-15 at 15:27 -0500, James Knott wrote: > On 11/15/2014 03:09 PM, ellanios82 wrote: > >> On 11/15/2014 02:04 AM, Andrei Borzenkov wrote: > >>> >For me on 13.2 it shows SUSE icon (I forgot English name for this > >>> >animal) > > - Gecko :) > > > I thought it was a "Geeko". ;-) FOr the love... ugh. He is a chameleon, named "Geeko" which is a pun on the name of another lizard species juxtaposed with 'geek'. -- Roger Luedecke openSUSE Project Member and Advocate since 2011 http://www.opensuseadventures.blogspot.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 15 Nov 2014 14:47:41 -0500
James Knott
On 11/15/2014 02:04 AM, Andrei Borzenkov wrote:
For me on 13.2 it shows SUSE icon (I forgot English name for this animal) for openSUSE menu entries. Do you want to replace SUSE icon with something else or you mean something different? --
I'm running 13.1 and see nothing next to the openSUSE items.
Assuming that you are using openSUSE bootloader theme - copy /boot/grub2/themes/openSUSE/icons/opensuse.png to opensuse-13-1.png in the same directory. Otherwise check --class options in menuentry command(s) in grub.cfg - grub will search icons with corresponding names in order they appear in "menuentry" command. Note that on 13.1 selected menu entry highlighting will hide icon for this menu entry ... at least that is what I see. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Another problem. WiFi does not remember passwords, so I have to enter it each time I connect. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 07:39 AM, James Knott wrote:
Another problem. WiFi does not remember passwords, so I have to enter it each time I connect.
Not only that, it's now forgetting that I connected with WiFi previously and I'm back to the "Failed to add connection" problem. Also, there appears to be a problem with getting the DNS via DHCP when connecting via WiFi. Did anyone test this package? How can it be possible for so many serious faults to make it through? I may, for the first time ever, roll back to the previous version. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Minor comment - SusE has asked for a user during installation for some
time now, at least the way I do it (fresh install to root with /home
preserved - after some bad experiences with upgrades I avoid them).
The simplest way to avoid later problems is to define a unique user
just for installation e.g. name=user name + opensuse version. You can
later remove this user when you set up the "real" users after
successful installation.
On 9 November 2014 21:55, James Knott
I just tried upgrading to 13.2 and I've noticed a couple of worrisome "features". First, when I boot from the installation, there is no longer any option to upgrade an existing system. After passing the licence (twice) and time zone, I'm immediately taken to "Suggested Partitioning". Unless I go into "Expert Partioner", btrfs will be used and the existing Windows partition is ignored and not mounted. Then, once past there, it wants to create a user, even though there already is one. Shouldn't it use the existing user(s)?
At this point I decided to cancel the upgrade, as I don't know what damage might result to my existing system.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Due to all the show stopper problems with 13.2, I decided to restore my original 13.1 system. After restoring from backup, the system is not bootable. I am following the instructions to restore grub from here: https://forums.opensuse.org/content.php/128-Re-install-Grub2-from-DVD-Rescue However, while following those instructions, the steps mount /proc and mount /sys fail with no such file or directory. Is there any way past this point? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 19:34 (UTC-0500):
Due to all the show stopper problems with 13.2, I decided to restore my original 13.1 system. After restoring from backup, the system is not bootable. I am following the instructions to restore grub from here:
https://forums.opensuse.org/content.php/128-Re-install-Grub2-from-DVD-Rescue
However, while following those instructions, the steps mount /proc and mount /sys fail with no such file or directory. Is there any way past this point?
Use chrooting instructions at https://en.opensuse.org/SDB:Recover_root_password instead. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 07:45 PM, Felix Miata wrote:
Use chrooting instructions at https://en.opensuse.org/SDB:Recover_root_password instead. --
That doesn't work either. When I enter the command mount -o remount,rw /dev/sda6/ /mnt, I get a long listing of the mount command options followed by "mount.bin: /mnt not mounted or bad option". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 20:27 (UTC-0500):
Felix Miata wrote:
Use chrooting instructions at https://en.opensuse.org/SDB:Recover_root_password instead.
That doesn't work either. When I enter the command mount -o remount,rw /dev/sda6/ /mnt, I get a long listing of the mount command options followed by "mount.bin: /mnt not mounted or bad option".
Try: mount -o remount,rw /dev/sda6 /mnt -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 08:43 PM, Felix Miata wrote:
That doesn't work either. When I enter the command mount -o remount,rw
/dev/sda6/ /mnt, I get a long listing of the mount command options followed by "mount.bin: /mnt not mounted or bad option". Try: mount -o remount,rw /dev/sda6 /mnt
That was a typo in my email. I didn't have sda6/ when I entered the command. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 20:48 (UTC-0500):
Felix Miata wrote:
That doesn't work either. When I enter the command mount -o remount,rw /dev/sda6/ /mnt, I get a long listing of the mount command options followed by "mount.bin: /mnt not mounted or bad option".
Try: mount -o remount,rw /dev/sda6 /mnt
That was a typo in my email. I didn't have sda6/ when I entered the command.
AFAIK, remount is a valid option only when the device is already mounted, and rw probably only if not already mounted rw. If following the instructions, why would you need to *re*-mount your / partition? Maybe https://en.opensuse.org/SDB:Disaster_Recovery will help? Maybe your whole process should be shared here for people to look for a flaw. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 09:10 PM, Carlos E. R. wrote:
On 2014-11-11 03:02, Felix Miata wrote:
James Knott composed on 2014-11-10 20:48 (UTC-0500): ... Maybe your whole process should be shared here for people to look for a flaw. Yes, please!
What I need right now is a way to get a working system again. I need this computer for work tomorrow and currently can't boot anything. Also, it's bed time in about 1.5 hours. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-11 03:25, James Knott wrote:
On 11/10/2014 09:10 PM, Carlos E. R. wrote:
On 2014-11-11 03:02, Felix Miata wrote:
James Knott composed on 2014-11-10 20:48 (UTC-0500): ... Maybe your whole process should be shared here for people to look for a flaw. Yes, please!
What I need right now is a way to get a working system again. I need this computer for work tomorrow and currently can't boot anything. Also, it's bed time in about 1.5 hours.
It is past bedtime here by several hours. But I don't know what you are trying to do do. Mount sda6 again, rw, why? Where? What for? Then what? Please, full details. What exact commands you type, what exact response you get. Either type, or photos. If you want help from people not on your seat, you have to help us understand, first. You should know that, I have known you here for years, you are no novice in help-mail-lists. Take your time. I'm going to bed now. :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/10/2014 09:40 PM, Carlos E. R. wrote:
But I don't know what you are trying to do do. Mount sda6 again, rw, why? Where? What for? Then what?
I upgraded 13.1 to 13.2. Due to problems with 13.2, I decided to go back to 13.1. I restored the sda6 partition, which contained 13.1 from backup. After that, Grub wouldn't boot. I'd wind up in "Grub rescue". I'd like to have a working 13.1 system again. At the moment, I'm reinstalling 13.2, so that I'll have a working system for work tomorrow.
Please, full details. What exact commands you type, what exact response you get. Either type, or photos.
I have done that for some things that caused errors. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 09:02 PM, Felix Miata wrote:
Maybe your whole process should be shared here for people to look for a flaw. --
Well, I started with a working 13.1 system on my ThinkPad and ran the 13.2 update. I then came across that error with the networking during install. After I got it running, I found some problems with WiFi that make it unusable, as described in other messages. I then restored my original 13.1 partition, but cannot get it to boot. If I can't find a solution soon, I'm going to have to reinstall 13.2 just so that I have a working system, so that I'll have a computer for work tomorrow. If all else fails, I'll see about having it boot directly into Windows, so I can do my work tomorrow. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
your whole process should be shared here for people to look for a flaw.
What I meant was in meticulous detail. You've only provided part of the puzzle pieces we need to assemble to figure out what you need to do. Booting from a Grub prompt should be doable, as should chroot, but only if all your typing is done as necessary for your environment. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 08:48 PM, James Knott wrote:
On 11/10/2014 08:43 PM, Felix Miata wrote:
That doesn't work either. When I enter the command mount -o remount,rw
/dev/sda6/ /mnt, I get a long listing of the mount command options followed by "mount.bin: /mnt not mounted or bad option". Try: mount -o remount,rw /dev/sda6 /mnt That was a typo in my email. I didn't have sda6/ when I entered the command.
Also, one thing that article doesn't mention is the mount /dev/sda6 /mnt must be issued before remount. However, that first part, isn't relevant. I started with the part that begins with mount /dev/hdxy /mnt and went from there. I was able to run Yast > boot loader, but it complained about the partitioning. One other thing I can do is boot the system and am taken to a grub rescue prompt. Can I do anything there? I've tried searching on the Internet, but not found much. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 21:02 (UTC-0500):
One other thing I can do is boot the system and am taken to a grub rescue prompt. Can I do anything there? I've tried searching on the Internet, but not found much.
What can be done via Grub's menu can be done at the Grub prompt. http://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub... should get you through the process, but note you don't need to know or type more than vmlinuz and initrd, which are openSUSE's symlinks to whatever the current kernel and initrd's versions are. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 09:15 PM, Felix Miata wrote:
What can be done via Grub's menu can be done at the Grub prompt. http://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub... should get you through the process, but note you don't need to know or type more than vmlinuz and initrd, which are openSUSE's symlinks to whatever the current kernel and initrd's versions are.
I hope that works with LVM as in root=/dev/mapper/vgmain-vROOT -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 09:15 PM, Felix Miata wrote:
James Knott composed on 2014-11-10 21:02 (UTC-0500):
One other thing I can do is boot the system and am taken to a grub rescue prompt. Can I do anything there? I've tried searching on the Internet, but not found much. What can be done via Grub's menu can be done at the Grub prompt. http://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub... should get you through the process, but note you don't need to know or type more than vmlinuz and initrd, which are openSUSE's symlinks to whatever the current kernel and initrd's versions are.
I actually found that earlier. It fails on this line: "grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1" with Unknown command 'linux'. I keep finding all sorts of things that are supposed to work, but fail at one point or another. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 21:33 (UTC-0500):
http://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub...
I actually found that earlier. It fails on this line:
"grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1" with Unknown command 'linux'.
Maybe you are dealing with a Grub Legacy prompt? Try substituting kernel for linux there.
I keep finding all sorts of things that are supposed to work, but fail at one point or another.
Your kind of problem is justfication for creating multiboot installations as a habit (as I do), having something familiar and handy to fall back on *easily* when a new installation turns fubar. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 09:47 PM, Felix Miata wrote:
Maybe you are dealing with a Grub Legacy prompt? Try substituting kernel for linux there.
That will have to wait for another time. At the moment, I'm reinstalling 13.2, so that I can do my work tomorrow.
Your kind of problem is justfication for creating multiboot installations as a habit (as I do), having something familiar and handy to fall back on *easily* when a new installation turns fubar.
That would take disk space I don't have. I put a 700 GB drive in this computer several months ago, because I ran out of space for work stuff on the Windows 7 partition. The reinstall just completed and I'm back at the grub rescue prompt. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 22:34 (UTC-0500):
On 11/10/2014 09:47 PM, Felix Miata wrote:
Your kind of problem is justfication for creating multiboot installations as a habit (as I do), having something familiar and handy to fall back on *easily* when a new installation turns fubar.
That would take disk space I don't have.
Are you sure? The largest / filesystem under this roof is 10.2G. Most are much smaller. How big was your 13.1 /, and how much of it was used?
I put a 700 GB drive in this computer several months ago, because I ran out of space for work stuff on the Windows 7 partition.
The reinstall just completed and I'm back at the grub rescue prompt.
Installed to which partition, and on which partition(s) is/are Windows'? What other partitions exist? Did number or size change via 13.2 installation? Earlier and separately you suggested / was on both sda1 and sda6. Which is/are correct? Usually Windows Vista+ get sda1 and sda2 at least. Having Windows installed, and where it's installed, affects what needs to be done WRT bootloader installation and operation. You have a habit of providing so little information it is difficult to impossible to give you the help you need. Has the low number trying to help in today's thread escaped your notice? When in doubt how much information to provide, choose more, not less. There is little clairvoyance to be found here. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 11:00 PM, Felix Miata wrote:
Usually Windows Vista+ get sda1 and sda2 at least. Having Windows installed, and where it's installed, affects what needs to be done WRT bootloader installation and operation.
It's Windows 7 and has 3 primary partitions. I created an extended partition to hold /, /home and swap. However, I just did an install, not upgrade to 13.2, so that I could get the computer working for tomorrow. I can now boot into both Linux and Windows, so I can now go to bed and to work tomorrow. BTW, I noticed the boot menu screen looks different between the install and upgrade versions, but that sda1 recovery partition is still listed. I'd like to know how to remove that. When I have time, I can try restoring that 13.1 system, if the problems remain in 13.2. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 23:19 (UTC-0500):
It's Windows 7 and has 3 primary partitions. I created an extended partition to hold /, /home and swap.
However, I just did an install, not upgrade to 13.2, so that I could get the computer working for tomorrow. I can now boot into both Linux and Windows, so I can now go to bed and to work tomorrow.
\o/
BTW, I noticed the boot menu screen looks different between the install and upgrade versions,
If you had upgraded to 13.1 from 12.3, and to 12.3 from 12.2, almost certainly you were using Grub Legacy, not Grub2. Those upgrades would not have replaced Grub Legacy with Grub2 unless you took intentional steps to have that done.
but that sda1 recovery partition is still listed. I'd like to know how to remove that.
Edit /etc/grub.d/30_os-prober have Grub ignore it, then rebuild the Grub menu.
When I have time, I can try restoring that 13.1 system, if the problems remain in 13.2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 11:19 PM, James Knott wrote:
However, I just did an install, not upgrade to 13.2, so that I could get the computer working for tomorrow. I can now boot into both Linux and Windows, so I can now go to bed and to work tomorrow.
Once again, WiFi passwords are not remembered. It shouldn't be necessary to re-enter the password every time. When I get time, I'll again try to reinstall the old 13.1 system. One thing that might have been causing problems is it was Grub and not Grub 2. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/11/2014 07:39 AM, James Knott wrote:
Once again, WiFi passwords are not remembered. It shouldn't be necessary to re-enter the password every time.
The password appears to stick if you go into the settings and edit the connection. Also, the DNS problem appears to have gone. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 11 november 2014 08:00:32 schreef James Knott:
On 11/11/2014 07:39 AM, James Knott wrote:
Once again, WiFi passwords are not remembered. It shouldn't be necessary to re-enter the password every time.
The password appears to stick if you go into the settings and edit the connection.
It probably should be in the Release Notes that after using WiFi in the installation, the password given there is not remembered and, after logging in, one should click on the NM widget to configure a WiFi connection to get a network up and running. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/11/2014 08:19 AM, Freek de Kruijf wrote:
Op dinsdag 11 november 2014 08:00:32 schreef James Knott:
On 11/11/2014 07:39 AM, James Knott wrote:
Once again, WiFi passwords are not remembered. It shouldn't be necessary to re-enter the password every time. The password appears to stick if you go into the settings and edit the connection. It probably should be in the Release Notes that after using WiFi in the installation, the password given there is not remembered and, after logging in, one should click on the NM widget to configure a WiFi connection to get a network up and running.
Or rather it should just work as it did in 13.1. It should be necessary to only enter the password when first requested and not have to go into the settings at all. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/11/2014 14:32, James Knott a écrit :
Or rather it should just work as it did in 13.1. It should be necessary to only enter the password when first requested and not have to go into the settings at all.
in 13.1 you coudn't setup the wifi during install :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/11/2014 09:27 AM, jdd wrote:
Le 11/11/2014 14:32, James Knott a écrit :
Or rather it should just work as it did in 13.1. It should be necessary to only enter the password when first requested and not have to go into the settings at all.
in 13.1 you coudn't setup the wifi during install :-(
jdd
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-12 03:14, James Knott wrote:
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing.
Then, why didn't you test and report it? It was you duty >;-) It probably did not happen to many, that's why it was not, probably. Or did not happen to anybody that thought about reporting it then instead of telling here and now. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Le 12/11/2014 03:14, James Knott a écrit :
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing.
OK you have to go to the wifi parameters and give the pass there. the wifi app should probably ask (tick option) if one wants to keep the pass when asking for one jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 03:05 AM, jdd wrote:
Le 12/11/2014 03:14, James Knott a écrit :
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing.
OK
you have to go to the wifi parameters and give the pass there.
the wifi app should probably ask (tick option) if one wants to keep the pass when asking for one
jdd
What are you going on about? I have been using WiFi for years and have never seen the behaviour you describe. Not in Linux, Windows, Android, iPhone, iPad etc.. Never. Why is it supposed to be the case now? With all those, you're asked for the password when you first try to connect and it is then remembered. This is clearly a bug. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 07:49 AM, James Knott wrote:
On 11/12/2014 03:05 AM, jdd wrote:
Le 12/11/2014 03:14, James Knott a écrit :
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing.
OK
you have to go to the wifi parameters and give the pass there.
the wifi app should probably ask (tick option) if one wants to keep the pass when asking for one
jdd
What are you going on about? I have been using WiFi for years and have never seen the behaviour you describe. Not in Linux, Windows, Android, iPhone, iPad etc.. Never. Why is it supposed to be the case now? With all those, you're asked for the password when you first try to connect and it is then remembered. This is clearly a bug.
Left click on the NM icon in the task bar; then click on the wrench icon. You should then be able to edit each connection and set the password for each. The password will then be remembered. This is perhaps a new "feature" of NM. :-) -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/11/14 00:33, Ken Schneider - openSUSE wrote:
On 11/12/2014 07:49 AM, James Knott wrote:
On 11/12/2014 03:05 AM, jdd wrote:
Le 12/11/2014 03:14, James Knott a �crit :
I'm not talking about during the install. I'm talking about after the installation is complete. I install using an Ethernet connection. Just to verify, I connected to another SSID with the appropriate password and connected. I then rebooted and tried the same connection. It is again asking for the password. This is clearly a bug that should never have made it past testing.
OK
you have to go to the wifi parameters and give the pass there.
the wifi app should probably ask (tick option) if one wants to keep the pass when asking for one
jdd
What are you going on about? I have been using WiFi for years and have never seen the behaviour you describe. Not in Linux, Windows, Android, iPhone, iPad etc.. Never. Why is it supposed to be the case now? With all those, you're asked for the password when you first try to connect and it is then remembered. This is clearly a bug.
Left click on the NM icon in the task bar; then click on the wrench icon. You should then be able to edit each connection and set the password for each. The password will then be remembered. This is perhaps a new "feature" of NM. :-)
Sorry to butt in here, and I have not had the time to read all the posts in this thread (lost my phone line for over a week and just got it back), but I suspect that not getting wifi connection depends on whether you have installed the release version of oS 13.2 or are working from something like RC1 which was then 'updated' to the final 13.2. The behaviour mentioned where it was necessary to enter the password each and everytime you booted into '13.2' and to have wifi was the case with RC1. Annoyed the heck out of me to say the least. But doing a *clean* install of the "final" oS 13.2 solved this annoyance. At least this is what happened here. BC -- Using openSUSE 13.1, KDE 4.14.3 & kernel 3.17.2-3 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 12/11/2014 15:02, Basil Chupin a écrit :
The behaviour mentioned where it was necessary to enter the password each and everytime you booted into '13.2' and to have wifi was the case with RC1. Annoyed the heck out of me to say the least. But doing a *clean* install of the "final" oS 13.2 solved this annoyance.
At least this is what happened here.
no it's from clean 13.2 install. and not sure it's an annoyance, a passwd is a poasswd and don't have to be stored if not instructed to do so. but a simple tick box on the passwd dialog could solve the problem (as for most mailbox) now one have to go to the wifi setup, after this no more password asked jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 09:37 AM, jdd wrote:
and not sure it's an annoyance, a passwd is a poasswd and don't have to be stored if not instructed to do so.
Where are you getting that nonsense from??? I have set up WiFi on many computers and other devices and have never, ever come across what you describe. It certainly wasn't that way in 13.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 09:02 AM, Basil Chupin wrote:
The behaviour mentioned where it was necessary to enter the password each and everytime you booted into '13.2' and to have wifi was the case with RC1. Annoyed the heck out of me to say the least. But doing a *clean* install of the "final" oS 13.2 solved this annoyance.
At least this is what happened here.
This is on a clean install. I first experienced it when I tried to upgrade from 13.1. I then did a new install and the problem remained, though another problem with DNS was fixed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott
What are you going on about? I have been using WiFi for years and have never seen the behaviour you describe. Not in Linux, Windows, Android, iPhone, iPad etc.. Never. Why is it supposed to be the case now? With all those, you're asked for the password when you first try to connect and it is then remembered. This is clearly a bug.
Then your "wifi" experiences clearly differ *greatly* from mine. Even the brain-dead sudo operating system asks me on first connect or offers on setting up a new connection wether to "auto" connect and/or save the password defaulting usually to saving when "auto" is selected. My windoz repair station is remote to my router and I *never* save connection info (password) when attaching other peoples devices to my network and I *never* setup "guest" connections. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 09:37 AM, Patrick Shanahan wrote:
Then your "wifi" experiences clearly differ *greatly* from mine. Even the brain-dead sudo operating system asks me on first connect or offers on setting up a new connection wether to "auto" connect and/or save the password defaulting usually to saving when "auto" is selected. My windoz repair station is remote to my router and I *never* save connection info (password) when attaching other peoples devices to my network and I *never* setup "guest" connections.
I have also seen that auto connect option (sadly missing from Android) where it can automatically connect or require manual connect¹. Either way, the password is remembered from the first time the connection is made. It is not necessary to enter the password every time. 1. In fact, I use that manual connect here for my guest WiFi access. I want my devices to automatically connect to my main SSID, but not the guest one. This results in the situation where, if I want to use the guest SSID, I have to manually select it. I do not have to enter in the guest password every time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott
On 11/12/2014 09:37 AM, Patrick Shanahan wrote:
Then your "wifi" experiences clearly differ *greatly* from mine. Even the brain-dead sudo operating system asks me on first connect or offers on setting up a new connection wether to "auto" connect and/or save the password defaulting usually to saving when "auto" is selected. My windoz repair station is remote to my router and I *never* save connection info (password) when attaching other peoples devices to my network and I *never* setup "guest" connections.
I have also seen that auto connect option (sadly missing from Android) where it can automatically connect or require manual connect¹.
My android experience also differes tremendously from yours as I can auto-access mountpoints w/o re-entering passwords although some such as hotels do require re-auth.
Either way, the password is remembered from the first time the connection is made. It is not necessary to enter the password every time.
1. In fact, I use that manual connect here for my guest WiFi access. I want my devices to automatically connect to my main SSID, but not the guest one. This results in the situation where, if I want to use the guest SSID, I have to manually select it. I do not have to enter in the guest password every time.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/12/2014 10:52 AM, Patrick Shanahan wrote:
I have also seen that auto connect option (sadly missing from Android)
where it can automatically connect or require manual connect¹. My android experience also differes tremendously from yours as I can auto-access mountpoints w/o re-entering passwords although some such as hotels do require re-auth.
I think you missed something. My comment was that Android doesn't offer the option of manual connect. You either have auto connect or you have to forget the connection and reconnect again later. If that WiFi requires a password, then you then have to enter the password again. As an example, I frequent the local community centres where there is free WiFi. But in order to use it, you have to use a browser to accept the conditions. If I have that WiFi enabled on my phone, it connects to it as soon as I enter the building. In the process, it diverts IP away from the cell network to WiFi. But since I haven't opened a browser to accept the conditions, my phone is now effectively disconnected from the Internet, which means that I no longer get email, VoIP calls etc.. If Android supported manual connection, then I could connect when I wanted to, and not have to worry about being disconnected from the Internet when I don't. With both Linux and Windows, there is the option of manual or automatic connects that one can set as desired. While this situation doesn't require a password, WiFi at some customer sites does. I don't always want my phone connected to a customer's WiFi, unless I specifically want to. This means I have to enter the password to use the WiFi and then forget the connection. Then the next time I want to use it, I have to enter the password again and again forget. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-12 17:04, James Knott wrote:
As an example, I frequent the local community centres where there is free WiFi. But in order to use it, you have to use a browser to accept the conditions. If I have that WiFi enabled on my phone, it connects to it as soon as I enter the building. In the process, it diverts IP away from the cell network to WiFi. But since I haven't opened a browser to accept the conditions, my phone is now effectively disconnected from the Internet, which means that I no longer get email, VoIP calls etc.. If Android supported manual connection, then I could connect when I wanted to, and not have to worry about being disconnected from the Internet when I don't.
Yes, you have the option, but the name is different. You have to disable automatic browsing for "free wifi", or something like that. My phone does not automatically connect, I have to tap the wifi icon manually, then it offers a list of choices. It only connects automatically to those "known" connections, those that have been used previously. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/12/2014 11:55 AM, Carlos E. R. wrote:
Yes, you have the option, but the name is different. You have to disable automatic browsing for "free wifi", or something like that. My phone does not automatically connect, I have to tap the wifi icon manually, then it offers a list of choices. It only connects automatically to those "known" connections, those that have been used previously.
This should be an option for each connection, just as it is in Linux & Windows. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 11 november 2014 08:32:07 schreef James Knott:
Or rather it should just work as it did in 13.1. It should be necessary to only enter the password when first requested and not have to go into the settings at all.
There is nothing you can do about the installation iso, so a note in the Release Notes is worthwhile and the only option to improve. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-11 17:43, Freek de Kruijf wrote:
Op dinsdag 11 november 2014 08:32:07 schreef James Knott:
Or rather it should just work as it did in 13.1. It should be necessary to only enter the password when first requested and not have to go into the settings at all.
There is nothing you can do about the installation iso, so a note in the Release Notes is worthwhile and the only option to improve.
... for which somebody has to open a bugzilla against the notes, requesting to add that paragraph. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Le 11/11/2014 14:19, Freek de Kruijf a écrit :
It probably should be in the Release Notes that after using WiFi in the installation, the password given there is not remembered and, after logging in, one should click on the NM widget to configure a WiFi connection to get a network up and running.
yes, the wifi infos from install are not included in install (as I see it) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/11/2014 13:39, James Knott a écrit :
On 11/10/2014 11:19 PM, James Knott wrote:
However, I just did an install, not upgrade to 13.2, so that I could get the computer working for tomorrow. I can now boot into both Linux and Windows, so I can now go to bed and to work tomorrow.
Once again, WiFi passwords are not remembered. It shouldn't be necessary to re-enter the password every time.
When I get time, I'll again try to reinstall the old 13.1 system. One thing that might have been causing problems is it was Grub and not Grub 2.
I have sometime problems with kwallet, if I don't save the pass once, it do not ask anymore jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 11:00 PM, Felix Miata wrote:
That would take disk space I don't have. Are you sure? The largest / filesystem under this roof is 10.2G.
Same here. The under-my-desk "server" running 11.2, the one from the Closet of Anxieties, the 800MHz discarded desktop with 1G of memory, runs Postfix, DNS and DHCP, headless, but with Xorg/LXDE installed ... on a 30G disk. The system partition is 10G, the /var is 15G (in case of spool for outgoing mail being held up) and /usr/share is 3G, /home is 2G. What for do I need a 1T drive on my desktop? Music and photographs! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2014-11-10 21:33 (UTC-0500):
It fails on this line:
"grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1" with Unknown command 'linux'.
[later]
Earlier and separately you suggested / was on both sda1 and sda6
IIRC, the only time I mentioned sda1 was in reference to it showing up in the boot menu.
Exactly what did/are you tried/trying to do when you see a grub> prompt? Given the little information you have provided, I'm guessing the following should get you booted if the / filesystem is sda6, you don't have a separate /boot partition, and grub> is Grub2: grub> set root=(hd0,6) grub> linux /boot/vmlinuz root=/dev/sda6 grub> initrd /boot/initrd grub> boot If Grub Legacy: grub> root (hd0,5) grub> kernel /boot/vmlinuz root=/dev/sda6 grub> initrd /boot/initrd grub> boot -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (20)
-
Andrei Borzenkov -
Anton Aylward -
Basil Chupin -
Carlos E. R. -
Carlos E. R. -
David Haller -
ellanios82 -
Felix Miata -
Freek de Kruijf -
James Knott -
jdd -
John Andersen -
John Connor -
Ken Schneider - openSUSE -
lynn -
Patrick Shanahan -
Per Inge Oestmoen -
Roger Luedecke -
Timothy Butterworth -
Werner Flamme