From owner-freebsd-current Mon Aug 21 12:20:20 2000 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 3D3C537B7F3 for ; Mon, 21 Aug 2000 12:20:13 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA94117; Mon, 21 Aug 2000 21:19:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: PATCH: devfs mkIII test & review please. In-Reply-To: Your message of "Mon, 21 Aug 2000 11:15:45 +0200." <21077.966849345@axl.fw.uunet.co.za> Date: Mon, 21 Aug 2000 21:19:53 +0200 Message-ID: <94115.966885593@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <21077.966849345@axl.fw.uunet.co.za>, Sheldon Hearn writes: > > >On Sat, 19 Aug 2000 21:26:24 +0200, Poul-Henning Kamp wrote: > >> Ahh, right, this is something else than I thought: These are >> symlinks in the normal case, for instance: >> >> /dev/audio -> /dev/audio0 > >What's the plan for things like these? Are we going to take the soft >option and teach /etc/rc to create symlinks for device nodes found on >startup and require folks to make the rest themselves? Or can this be >handled gracefully in the kernel? DEVFS supports symlinks. Symlinks can be made from userland with the normal "ln -s" They can also be made by the driver using make_dev_alias(). Who makes the symlinks and when should be decided by the driver writer. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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