Re: systemd failure to boot

2010-07-29 Thread Bill Nottingham
Michal Jaegermann (mic...@harddata.com) said: > Oh, and the next surprise. After a boot with 'init=/sbin/upstart' > a simple "reboot" powered the whole machine down while it should > not. https://bugzilla.redhat.com/show_bug.cgi?id=618678 Bill -- test mailing list test@lists.fedoraproject.org

Re: systemd failure to boot

2010-07-28 Thread Rahul Sundaram
On 07/29/2010 09:41 AM, Horst H. von Brand wrote: > Then it should panic, like it does if there isn't an init around... https://bugzilla.redhat.com/show_bug.cgi?id=618315 Please file any further issues in bugzilla. Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: htt

Re: systemd failure to boot

2010-07-28 Thread Horst H. von Brand
Adam Williamson wrote: > On Wed, 2010-07-28 at 22:02 -0400, Horst H. von Brand wrote: > > > > After you boot with upstart, run > > > > > > ln -sf /lib/systemd/system/graphical.target > > > /etc/systemd/system/default.target > > > > Done (before rebooting, thanks!) > > > > Shouldn't there be

Re: systemd failure to boot

2010-07-28 Thread Adam Williamson
On Wed, 2010-07-28 at 22:02 -0400, Horst H. von Brand wrote: > > After you boot with upstart, run > > > > ln -sf /lib/systemd/system/graphical.target > > /etc/systemd/system/default.target > > Done (before rebooting, thanks!) > > Shouldn't there be some hardwired default target for this kind

Re: systemd failure to boot

2010-07-28 Thread Horst H. von Brand
Rahul Sundaram wrote: > On 07/29/2010 04:25 AM, Michal Jaegermann wrote: > > The latest rawhide updates switched a default init from upstart to > > systemd and systemd-sysvinit. An attempt to boot a system after > > those changes ended up with: > > > > .. > > init[1]: Set hostname to . >

Re: systemd failure to boot

2010-07-28 Thread Michal Jaegermann
On Wed, Jul 28, 2010 at 06:32:40PM -0600, Michal Jaegermann wrote: > > Thanks Rahul! It looks that the thing is seriously buggy. Oh, and the next surprise. After a boot with 'init=/sbin/upstart' a simple "reboot" powered the whole machine down while it should not. OTOH after 'shutdown -h now'

Re: systemd failure to boot

2010-07-28 Thread Michal Jaegermann
On Thu, Jul 29, 2010 at 04:40:13AM +0530, Rahul Sundaram wrote: > On 07/29/2010 04:25 AM, Michal Jaegermann wrote: > > The latest rawhide updates switched a default init from upstart to > > systemd and systemd-sysvinit. An attempt to boot a system after > > those changes ended up with: > > > > ..

Re: systemd failure to boot

2010-07-28 Thread Rahul Sundaram
On 07/29/2010 04:25 AM, Michal Jaegermann wrote: > The latest rawhide updates switched a default init from upstart to > systemd and systemd-sysvinit. An attempt to boot a system after > those changes ended up with: > > .. > init[1]: Set hostname to . > init[1]: Failed to load configuratio

systemd failure to boot

2010-07-28 Thread Michal Jaegermann
The latest rawhide updates switched a default init from upstart to systemd and systemd-sysvinit. An attempt to boot a system after those changes ended up with: .. init[1]: Set hostname to . init[1]: Failed to load configuration for distcache.service: No such file or directory init[1]: Fa