Date: Tue, 22 Jan 2008 09:11:33 -0800 From: Sam Leffler <sam@errno.com> To: Ken Smith <kensmith@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: 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 ... Message-ID: <479623C5.9030804@errno.com> In-Reply-To: <200801221635.m0MGZA9a056058@repoman.freebsd.org> References: <200801221635.m0MGZA9a056058@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
> Log:
> 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).
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479623C5.9030804>