On Fri, Sep 22, 2000, Boris Popov wrote:
> 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.
> These (and probably other confusing) characters can be replaced
> with underscores without much harm.
That shouldn't be that hard to do. What do others think?
Adrian Chadd "The main reason Santa is so jolly is
<[EMAIL PROTECTED]> because he knows where all the bad girls
live." -- Random IRC quote
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message