Date: 22 Oct 2000 20:27:52 +0200 From: Dag-Erling Smorgrav <des@thinksec.com> To: Marius Bendiksen <mbendiks@eunet.no> Cc: arch@freebsd.org Subject: Re: Ideas concerning fsck Message-ID: <xzp66mk4tp3.fsf@aes.thinksec.com> In-Reply-To: Marius Bendiksen's message of "Sun, 22 Oct 2000 19:37:10 %2B0200 (CEST)" References: <Pine.BSF.4.05.10010221929290.32404-100000@login-1.eunet.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Marius Bendiksen <mbendiks@eunet.no> writes:
> > 2) if the mountpoint is "none", skip this entry.
>
> Please don't. =)
>
> It is entirely sensible to be able to fsck a filesystem upon boot without
> actually mounting it.
That's what noauto is for. The "none" mountpoint denotes a swap
partition.
> > 3) if the fs type is known, run the appropriate command (which can
> > be null, e.g. for cd9660), and skip to the next entry.
> > 4) if the fs type is unknown, but fsck_${fstype} exists, run it and
> > skip to the next entry.
> Why this distinction ?
Because you may want to treat some systems specially (e.g. don't do
anything for cd9660), so you only try to run fsck_${fstype} if you
don't know of anything else to do.
> I would think you'd either want to go entirely with the approach in (4),
> or add a new file in /etc, say "fstypes" or "fscktab".
Yes, that might be a good idea.
> The logic to avoid thrashing would be a must. Currently, this can be
> avoided by logic on the part of the admin, by using pass 1 where
> neccessary. As to doing / first, why?
Doing anything at all before you know you can trust your root
partition (where fsck itself is stored) is not a very good idea.
DES
--
Dag-Erling Smørgrav - des@thinksec.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp66mk4tp3.fsf>