Date: Fri, 29 May 1998 21:38:19 -0700 From: Mike Smith <mike@smith.net.au> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Mike Smith <mike@smith.net.au>, Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... Message-ID: <199805300438.VAA00666@antipodes.cdrom.com> In-Reply-To: Your message of "Fri, 29 May 1998 22:25:44 PDT." <21984.896505944@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You could make a strong case for having mknod ignore the (dev) argument > > and just look the name up in the reference devfs copy, and then > > duplicate it at the path given (presuming that's inside a devfs). > > Well, the way I figured it, devfs is going to have a mechanism for > creating aliases anyway (for ln and friends), so an attempt to mknod > something would result in devfs doing a reverse-lookup on the > major/minor pair and creating an alias for the entry found. If none > is found at all, you treat the mknod as a bogus operation and punt it. 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. If/When dev_t finally disappears, this won't even be feasible. The only useful way to do it is to recover something by its original name. -- \\ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805300438.VAA00666>