[opensuse-factory] release notes 13.1 review
Hi, I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed: 2.2. No Network after Installation 2.3. The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices 3.1. openSUSE Documentation 3.4. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode 3.5. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment 3.6. Crypted LVM in UEFI Mode Needs /boot Partition 4.1. systemd: Activating NetworkManager with a network.service Alias Link The following items still apply 3.3. UEFI—Unified Extensible Firmware Interface 4.2. SYSLOG_DAEMON Variable Removed 5.2. Configuring Postfix I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove? 5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection -> someone from the gnome team may be able to comment here cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi guys, Personally I think these might be worthy mentioning: 1. udev, the predictable NIC name thing. And how to stay at the previous naming scheme. 2. the "cleanup on package deletion" and "allow verndor change" in yast-ncurses now becomes temporary option. You have to check that every time or you have to edit /etc/zypp/zypp.conf 3. yast dropped some modules for this release but they're looking for community maintainers. eg: yast-fingerreader..and what are the alternatives existing out there? Greetings Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marguerite Su <i@marguerite.su> writes:
Personally I think these might be worthy mentioning:
1. udev, the predictable NIC name thing. And how to stay at the previous naming scheme.
2. the "cleanup on package deletion" and "allow verndor change" in yast-ncurses now becomes temporary option. You have to check that every time or you have to edit /etc/zypp/zypp.conf
3. yast dropped some modules for this release but they're looking for community maintainers. eg: yast-fingerreader..and what are the alternatives existing out there?
Ok, sensible requests, but I probably need more detailed input (if possible via bugzilla). ATM, I do not have time to do researching on my own. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Karl Eichwalder wrote:
Marguerite Su <i@marguerite.su> writes:
Personally I think these might be worthy mentioning:
1. udev, the predictable NIC name thing. And how to stay at the previous naming scheme.
2. the "cleanup on package deletion" and "allow verndor change" in yast-ncurses now becomes temporary option. You have to check that every time or you have to edit /etc/zypp/zypp.conf
3. yast dropped some modules for this release but they're looking for community maintainers. eg: yast-fingerreader..and what are the alternatives existing out there?
Ok, sensible requests, but I probably need more detailed input (if possible via bugzilla). ATM, I do not have time to do researching on my own.
Marguerite, would you mind filing bug reports for the release notes component? That way NEEDINFO can be used to get info from develoepers on those topics. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Oct 31, 2013 at 12:59:44PM +0100, Ludwig Nussel wrote:
Hi,
I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed:
I'd add a note about Predictable Network Interface Names http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... Regards Michal Vyskocil
Hello, Am Donnerstag, 31. Oktober 2013 schrieb Ludwig Nussel:
I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed:
2.3. The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices
Did you test if this is still needed with the latest nvidia driver?
I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove?
The nvidia driver still requires disabling KMS... That said - I understand the goal of cleaning up the release notes, which should IMHO only contain information about important changes and last-minute information that didn't make it into the "normal" documentation/manuals (doc.o.o) early enough. This also means some of the sections (KMS is the perfect example) should be moved to the manuals instead of just deleting them. Regards, Christian Boltz -- Lieber WoKo, bitte versuche in Zukunft, sig-gerecht zu schreiben, d.h etwa auf 3 Zeilen Kürzen. Danke. ;-) [Christopher Brosch in dafb] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Christian Boltz <opensuse@cboltz.de> writes:
I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove?
The nvidia driver still requires disabling KMS...
That said - I understand the goal of cleaning up the release notes, which should IMHO only contain information about important changes and last-minute information that didn't make it into the "normal" documentation/manuals (doc.o.o) early enough.
This also means some of the sections (KMS is the perfect example) should be moved to the manuals instead of just deleting them.
I completely agree. Unfortunately, it is probably too late now to move this info to the official documentation... -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Dienstag, 5. November 2013 schrieb Karl Eichwalder:
Christian Boltz <opensuse@cboltz.de> writes:
This also means some of the sections (KMS is the perfect example) should be moved to the manuals instead of just deleting them.
I completely agree. Unfortunately, it is probably too late now to move this info to the official documentation...
For 13.1, yes. Nevertheless you should add it on your ToDo list to do it directly after the 13.1 release (or make sure there's a 13.1 branch and do it in the factory version only). Otherwise we'll discuss the same for the 13.2 release notes ;-) Regards, Christian Boltz -- ah, sie haben einen doktortitel. in welchem fach haben sie denn plagiiert? [barfman auf http://ahoipolloi.blogger.de/stories/1844699/] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 5 november 2013 21:50:46 schreef Christian Boltz:
Hello,
The release notes also mention a new version, 2.4, of Apache. I submitted changes in the openSUSE configuration files in Factory taking care of the obsolete DefaultType and the introduction of Release{|Any|All|None} as replacement for Order and Grant or Deny directives. I tried to submit these changes also in 13.1, but was unable to do so. Also an Update branch of 13.1 is not available yet. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2013-11-06 00:42, Freek de Kruijf wrote:
Op dinsdag 5 november 2013 21:50:46 schreef Christian Boltz:
Hello,
The release notes also mention a new version, 2.4, of Apache. I submitted changes in the openSUSE configuration files in Factory taking care of the obsolete DefaultType and the introduction of Release{|Any|All|None} as replacement for Order and Grant or Deny directives.
I tried to submit these changes also in 13.1, but was unable to do so. Also an Update branch of 13.1 is not available yet.
The branch is available in OBS, however, so submits can be created. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Christian Boltz <opensuse@cboltz.de> writes:
For 13.1, yes.
Nevertheless you should add it on your ToDo list to do it directly after the 13.1 release (or make sure there's a 13.1 branch and do it in the factory version only).
Yes, I thought about this. I'll probably move it back from the release notes to bugzilla and make it a documentation enhancement bug. ATM, it isn't known how and what documentation will be done for 13.2...
Otherwise we'll discuss the same for the 13.2 release notes ;-)
This will probably happen nevertheless ;) -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 31/10/13 08:59, Ludwig Nussel escribió:
Hi,
I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed:
2.2. No Network after Installation 2.3. The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices 3.1. openSUSE Documentation 3.4. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode 3.5. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment 3.6. Crypted LVM in UEFI Mode Needs /boot Partition 4.1. systemd: Activating NetworkManager with a network.service Alias Link
The following items still apply 3.3. UEFI—Unified Extensible Firmware Interface 4.2. SYSLOG_DAEMON Variable Removed 5.2. Configuring Postfix
I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove?
5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection -> someone from the gnome team may be able to comment here
Note to add: - When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc This is particularly important for gnome users, otherwise gnome terminal will fail with "grantpt failed: Operation not permitted", these mount points are managed by systemd and should not be present in /etc/fstab unless the user knows exactly what he is doing (i.e a kernel developer or advanced system administrator) -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2013-11-01 00:35, Cristian Rodríguez wrote:
Note to add:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users,
Uhm, pretty much all SUSE systems have these lines proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 They are already marked "noauto" since aeons because the init scripts mounted them anyway, but the entries were kept in fstab in case.... in case you need to do something with it ;) So if GNOME requires that they be nuked from fstab, you better come up with a solution Real Fast Now, because everybody is going to have them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-11-01 00:51 (GMT+0100) Jan Engelhardt composed:
Uhm, pretty much all SUSE systems have these lines
proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
They are already marked "noauto" since aeons because the init scripts mounted them anyway, but the entries were kept in fstab in case.... in case you need to do something with it ;)
So if GNOME requires that they be nuked from fstab, you better come up with a solution Real Fast Now, because everybody is going to have them.
No fresh 13.1 installs I've done have them, at least not any done since start of summer, and all my upgrades have been done with zypper. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 31/10/13 21:00, Felix Miata escribió:
No fresh 13.1 installs I've done have them, at least not any done since start of summer, and all my upgrades have been done with zypper.
Correct, YaST has been corrected to no longer create them at install time and remove them during yast-assisted upgrade. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 31/10/13 20:51, Jan Engelhardt escribió:
On Friday 2013-11-01 00:35, Cristian Rodríguez wrote:
Note to add:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users,
Uhm, pretty much all SUSE systems have these lines
proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
They are already marked "noauto" since aeons because the init scripts mounted them anyway, but the entries were kept in fstab in case.... in case you need to do something with it ;)
So if GNOME requires that they be nuked from fstab, you better come up with a solution Real Fast Now, because everybody is going to have them.
I did not find any clean way to do this cleanup in packages, there seems to be no known working tool in the base system to cleanly remove mount points from fstab programatically..(as opossed to hacks with sed) The particular gnome-terminal error is due to the /dev/pts entry. Note that this is nothing new, it should have been fixed when systemd was introduced in 12.2 or so.. but fell through the cracks. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 01 November 2013, Cristian Rodríguez wrote:
El 31/10/13 20:51, Jan Engelhardt escribió:
On Friday 2013-11-01 00:35, Cristian Rodríguez wrote:
Note to add:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users,
Uhm, pretty much all SUSE systems have these lines
proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
They are already marked "noauto" since aeons because the init scripts mounted them anyway, but the entries were kept in fstab in case.... in case you need to do something with it ;)
So if GNOME requires that they be nuked from fstab, you better come up with a solution Real Fast Now, because everybody is going to have them.
I did not find any clean way to do this cleanup in packages, there seems to be no known working tool in the base system to cleanly remove mount points from fstab programatically..(as opossed to hacks with sed)
The particular gnome-terminal error is due to the /dev/pts entry.
Note that this is nothing new, it should have been fixed when systemd was introduced in 12.2 or so.. but fell through the cracks.
man fstab "fstab is only read by programs, and not written; it is the duty of the system administrator to properly create and maintain this file" cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-01 01:01, Cristian Rodríguez wrote:
I did not find any clean way to do this cleanup in packages, there seems to be no known working tool in the base system to cleanly remove mount points from fstab programatically..(as opossed to hacks with sed)
Why don't you people create a specialized upgrade tool (script?) for each release that does all those task that yast does but zypper dup doesn't? - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJy8PYACgkQtTMYHG2NR9UlZwCfecEfd3lztJ/NGbskU4691+q9 ykAAnRSrmbN7CHtQT61rSnTAWJHwWg74 =DRRw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-31 21:01 (GMT-0300) Cristian Rodríguez composed:
I did not find any clean way to do this cleanup in packages, there seems to be no known working tool in the base system to cleanly remove mount points from fstab programatically..(as opossed to hacks with sed)
Something certainly lays claim to on every zypper dup that installs a new version of openSUSE-release. It's really annoying that the timestamp on fstab changes each such time even though its content hasn't been touched. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Thu, 31 Oct 2013 21:01:08 -0300 Cristian Rodríguez <crrodriguez@opensuse.org> пишет:
The particular gnome-terminal error is due to the /dev/pts entry.
Could you be more specific? Somehow I do not see any issues (on 12.3) bor@opensuse:~> grep /dev/pts /etc/fstab devpts /dev/pts devpts mode=0620,gid=5 0 0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 31/10/13 23:45, Andrey Borzenkov escribió:
В Thu, 31 Oct 2013 21:01:08 -0300 Cristian Rodríguez <crrodriguez@opensuse.org> пишет:
The particular gnome-terminal error is due to the /dev/pts entry.
Could you be more specific? Somehow I do not see any issues (on 12.3)
bor@opensuse:~> grep /dev/pts /etc/fstab devpts /dev/pts devpts mode=0620,gid=5 0 0
Stefan Bruns suggested a much more plausible failure cause than this in a later message. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 01 November 2013, Jan Engelhardt wrote:
On Friday 2013-11-01 00:35, Cristian Rodríguez wrote:
Note to add:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users,
Uhm, pretty much all SUSE systems have these lines
proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
They are already marked "noauto" since aeons because the init scripts mounted them anyway, but the entries were kept in fstab in case.... in case you need to do something with it ;)
So if GNOME requires that they be nuked from fstab, you better come up with a solution Real Fast Now, because everybody is going to have them.
Why should gnome terminal care about /etc/fstab at all? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 31/10/13 21:03, Ruediger Meier escribió:
Why should gnome terminal care about /etc/fstab at all?
I never said that gnome-terminal cares about /etc/fstab, this surfaced after the removal of glibc pt_chown. side effect of fixing CVE-2013-2207. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 1 Nov 2013 01:11, Cristian Rodríguez <crrodriguez@...> wrote:
El 31/10/13 21:03, Ruediger Meier escribió:
Why should gnome terminal care about /etc/fstab at all?
I never said that gnome-terminal cares about /etc/fstab, this surfaced after the removal of glibc pt_chown. side effect of fixing CVE-2013-2207.
What EXACTLY is the diverence between /dev/pts mounted by systemd and the fstab entry? Looks like a wrong owner/rights handling. On 12.3 fresh install on blank disk, fstab has: devpts /dev/pts devpts mode=0620,gid=5 0 0 and calling mount gives: devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) What "should it be" viewed from glibc / gnome-terminal? IMHO just adding 'noauto' to the options would be the best for a existing fstab line, aka update, or dist-upgrade. As glibc is part of the cause should it handled there, or in systemd, as the other trouble-maker in this case. Or it should be added to aaa_base, as this is a integral part of the base system. Either way, shout it out loud, pack at least the hint on how to handle the error (should it surface) into the release notes. - Yamaban.
El 31/10/13 21:44, Yamaban escribió:
On Fri, 1 Nov 2013 01:11, Cristian Rodríguez <crrodriguez@...> wrote:
El 31/10/13 21:03, Ruediger Meier escribió:
Why should gnome terminal care about /etc/fstab at all?
I never said that gnome-terminal cares about /etc/fstab, this surfaced after the removal of glibc pt_chown. side effect of fixing CVE-2013-2207.
What EXACTLY is the diverence between /dev/pts mounted by systemd and the fstab entry? Looks like a wrong owner/rights handling.
On 12.3 fresh install on blank disk, fstab has: devpts /dev/pts devpts mode=0620,gid=5 0 0
and calling mount gives: devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
What "should it be" viewed from glibc / gnome-terminal?
This line is correct, yet it does not work for some people when such entry exists in fstab (even when gid= and mode= are correct) Cfarrell@suse reports it here: https://plus.google.com/113239224590825114668/posts/fbgx9eSZn8X arch users: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-August/025332.h... I am not exactly sure what is going on, never seen it myself, I only brought this up because cfarrell 's issue came to mind after reading the release notes. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 31 October 2013 22:56:16 Cristian Rodríguez wrote:
El 31/10/13 21:44, Yamaban escribió:
On Fri, 1 Nov 2013 01:11, Cristian Rodríguez <crrodriguez@...> wrote:
El 31/10/13 21:03, Ruediger Meier escribió:
Why should gnome terminal care about /etc/fstab at all?
I never said that gnome-terminal cares about /etc/fstab, this surfaced after the removal of glibc pt_chown. side effect of fixing CVE-2013-2207.
What EXACTLY is the diverence between /dev/pts mounted by systemd and the fstab entry? Looks like a wrong owner/rights handling.
On 12.3 fresh install on blank disk, fstab has: devpts /dev/pts devpts mode=0620,gid=5 0 0
and calling mount gives: devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
What "should it be" viewed from glibc / gnome-terminal?
This line is correct, yet it does not work for some people when such entry exists in fstab (even when gid= and mode= are correct)
Cfarrell@suse reports it here: https://plus.google.com/113239224590825114668/posts/fbgx9eSZn8X
Ciaran might have been hit by this one: Information for patch openSUSE-2013-753: ---------------------------------------- Name: openSUSE-2013-753 Version: 1 Arch: noarch Vendor: maint-coord@suse.de Status: Installed Category: recommended Created On: Wed 09 Oct 2013 09:35:35 PM CEST Reboot Required: No Package Manager Restart Required: No Interactive: No Summary: build: avoid modifying devpts mount during build Description: The build script used the incorrect devpts permissions which changed the global devpts mount incorrectly and in turn made konsole and other terminals not work. Provides: patch:openSUSE-2013-753 == 1 ------------ after running osc build, /dev/pts had mode=0600,gid=0 Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019
El 31/10/13 23:16, Stefan Brüns escribió:
Ciaran might have been hit by this one:
The build script used the incorrect devpts permissions which changed the global devpts mount incorrectly and in turn made konsole and other terminals not work.
That makes sense, maybe in his case removing the /etc/fstab line was just the placebo and the real fix was rebooting to correct the mess build created in the first place... :-) -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez <crrodriguez@opensuse.org> writes:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users, otherwise gnome terminal will fail with "grantpt failed: Operation not permitted", these mount points are managed by systemd and should not be present in /etc/fstab unless the user knows exactly what he is doing (i.e a kernel developer or advanced system administrator)
Ok, I'll add to the RN: <sect2> <title>Upgrading with Zypper (dup) Requires /etc/fstab Cleanup</title> <para> When upgrading with <command>zypper dup</command> (&yast; upgrade handles it automatically) users should remove the following <filename>/etc/fstab</filename> entries if present: </para> <screen>tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc</screen> <para> This is especially important for Gnome users, otherwise the Gnome terminal will fail with "<literal>grantpt failed: Operation not permitted</literal>". These mount points are managed by <command>systemd</command> and should no longer be present in <filename>/etc/fstab</filename>. </para> </sect2> -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 4, 2013 at 10:13 AM, Karl Eichwalder <ke@suse.de> wrote:
Cristian Rodríguez <crrodriguez@opensuse.org> writes:
- When upgrading with zypper dup (YAST upgrade handles this automatically) users want to remove the following entries from /etc/fstab if present
tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc
This is particularly important for gnome users, otherwise gnome terminal will fail with "grantpt failed: Operation not permitted", these mount points are managed by systemd and should not be present in /etc/fstab unless the user knows exactly what he is doing (i.e a kernel developer or advanced system administrator)
Ok, I'll add to the RN:
<sect2> <title>Upgrading with Zypper (dup) Requires /etc/fstab Cleanup</title> <para> When upgrading with <command>zypper dup</command> (&yast; upgrade handles it automatically) users should remove the following <filename>/etc/fstab</filename> entries if present: </para> <screen>tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc</screen>
<para> This is especially important for Gnome users, otherwise the Gnome terminal will fail with "<literal>grantpt failed: Operation not permitted</literal>". These mount points are managed by <command>systemd</command> and should no longer be present in <filename>/etc/fstab</filename>. </para> </sect2>
-- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5
I don't see anything in the release notes about BNC#802525. Due to this bug, zypper dup to 13.1 will fail for most, if not all, people upgrading unpatched 12.X systems via zypper dup. As described in comments 86 and 88 the fix is to ensure patch openSUSE-RU-2013:1544-1 is installed prior to updating from 12.X to 13.1 https://bugzilla.novell.com/show_bug.cgi?id=802525#c86 https://bugzilla.novell.com/show_bug.cgi?id=802525#c88 == Similarly, I don't see any reference to systems using BtrFS as the system disk (ie. for /usr). Due to BNC#835695 a non-patched 12.3 release will fail to upgrade via zypper dup in some circumstances. Jeff Mahoney said he would address it: http://markmail.org/message/nfiwsnvfgdhthcsj I don't know if it was addressed. If not, the best workaround is to download the ISO and upgrade via DVD. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg Freemyer wrote:
I don't see anything in the release notes about BNC#802525.
Due to this bug, zypper dup to 13.1 will fail for most, if not all, people upgrading unpatched 12.X systems via zypper dup.
As described in comments 86 and 88 the fix is to ensure patch openSUSE-RU-2013:1544-1 is installed prior to updating from 12.X to 13.1
I think in general one needs to install all available updates on the old distro prio to upgrading. http://en.opensuse.org/Upgrade also states that. Maybe it needs to be made more explicit.
== Similarly, I don't see any reference to systems using BtrFS as the system disk (ie. for /usr).
Due to BNC#835695 a non-patched 12.3 release will fail to upgrade via zypper dup in some circumstances.
Jeff Mahoney said he would address it: http://markmail.org/message/nfiwsnvfgdhthcsj
Thanks for the hint Greg. Would you mind filing a bug against the release notes component and set NEEINFO to Jeff or David? They should be able to either tell that the issue is fixed or provide a paragraph describing the workaround. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 4, 2013 at 10:59 AM, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
I think in general one needs to install all available updates on the old distro prio to upgrading. http://en.opensuse.org/Upgrade also states that. Maybe it needs to be made more explicit.
I had failed to note that was already recommended. I think I looked for "zypper patch" instead of "zypper up". Is the above correct that users should invoke "zypper up" as opposed to "zypper patch", or does it not matter. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg Freemyer wrote:
On Mon, Nov 4, 2013 at 10:59 AM, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
I think in general one needs to install all available updates on the old distro prio to upgrading. http://en.opensuse.org/Upgrade also states that. Maybe it needs to be made more explicit.
I had failed to note that was already recommended.
I think I looked for "zypper patch" instead of "zypper up". Is the above correct that users should invoke "zypper up" as opposed to "zypper patch", or does it not matter.
zypper patch would by slightly more correct I think as it would potentially be able to also remove packages if needed. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 4, 2013 at 10:59 AM, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
== Similarly, I don't see any reference to systems using BtrFS as the system disk (ie. for /usr).
Due to BNC#835695 a non-patched 12.3 release will fail to upgrade via zypper dup in some circumstances.
Jeff Mahoney said he would address it: http://markmail.org/message/nfiwsnvfgdhthcsj
Thanks for the hint Greg. Would you mind filing a bug against the release notes component and set NEEINFO to Jeff or David? They should be able to either tell that the issue is fixed or provide a paragraph describing the workaround.
Done: https://bugzilla.novell.com/show_bug.cgi?id=849039 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2013-11-04 16:13, Karl Eichwalder wrote:
Cristian Rodríguez <crrodriguez@opensuse.org> writes: Ok, I'll add to the RN:
handles it automatically) users should remove the following <filename>/etc/fstab</filename> entries if present: </para> <screen>tmpfs /dev/shm devpts /dev/pts sysfs /sys sysfs proc /proc proc</screen>
Should we also add usbfs /proc/bus/usb usbfs noauto 0 0 for removal? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ludwig Nussel <ludwig.nussel@suse.de> writes:
I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed:
3.1. openSUSE Documentation
I kept the description of the Start-Up Guide that we still intend to ship...
The following items still apply 3.3. UEFI—Unified Extensible Firmware Interface 4.2. SYSLOG_DAEMON Variable Removed 5.2. Configuring Postfix
ok.
I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove?
I'm also unsure about this. Sometimes we updated it a little bit.
5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection -> someone from the gnome team may be able to comment here
Ok, but ATM, I commented it (thus it is invisible for the moment). Now studying the other mails... -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (15)
-
Andrey Borzenkov -
Carlos E. R. -
Christian Boltz -
Cristian Rodríguez -
Felix Miata -
Freek de Kruijf -
Greg Freemyer -
Jan Engelhardt -
Karl Eichwalder -
Ludwig Nussel -
Marguerite Su -
Michal Vyskocil -
Ruediger Meier -
Stefan Brüns -
Yamaban