To log boot events:
echo 'BOOTLOGD_ENABLE=Yes' > /etc/default/bootlogd sed --in-place 's/BOOTLOGD_ENABLE=No/BOOTLOGD_ENABLE=Yes/' /etc/default/bootlogd sed -i 's/BOOTLOGD_ENABLE=No/BOOTLOGD_ENABLE=Yes/' /etc/default/bootlogd perl -i -pe 's/BOOTLOGD_ENABLE=No/BOOTLOGD_ENABLE=Yes/' /etc/default/bootlogd
But there are some bad consequences of this action. See the BTS but they include logging single user mode keyboard sessions, not working with udev, etc.
The 'powermgmt-base' package is needed in order to have a system automatically power down when the reboot halt command is issued. Also, you need to have 'apm' loaded into the kernel.
apt-get install powermgmt-base
echo apm >> /etc/modules
The 8139too driver is loaded as a module only in the 2.4.18-k6 kernel. The 8139too driver was included in the 2.4.18-bf24 kernel. What this means is that if you had a DFE-530TX+ network card in your machine to do the original installation then everything just worked. But then when you updated to the k6 optimized kernel the networking stopped working. At that time you have to include 8139too in /etc/modules so that it will get loaded on boot. But you can't include it before with the bf24 kernel since it is not a module there. Also the modconf program knows nothing about the 8139too and therefore trying to use modconf to configure this driver is futile.
Donald Becker wrote the original Realtek driver along with many other network drivers for use in beowulf clusters. Somewhere along the way Jeff Garzik jgarzik@mandrakesoft.com forked the code. It is Jeff's code that is included in the Linux kernel source by default. However you can use Donald's code instead.
grep-dctrl allows bash completion for dpkg-reconfigure to work.
http://lists.debian.org/debian-user/2002/debian-user-200208/msg02808.html
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html