From owner-freebsd-fs Fri Sep 22 4: 0:14 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id DDD4A37B423; Fri, 22 Sep 2000 04:00:08 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 0626E28805; Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id E740828803; Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) Date: Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) From: Boris Popov To: Adrian Chadd Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited In-Reply-To: <20001223114150.A38052@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message