From owner-freebsd-hackers Wed Apr 19 01:37:32 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12221 for hackers-outgoing; Wed, 19 Apr 1995 01:37:32 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA12213 for ; Wed, 19 Apr 1995 01:37:23 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA28041; Wed, 19 Apr 1995 18:30:55 +1000 Date: Wed, 19 Apr 1995 18:30:55 +1000 From: Bruce Evans Message-Id: <199504190830.SAA28041@godzilla.zeta.org.au> To: julian@ref.tfs.com, rgrimes@gndrsh.aac.dev.com Subject: Re: [DEVFS] your opinions sought! Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >I take it that you mean flat vs hierarchial. How about both :-) :: >mount -t devfs -o flat /dev >mount -t devfs -o hier /dev Programs should use canonical names so the user can't decide everything here. >I personally have always prefered the flat scheme of /dev (with possible >exceptions for /dev/fd/*). This is a religious issue, I have spoken my >religion. I like it fairly flat. There certainly shouldn't be subdirectories for pieces of one device. >> The naming is not implimented yet because it would be the >> responsibility of the SLICE code to do the naming.. the DEVFS doesn't care.. >> it just shows what it's told to show by the device driver (or the slice >> code in this case). /dev/driver_name/all_devices_handled_by_this_drive_in_one_directory is easiest for drivers, but not quite what is wanted by programs. How should ps find and name tty devices? There aren't enough letters for a 2 letter namespace. Bruce