From owner-freebsd-hackers Wed Mar 26 06:28:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA11188 for hackers-outgoing; Wed, 26 Mar 1997 06:28:19 -0800 (PST) Received: from orchard.east-arlington.ma.us (sommerfeld.ne.highway1.com [24.128.53.76]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA11168 for ; Wed, 26 Mar 1997 06:28:08 -0800 (PST) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by orchard.east-arlington.ma.us (8.8.5/1.34) with SMTP id OAA10034; Wed, 26 Mar 1997 14:26:39 GMT Message-Id: <199703261426.OAA10034@orchard.east-arlington.ma.us> To: Jonathan Stone cc: Terry Lambert , perry@piermont.com, hackers@freebsd.org, port-i386@netbsd.org Subject: Re: how to name fs specific programs In-reply-to: Your message of "Tue, 25 Mar 1997 22:46:15 -0800 ." <199703260646.WAA14086@Pescadero.DSG.Stanford.EDU> Date: Wed, 26 Mar 1997 09:26:35 -0500 From: Bill Sommerfeld Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I believe I understand what Terry's suggesting. He wants to be able to be able to have a new filesystem type appear by simply mounting (or symlinking, or copying) the implementation of a new filesystem type into /sbin/fs/foo, and he believes that the name of the filesystem type should be defined purely by the name used in the /sbin/fs directory, and not by anything inherent in the binaries found inside /sbin/fs/foo/. so that, as an extreme case, one could do mv /sbin/fs/{nfs,losefs} and sed 's/nfs/losefs/' /etc/fstab.NEW && mv /etc/fstab{.NEW,} and reboot, and everything will keep working.. - Bill