> the basic rule of thumb is: "if i'm likely to need it to boot or if it's
> essential for what the machine is supposed to do, then it gets compiled
in to
> the kernel. otherwise as a module".
>
> craig
Agree completely. In or case, we also compile in the 3ware RAID stuff, a
few common NIC drive
On Thu, Sep 30, 2004 at 12:12:30AM +1000, Donovan Baarda wrote:
> > Le mercredi 29 septembre 2004 ? 12:37, Gavin Hamill ?crivait:
> > > My question is... how does dpkg know that I need to load the megaraid
> > > module in the initrd so the system can mount / for init to boot the
> > > machine? I've
G'day,
From: "Aurélien Beaujean" <[EMAIL PROTECTED]>
[...]
> Le mercredi 29 septembre 2004 à 12:37, Gavin Hamill écrivait:
> > My question is... how does dpkg know that I need to load the megaraid
> > module in the initrd so the system can mount / for init to boot the
> > machine? I've looked in /
On Wednesday 29 September 2004 13:38, Aurélien Beaujean wrote:
> Hi,
> The only way to have mageraid at boot time is to include it in builtin
> (not in module) in the kernel. So rebuild a 2.4.27 with the same custom
> options than your old 2.4.21.
That's interesting..
Since I wrote, I did some m
Hi,
Le mercredi 29 septembre 2004 à 12:37, Gavin Hamill écrivait:
> My question is... how does dpkg know that I need to load the megaraid
> module in the initrd so the system can mount / for init to boot the
> machine? I've looked in /etc/mkinitrd and seen the 'modules' file -
> should I just stic
Hullo.
I've often wondered this but never been able to find a solution.. so here we
go...
I'm using a custom Debianised kernel on a Dell poweredge 1600SC with the AMI
megaraid module compiled into the kernel. Also, the kernel has no module
support
It's still running 2.4.21 and disk performan
6 matches
Mail list logo
