atom feed15 messages in org.freebsd.freebsd-currentRe: Fsck wrappers, revisited
FromSent OnAttachments
Adrian ChaddSep 21, 2000 10:10 am 
Adrian ChaddSep 22, 2000 2:17 am 
Boris PopovSep 22, 2000 2:27 am 
Adrian ChaddSep 22, 2000 2:38 am 
Adrian ChaddSep 22, 2000 2:49 am 
Boris PopovSep 22, 2000 3:59 am 
Adrian ChaddSep 22, 2000 4:36 am 
Bruce EvansSep 22, 2000 8:59 am 
Adrian ChaddSep 22, 2000 12:55 pm 
Adrian ChaddSep 23, 2000 2:44 am 
Kris KennawaySep 24, 2000 1:37 am 
Adrian ChaddSep 24, 2000 1:56 am 
Bruce EvansSep 25, 2000 9:51 am 
Bruce EvansSep 25, 2000 10:07 am 
Adrian ChaddSep 27, 2000 10:57 pm 
Subject:Re: Fsck wrappers, revisited
From:Adrian Chadd (adr@freebsd.org)
Date:Sep 22, 2000 2:38:42 am
List:org.freebsd.freebsd-current

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

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message