Date: Tue, 30 Jan 2001 07:41:11 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Boris Popov <bp@butya.kz> Cc: Greg Lehey <grog@lemis.com>, Steve Ames <steve@virtual-voodoo.com>, John Baldwin <jhb@FreeBSD.ORG>, John Indra <john@naver.co.id>, freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... Message-ID: <26964.980836871@critter> In-Reply-To: Your message of "Tue, 30 Jan 2001 08:37:56 %2B0600." <Pine.BSF.4.21.0101300832480.46219-100000@lion.butya.kz>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.21.0101300832480.46219-100000@lion.butya.kz>, Boris Popov writes: >On Tue, 30 Jan 2001, Greg Lehey wrote: > >> > You can create symlinks in /dev, you cannot mknod there. >> >> What is the reason for this? How does a program or script know >> whether the system is running DEVFS or not? > > I don't see any good reason why this can't be supported. We may >talk about 'broken' devices, etc., but while there any - mknod needs to be >supported to make transition more smooth. No, mknod needs to be broken so people fix all drivers to be DEVFS aware. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?26964.980836871>