Re: Why no "initrd" for Debian?
From: Andreas Janssen (andreas.janssen_at_bigfoot.com)
Date: 09/10/04
- Previous message: Marcos Carneiro da Rocha: "Re: CPU and Other Information ?"
- In reply to: Eric Dickner: "Why no "initrd" for Debian?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: debian-user@lists.debian.org Date: Fri, 10 Sep 2004 17:06:01 +0200
Hello
Eric Dickner (<ejdickner@yahoo.com>) wrote:
> [compiling kernel]
> Do I need to get some kind of mkinitrd and get that
> into lilo.conf? Is this one of those areas where
> debian diverges from other linuces?
You only need an initrd if you want to compile support to access the
root file system as modules.
This very likely are the IDE hard disk drivers and support for the file
system on your root partition. If the drivers are compiled into the
kernel instead of as modules, you don't need an initrd. Obviously
you /can/ boot your system with the kernel you created, which means
that the drivers /have/ been compiled into the kernel, so everything is
fine.
If you have problems with other components (floppy, cdrom), make sure
the drivers are there, and - if compiled as modules - are loaded.
best regards
Andreas Janssen
-- Andreas Janssen <andreas.janssen@bigfoot.com> PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Marcos Carneiro da Rocha: "Re: CPU and Other Information ?"
- In reply to: Eric Dickner: "Why no "initrd" for Debian?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]