[opensuse] Upgrade to 13.1 horror stories
Does anyone else here get the feeling we're not gonna get any? L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
Does anyone else here get the feeling we're not gonna get any?
Well, as mentioned in another note, I couldn't even install it on one system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2013-11-21 at 11:41 -0500, James Knott wrote:
lynn wrote:
Does anyone else here get the feeling we're not gonna get any?
Well, as mentioned in another note, I couldn't even install it on one system.
That's more like it. It's 12.3 to 13.1 decision day tomorrow over here. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On a positive and promising note, I couldn't get 12.3 to install on my HP NC6400 at home (the installer would freeze a few seconds into the boot,) but 13.1 went fine, and seems to be working better than 12.2 on it performance-wise so far :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/13 16:39, lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
The lack of proprietary nvidia drivers (and hence CUDA) means I won't even be trying it yet... Dx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2013-11-21 at 16:51 +0000, Dylan wrote:
On 21/11/13 16:39, lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
The lack of proprietary nvidia drivers (and hence CUDA) means I won't even be trying it yet...
Dx
OK. Tks. Keep 'em coming. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Nov 21, 2013 at 5:53 PM, lynn wrote:
On Thu, 2013-11-21 at 16:51 +0000, Dylan wrote:
On 21/11/13 16:39, lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
The lack of proprietary nvidia drivers (and hence CUDA) means I won't even be trying it yet...
Dx
OK. Tks. Keep 'em coming. L x
I've got it running on my tablet/laptop (i3, 4GB, Intel video), and so far it's been problem free. It's a clean install and I've installed KDE and Gnome. Both WMs are working smoothly (I added the Tablet pattern as well). Things that aren't working - and are known are.. Bluetooth (bluez5) isn't 100% yet - it works OK with Gnome, but not so well in KDE... I still cannot properly pair my BT keyboard, but this is the same in all distros right now. Power management isn't working right on the 3.11 kernel. I've bumped to 3.12 KOTD, but haven't been able to do basic things like dim the screen yet. These are MINOR issues... I wouldn't consider them showstoppers or horror stories at all. This release is working very smooth right from initial install. I haven't yet upgraded (prob do a clean install) on my main machine because the NVidia driver repo isn't ready and I can't be bothered to build my own driver... ie, I can wait :-) C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 21/11/2013 17:53, Bernhard Voelker ha scritto:
On 11/21/2013 05:39 PM, lynn wrote:
Does anyone else here get the feeling we're not gonna get any?
No, using it happily since day -5 ;-)
Have a nice day, Berny Investigating better before say anything, but just 10 minutes ago, after a reboot i have: network.service failed, postfix main.cf changed...
Better testing is in progress anyway.... soon to tell if there is some problems or not. Claudio. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 21/11/2013 14:53, Bernhard Voelker ha scritto:
On 11/21/2013 05:39 PM, lynn wrote:
Does anyone else here get the feeling we're not gonna get any?
No, using it happily since day -5 ;-)
Have a nice day, Berny
Upgraded from 12.3 to RC2 and beyond and satisfied so far, despite Yast qt UI error. But I heard it is having a migration to Ruby then I wait a bit more. Good Luck! P.S.>Following signature is from another computer not from my 13.1! -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.16-desktop Gnome 3.8.3 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[21.11.2013 17:39] [lynn]:
Does anyone else here get the feeling we're not gonna get any? L x
There will be enough, as always ;-) Today, I did the upgrade on my Thinkpad running Tumbleweed, which is currently based on 13.1. Some repo adjustements, and everything is running fine, even after I switched (via YaST2 3.x :-) to grub2. But that was a simple task - the Thinkpad has Intel graphics, my home and my office desktop both have nVidia cards, so I'll still wait :-) Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Werner Flamme <werner.flamme@email.de> [11-21-13 12:26]: [...]
Today, I did the upgrade on my Thinkpad running Tumbleweed, which is currently based on 13.1. Some repo adjustements, and everything is running fine, even after I switched (via YaST2 3.x :-) to grub2.
But that was a simple task - the Thinkpad has Intel graphics, my home and my office desktop both have nVidia cards, so I'll still wait :-)
Was there any difficulties switching from grub->grub2? -- (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
[21.11.2013 18:39] [Patrick Shanahan]:
* Werner Flamme <werner.flamme@email.de> [11-21-13 12:26]: [...]
Today, I did the upgrade on my Thinkpad running Tumbleweed, which is currently based on 13.1. Some repo adjustements, and everything is running fine, even after I switched (via YaST2 3.x :-) to grub2.
But that was a simple task - the Thinkpad has Intel graphics, my home and my office desktop both have nVidia cards, so I'll still wait :-)
Was there any difficulties switching from grub->grub2?
Not at all, Patrick. In YaST2, I chose Boot Manager, where I selected GRUB2. The appearance of the applet changed. I klicked on "Options" just to see what is there, but didn't touch anything. For me, Grub2 is kind of magic, and I'm not a magician ;-) A few minutes later, I rebootet the Thinkpad and was greeted with a significantly other-looking :-) boot screen. I chose the first entry and everything went fine. Later, I saw that this entry boots the 3.12.x kernel I still had "on board" from the old times ;-) when Tumbleweed was based on 12.3 and provided this kernel version. Chosing the second boot entry (labeled "options for 13.1") would have offered booting the standard 3.11.x kernel of openSUSE 13.1, which I did not test yet. Regards, Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Werner Flamme <werner.flamme@email.de> [11-21-13 12:59]:
[21.11.2013 18:39] [Patrick Shanahan]:
* Werner Flamme <werner.flamme@email.de> [11-21-13 12:26]: [...]
Today, I did the upgrade on my Thinkpad running Tumbleweed, which is currently based on 13.1. Some repo adjustements, and everything is running fine, even after I switched (via YaST2 3.x :-) to grub2.
But that was a simple task - the Thinkpad has Intel graphics, my home and my office desktop both have nVidia cards, so I'll still wait :-)
Was there any difficulties switching from grub->grub2?
Not at all, Patrick.
In YaST2, I chose Boot Manager, where I selected GRUB2. The appearance of the applet changed. I klicked on "Options" just to see what is there, but didn't touch anything. For me, Grub2 is kind of magic, and I'm not a magician ;-)
A few minutes later, I rebootet the Thinkpad and was greeted with a significantly other-looking :-) boot screen. I chose the first entry and everything went fine.
Thanks, I will probably do the same. My present system is Tumbleweed from the start of Tumbleweed and is still booting grub. But since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems), so I will change soon.
Later, I saw that this entry boots the 3.12.x kernel I still had "on board" from the old times ;-) when Tumbleweed was based on 12.3 and provided this kernel version. Chosing the second boot entry (labeled "options for 13.1") would have offered booting the standard 3.11.x kernel of openSUSE 13.1, which I did not test yet.
I have: zypper ll # | Name | Type | Repository --+----------------------+---------+------------------------- 1 | kernel-devel | package | openSUSE Current OSS 2 | kernel-desktop | package | openSUSE Current OSS 3 | kernel-desktop-devel | package | openSUSE Current OSS rather than continue to deny install of lessor version kernels :^) I probably should change as I notice some (few) irregularities that haven't presented enough concern for discussion, yet :^), but doubt that they are kernel related. -- (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 2013-11-21 13:06 (GMT-0500) Patrick Shanahan composed:
...since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems)...
Can't imagine why. I have more than a dozen 13.1 installations booting via Grub Legacy to multiuser.target (aka runlevel 3) rather than graphical.target (aka runlevel 5). I don't pay attention to which ever wind up specified as systemd default. All my Grub stanzas end in "3 ". I just backspace twice and add a 5 if I want to see a GUI login manager before a tty's login prompt. -- "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
[21.11.2013 19:06] [Patrick Shanahan]:
Thanks, I will probably do the same. My present system is Tumbleweed from the start of Tumbleweed and is still booting grub. But since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems), so I will change soon.
Do you have a symlink </etc/systemd/system/default.target> pointing to </usr/lib/systemd/system/runlevel3.target>?
I have:
zypper ll # | Name | Type | Repository --+----------------------+---------+------------------------- 1 | kernel-devel | package | openSUSE Current OSS 2 | kernel-desktop | package | openSUSE Current OSS 3 | kernel-desktop-devel | package | openSUSE Current OSS
rather than continue to deny install of lessor version kernels :^)
I do not deny it. If they are from Tumbleweed repo, they'll work. And there are only two repos they may come from on my systems, the "update-current" und the "Tumbleweed" one. Just two lines in </etc/zypp/zypp.conf>: multiversion = provides:multiversion(kernel) multiversion.kernels = latest,running,oldest At boot time, you can select which kernel to use, so there may be a dozen kernels lying around - the only discomfort might be that you have to tap the "down" arrow key several times until you get to the desired version ;-) Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Werner Flamme <werner.flamme@email.de> [11-22-13 04:38]:
[21.11.2013 19:06] [Patrick Shanahan]:
Thanks, I will probably do the same. My present system is Tumbleweed from the start of Tumbleweed and is still booting grub. But since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems), so I will change soon.
Do you have a symlink </etc/systemd/system/default.target> pointing to </usr/lib/systemd/system/runlevel3.target>?
no, it points to /usr/lib/systemd/system/runlevel5.target for some *unknown* reason but it is a simple move to correct. What makes this symlink as that must be broken or at least broken on my system?
I have:
zypper ll # | Name | Type | Repository --+----------------------+---------+------------------------- 1 | kernel-devel | package | openSUSE Current OSS 2 | kernel-desktop | package | openSUSE Current OSS 3 | kernel-desktop-devel | package | openSUSE Current OSS
rather than continue to deny install of lessor version kernels :^)
I do not deny it. If they are from Tumbleweed repo, they'll work. And there are only two repos they may come from on my systems, the "update-current" und the "Tumbleweed" one. Just two lines in </etc/zypp/zypp.conf>:
multiversion = provides:multiversion(kernel) multiversion.kernels = latest,running,oldest
I have: multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,latest-2,running
At boot time, you can select which kernel to use, so there may be a dozen kernels lying around - the only discomfort might be that you have to tap the "down" arrow key several times until you get to the desired version ;-)
I sometimes trim previous Tumbleweed kernels as sometimes they come very quickly and I prefer to keep those that endured for a longer period and caused no noticable problems :^) tks, -- (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
El 22/11/13 18:56, Patrick Shanahan escribió:
* Werner Flamme <werner.flamme@email.de> [11-22-13 04:38]:
[21.11.2013 19:06] [Patrick Shanahan]:
Thanks, I will probably do the same. My present system is Tumbleweed from the start of Tumbleweed and is still booting grub. But since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems), so I will change soon.
Do you have a symlink </etc/systemd/system/default.target> pointing to </usr/lib/systemd/system/runlevel3.target>?
no, it points to /usr/lib/systemd/system/runlevel5.target for some *unknown* reason but it is a simple move to correct.
What makes this symlink as that must be broken or at least broken on my system?
You have to select the default target, by default it boots into graphical.target..change it with systemctl set-default multi-user.target -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Cristian Rodríguez <crrodriguez@opensuse.org> [11-22-13 17:14]:
El 22/11/13 18:56, Patrick Shanahan escribió:
* Werner Flamme <werner.flamme@email.de> [11-22-13 04:38]:
[21.11.2013 19:06] [Patrick Shanahan]:
Thanks, I will probably do the same. My present system is Tumbleweed from the start of Tumbleweed and is still booting grub. But since the upgrade to 13.1 my preference to boot to runlevel 3 is disreguarded (not so on two other systems), so I will change soon.
Do you have a symlink </etc/systemd/system/default.target> pointing to </usr/lib/systemd/system/runlevel3.target>?
no, it points to /usr/lib/systemd/system/runlevel5.target for some *unknown* reason but it is a simple move to correct.
What makes this symlink as that must be broken or at least broken on my system?
You have to select the default target, by default it boots into graphical.target..change it with systemctl set-default multi-user.target
I had previously set boot to runlevel 3 in grub via "yast bootloader" and did so again. yast/yast2 *is* the openSUSE way for most and systemctl is the keyboard/?hacker? way and it *not* prominent to casual users. My two other systems just promoted via Tumbleweek/zypper dup to 13.1 still boot to runlevel 3 as expected and configured. *Why* not this one and why doesn't "yast{2} bootloader" accomplish the same? tks, -- (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
El 22/11/13 19:19, Patrick Shanahan escribió:
I had previously set boot to runlevel 3 in grub via "yast bootloader" and did so again.
Yeah. yast/yast2 *is* the openSUSE way for most and systemctl is
the keyboard/?hacker? way and it *not* prominent to casual users. My two other systems just promoted via Tumbleweek/zypper dup to 13.1 still boot to runlevel 3 as expected and configured. *Why* not this one and why doesn't "yast{2} bootloader" accomplish the same?
There is no problem in passing "3" in the kernel command line, it will do exactly the same thing.. boot into multi-user.target. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Cristian Rodríguez <crrodriguez@opensuse.org> [11-22-13 17:42]:
El 22/11/13 19:19, Patrick Shanahan escribió:
I had previously set boot to runlevel 3 in grub via "yast bootloader" and did so again.
Yeah.
yast/yast2 *is* the openSUSE way for most and systemctl is
the keyboard/?hacker? way and it *not* prominent to casual users. My two other systems just promoted via Tumbleweek/zypper dup to 13.1 still boot to runlevel 3 as expected and configured. *Why* not this one and why doesn't "yast{2} bootloader" accomplish the same?
There is no problem in passing "3" in the kernel command line, it will do exactly the same thing.. boot into multi-user.target.
Ah, but that *is* the problem. The "3" *is* on the kernel command line and the system *still* boots to rl5 ??? :^( tks, -- (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
El 22/11/13 19:44, Patrick Shanahan escribió:
Ah, but that *is* the problem. The "3" *is* on the kernel command line and the system *still* boots to rl5 ??? :^(
I just rebooted my 13.1 machine for a kernel update.. tested passing 3 in the kernel cmdline, it works exactly as intended, you must be doing something wrong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-22 17:44 (GMT-0500) Patrick Shanahan composed:
There is no problem in passing "3" in the kernel command line, it will do exactly the same thing.. boot into multi-user.target.
Ah, but that *is* the problem. The "3" *is* on the kernel command line and the system *still* boots to rl5 ??? :^(
What's the entire content of /proc/cmdline? What's the upgrade lineage of this system? Does it predate systemd as default init system? -- "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 <mrmazda@earthlink.net> [11-22-13 19:11]:
On 2013-11-22 17:44 (GMT-0500) Patrick Shanahan composed:
There is no problem in passing "3" in the kernel command line, it will do exactly the same thing.. boot into multi-user.target.
Ah, but that *is* the problem. The "3" *is* on the kernel command line and the system *still* boots to rl5 ??? :^(
What's the entire content of /proc/cmdline?
cat /proc/cmdline root=/dev/sdc5 splash=verbose quiet vga=0x346 3
What's the upgrade lineage of this system? Does it predate systemd as default init system?
Definitely, began with Tumbleweed's inseption. But has had/used systemd for quite some time, when Tumbleweed made systemd default. but </etc/systemd/system/default.target> points to </usr/lib/systemd/system/runlevel5.target> yast bootlevel and the kernel cmd-line both show "3". -- (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 2013-11-22 19:30 (GMT-0500) Patrick Shanahan composed:
* Felix Miata composed:
What's the entire content of /proc/cmdline?
cat /proc/cmdline root=/dev/sdc5 splash=verbose quiet vga=0x346 3
Not that I expect it to matter, but what's your boot process look like? None of my cmdlines include quiet, and Plymouth is not installed.
What's the upgrade lineage of this system? Does it predate systemd as default init system?
Definitely, began with Tumbleweed's inseption. But has had/used systemd for quite some time, when Tumbleweed made systemd default.
but </etc/systemd/system/default.target> points to </usr/lib/systemd/system/runlevel5.target>
Did you try what Cristian wrote?: systemctl set-default multi-user.target
yast bootlevel and the kernel cmd-line both show "3".
Dunno. I've yet to have cmdline including 3 start graphical.target. Maybe rpm -e --nodeps systemd and its kin, then reinstalling with zypper or yast would fix something. -- "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 <mrmazda@earthlink.net> [11-22-13 19:48]:
On 2013-11-22 19:30 (GMT-0500) Patrick Shanahan composed:
* Felix Miata composed: [...] Not that I expect it to matter, but what's your boot process look like? None of my cmdlines include quiet, and Plymouth is not installed.
Plymouth is installed. All four boxes locat w/linux contain "quiet" on the kernel cmd line and have for a *long* time, and the particular reason for it's inclusion eludes me atm. according to: http://oreilly.com/linux/excerpts/9780596100797/kernel-boot-command-line-par... Name quiet — Disable all log messages. Synopsis quiet Set the default kernel log level to KERN_WARNING (4), which suppresses all messages during boot except extremely serious ones. (Log levels are defined under the loglevel parameter.)
What's the upgrade lineage of this system? Does it predate systemd as default init system?
Definitely, began with Tumbleweed's inseption. But has had/used systemd for quite some time, when Tumbleweed made systemd default.
but </etc/systemd/system/default.target> points to </usr/lib/systemd/system/runlevel5.target>
Did you try what Cristian wrote?: systemctl set-default multi-user.target
not yet and I am sure that it will work. The *question* is why it is not presently working as it did prior to upgrade to 13.1 via Tumbleweed and has not been changed for many a year (this box). And why yast appears unable to properly set it.
yast bootlevel and the kernel cmd-line both show "3".
Dunno. I've yet to have cmdline including 3 start graphical.target. Maybe rpm -e --nodeps systemd and its kin, then reinstalling with zypper or yast would fix something.
It might, but I don't think that I am quite that adverturing atm. :^) tks, -- (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 2013-11-22 20:07 (GMT-0500) Patrick Shanahan composed:
The *question* is why it is not presently working as it did prior to upgrade to 13.1 via Tumbleweed and has not been changed for many a year (this box).
No idea from me presently.
And why yast appears unable to properly set it.
Yast isn't done being converted from sysvinit to systemd. Seems lots of people prefer zypper to Yast, leaving Yast with a love deficiency. Maybe the question should be asked on the yast-devel list. Maybe it got fixed after 13.1 string freeze and hasn't made it into Factory's Tumbleweed subset yet? -- "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/22/2013 5:24 PM, Felix Miata wrote:
Yast isn't done being converted from sysvinit to systemd. Seems lots of people prefer zypper to Yast, leaving Yast with a love deficiency.
Only command line jockeys that post here would give you that impression. If YAST is dropped, or left to languish, just about every reason for using OpenSuse disappears, especially for the new users. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [11-22-13 20:51]:
On 11/22/2013 5:24 PM, Felix Miata wrote:
Yast isn't done being converted from sysvinit to systemd. Seems lots of people prefer zypper to Yast, leaving Yast with a love deficiency.
Only command line jockeys that post here would give you that impression.
Don't know why you think that. I *consider* myself a "command line jockey" as that is what I learned sometime before mice were born. I prefer zypper to yast for updating and installation, but zypper is only about package installation/deletion/updating and not about setting ntp and samba and .....
If YAST is dropped, or left to languish, just about every reason for using OpenSuse disappears, especially for the new users.
I *would* hate to see yast disappear but see no indication that road is intended. I see that conversion to ruby in ongoing and very active. Your post borders on fud, imnsho! -- (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 2013-11-22 17:49 (GMT-0800) John Andersen composed:
Felix Miata wrote:
Yast isn't done being converted from sysvinit to systemd. Seems lots of people prefer zypper to Yast, leaving Yast with a love deficiency.
Only command line jockeys that post here would give you that impression.
If YAST is dropped, or left to languish, just about every reason for using OpenSuse disappears, especially for the new users.
I didn't mean to imply Yast wasn't important to openSUSE users, only that its conversion to Ruby and Systemd hasn't as of 13.1 had enough resources applied to it to be as complete as it was before either of those conversions began. Previous post I meant to include a Ruby reference, but forgot. -- "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/22/2013 6:16 PM, Felix Miata wrote:
On 2013-11-22 17:49 (GMT-0800) John Andersen composed:
Felix Miata wrote:
Yast isn't done being converted from sysvinit to systemd. Seems lots of people prefer zypper to Yast, leaving Yast with a love deficiency.
Only command line jockeys that post here would give you that impression.
If YAST is dropped, or left to languish, just about every reason for using OpenSuse disappears, especially for the new users.
I didn't mean to imply Yast wasn't important to openSUSE users, only that its conversion to Ruby and Systemd hasn't as of 13.1 had enough resources applied to it to be as complete as it was before either of those conversions began. Previous post I meant to include a Ruby reference, but forgot.
Well the ruby reference wasn't necessary, I believe the conversion project is well known. I'm exactly the opposite of you and Patrick. I configure many machines at the command line, (even when yast is available), things like Samba, firewalls, ssh, Postfix, Cyrus, ftp and web, run level services, etc. I actually prefer doing this to get the tuning just the way I want it, and I'm use to it. But picking and choosing packages that I want to install is where yast really shines, and being able to browse packages en-mas is the beauty of Yast. Its all zypper on the back end anyway. With each succeeding release then creeping levels of nested indirection, (config files become config directory structures, which become mere references to some other entity) the the wholesale replacement of Sysvinit with Systemd everyone is back in a learning curve, and I feel like a newbee again. The totally new user is worse off, because they people they turned to for help are still learning. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 22 Nov 2013 18:34:57 -0800 John Andersen <jsamyth@gmail.com> wrote:
The totally new user is worse off, because they people they turned to for help are still learning.
That is another reason that openSUSE people at SUSE have to adjust new software introduction process. Kind of RFC to project: http://lists.opensuse.org/opensuse-project/2013-11/msg00069.html -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 22/11/13 22:24, Felix Miata escribió:
Yast isn't done being converted from sysvinit to systemd.
Which has nothing to do with the problem discussed here. I just tried with "3" in a live cd as well and again, it works exactly as intended. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-21 17:39 (GMT+0100) lynn composed:
Does anyone else here get the feeling we're not gonna get any?
KDE4 users may or may not like post-4.10.5 decorations changes in KWin[1] or the impact of replacement of Krandr with KScreen[2]. I dislike both, and am very glad to have Ilya still keeping KDE3 alive. Panning is still missing[3] as it was in 12.3, and in 12.2 without appropriate home repos enabled. Those who want or need to keep a NIC named eth0 may have some manual tweaking to do.[4] Users cannot be made passwordless WRT traditional login (aka on a vtty) with passwd command or in YaST2.[5] Applications may get stuck on the Plasma task bar at session restore time.[6] UI bits may be missing in KDE running GTK apps.[7] [1] https://bugs.kde.org/show_bug.cgi?id=325286 [2] https://bugs.kde.org/show_bug.cgi?id=317929 [3] https://bugs.freedesktop.org/show_bug.cgi?id=39949 [4] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... [5] https://bugzilla.novell.com/show_bug.cgi?id=833253 [6] https://bugs.kde.org/show_bug.cgi?id=320561 https://bugzilla.novell.com/show_bug.cgi?id=847479 [7] https://bugzilla.novell.com/show_bug.cgi?id=843086 -- "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 Thursday, November 21, 2013 05:39:06 PM lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x My Logitech bluetooth mouse sometimes works, sometimes does not, but seem that it's known bug. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
imeo@favadi.com wrote:
On Thursday, November 21, 2013 05:39:06 PM lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x My Logitech bluetooth mouse sometimes works, sometimes does not, but seem that it's known bug.
Gnome should work. KDE is probably a week or two away. I don't know a out others. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Čt 21. listopadu 2013 17:39:06, lynn napsal(a):
Does anyone else here get the feeling we're not gonna get any? L x
No, all upgrades as well as new install were perfectly smooth and easy. No problems here. Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
It's perhaps a bit early yet. Sofar I've got a scanner that doesn't work, hardly qualifies as a horror-story, even if a show-stopper :-) -- Per Jessen, Zürich (3.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Donnerstag, 21. November 2013 17:39:06 lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
Hmm, doesn't that depend on your personal definition of what qualifies as a horror story. Here's my collection of issues from the "not so funny" department: fiddling seriously with disk partitions on install -> no /etc/fstab generated better create your own manually, and reinstall grub2 before reboot.. https://bugzilla.novell.com/show_bug.cgi?id=852027 emergency mode damaged -> non fatal boot error results in endless boot boot in recovery mode and fix issues "from outside" https://bugzilla.novell.com/show_bug.cgi?id=852232 service ntp hangs forever, if no 127.0.0.2 is configured -> https://bugzilla.novell.com/show_bug.cgi?id=852104 certain operations with radeon HD7770 crashes the X server -> due to a non production quality lib called glamor some fixes (current git state of affairs I built in OBS but finally decided to avoid these crashes by avoiding libglamor https://bugzilla.novell.com/show_bug.cgi?id=851985 The rest is more in the "serious annoyances" class: 3rd party scanner driver setup failed with yast -> https://bugzilla.novell.com/show_bug.cgi?id=851995 Realtek RTL8188CE looses connection to AP on a regular base: -> https://bugzilla.novell.com/show_bug.cgi?id=851366 combined with the usual collection of minor issues here and there. Note: I just started with 4 systems, but you might want to call my a heavy user. Google Earth, Teamviewer, Skype and VMware Workstation 9 seem do fine. All in all not earth shaking, but much room for improvement is left. Cheers, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hans-Peter Jansen wrote:
On Donnerstag, 21. November 2013 17:39:06 lynn wrote:
Does anyone else here get the feeling we're not gonna get any? L x
Hmm, doesn't that depend on your personal definition of what qualifies as a horror story.
Here's my collection of issues from the "not so funny" department:
[snip]
service ntp hangs forever, if no 127.0.0.2 is configured -> https://bugzilla.novell.com/show_bug.cgi?id=852104
I don't have 127.0.0.2, but ntp works just fine. No mention of 127.0.0.2. -- Per Jessen, Zürich (-0.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-26 09:48, Per Jessen wrote:
Hans-Peter Jansen wrote:
I don't have 127.0.0.2, but ntp works just fine. No mention of 127.0.0.2.
And if you add it, you will have problems with postfix and others. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Carlos E. R. wrote:
On 2013-11-26 09:48, Per Jessen wrote:
Hans-Peter Jansen wrote:
I don't have 127.0.0.2, but ntp works just fine. No mention of 127.0.0.2.
And if you add it, you will have problems with postfix and others.
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems. -- Per Jessen, Zürich (1.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-26 14:53, Per Jessen wrote:
Carlos E. R. wrote:
On 2013-11-26 09:48, Per Jessen wrote:
Hans-Peter Jansen wrote:
I don't have 127.0.0.2, but ntp works just fine. No mention of 127.0.0.2.
And if you add it, you will have problems with postfix and others.
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems.
Don't doubt it, as it is a known problem with bugzillas :-) The same way as other apps need it (sendmail, I think). -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On Tue, Nov 26, 2013 at 03:32:09PM +0100, Carlos E. R. wrote:
On 2013-11-26 14:53, Per Jessen wrote:
Carlos E. R. wrote:
On 2013-11-26 09:48, Per Jessen wrote:
Hans-Peter Jansen wrote:
I don't have 127.0.0.2, but ntp works just fine. No mention of 127.0.0.2.
And if you add it, you will have problems with postfix and others.
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems.
Don't doubt it, as it is a known problem with bugzillas :-)
The same way as other apps need it (sendmail, I think).
Why does sendmail/postfix need or need not 127.0.0.2? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 2013-11-27 10:03, Dr. Werner Fink wrote:
On Tue, Nov 26, 2013 at 03:32:09PM +0100, Carlos E. R. wrote:
On 2013-11-26 14:53, Per Jessen wrote:
Carlos E. R. wrote:
Don't doubt it, as it is a known problem with bugzillas :-)
The same way as other apps need it (sendmail, I think).
Why does sendmail/postfix need or need not 127.0.0.2?
I don't know. I only know that some people or somewhere I read that it was so. I'm not using that program since... who knows when, so I did not investigate. YaST creates an entry for that IP in hosts file if you tick a certain file in yast network module. If you do, postfix complains bitterly and verbosely in the log, even stops working. There is a bugzilla about this, requesting that yast don't create that entry. However, it appear that other apps do need that entry! I did ask in the postfix mail list why postfix broke with it and got an explanation. It is in the bugzilla, IIRC. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On Wed, Nov 27, 2013 at 12:33:38PM +0100, Carlos E. R. wrote:
On 2013-11-27 10:03, Dr. Werner Fink wrote:
On Tue, Nov 26, 2013 at 03:32:09PM +0100, Carlos E. R. wrote:
On 2013-11-26 14:53, Per Jessen wrote:
Carlos E. R. wrote:
Don't doubt it, as it is a known problem with bugzillas :-)
The same way as other apps need it (sendmail, I think).
Why does sendmail/postfix need or need not 127.0.0.2?
I don't know. I only know that some people or somewhere I read that it was so. I'm not using that program since... who knows when, so I did not investigate.
YaST creates an entry for that IP in hosts file if you tick a certain file in yast network module. If you do, postfix complains bitterly and verbosely in the log, even stops working. There is a bugzilla about this, requesting that yast don't create that entry. However, it appear that other apps do need that entry!
I did ask in the postfix mail list why postfix broke with it and got an explanation. It is in the bugzilla, IIRC.
hmmm ... one can use 127.0.0.2 to have an address for a hostname which is not localhost. I do this at home and have configured sendmail to accept this address as well as the loopback. But ... IMHO ... no one is enforced to do this this way. This is more than an emtry in /etc/hosts at least for sendmail, for this and for the openvpm I've running a named. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
Dr. Werner Fink wrote:
hmmm ... one can use 127.0.0.2 to have an address for a hostname which is not localhost. I do this at home and have configured sendmail to accept this address as well as the loopback. But ... IMHO ... no one is enforced to do this this way. This is more than an emtry in /etc/hosts at least for sendmail, for this and for the openvpm I've running a named.
There's no reason why you couldn't have multiple names pointing to the same address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 2013-11-27 at 11:07 -0500, James Knott wrote:
Dr. Werner Fink wrote:
hmmm ... one can use 127.0.0.2 to have an address for a hostname which is not localhost. I do this at home and have configured sendmail to accept this address as well as the loopback. But ... IMHO ... no one is enforced to do this this way. This is more than an emtry in /etc/hosts at least for sendmail, for this and for the openvpm I've running a named.
There's no reason why you couldn't have multiple names pointing to the same address.
Hope I'm not hijacking, but wouldn't you just use CNAME's? Do we really have to alter configs on a per app basis? Maybe the 127 addresses are special? L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
There's no reason why you couldn't have multiple names pointing to the
same address. Hope I'm not hijacking, but wouldn't you just use CNAME's? Do we really have to alter configs on a per app basis? Maybe the 127 addresses are special?
As far as I know, there's no difference between addresses in the loopback range. As I mentioned, IPv6 needs only one. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems.
I have long wondered why an entire IPv4 class A range was assigned to loopback. IPv6, with it's unbelivably huge address range, assigns only ::1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott [26.11.2013 16:35]:
Per Jessen wrote:
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems.
I have long wondered why an entire IPv4 class A range was assigned to loopback. IPv6, with it's unbelivably huge address range, assigns only ::1.
As IPv4 was created, nobody thought that addresses would become rare. So every bigger institution in the U.S. got a class A network ;-) while my company in Germany only got a class B net... -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Werner Flamme wrote:
James Knott [26.11.2013 16:35]:
Per Jessen wrote:
I doubt it, it's just an address. I'm using other 127.x.x.x addresses elsewhere with no problems. I have long wondered why an entire IPv4 class A range was assigned to loopback. IPv6, with it's unbelivably huge address range, assigns only ::1. As IPv4 was created, nobody thought that addresses would become rare. So every bigger institution in the U.S. got a class A network ;-) while my company in Germany only got a class B net...
My point was why did they think they needed 16M loopback addresses? Even a class C block would have been plenty. I'm well aware of the huge blocks handed out when the Internet was new, with so few hosts on it. BTW, I have a /56 IPv6 subnet. That provides 2^72 addresses or about a trillion times the entire IPv4 address space. I still have only 1 IPv6 loopback address though. -- 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 Thursday, 2013-11-21 at 17:39 +0100, lynn wrote:
Does anyone else here get the feeling we're not gonna get any?
Browse the forums, there are a few. For instance, a chap could not install nor upgrade to 13.1 64, many problems. However, he just tried the 32 bit version and it works nicely. Go figure... - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKT9hEACgkQtTMYHG2NR9Uj6wCfdyosxHDibyG0sloaoFh7VMBK O6sAn1Qpwt2lXjWaJ1KAf4hVQe7NZ33o =5Woe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
For instance, a chap could not install nor upgrade to 13.1 64, many problems. However, he just tried the 32 bit version and it works nicely. Go figure...
As I mentioned earlier, it won't install on my IBM Nefinity server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (21)
-
Bernhard Voelker -
C -
Carlos E. R. -
Christopher Myers -
Claudio ML -
Cristian Rodríguez -
Dr. Werner Fink -
Dylan -
Felix Miata -
Greg Freemyer -
Hans-Peter Jansen -
imeo＠favadi.com -
James Knott -
John Andersen -
lynn -
Marco Calistri -
Patrick Shanahan -
Per Jessen -
Rajko -
Vojtěch Zeisek -
Werner Flamme