Hi, On 28/06/12 08:34, Peter Simons wrote:
> I booted my EeePC laptop with the new busybox-based init ramdisk today, and > I got a (non-fatal) error because the program "fsck.auto" is absent. I'm not > sure what that means, but I reckon our new fsck binary from busybox can't > guess the file system type like the old implementation could and thus fails. Yeah, busybox's fsck isn't as smart as the regular fsck. I've fixed this by adding some code to auto-detect the filesystem type before calling fsck. -- Eelco Dolstra | LogicBlox, Inc. | http://www.st.ewi.tudelft.nl/~dolstra/ _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
