Date: Sun, 24 Sep 2000 01:37:41 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Boris Popov <bp@butya.kz>, freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <Pine.BSF.4.21.0009240137090.94665-100000@freefall.freebsd.org> In-Reply-To: <20001223114150.A38052@roaming.cacheboy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Dec 2000, Adrian Chadd wrote:
> On Fri, Sep 22, 2000, Boris Popov wrote:
> > On Sat, 23 Dec 2000, Adrian Chadd wrote:
> >
> > > So now is a problem which I'm sure the NetBSD people came up against.
> > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
> > > this by creating a new list 'mountnames[]', which maps the fs type to
> > > a string.
> >
> > Probably a hard link to fsck_ffs will do the job fine and makes it
> > clear to see which fs'es are supported:
> >
> > # ls -ail fsck*
> > 6338 -r-xr-xr-x 1 root wheel 66032 22 sen 16:24 fsck
> > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_4.2BSD
> > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ffs
> > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ufs
>
> The trouble is that some of the FS strings have spaces in their filenames.
> This might confuse a few people.
How about mapping spaces to '_' characters - I doubt it would cause any
namespace collisions.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009240137090.94665-100000>