Vasily Averin wrote:
> While /dev mounted as tmpfs it does not contain /dev/disk/by-uuid directory,
> 10_linux script did not check it properly and do not set root device via UUID.
> Therefore following kernel boot can fail (incorrect root device) if device
> names
> was changed.
>
>
I would be
Am Samstag, den 17.10.2009, 13:56 +0100 schrieb Colin Watson:
> On Sat, Oct 17, 2009 at 02:50:41PM +0200, Felix Zielcke wrote:
> > If /dev/disk/by-uuid/abc123 doestn't exit, then this implies
> > that /dev/disk/by-uuid is not a directory.
>
> I think you are misreading the original patch. Check it
On Sat, Oct 17, 2009 at 02:50:41PM +0200, Felix Zielcke wrote:
> If /dev/disk/by-uuid/abc123 doestn't exit, then this implies
> that /dev/disk/by-uuid is not a directory.
I think you are misreading the original patch. Check it again ...
--
Colin Watson [cjwa
On Sat, Oct 17, 2009 at 04:24:53PM +0400, Vasily Averin wrote:
> While /dev mounted as tmpfs it does not contain /dev/disk/by-uuid directory,
> 10_linux script did not check it properly and do not set root device via UUID.
> Therefore following kernel boot can fail (incorrect root device) if device
Am Samstag, den 17.10.2009, 16:24 +0400 schrieb Vasily Averin:
> While /dev mounted as tmpfs it does not contain /dev/disk/by-uuid
> directory,
> 10_linux script did not check it properly and do not set root device
> via UUID.
> Therefore following kernel boot can fail (incorrect root device) if
>
While /dev mounted as tmpfs it does not contain /dev/disk/by-uuid directory,
10_linux script did not check it properly and do not set root device via UUID.
Therefore following kernel boot can fail (incorrect root device) if device names
was changed.
Attached path fixes this issue. Please review an
