"Not necessary to have it start immediately?" How does that work? I'm quite sure you could know something I don't, but I have only ever seen ide-scsi started from the boot loader. I have never seen it in modules.conf, for example. If the drive isn't to be mapped scsi right away, are you suggesting it can start mapped ide and be switched to scsi somewhere after booting? That's a pretty radical suggestion, imho. But, let's take this back to the original point. If ide-scsi can be modular, and started from the boot loader, why not Speakup? That was the original point, after all. Lorenzo Prince writes: > From: Lorenzo Prince <lorenzo at princenet.sytes.net> > > I believe it is loaded after all the drives are detected and it knows > where the ide ports are and which one has the CDRW drive. This can be > compiled as a module, but it isn't necessary to have it start immediately. > It can start at any time before the CDRW drive is used for writing. > Basically, my point was that a module has to be loaded either from a > script, from the command line, or in /etc/modules.conf using the module > loader. Even if run from the /etc/rc.d/rc.S script, a module won't be > loaded before any text is printed to the screen. This is why I thought, > in the case of a modularized speakup, that it would probably still be > necessary to patch the kernel itself to cause it to buffer console output > until the Speakup module is actually loaded, as someone mentioned in an > earlier post on this thread. > > Lorenzo -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175
