Re: [gentoo-user] problems debugging a systemd problem

[Canek Peláez Valdés]

On Thu, May 28, 2015 at 5:23 PM, Rich Freeman <rich0@g.o> wrote:
>
> On Thu, May 28, 2015 at 5:32 PM, Canek Peláez Valdés <caneko@×××××.com>
wrote:
> >
> > As I said, I did the following tests:
> >
> > 1. Adding "emergency" to the kernel command line, with a valid root=.
> > 2. Adding "rescue" to the kernel command line, with a valid root=.
> > 2. Leaving root= invalid without adding neither "emergency" nor
"rescue".
> >
> > If root= is valid, with emergency systemd drops you to a shell with your
> > root filesystem mounted read-only. With rescue, systemd drops you to a
shell
> > with all your filesystems mounted read-write.
> >
> > If root= is invalid, it doesn't matter if you use emergency, rescue, or
> > neither, *dracut* drops you to a shell, still inside the initramfs
> > obviously. It takes a while; I didn't took the time, but I think it was
3
> > minutes. Inside this shell, you can use systemd normally, and if you
manage
> > to mount the root filesystem, I'm sure you could continue the normal
boot
> > process. You'll have to pivot root manually, though.
>
> That was basically my understanding of how dracut behaved.  I think
> we're just having a communication gap or something, because you seem
> to be disagreeing with me when I'm basically trying to describe the
> behavior you just listed above.

It's possible; I was wrong about emergency doing anything when root= is
invalid, but I did not understood the above behavior from your previous
mails.

Anyway, if dracut cannot mount the root filesystem, it will drop you into a
shell with a functional systemd. Eventually.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México