[ILUG] Re: etch and kernel modules

[martin f krafft]

also sprach Niall O Broin <niall at magicgoeshere.com> [2006.11.22.0848 +1100]:
> >Well, Debian switched to initramfs since 2.6.12 or so. Initramfs
> >is a joint development by the Ubuntu and Debian folks and it's
> >just a gzipped cpio file; that's a lot easier to deal with than
> >cramfs.
> 
> Yes, it's a little easier to deal with, though I guess most
> distros now have cramfs in the kernel. At boot time, where do the
> files in an  initram fs file GO?

As you postulated correctly: a tmpfs.

> psmouse uhci_hcd ehci_hcd pcspkr parport_pc parport shpchp
> pci_hotplug
> 
> These are all for hardware features which I simply don't ever
> intend to use on a server in a data centre - all these modules can
> be unloaded.
>
> floppy usbcore
> 
> These are also for hardware features which I simply don't ever intend
> to use on a server in a data centre but these modules can't be unloaded.
> An attempt to rmmod them results in a hanging unkillable process.

Add lines like

  install psmouse /bin/true

to /etc/modprobe.d/local-disabled-modules to blacklist them. Then
remake the initramfs. I suggest to keep a backup in case the boot
does not work, then you can always use grub to load the backed up
initramfs.

> dm_snapshot dm_mirror
> 
> These are device mapper modules that I won't use.

Ditto, if you're sure you won't need them.

> raid10 raid0 raid456 xor
> 
> I use RAID1 on this box - I have no need for all these modules.
> And prior to 2.6.18 it was worse, as raid[456] were separate
> modules.

I am curious why raid456 and raid10 get loaded. Could you post your
initramfs somewhere for me to download?



also sprach Cian Davis <davisc at skynet.ie> [2006.11.22.0911 +1100]:
> >> (I am working on a new edition, but it's going to take
> >> substantially longer than etch itself).
> >
> > That's the problem with a comprehensive reference work on such
> > a fast moving subject, isn't it - getting it out before it's
> > obsolete.
> 
> Well, with Debian you'd have a pretty good chance of getting it
> out before the next release ;-)

Old habits die hard, huh? If you didn't notice, then we're close to
releasing etch 18 months after sarge. It took me a year to write the
book for sarge, which took 3 years to complete. A *lot* changed
between sarge and etch. It pains me that I cannot release an updated
edition with etch, but it's just not economically feasible, and
I did spend most of the time since sarge with severe health
problems, not unrelated to typing for many hours every day for 12
months in a row.

But a new edition will follow. Whether for etch or lenny (etch+1),
I am not sure yet.

Please keep me on Cc.

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net at madduck
 
"no woman should ever be quite accurate about her age.
 it looks so calculating."
                                                        -- oscar wilde