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:
>
> ..........
> init[1]: Set hostname to <localhost.localdomain>.
> init[1]: Failed to load configuration for distcache.service: No such file or
directory
> init[1]: Failed to load configuration for default.target: No such file or directory
> init[1]: Failed to start default target: Unit default.target failed to load. See log
for details.
> systemd-cgroups used greatest stack depth: 3600 bytes left
>
After you boot with upstart, run
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Reboot and check again.
Thanks Rahul! It looks that the thing is seriously buggy. Indeed
after I followed your advice a system is up in that sense that, for
example, I can log on over a network. 'boot.log' ends up with:
....
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Starting Starts/stop the "at" daemon...
Starting smartd: Starting atd: [ OK ]
[ OK ]
[ OK ]
and that is it. No further progress and no local login of any kind;
either graphic or console. Quite possible that this is an issue
identified in
https://bugzilla.redhat.com/show_bug.cgi?id=618315#c3
I do not see any tty programs running. If this is the case that
would make the last sentence in that comment rather false. At this
moment I have to do other things so trying to figure that out have
to be delayed for better times.
I wonder what if I have a system which boots only to a text console
(I do have such things but they do not run rawhide). It seems that
'graphical.target' as a 'default.target' would be not something to
be used. In any case a number of services in a systemd sequence
ended up as "failed". OTOH these could be, for example, something
like "Starting Initialize SCSI tape drives with /sbin/stinit". Who,
on earth, asked for it?
Michal