Date: Sat, 30 May 1998 15:53:10 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... Message-ID: <Pine.BSF.3.95.980530154859.10304C-100000@current1.whistle.com> In-Reply-To: <1416.896556860@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
I agree with this it's not a bad idea If the device being made does not exist then the master directory corresponding with that the mknod is in is scanned for that name. if it exists, it's made. Now, here are some implementatioan details.. If it already exists there but was just renamed, should I make it a link? I think yes (I can do this quite easily). If the entire directory has been renamed? with On Sat, 30 May 1998, Poul-Henning Kamp wrote: > > Julian, > > Just to get peace over the land again, I think you should implement > it so that one can mknod a device again, but discard the dev_t, > and use whatever DEVFS knows (better). > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > 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?Pine.BSF.3.95.980530154859.10304C-100000>