On Tue, Jan 03, 2006 at 02:45:26PM -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in module
On Tue, Jan 03, 2006 at 02:45:26PM -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in module
John Hasler wrote:
Joey Hess writes:
This assumes a best case scenario that you will never need to get some
new peice of hardware working at a time when taking the time out to set
up a new kernel will be painful.
You seem to be equating initrd to modular kernel. I have the drivers for
my
Joey Hess writes:
> This assumes a best case scenario that you will never need to get some
> new peice of hardware working at a time when taking the time out to set
> up a new kernel will be painful.
You seem to be equating initrd to modular kernel. I have the drivers for
my present hardware comp
On Tue, 2006-01-03 at 14:45 -0500, Joey Hess wrote:
> J.F. Gratton wrote:
> > - I know my hardware, it's unlikely to change in a near-future; a new
> > kernel is more likely to come out thant my hardware to change; why using
> > an initrd then if I know exactly what needs to be put in modules and
>
J.F. Gratton wrote:
> - I know my hardware, it's unlikely to change in a near-future; a new
> kernel is more likely to come out thant my hardware to change; why using
> an initrd then if I know exactly what needs to be put in modules and
> must not ?
This assumes a best case scenario that you will
On Tue, 2006-01-03 at 10:09 -0800, Andrew Sackville-West wrote:
>
> J.F. Gratton wrote:
> > solved, but not at my full satisfaction...
> >
> > I compiled the kernel with initrd support and it went fine, using a
> > 2.6.12-10 config file.
> >
> > I therefore voided one of the main gain I wanted b
On Sat, 12 Oct 2002 08:06, Brian Nelson wrote:
> bob parker <[EMAIL PROTECTED]> writes:
> > 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
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
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 )
if scsi is built into the kernel, you wont need initrd ??
most people compile the ide drivers into their kernel
initrd i
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 modu
11 matches
Mail list logo
