From owner-freebsd-hackers  Wed Apr 19 20:04:42 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA11729
          for hackers-outgoing; Wed, 19 Apr 1995 20:04:42 -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 UAA11704
          for <hackers@FreeBSD.org>; Wed, 19 Apr 1995 20:04:30 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA31880; Thu, 20 Apr 1995 13:02:14 +1000
Date: Thu, 20 Apr 1995 13:02:14 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504200302.NAA31880@godzilla.zeta.org.au>
To: bde@zeta.org.au, peter@bonkers.taronga.com
Subject: Re: [DEVFS] your opinions sought!
Cc: hackers@FreeBSD.org, julian@ref.tfs.com, rgrimes@gndrsh.aac.dev.com
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>> /dev/driver_name/all_devices_handled_by_this_drive_in_one_directory  is
>> easiest for drivers, but not quite what is wanted by programs.

>Why not?

To handle /dev/sio/*, /dev/cx/*, /dev/ity/* and /dev/cy/*, ps would have
to know that the set of tty drivers is precisely { sio, cx, ity, cy }.

>> How
>> should ps find and name tty devices?  There aren't enough letters for a
>> 2 letter namespace.

>Two solutions....

>Give up the 2 letter namespace?

Yes, someday.

>Symlink /dev/ttyxx to /devices/whatever?

No.  Then whatever does the symlinks would have to know which tty drivers
are configured, and /dev would end up twice as messy as now.

Bruce