On Wed, Aug 25, 2010 at 08:02:45PM -0700, Adam Williamson wrote: > On Wed, 2010-08-25 at 21:18 -0400, Tom Horsley wrote: > > > > http://home.comcast.net/~tomhorsley/wisdom/braindump/oss-happens.html > > > > Another example of the Vogon effect :-). > > No, not really. It's not the Vogon effect. This is a very public, > very open project; the use of systemd has been discussed > extensively on this list, and on -test list, and is listed in the > Alpha release notes - it's the very first item under 'what's new' > http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Better_System_and_Session_Management > - and the Alpha release announcement - > https://fedoraproject.org/wiki/F14_Alpha_release_announcement - > again it's the first item. OK, let's try this "first item" in its entirety. Fedora 14 introduces systemd, a smarter, more efficient way of starting up and managing background daemons and services. It is a drop-in replacement for sysvinit and upstart, maintaining compatibility with SysV and LSB init scripts. Ahem! So far AFAICT "smarter, more efficient" are quite far from being demonstrated, "drop-in" is debatable and "maintaining compatibility" in the curent state it certainly is not. So where this leaves us? Searching bugzilla for systemd and reading through search results can be an enlightening experience. One way around these issues would be to make sure that /sbin/upstart is installed and booting with 'init=/sbin/upstart' in kernel parameters. Of course then you are not testing systemd. OTOH adding '5' there may just work (maybe). Michal -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
