Re: since last update system does not boot any more
Al Dunsmuir al.dunsm...@sympatico.ca wrote on Tue, 12 Apr 2011 12:36:53 -0400: I think these [file names such as multi-user.target] should be viewed more as keywords, or reserved phrases and not subject to translation. This is similar to a C program, where one has 3 cases: - Comments and literal string can have nearly any value. - Variable names are only restricted in the character set that can be used. - Language keywords must conform exactly. Having them be NLS-sensitive in a global subsystem in a multi-user environment (where each user (or even process) is able to use a different locale) seems to me a recipe for disaster. More like variable names than keywords. Keywords usually are from a small, fixed set. Sometimes they have a prescribed syntax (e.g. a distinctive character, such as the initial colon that denotes a Common Lisp keyword) that permits a vast number of keywords. Systemd targets are ordinary file names. They come from no enumerable set; there is no syntax that identifies a target name. English users are likely to find the standard target names descriptive. Other users will find them opaque, and the larger (more flexible) set of target names will be a challenge compared to single digits from 1-6. I have had experiences where I sought to understand C programs written by programmers not fluent in English. Despite a lot of C program experience and a good understanding of the C language, this was enormously more difficult than examination of similar programs written by English- speaking authors. This experience suggests the burden of systemd will be heavier for those not fluent in English. This is true for many aspects of Linux that derive from its English roots and development. I concur with your view it is unwise to undertake some sort of internationalization of systemd target names. I believe the flexibility that systemd provides is valuable, and I do not want to discard systemd. My point is systemd makes Fedora a little more difficult for a large number of people. A little times a large enough number can be a significant cost, especially if this scenario is repeated with other features. It seems possible that we can make a substantial number of sound decisions that This feature is well worth the small breakage it costs. and fail to realize the aggregate cost may not be simply additive, but grow (for at least some users) beyond the total benefit these choices deliver. Fedora, with its leading-edge ambition, is a good vehicle to explore these issues, though I doubt we spend enough effort in retrospection. There have been many instances where Fedora replaced a facility with something new, a smaller number of cases where a feature was deemed too broken to fix and dropped, but few where a feature is successful but is abandoned because its cost is higher than expected. Maybe Red Hat Linux is the place for that, while Fedora chases the new, latest, and greatest. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Tuesday, April 5, 2011, 3:21:09 PM, Richard Ryniker wrote: On Sat, 2011-04-02 at 10:49 -0400, Genes MailLists wrote: Indeed ... there is something simplistically elegant about: 3 vs multi-user.target Or, you could look upon it as 'utterly cryptic'. At least multi-user.target takes a shot at explaining itself. 3...3, well, not so much. -- Adam Williamson One can reasonably argue for either scheme, though Adam might be acused of a desire to destroy venerable historic traditions of mystic Unix incantations... I should think 3 presents very little problem for internationalization, whereas multi-user.target demands translation before it explains itself to non-English-speaking users. Because these are descriptive file names, not just message text, and they are used fairly early in the boot process, I doubt translation is easy. Feasible, certainly, but messy and therefore unlikely to happen. I think these should be viewed more as keywords, or reserved phrases and not subject to translation. This is similar to a C program, where one has 3 cases: - Comments and literal string can have nearly any value. - Variable names are only restricted in the character set that can be used. - Language keywords must conform exactly. Having them be NLS-sensitive in a global subsystem in a multi-user environment (where each user (or even process) is able to use a different locale) seems to me a recipe for disaster. Al -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Tue, 5 Apr 2011, Adam Williamson wrote: On Tue, 2011-04-05 at 15:21 -0400, Richard Ryniker wrote: I should think 3 presents very little problem for internationalization, whereas multi-user.target demands translation before it explains itself to non-English-speaking users. Because these are descriptive file names, not just message text, and they are used fairly early in the boot process, I doubt translation is easy. Feasible, certainly, but messy and therefore unlikely to happen. This is hardly an issue unique to systemd. Just about everything names its files in English. You are right. The problem with systemd is that those arguments are filenames, but you can not use tab for autocompletition. ATM systemd can translate 3 to multi-user.target which is OK, but in the future who knows. Acctualy if I understand the concept right, maybe it is possible to make symlink 3 - multi-user.target, and it may work... -- Adam Williamson Adam Pribyl -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Wed, 2011-04-06 at 17:06 +0200, Adam Pribyl wrote: On Tue, 5 Apr 2011, Adam Williamson wrote: On Tue, 2011-04-05 at 15:21 -0400, Richard Ryniker wrote: I should think 3 presents very little problem for internationalization, whereas multi-user.target demands translation before it explains itself to non-English-speaking users. Because these are descriptive file names, not just message text, and they are used fairly early in the boot process, I doubt translation is easy. Feasible, certainly, but messy and therefore unlikely to happen. This is hardly an issue unique to systemd. Just about everything names its files in English. You are right. The problem with systemd is that those arguments are filenames, but you can not use tab for autocompletition. ATM systemd can translate 3 to multi-user.target which is OK, but in the future who knows. Acctualy if I understand the concept right, maybe it is possible to make symlink 3 - multi-user.target, and it may work... that's more or less what it does already. [root@adam Download]# ls /lib/systemd/system/runlevel3.target -l lrwxrwxrwx. 1 root root 17 Apr 5 09:58 /lib/systemd/system/runlevel3.target - multi-user.target [root@adam Download]# i dunno exactly where it handles 'runlevel3', but...yeah. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 07/04/11 01:06, Adam Pribyl wrote: You are right. The problem with systemd is that those arguments are filenames, but you can not use tab for autocompletition. ATM systemd can translate 3 to multi-user.target which is OK, but in the future who knows. Acctualy if I understand the concept right, maybe it is possible to make symlink 3 - multi-user.target, and it may work... You can use tab completion. Just install the bash-completion package and modify /etc/bash_completion.d/systemctl-bash-completion.sh as per the patch here https://bugzilla.redhat.com/show_bug.cgi?id=694321 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 04/05/2011 12:57 AM, Adam Williamson wrote: On Sat, 2011-04-02 at 10:49 -0400, Genes MailLists wrote: Indeed ... there is something simplistically elegant about: 3 vs multi-user.target Or, you could look upon it as 'utterly cryptic'. At least multi-user.target takes a shot at explaining itself. 3...3, well, not so much. Well i can't argue with you there .. :-) But 3 and 5 mean so much to us at this point too ... but hey I can move on .. even if you make me type so much more .. ;-[] Actually, since systemd supports a lot more than 3 run levels (that we use) ... it is far more powerful in principal - tho I am not sure how we use that increased functionality yet .. But I would still prefer shortening the option somewhat and making the extension .target assumed by default and therefore optional - assuming there is no ambiguity. So: ... --unit=multi-user would be equivalent to: ... --unit=multi-user.target Is that feasable I wonder ? gene/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Sat, 2011-04-02 at 10:49 -0400, Genes MailLists wrote: Indeed ... there is something simplistically elegant about: 3 vs multi-user.target Or, you could look upon it as 'utterly cryptic'. At least multi-user.target takes a shot at explaining itself. 3...3, well, not so much. -- Adam Williamson One can reasonably argue for either scheme, though Adam might be acused of a desire to destroy venerable historic traditions of mystic Unix incantations... I should think 3 presents very little problem for internationalization, whereas multi-user.target demands translation before it explains itself to non-English-speaking users. Because these are descriptive file names, not just message text, and they are used fairly early in the boot process, I doubt translation is easy. Feasible, certainly, but messy and therefore unlikely to happen. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Tue, 2011-04-05 at 15:21 -0400, Richard Ryniker wrote: I should think 3 presents very little problem for internationalization, whereas multi-user.target demands translation before it explains itself to non-English-speaking users. Because these are descriptive file names, not just message text, and they are used fairly early in the boot process, I doubt translation is easy. Feasible, certainly, but messy and therefore unlikely to happen. This is hardly an issue unique to systemd. Just about everything names its files in English. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Sat, 2011-04-02 at 10:49 -0400, Genes MailLists wrote: Indeed ... there is something simplistically elegant about: 3 vs multi-user.target Or, you could look upon it as 'utterly cryptic'. At least multi-user.target takes a shot at explaining itself. 3...3, well, not so much. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Fri, 1 Apr 2011, Adam Williamson wrote: On Thu, 2011-03-31 at 21:40 +0200, Adam Pribyl wrote: Did you found any way how to force systemd to boot to single-user? So far my installation of F15 with systemd has only one runlevel, I can not switch it - nor with grub option, neither with inittab or init command. systemd doesn't really use runlevels any more, but it has backward compatibility with them; inittab doesn't work (and there's a comment in it to this effect), but grub options and 'init' command are supposed to My inittab still states only that it is for upstart to set runlevel.. (and have done for me when I've used them). If this isn't working for you, please file a bug against systemd. This is fast moving target... few days ago it was not. Now init command works. Great. systemd's native concept is 'targets'; graphical.target is roughly equivalent to runlevel 5 and multi-user.target is roughly equivalent to runlevel 3. rescue.target is roughly equal to runlevel 1, and there's emergency.target that's more or less what it sounds like. IIRC, the 'native' kernel parameter you can use to specify a particular target is systemd.default , so you could try: Thanks. Even thou I am aware of this, I'm somehow not used to it, yet. All those commands and parameters are long and hard to remember. -- Adam Williamson Adam Pribyl -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 04/02/2011 04:44 AM, Adam Pribyl wrote: On Fri, 1 Apr 2011, Adam Williamson wrote: ... systemd's native concept is 'targets'; graphical.target is roughly equivalent to runlevel 5 and multi-user.target is roughly equivalent to runlevel 3. rescue.target is roughly equal to runlevel 1, and there's emergency.target that's more or less what it sounds like. IIRC, the 'native' kernel parameter you can use to specify a particular target is systemd.default , so you could try: Thanks. Even thou I am aware of this, I'm somehow not used to it, yet. All those commands and parameters are long and hard to remember. Indeed ... there is something simplistically elegant about: 3 vs multi-user.target -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 04/02/2011 02:14 PM, Adam Pribyl wrote My inittab still states only that it is for upstart to set runlevel.. Then the new file must have been written as /etc/inittab.rpmnew Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Thu, 2011-03-31 at 21:40 +0200, Adam Pribyl wrote: Did you found any way how to force systemd to boot to single-user? So far my installation of F15 with systemd has only one runlevel, I can not switch it - nor with grub option, neither with inittab or init command. systemd doesn't really use runlevels any more, but it has backward compatibility with them; inittab doesn't work (and there's a comment in it to this effect), but grub options and 'init' command are supposed to (and have done for me when I've used them). If this isn't working for you, please file a bug against systemd. systemd's native concept is 'targets'; graphical.target is roughly equivalent to runlevel 5 and multi-user.target is roughly equivalent to runlevel 3. rescue.target is roughly equal to runlevel 1, and there's emergency.target that's more or less what it sounds like. IIRC, the 'native' kernel parameter you can use to specify a particular target is systemd.default , so you could try: systemd.default=emergency.target or systemd.default=rescue.target as kernel parameters and see if those work. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Fri, Apr 1, 2011 at 7:58 PM, Adam Williamson awill...@redhat.com wrote: systemd's native concept is 'targets'; graphical.target is roughly equivalent to runlevel 5 and multi-user.target is roughly equivalent to runlevel 3. rescue.target is roughly equal to runlevel 1, and there's emergency.target that's more or less what it sounds like. IIRC, the 'native' kernel parameter you can use to specify a particular target is systemd.default , so you could try: systemd.default=emergency.target or systemd.default=rescue.target as kernel parameters and see if those work. It is also useful to know how to rescue a failed X session after booting and in the middle of a graphical problem once logged in. On the old (current!) days you could switch also to a non-graphical VT and enter telinit 3 to go into runlevel 3 during a normal session or if X broke, and then reenable runlevel 5 by telinit 5. Is there going to remain an equivalent after f15 release - i.e. will switching to say VT 3 using the standard shortcut still be possible - and then I guess login as root and do systemctl stop prefdm.service and then systemctl start prefdm.service to reenable the graphical screen? -- mike c -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Fri, Apr 01, 2011 at 09:44:03PM +0100, mike cloaked wrote: It is also useful to know how to rescue a failed X session after booting and in the middle of a graphical problem once logged in. On the old (current!) days you could switch also to a non-graphical VT and enter telinit 3 to go into runlevel 3 during a normal session or if X broke, and then reenable runlevel 5 by telinit 5. Is there going to remain an equivalent after f15 release - i.e. will switching to say VT 3 using the standard shortcut still be possible - and then I guess login as root and do systemctl stop prefdm.service and then systemctl start prefdm.service to reenable the graphical screen? This is all documented here: http://fedoraproject.org/wiki/Systemd systemctl isolate multi-user.target (or) systemctl isolate runlevel3.target -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
Hi, 2011/3/31 Matthias Runge mru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Matthias -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNlJ2NAAoJEOnz8qQwcaIWTt8IAJuFw3TJnAydkjyO5gMeqT+Q 6D6K3myS/QpPdHohfqPBn+5clfhoMMLBklrCVzb/3Y1ethkUxm43SCFbc58Vw4wK kxRfkG3RKdsG2NvH9ec1cOaFWlns+m3w59PIMwVmztcWGX3CmjSj29tY3QOsoNf+ ae4DQw3kDCR/eLh2v/DSbSLlow/u2u0FQlKrenFKtEK1nzcuZhhX/qv0wPLJFLBz maBn0g2zf9qKJL32PzIq98RZSWm2I+MnvANW5gxMm0adFjuJMtEDKEXLIe7SBeOk C2VRnuMXsaHcHAUeiVLdnqpXVRI8ccv4rRd9SsW0P4qjyqXq5LMjd46puBc3PX4= =lyqn -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
W dniu 31 marca 2011 17:39 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, 2011/3/31 Matthias Rungemru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Thu, Mar 31, 2011 at 05:39:41PM +0200, Joachim Backes wrote: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I thought that enforcing=0 was considered a better option, no, as it avoided relabling. (I would be grateful if someone can either confirm or correct that statement.) Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: Okay, this is starting to grate my cheese. These woods aren't that big. Now, I know we've beein going straight because I've been following the North Star. Willow: Xander, that's not the North Star. It's an airplane. Xander: No, that's not an airplane. That's definitely...a blimp. But I can see how one would make that airplane mistake. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 03/31/2011 05:50 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 17:39 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, 2011/3/31 Matthias Rungemru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) I had the same problem : selinux=disabled in /etc/selinux/config, nevertheless SElinux problems during boot. But selinux=0 helped! -- Joachim Backesjoachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Thu, Mar 31, 2011 at 11:58:22 -0400, Scott Robbins scot...@nyc.rr.com wrote: I thought that enforcing=0 was considered a better option, no, as it avoided relabling. (I would be grateful if someone can either confirm or correct that statement.) Yes, enforcing=0 is a better temporary workaround than selinux=0 because the latter will force a relabel. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 03/31/2011 09:58 AM, Scott Robbins wrote: Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. virt-rescue (part of libguestfs) is very handy for changing the grub timeout of an offline VM. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
W dniu 31 marca 2011 18:09 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:50 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 17:39 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, 2011/3/31 Matthias Rungemru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) I had the same problem : selinux=disabled in /etc/selinux/config, nevertheless SElinux problems during boot. But selinux=0 helped! Good to know that it works this way not only on my system. I think that Daniel Walsh might want to know about this phenomen. -- Joachim Backesjoachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2011 12:14 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 18:09 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:50 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 17:39 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, 2011/3/31 Matthias Rungemru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) I had the same problem : selinux=disabled in /etc/selinux/config, nevertheless SElinux problems during boot. But selinux=0 helped! Good to know that it works this way not only on my system. I think that Daniel Walsh might want to know about this phenomen. -- Joachim Backesjoachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes Well if you don't have /etc/selinux/config then booting without selinux=0 will cause the system to crash. If you want to disable SELinux you need to tell the system by settingup /etc/selinux/config. If the system is blowing up with /etc/selinux/config and the line SELINUX=disabled Then that would be a new bug. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UqU8ACgkQrlYvE4MpobMiWQCgi1lHpSbBwzybYVzS5TGyNbEP mbkAoOEH8CLmNb/nG0JcAYO12mxB50dc =r+Si -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31/03/11 18:09, Joachim Backes wrote: On 03/31/2011 05:50 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 17:39 użytkownik Joachim Backes joachim.bac...@rhrk.uni-kl.de napisał: On 03/31/2011 05:32 PM, Michał Piotrowski wrote: Hi, 2011/3/31 Matthias Rungemru...@matthias-runge.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the subject says all: Since systemd(?) update an hour ago, my test system does not boot any more. removing rhgb quiet from kernel command line shows Failed to load SELINUX policy Failed to set security context... for /run: invalid argument Failed to set ... for /sys: Invalid argument Failed to set ... for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No sich file or directory Did someone else see this? How to repair such a broken system? Problem of the same category here https://bugzilla.redhat.com/show_bug.cgi?id=692573 I need to find out how to boot into emergency... solution should be simple - systemd downgrade Or boot with selinux=0 I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) I had the same problem : selinux=disabled in /etc/selinux/config, nevertheless SElinux problems during boot. But selinux=0 helped! Yes, definitely, this helped! Thanks a lot. -- Joachim Backesjoachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNlKlxAAoJEOnz8qQwcaIWTrAIAJu4OPwuLLhfG7BCJqw0hgDf 0PBk9mqLw32U2UUTnDI7C/9vgEuGZDEWeD5KTQkrf4aYy6MQmroujw4+pG12Akm/ pgXnGFB/W5gF9obBDsxj5/Aj/FyOb5Jlw5VwrmT2k1WlaSt2HSkl9lQUhy1GOhXP WXtVM/iAc09/orgaCz+j/pl+vpRXEfsfXjdYGIoGqy8HINvHWGUTyBUo2KSb9ZuW vus6/8M4bZYf8p86JHvQjaF0d4Q2258AWsV1lDB5dYJEGmW8NGkTRc0wG92EDD/R CwnihjvxE2U7Unh3n7YGuB/+AH/69m7dbRudGJurq2ilgar66+PMTjt2kfQM8Ts= =bOSz -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
W dniu 31 marca 2011 18:18 użytkownik Daniel J Walsh dwa...@redhat.com napisał: [..] Well if you don't have /etc/selinux/config then booting without selinux=0 will cause the system to crash. If you want to disable SELinux you need to tell the system by settingup /etc/selinux/config. If the system is blowing up with /etc/selinux/config and the line SELINUX=disabled Then that would be a new bug. cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UqU8ACgkQrlYvE4MpobMiWQCgi1lHpSbBwzybYVzS5TGyNbEP mbkAoOEH8CLmNb/nG0JcAYO12mxB50dc =r+Si -END PGP SIGNATURE- -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 03/31/2011 06:12 PM, Bruno Wolff III wrote: On Thu, Mar 31, 2011 at 11:58:22 -0400, Scott Robbinsscot...@nyc.rr.com wrote: I thought that enforcing=0 was considered a better option, no, as it avoided relabling. (I would be grateful if someone can either confirm or correct that statement.) Yes, enforcing=0 is a better temporary workaround than selinux=0 because the latter will force a relabel. I think this plays no role for me because *I* have SELINUX=disabled in /etc/selinux/config. -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
2011/3/31 Scott Robbins scot...@nyc.rr.com Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. indeed, i had to boot another operating system to increase the timeout so that i can change the kernel line when needed -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2011 12:20 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 18:18 użytkownik Daniel J Walsh dwa...@redhat.com napisał: [..] Well if you don't have /etc/selinux/config then booting without selinux=0 will cause the system to crash. If you want to disable SELinux you need to tell the system by settingup /etc/selinux/config. If the system is blowing up with /etc/selinux/config and the line SELINUX=disabled Then that would be a new bug. cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UqU8ACgkQrlYvE4MpobMiWQCgi1lHpSbBwzybYVzS5TGyNbEP mbkAoOEH8CLmNb/nG0JcAYO12mxB50dc =r+Si -END PGP SIGNATURE- Does the link /etc/sysconfig/selinux still exist? dracut should be in charge of disabling selinux. /usr/share/dracut/modules.d/98selinux/selinux-loadpolicy.sh Which should turn SELinux off. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Uq0wACgkQrlYvE4MpobPojACeMTtg5hMVffKxD3wMly5wP+Lj 3agAoOkAae1DDiUSLRB/KC31is+axmt7 =JitZ -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 03/31/2011 07:51 PM, cornel panceac wrote: 2011/3/31 Scott Robbins scot...@nyc.rr.com mailto:scot...@nyc.rr.com Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. indeed, i had to boot another operating system to increase the timeout so that i can change the kernel line when needed Holding left shift during early boot used to bring up the grub menu, timeout or not. Doesn't seem to work in F15 anymore, although having swithed to a usb-keyboard might have something to do with it. In any case getting the system to boot to single-user equivalent to workaround this systemd/selinux issue was unnecessarily painful. - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Thu, Mar 31, 2011 at 07:51:43PM +0300, cornel panceac wrote: Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. indeed, i had to boot another operating system to increase the timeout so that i can change the kernel line when needed For what it's worth, on VM's I've learned (though sometimes forgetting) to get over to a console--on VirtualBox, it's hold the host key, usually right control, and use the F2--to get to a console, go into /mnt/sysimage and edit grub.conf to give me a 3 second timeout before the reboot. (I also remove the hidden menu line.) -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: This is just too much. I mean, yesterday's my life like, uh oh, pop quiz. Today, it's rain of toads. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
W dniu 31 marca 2011 18:26 użytkownik Daniel J Walsh dwa...@redhat.com napisał: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2011 12:20 PM, Michał Piotrowski wrote: W dniu 31 marca 2011 18:18 użytkownik Daniel J Walsh dwa...@redhat.com napisał: [..] Well if you don't have /etc/selinux/config then booting without selinux=0 will cause the system to crash. If you want to disable SELinux you need to tell the system by settingup /etc/selinux/config. If the system is blowing up with /etc/selinux/config and the line SELINUX=disabled Then that would be a new bug. cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UqU8ACgkQrlYvE4MpobMiWQCgi1lHpSbBwzybYVzS5TGyNbEP mbkAoOEH8CLmNb/nG0JcAYO12mxB50dc =r+Si -END PGP SIGNATURE- Does the link /etc/sysconfig/selinux still exist? No, it doesn't exist. I'm wondering why. Perhaps it was deleted when I removed selinux-policy package? dracut should be in charge of disabling selinux. /usr/share/dracut/modules.d/98selinux/selinux-loadpolicy.sh Which should turn SELinux off. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Uq0wACgkQrlYvE4MpobPojACeMTtg5hMVffKxD3wMly5wP+Lj 3agAoOkAae1DDiUSLRB/KC31is+axmt7 =JitZ -END PGP SIGNATURE- -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Thu, 31 Mar 2011, Panu Matilainen wrote: On 03/31/2011 07:51 PM, cornel panceac wrote: 2011/3/31 Scott Robbins scot...@nyc.rr.com mailto:scot...@nyc.rr.com Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. indeed, i had to boot another operating system to increase the timeout so that i can change the kernel line when needed Holding left shift during early boot used to bring up the grub menu, timeout or not. Doesn't seem to work in F15 anymore, although having swithed to a usb-keyboard might have something to do with it. In any case getting the system to boot to single-user equivalent to workaround this systemd/selinux issue was unnecessarily painful. Did you found any way how to force systemd to boot to single-user? So far my installation of F15 with systemd has only one runlevel, I can not switch it - nor with grub option, neither with inittab or init command. - Panu - Adam Pribyl -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On 03/31/2011 10:40 PM, Adam Pribyl wrote: On Thu, 31 Mar 2011, Panu Matilainen wrote: On 03/31/2011 07:51 PM, cornel panceac wrote: 2011/3/31 Scott Robbinsscot...@nyc.rr.commailto:scot...@nyc.rr.com Yet another reason setting grub's timeout to 0 was a very bad idea, especially in VMs. indeed, i had to boot another operating system to increase the timeout so that i can change the kernel line when needed Holding left shift during early boot used to bring up the grub menu, timeout or not. Doesn't seem to work in F15 anymore, although having swithed to a usb-keyboard might have something to do with it. In any case getting the system to boot to single-user equivalent to workaround this systemd/selinux issue was unnecessarily painful. Did you found any way how to force systemd to boot to single-user? So far my installation of F15 with systemd has only one runlevel, I can not switch it - nor with grub option, neither with inittab or init command. The good old single keyword on the kernel line is what I used and worked fine (it might be just an alias for something else in systemd, I dunno). - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
