On Wed, Aug 18, 2010 at 07:00:16PM -0400, Dave Jones wrote:
> On Thu, Aug 19, 2010 at 12:53:44AM +0200, Lennart Poettering wrote:
>
> > > > > It tells me to see the logs for details, but there's not a single
> message
> > > > > from systemd in the logs.
> > > >
> > > > There should be an explanation in dmesg, that it cannot find
> default.target.
> > >
> > > at the stage that it stopped, I guess syslog wasn't running, so it
> never made
> > > it into the boot logs.
> >
> > Hmm, could be. Note that we log to kmsg as long as syslog isn't up, so
> > nothing should get lost -- as long as you manage to get a shell somehow.
> >
> > BTW, as a side note: a simply fix to bypass the problem with a missing
> > default.target is to pass "5" on the kernel command line. This will then
> > boot into gdm regardless whether default.target exists or not.
> >
> > the git version of systemd will automatically enter signle user mode if
> > default.target is missing or borked.
>
> So I got it booting after creating the default.target symlink, but the
> network
> no longer comes up automatically (nor services dependant upon it, like sshd).
> Did I miss another mail ?
related to this I guess ?
[ 44.659412] init[1]: Failed to load configuration for
NetworkManager-by-dbus.service: No such file or directory
[ 44.659596] init[1]: D-Bus activation failed for
NetworkManager-by-dbus.service: Invalid argument
Dave
--
devel mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/devel
