From owner-freebsd-hackers Sat Apr 22 00:36:41 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA12260 for hackers-outgoing; Sat, 22 Apr 1995 00:36:41 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA12252 for ; Sat, 22 Apr 1995 00:36:36 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA01174; Sat, 22 Apr 1995 00:33:56 -0700 From: "Rodney W. Grimes" Message-Id: <199504220733.AAA01174@gndrsh.aac.dev.com> Subject: Re: More devfs stuff To: pritc003@maroon.tc.umn.edu (Mike Pritchard) Date: Sat, 22 Apr 1995 00:33:55 -0700 (PDT) Cc: hackers@FreeBSD.org In-Reply-To: <199504220716.CAA01395@mpp.com> from "Mike Pritchard" at Apr 22, 95 02:16:33 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 914 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... Then do it really right, and don't use leading zero's to imply an upper limit. Look at the current /dev/fd, it works just fine and has no upper bounds (well, okay the minor is still a limit at what, 24 bits??). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD