Date: Thu, 28 Sep 2000 07:57:47 +0200 From: Adrian Chadd <adrian@freebsd.org> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20000928075747.B1740@roaming.cacheboy.net> In-Reply-To: <Pine.BSF.4.21.0009260346491.12315-100000@besplex.bde.org>; from bde@zeta.org.au on Tue, Sep 26, 2000 at 03:51:51AM %2B1100 References: <20000923114434.A4419@roaming.cacheboy.net> <Pine.BSF.4.21.0009260346491.12315-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 26, 2000, Bruce Evans wrote:
> > Well, if you have any suggestions, I'm all for it. :-)
>
> I don't understand the problem. You get the filesystem type name
> (fstypename) from fs_vfstype in struct fstab or from f_fstypename in
> struct statfs. You attempt to execute strcat("/sbin/fsck_", fstypename)
> to see if fsck is supported on filesystems of type fstypename.
You don't try to auto-detect and fsck a mounted FS. If its mounted and you
are doing it during bootup, it'll generally be in fstab which the current
wrapper code looks in.
So, the question is: how do you take the raw disk device and figure out which
FS type it is, and then which fsck program to run?
Adrian
--
Adrian Chadd "The main reason Santa is so jolly is
<adrian@freebsd.org> because he knows where all the bad girls
live." -- Random IRC quote
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000928075747.B1740>