On Sun, 2002-12-29 at 13:18, Rob Weir wrote: > On Sat, Dec 28, 2002 at 11:33:10AM -0800, Bill Moseley wrote: > > On Sat, 28 Dec 2002, Bob Proulx wrote: > > > In /etc/lilo.conf place the following: > > > > > > append="hdc=ide-scsi hdd=ide-scsi" > > > > Now this confuses me. I assumed that if the ide-scsi was built as a > > module you would use options in the /etc/modutils setup to pass in the > > options when loading the module. I thought the append= line in lilo.conf > > was to pass in settings to compiled in code. Is that a wrong assumption? > > Otherwise the ide-cd system will grab the drives. If it's compiled in, > there's no way to get your CD drive back without a reboot. > > > Another question: I have everything compiled into the kernel instead of > > as modules. I have two IDE drives and I'm *not* using the append line, > > yet the drives are still setup correctly as SCSI. > > > > Why don't I need the append= line? > > AIUI, if you have ide-cd and ide-scsi (and sr_mod) compiled into the > kernel, ide-scsi will win and take everything. I compile all the > ide-scsi (and scsi) stuff as modules, because it's possible to play with > them without a reboot. > > -rob
I have two CDs on this machine on my secondary ide bus (CD-RW, and CD-ROM), with both ide-cd and ide-scsi compiled into the kernel, and ide-scsi doesn't pick up anything unless I specifically tell it to at boot time. Other than a few interesting vfs drivers I stumble across at SourceForge, I tend to stick to compiling into the kernel unless I know I may want to disable something (like my cheap camera that wants V4L for GnomeMeeting, but libusb access for GPhoto2,) but that is just my silly habits since I first got custom boot disks confused between two machines and got a spew of missing module messages and a kernel panic. -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
