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