Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] More scsi modules (Was: 0.9.5-test2 is out)

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: Karsten Behrmann <BearPerson AT gmx.net>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] More scsi modules (Was: 0.9.5-test2 is out)
  • Date: Sat, 24 Sep 2005 13:02:28 -0700 (PDT)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 24 Sep 2005, Karsten Behrmann wrote:
On Sat, 24 Sep 2005 12:25:15 -0700 (PDT), Eric Sandall wrote:
On Sat, 24 Sep 2005, Karsten Behrmann wrote:
<snip>
Sure, here's what we can do:

1. Put modules on the initrd
=> All I need is the directory they are in, and I can put them in

Doesn't the initrd menu just list the module directories available in
/lib/modules/`uname -r`/kernel/drivers or you have to manually add
those directories?

The initrd just lists those modules, but we aren't putting the entire
directory on the initrd (I don't see why anyone would want to start
sound from the initrd, for example). The list of dirs to include
on the initrd has to be edited manually.

Perhaps it'd be easier/faster to have an exludes list (e.g. sound,
alsa) and list the rest via a script?

4. Use hotplug
=> We already have hotplug on the ISO, we just need to install its init
script too (by default no initscripts are installed to the ISO itself)

I'd prefer this 'automagic' method. :)

Okay. I have one thing we may want to consider:
In rare cases, loading a certain module causes Bad Things to happen on
certain machines. ACPI comes to mind.

Instead of relying on kernel parameters to work around these, I'd suggest
adding a "disable hotplug" menu button on the initrd that triggers a
removal of the hotplug init script on booting through. We can make it
a bistate option that switches between disable and enable.

That could work as well.

The last two solutions do not work if the modules might be needed for
the cdrom; if the cdrom is on a scsi disk needing those drivers.

Correct, those should be built-in, IMO.

Is this critical for 0.9.5?

It should already be fixed, I thought. "Critical" devices (harddisks,
CD-ROMs, USB (for keyboard support, at least)) should be built-in.

So Far,
Karsten

- -sandalle

- --
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDNbDYHXt9dKjv3WERAi1qAKC1Ta/ppQSXU/4Ka81ay4VrkTVxggCgwn/H
55oTIyBvaBC6adJJSLH6rqc=
=H0nG
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.24.

Top of Page