From owner-freebsd-current Fri May 29 23:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01419 for freebsd-current-outgoing; Fri, 29 May 1998 23:35:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01398 for ; Fri, 29 May 1998 23:35:50 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00926; Fri, 29 May 1998 22:31:22 -0700 (PDT) Message-Id: <199805300531.WAA00926@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 23:26:02 PDT." <29532.896509562@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 22:31:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Uh, doing a reverse lookup on the major/minor pair would be pretty > > unuseful. If you've just deleted the device, you have no idea what > > it's (dev) is, so you can't possibly supply them as arguments. > > Eh? You still have an instance in your "template" mount that you can > match up. I also _know_ that majors and minors are going away - I'm > not trying to argue for their long-term preservation, simply that they > continue to have as much "meaning" as possible during the transition > period (which I would expect to last as long as 1 maybe 2 years before > people are entirely accustomed to the new model). Yes, but you can't *look*at* the template mount to find out what these numbers *are*. As a user, if I have just nuked /dev/foo0, what I am going to want to do is "mknod /dev/foo0 ". My suggestion was simply that the name /dev/foo0 contains everything that's required to reconstruct the node, providing you haven't done something smart like renaming it. ie. you could only mknod "original" devices. As an alternative, whiteout support might be better, although I don't think that many people are familiar with whiteouts. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message