From owner-freebsd-current Mon Jan 29 22:40:18 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 2C8E637B400; Mon, 29 Jan 2001 22:40:01 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0U6dsK26897; Tue, 30 Jan 2001 07:39:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Tue, 30 Jan 2001 11:48:48 +1030." <20010130114848.B48269@wantadilla.lemis.com> Date: Tue, 30 Jan 2001 07:39:54 +0100 Message-ID: <26895.980836794@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010130114848.B48269@wantadilla.lemis.com>, Greg Lehey writes: >> 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? The reson for not creating device nodes is that you don't have all the information you'll need to really do it. To find out if you are running on a DEVFS system, look for existence of the sysctl variable "vfs.devfs.generation" -- 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