On Apr 26, 1:00 pm, Marco d'Itri m...@linux.it wrote:
On Apr 26, Damien Wyart damien.wy...@free.fr wrote:
May I ask how you guessed that my problem could be related to this?
With devtmpfs, devices are created earlier.
I thought udev creating a tmpfs for /dev when devtmpfs is not enabled
Hi,
I am not using LVM, so I do not reproduce the exact same problem, but
after upgrading to udev 168-1 my system also became unbootable.
It looks like root gets mounted (I do not use an initrd), but some disk
device nodes in /dev are not yet present when the fsck are started, so
they fail, and
On Apr 26, Damien Wyart damien.wy...@free.fr wrote:
It looks like root gets mounted (I do not use an initrd), but some disk
device nodes in /dev are not yet present when the fsck are started, so
they fail, and I get an emergency prompt. If I press C-d, boot continues
So you are using a custom
On Apr 26, Damien Wyart damien.wy...@free.fr wrote:
May I ask how you guessed that my problem could be related to this?
With devtmpfs, devices are created earlier.
I thought udev creating a tmpfs for /dev when devtmpfs is not enabled
was not affecting its subsequent behaviour.
Indeed. This is
* m...@linux.it (Marco d'Itri) [110426 15:21]:
It looks like root gets mounted (I do not use an initrd), but some
disk device nodes in /dev are not yet present when the fsck are
started, so they fail, and I get an emergency prompt. If I press
C-d, boot continues
So you are using a custom
5 matches
Mail list logo
