Re: different configs for 386 and 686 kernel
On Mon, Jan 06, 2003 at 09:58:24AM -0600, Chad Walstrom wrote:
> "H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote:
> > Umm... isn't this a bug?? AFAIK, a kernel with ext2 compiled as a
> > module won't be able to boot on an ext2 system.
>
> IIRC, the Debian kernel supports initrd images by default. The
> initrd-tools examines the filesystems mounted and modules loaded by a
> running kernel and creates it's initrd image from that reference. i.e.
> When you install 2.4.19-xx kernels, it forces you to install
> initrd-tools, ash, and cramfs tools.
Ah, I see.
> This may not be your preferred way of doing things, but it allows the
> installation team to concentrate on delivering small-footprint kernels
> that support a wide variety of hardware through modules, including the
> ext2 filesystem support. Not everyone wants ext2 systems.
Preferred or not, my current kernel comes from an analogous configuration
I had way back in the 2.0.x days when I first starting using Linux.
> Personally, I don't use the upstream Debian kernels because of module
> problems with my network cards. Some prefer not to use module-enable
> kernels for security reasons, but that's what 'kernel-package' is for.
> ;-)
Yep, I've been using kernel-package all these years. Probably why I never
clued in to how useful initrd images can be. (Most of the time, I just
download a new kernel, configure it almost the same as before, and off I
go. Never did bother to add new stuff to it.) :-)
T
--
Why do conspiracy theories always come from the same people??
Reply to: