From owner-freebsd-current Mon Jan 29 22:41:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id E37F437B402; Mon, 29 Jan 2001 22:41:25 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0U6fBK26966; Tue, 30 Jan 2001 07:41:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Boris Popov Cc: Greg Lehey , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Tue, 30 Jan 2001 08:37:56 +0600." Date: Tue, 30 Jan 2001 07:41:11 +0100 Message-ID: <26964.980836871@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , 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