cvs commit: src/release/amd64 boot_crunch.conf src/release/i386
boot_crunch.conf src/release/ia64 boot_crunch.conf src/release/pc98
boot_crunch.conf src/release/powerpc boot_crunch.conf
src/release/sparc64 boot_crunch.conf ...
sam at errno.com
Tue Jan 22 09:11:34 PST 2008
Ken Smith wrote:
> kensmith 2008-01-22 16:35:10 UTC
> FreeBSD src repository
> Modified files:
> release/amd64 boot_crunch.conf
> release/i386 boot_crunch.conf
> release/ia64 boot_crunch.conf
> release/pc98 boot_crunch.conf
> release/powerpc boot_crunch.conf
> release/sparc64 boot_crunch.conf
> release/sun4v boot_crunch.conf
> In 'fixit mode' running "fsck /dev/ad0s1a" typically complains that it
> can't find fsck_4.2bsd because there was no fstab file saying what
> filesystem type it is looking at so it got the filesystem type from
> the disk's label. When that fails admins who haven't been in this
> situation before are most likely to try "fsck -t ufs /dev/ad0s1a" because
> ufs is the type used in fstab files on working systems but that also fails
> complaining it can't find fsck_ufs.
> This just sets it up so /stand in the MFS image (/sbin is a symlink
> to /stand) includes hard links pointing fsck_4.2bsd and fsck_ufs to
> fsck_ffs which is what is present in /sbin on installed systems.
Thank you, this has been item #1 on my TODO list for several years!
Want to go for #2? :-) (loading a module via loader w/ undefined symbols
causes the system to panic at boot).
More information about the cvs-all