Date: Sat, 14 Feb 1998 10:28:25 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br> Cc: julian@whistle.com (Julian Elischer), mike@smith.net.au, committers@FreeBSD.ORG Subject: Re: devfs persistance Message-ID: <7804.887448505@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 14 Feb 1998 02:36:35 -0200." <199802140436.CAA01747@gaia.coppe.ufrj.br>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199802140436.CAA01747@gaia.coppe.ufrj.br>, Joao Carlos Mendes Luis writes: >Some questions about DEVFS. (Shouldn't this go to freebsd-hackers ?) > >1) What will be the impact on hand-created devices ? Will still be possible > to simply mknod some file on some dir and use it ? I don't like the > ideia of having to use DEVFS on chrooted environments. In such > environments not all devices should be seen, and the permissions > could be even different from the defaults. No, you cannot hand-create devices anymore. Chroot will be dealt with some way, yet to be agreed on. I share your desire about chrooted environment.s >2) What's the practical meaning of "turning DEVFS default" ? A lot of gunk like /etc/MAKEDEVS become unneeded. >3) Will DEVFS in any sense make major numbers random ? if so, my #1 > question is already answered. Not to hardcode device number is > good, but letting the kernel choose them on the fly is not good. > I like, for example, the Solaris' /etc/name_to_major approach. Better yet, it eventually will make them go away. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7804.887448505>