Date: Sat, 15 Apr 2000 09:28:55 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Steve Ames <steve@virtual-voodoo.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with MAKEDEV. Message-ID: <00Apr15.092900est.115218@border.alcanet.com.au> In-Reply-To: <20000414074858.B18551@virtual-voodoo.com>; from steve@virtual-voodoo.com on Fri, Apr 14, 2000 at 10:49:40PM %2B1000 References: <20000414114155.A61941@twilight.bastard.co.uk> <00Apr14.205835est.115320@border.alcanet.com.au> <20000414074858.B18551@virtual-voodoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2000-Apr-14 22:49:40 +1000, Steve Ames <steve@virtual-voodoo.com> 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. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00Apr15.092900est.115218>