Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!news.radio.cz!newsbastard.radio.cz!news.radio.cz!CESspool!newsgate.cistron.nl!news.iac.net!news.kudra.com!tabby.kudra.com!robert From: robert@tabby.kudra.com (Robert Sexton) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Q: Assignment of disk names. Date: 14 Mar 1997 19:34:58 GMT Organization: Kudra.Com Web Services Lines: 30 Message-ID: <5gc992$1tl$1@tabby.kudra.com> NNTP-Posting-Host: localhost.kudra.com X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37046 Greetings, I'm having a slightly wierd situation: I have two NCR host adapters, one for internal drives, and one for external drives. For the sake of predictabilty, I hardwired the devicies in my config file: controller ncr0 controller ncr1 controller scbus0 at ncr0 controller scbus1 at ncr1 device sd0 at scbus0 target 0 device sd1 at scbus0 target 1 device sd2 at scbus1 target 0 device sd3 at scbus1 target 1 The strange thing is that when I attach a disk to controller 1, ID 0, FreeBSD refers to it as sd4! Have I screwed up the config file, or simply missed something? On a related note, whats a good naming scheme for more than 10 drives? I had considered using sd00, sd01, sd02, etc for controller 0, and sd10,sd11,sd12 for controller 0, etc. Alternately, I can just let things increment, but the name->controller/drive mapiing is going to get hairy Thanks for any suggestions. -- Robert Sexton - robert@kudra.com The UN is not going to descend from the sky at night in black helicopters and steal our lawn furniture - Margaret Tutweiler, State Department Spokesperson