Re: Problems with MAKEDEV.
On Fri, Apr 14, 2000 at 11:41:55AM +0100, Ashley Penney wrote: > When booting up I noticed the block device warning message. I > did some investigation and discovered that some ad4/ad5 devices > were still block ones. It seems that the MAKEDEV script only > makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). /dev/MAKEDEV.local N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
At 18:12 -0600 14/4/00, Nate Williams wrote: >[...] >You can easily run out of inodes on the roof partition. Sure, my roof leaks from time to time. But _inodes_? :-) :-) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
> > >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? You can easily run out of inodes on the roof partition. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On Fri 2000-04-14 (18:34), David Scheidt wrote: > 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? 'std' is standard devices (leaving out exotic ones), and 'all' is at least one of every device out there. Neil -- Neil Blakey-Milner Hacker In Chief, Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On Sat, 15 Apr 2000, Peter Jeremy wrote: > On 2000-Apr-14 22:49:40 +1000, Steve Ames <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On 2000-Apr-14 22:49:40 +1000, Steve Ames <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On Fri, Apr 14, 2000 at 11:41:55AM +0100, Ashley Penney wrote: > When booting up I noticed the block device warning message. I > did some investigation and discovered that some ad4/ad5 devices > were still block ones. It seems that the MAKEDEV script only > makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). > > Simply adding ad4 ad5 onto the script fixes it, but it's not > the best fix, I feel. Nope. What you've done is to have the standard ``MAKEDEV all'' create ad4 & ad5, which isn't really what is wanted. You probably created the non-by-default ad[45] devices before MAKEDEV was converted to only make raw devices. In your case a simple ``MAKEDEV ad4 ; MAKEDEV ad5'' with a current MAKEDEV should have fixed you right up. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On Fri, Apr 14, 2000 at 08:58:29PM +1000, Peter Jeremy wrote: > On 2000-Apr-14 20:43:12 +1000, Ashley Penney <[EMAIL PROTECTED]> wrote: > > It seems that the MAKEDEV script only > >makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). > > "MAKEDEV all" is designed to create a generic set of devices that > covers most situations. It _doesn't_ cover all situations - in > particular sound devices and disk slices. You have to make those > devices manually. 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* -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On 2000-Apr-14 20:43:12 +1000, Ashley Penney <[EMAIL PROTECTED]> wrote: > It seems that the MAKEDEV script only >makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). "MAKEDEV all" is designed to create a generic set of devices that covers most situations. It _doesn't_ cover all situations - in particular sound devices and disk slices. You have to make those devices manually. In this case, I don't believe it's appropriate to automatically create ad4/ad5 because the majority of people won't have them - common hardware provides 2 IDE channels, each capable of supporting 2 devices. If you have a 3rd IDE channel, then you would have had to create the wd/ad devices manually anyway. I'd recommend "find /dev -type b -ls", or for the more paranoid "find /dev -type d -o -type c -o -type l -o -ls", followed by manual MAKEDEV or rm commands as appropriate. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
