From owner-freebsd-hackers Tue Mar 25 20:24:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA13067 for hackers-outgoing; Tue, 25 Mar 1997 20:24:13 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA13061 for ; Tue, 25 Mar 1997 20:24:07 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA26886; Tue, 25 Mar 1997 21:10:04 -0700 From: Terry Lambert Message-Id: <199703260410.VAA26886@phaeton.artisoft.com> Subject: Re: how to name fs specific programs To: cjs@portal.ca (Curt Sampson) Date: Tue, 25 Mar 1997 21:10:04 -0700 (MST) Cc: terry@lambert.org, perry@piermont.com, thorpej@nas.nasa.gov, joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org, port-i386@NetBSD.ORG, darrenr@cyber.com.au In-Reply-To: from "Curt Sampson" at Mar 25, 97 05:43:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > $FSBIN/$FSTYPE/$FSCMD $ARGS > > ... > > for i in * > > do > > # for each FS for which an "fstyp" exists.. > > if test -x $i/fstyp > > then > > [stuff] > >... > > So what you're saying is that the above is significantly better than > > $FSCMD_$FSTYPE $ARGS > > and > > for i in *_fstyp; do [stuff] ... > > Or am I missing something here? You're missing the fact that the file system support may have arrived as the rsult of a union mount, and that the organization to allow this requires that the per-FS components be logically and simply seperable from the other components. For instance, I may wish to have a directory overlay from /usr for the additional fs's other than FFS, since only FFS is needed for boot. This is only an example of something I might want to do. I can provide others, if necessary, and if you want to spend the time on them. In reality, given the discussion Doug Rabson, Mike Smith, and I had, it should be obious that an ELF executable could be considered a "bootfs" image, and all other FS types could result from a directed overlay from that into a real FS name space. That is, i support variosu FS types as single modules which may be agregated with boot and kernel images. All the better to boot from VFATSFS or EXT2FS as root and have a kernel that doesn't support FFS at all until a module is loaded from one of the FS types it does support. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.