From owner-freebsd-hackers Sat Apr 22 00:17:30 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA12093 for hackers-outgoing; Sat, 22 Apr 1995 00:17:30 -0700 Received: from mpp.com (dialup-5-137.gw.umn.edu [128.101.96.137]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA12081 for ; Sat, 22 Apr 1995 00:17:14 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id CAA01395 for hackers@freebsd.org; Sat, 22 Apr 1995 02:16:33 -0500 From: Mike Pritchard Message-Id: <199504220716.CAA01395@mpp.com> Subject: More devfs stuff To: hackers@FreeBSD.org Date: Sat, 22 Apr 1995 02:16:33 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 634 Sender: hackers-owner@FreeBSD.org Precedence: bulk Before I forget, it seems like people are leaning towards the /dev/xxx/zzz style for the DEVFS project. I've seen quite a few examples that list /dev/pty/00 as the format they want (for example). Please, lets save us a lot of trouble down the road and make it /dev/pty/000. I've been through one conversion that went from a 64 to a 256+ limit in this area, and I would not like to do it again. Heck, even /dev/pty/0000 isn't even really out of line these days. Repeat after me: future expansion, future expansion... -- Mike Pritchard pritc003@maroon.tc.umn.edu "Go that way. Really fast. If something gets in your way, turn"