From owner-freebsd-current Mon Sep 25 10: 8:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1628B37B42C; Mon, 25 Sep 2000 10:08:10 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA02688; Tue, 26 Sep 2000 04:08:06 +1100 Date: Tue, 26 Sep 2000 04:08:01 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Adrian Chadd Cc: Kris Kennaway , freebsd-fs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fsck wrappers, revisited In-Reply-To: <20000924105645.A7573@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Sep 2000, Adrian Chadd wrote: > On Sun, Sep 24, 2000, Kris Kennaway wrote: > > > > 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. > > Yes, as bp mentioned to me before, so I'm thinking about passing the fsname > through a tolower() and a s/ /_/g before using it as a filename. > > Any problems with this? This shouldn't be necessary. All fstypenames for currently supported filesystems are in lower case with no underscores, and new ones should follow this convention. Spaces in the names would probably break /etc/fstab. Fstypenames for currently supported filesystems as found by grepping for VFS_SET in /sys: cd9660 coda devfs ext2fs fdesc hpfs kernfs linprocfs mfs msdos nfs ntfs ntfs nullfs nwfs portal procfs ufs umap union Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message