From owner-freebsd-current  Fri Feb  9 14:49:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA21956
          for current-outgoing; Fri, 9 Feb 1996 14:49:06 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA21951
          for <current@freebsd.org>; Fri, 9 Feb 1996 14:49:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id OAA21840; Fri, 9 Feb 1996 14:48:19 -0800
To: Julian Elischer <julian@ref.tfs.com>
cc: phk@critter.tfs.com, terry@lambert.org, current@freebsd.org
Subject: Re: FS PATCHES: THE NEXT GENERATION 
In-reply-to: Your message of "Fri, 09 Feb 1996 12:25:15 PST."
             <199602092025.MAA00293@ref.tfs.com> 
Date: Fri, 09 Feb 1996 14:48:18 -0800
Message-ID: <21838.823906098@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
Precedence: bulk

> I think that mount_devfs should be able to look somewhere for a
> configuration script regarding the filesystem it's making. however there
> is NO ANSWER anywhere, for what to do about a new device that just pops up...

That's a different problem, and not one I even suggested we try and
address.  It's also not in any way relevant to the current discussion.

						Jordan