Re: [Thinstation-developer] packages and modules

[Roger O. <ro...@op...>]

On Fri, 2006-01-13 at 10:35 +0100, Roger Oberholtzer wrote:
> I have added a few kernel modules to thinstation to support sata disks.
> I copied the additional modules to the kernel package directory. Then I
> made a file in the kernel/dependencies_package directory that listed the
> modules I wanted. I then added it as a package in my build.conf. The
> modules are happily now in the image.
> 
> However, the modules are not actually loaded. What is the best way to
> get the modules loaded? I can of course use a script. But what is the
> way the other modules actually get loaded?
> 
> I took the package approach as I may add other things. Otherwise, might
> I have gottne the same results if I had simple refered to the various
> modules directly in my build.conf?

OK. I see that if I use a module statement in build.conf, the module is
actually loaded. If I use the kernel/dependencies_package, the module in
included in the image, but not loaded.

But what about this:

If I load sd_mod via 'module sd_mod' in my build.conf, the module is
indeed loaded and the SATA disks properly located and entries are made
in /dev. However, none of the udev stuff seems to be done. If, however,
I load sd_mod after the system boots (say via a telnet session), the
udev calls for each disk are made.

Could this be because the udev stuff is not complete yet is the modules
are loaded at boot? This would be a broken setup, IMHO. I am a bit
confused at why there would be a difference.

-- 
Roger Oberholtzer
OPQ Systems AB