GNU bug report logs -
#25917
operating-system file-system with (check? #t) but (needed-for-boot #f) pauses boot until user interaction
Previous Next
Full log
Message #20 received at 25917 <at> debbugs.gnu.org (full text, mbox):
> One thing I don’t get is that, if the file system is not
> needed-for-boot?, then it doesn’t get a Shepherd service in the first
> place.
But what is supposed to happen to filesystems where mount? but not needed-for-boot? if Shepherd doesn't mount it? Does some other part mount it ? Is it just put into fstab or something ?
> In your original message, you wrote that the problem is that “the initrd
> doesn't contain the fsck tool”, so it’s a problem in linux-initrd.scm,
> no?
I don't know where we should fix it. If you want to reproduce it, I tested it with this config
(file-systems (cons* ...
(file-system
(device "NO NAME")
(title 'label)
(mount-point "/mnt/tmp")
(type "vfat")
(needed-for-boot? #f)
(mount? #t)
(check? #t))
%base-file-systems))
and an USB flash memory stick with name "NO NAME" (the default of the stick :) ).
The effect is if not needed-for-boot? but check? , the boot breaks because it can't find fsck.vfat .
vfat is good for testing this since it's usually the only filesystem of that type on the system and so it can't be required by another filesystem entry and mask the problem.
This bug report was last modified 8 years and 33 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.