From a1435ad4915e20a95f0606877708b2145fc3acff Mon Sep 17 00:00:00 2001 From: Ken Smith Date: Tue, 22 Jan 2008 16:35:10 +0000 Subject: 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. Prodded by: obrien MFC after: 1 day --- release/amd64/boot_crunch.conf | 2 ++ 1 file changed, 2 insertions(+) (limited to 'release/amd64') diff --git a/release/amd64/boot_crunch.conf b/release/amd64/boot_crunch.conf index e478b258815d..2cefa5a20818 100644 --- a/release/amd64/boot_crunch.conf +++ b/release/amd64/boot_crunch.conf @@ -25,6 +25,8 @@ progs route progs rtsol progs slattach progs tunefs +ln fsck_ffs fsck_4.2bsd +ln fsck_ffs fsck_ufs srcdirs /usr/src/usr.bin progs find -- cgit v1.2.3