From owner-freebsd-fs Fri Sep 22 2:39: 8 2000 Delivered-To: freebsd-fs@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 58A9137B423; Fri, 22 Sep 2000 02:39:04 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBNAfo338064; Sat, 23 Dec 2000 11:41:50 +0100 (CET) (envelope-from adrian) Date: Sat, 23 Dec 2000 11:41:50 +0100 From: Adrian Chadd To: Boris Popov Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20001223114150.A38052@roaming.cacheboy.net> References: <20001223112038.A37548@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bp@butya.kz on Fri, Sep 22, 2000 at 04:27:58PM +0700 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message