From owner-freebsd-current Sat May 30 16:22:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23635 for freebsd-current-outgoing; Sat, 30 May 1998 16:22:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23618 for ; Sat, 30 May 1998 16:21:56 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id XAA03982; Sat, 30 May 1998 23:14:10 GMT Date: Sun, 31 May 1998 08:14:10 +0900 (JST) From: Michael Hancock To: Poul-Henning Kamp cc: "Jordan K. Hubbard" , Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <17376.896521066@critter.freebsd.dk> 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 Sat, 30 May 1998, Poul-Henning Kamp wrote: > Devfs is synthetic and maybe we shouldn't even allow removes in the > first place but a whiteout/undelete solution is the "POLA" choice. > > Alternatively devfs could allow mknod, but ignore the major/minor > numbers given and just "DTRT", that would work also after we have > killed dev_t. I agree with either of these options. The whiteout solution would mean a lot of hacking on a devfs_lookup(). Being able to refresh the node using mknod without the major/minor arguments or ignoring the arguments and just DTRT sounds good to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message