Re: initrd or not

[bob parker <bob_parker@dodo.com.au>]

On Sat, 12 Oct 2002 05:10, Alvin Oga wrote:
> hi ya
>
> i say initrd is not generally needed ...
>
> my simplistic view...
>
> i use initrd only when i am booting a scsi system
> from a ide-based kernel  ( same as lots of distros )

I have a real scsi cdrw but I doubt that it plays any part
in the boot process.

>
> if scsi is built into the kernel, you wont need initrd ??
> most people compile the ide drivers into their kernel

Right I'll try that on my next build of the 2.4.19 kernel.
Fortunately I'm still using 2.4.18 as my production kernel
and hand editing lilo etc rather than 'make install' after
the kernel build.

> initrd is good to boot into if you need to load other
> modules in order for the system to recognize the hardware

I still have the /boot/config-2.2.20-idepci hanging around so
maybe if I diff it with the /boot/config-2.4.18-k7 it will give me
a clue about what must be compiled in.

>
> and amd-kernels are very picky about its instruction set
> that it uses vs running ix86 based kernels on amd boxes
> and vice versa  .. it supposed to be compatible but its not
> always interchangeable....
>
> c ya
> alvin

Thanks, should be done over the next day or 2

Regards
Bob


>
> On Sat, 12 Oct 2002, bob parker wrote:
> > hi Debian-users,
> >
> > I installed Woody and got the default 2.2.20-idepci kernel.
> > Later I updated that to 2.4.18-k7 kernel using apt-get.
> > Then just for fun I compiled a 2.4.19 from tarball making the
> > .config from what came  with the 2.4.18 kernel without any
> > changes. I did the make modules, make modules_install etc.
> >
> > I had to mkinitrd in order to get this new kernel to boot.
> >
> > What are the pros and cons of initrd?
> > And also, if not use it, how to configure the kernel to
> > do without it?