Re: setting up an encrypted filesystem..

[Digby Tarvin <digbyt@acm.org>]

On Thu, Apr 27, 2006 at 12:12:32PM +0200, Jochen Schulz wrote:
> Digby Tarvin:
> > 
> > However it seems that I need to add an entry to /etc/modprobe.d in
> > order to get the device mapper module loaded. Or should it be
> > /etc/modules.conf or /etc/modules that I edit?
> 
> Modules which you want to load at boot have to be named in /etc/modules
> (one module name er line).

Ok, that worked - thanks!

However it leads me on to another related question..

After the install (Etch, netinstall) the /etc/modules file
contained the following:
  # /etc/modules: kernel modules to load at boot time.
  #
  # This file contains the names of kernel modules that should be loaded
  # at boot time, one per line. Lines beginning with "#" are ignored.
  
  ide-cd.load
  ide-disk.load
  ide-generic.load
  psmouse.load
  sbp2.load

But I have no idea why the '.load' suffixes - and it would appear
that the system doesn't know either, because all it does is produce
a series of 'FATAL' messages on the console during boot...

Does anyone know of a reason for this? Or is this something that should
go into a bug report to the install people?

> > Is this expected behavior - should I not have expected that
> > installing cryptosetup to have done this? 
>
> Don't know. Generally, every module should be loaded automatically with
> recent kernels. There may be exceptions.

I think its fairly recent (2.6.15-1-686).

Regards,
DigbyT
-- 
Digby R. S. Tarvin                                          digbyt(at)digbyt.com
http://www.digbyt.com