From owner-freebsd-current  Fri Feb  9 14:41:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA21128
          for current-outgoing; Fri, 9 Feb 1996 14:41:53 -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 OAA21119
          for <current@freebsd.org>; Fri, 9 Feb 1996 14:41:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id OAA21808; Fri, 9 Feb 1996 14:40:49 -0800
To: Terry Lambert <terry@lambert.org>
cc: roberto@keltia.freenix.fr (Ollivier Robert), phk@critter.tfs.com,
        julian@ref.tfs.com, current@freebsd.org
Subject: Re: FS PATCHES: THE NEXT GENERATION 
In-reply-to: Your message of "Fri, 09 Feb 1996 13:07:38 MST."
             <199602092007.NAA11001@phaeton.artisoft.com> 
Date: Fri, 09 Feb 1996 14:40:49 -0800
Message-ID: <21806.823905649@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
Precedence: bulk

> And you could "save" the current settings to the database in an
> "rc.shutdown" or some similar method.

I don't care where it lives, just so long as it's transparent and
I don't have to learn about the secret life of Yet Another Etc File.

> The point is, that this is a solvable problem, and you don't need to
> delay devfs deployment until after it is solved just because someone

Terry, I'm wondering if you've gone blind here again or something
because I've said *several* times that there's NO PROBLEM WITH
DEPLOYING IT RIGHT NOW, JUST DON'T MAKE IT FRIGGIN' *MANDATORY* YET
UNTIL IT'S FIXED!

I'm hoping that capital letters will penetrate your cranium since no
other forms of explanation seem to have succeeded so far! :-)

						Jordan