From owner-freebsd-current Fri Apr 14 16:34:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id ED22537BF5A for ; Fri, 14 Apr 2000 16:34:27 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id SAA21562; Fri, 14 Apr 2000 18:34:13 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 14 Apr 2000 18:34:13 -0500 (CDT) From: David Scheidt To: Peter Jeremy Cc: Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: Problems with MAKEDEV. In-Reply-To: <00Apr15.092900est.115218@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Apr 2000, Peter Jeremy wrote: > On 2000-Apr-14 22:49:40 +1000, Steve Ames wrote: > >That's always struck me a bit odd... I thought 'MAKEDEV std' made > >the generic set of devices and that 'MAKEDEV all' should make... well.. > >_ALL_. *shrug* > > What do you define as `all'? Say I have a big FTP server with 8 wide > SCSI controllers, each with 15 disks - that's da0..da119. I might > have a big shell (or similar) server that needs a few thousand PTYs. > I could have all sorts of other wierd hardware. "MAKEDEV all" has to > draw the line somewhere. Sure. What's the point of having both std and all, though? How much does it hurt to have a few extra device files kicking around? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message