Hi, On Sun, 20 Aug 2006 16:07:41 +0200 [EMAIL PROTECTED] wrote: > Since long I have two questions, and this is the first one: > > I see initrd kernels all around, and i can imagine the benefits > for 'hijacking' systems (like installers) which need to discover the > hardware first to select the appropriate kernel modules and settings. > > But when i'm going to configure a custom kernel, on known hardware, > why should i use initrd at all ? I mean, what is the advantage of > initrd over non-initrd in this case ? Really, any argument ?
There is just none. If you have a customized kernel, you do not need an initrd. The Debian kernels have to boot on many different machines, they need an initrd. You have one machine and a kernel configured for this one. It's okay than. Regards Evgeni -- ^^^ | Evgeni -SargentD- Golov ([EMAIL PROTECTED]) d(O_o)b | PGP-Key-ID: 0xAC15B50C >-|-< | WWW: http://www.die-welt.net ICQ: 54116744 / \ | IRC: #sod @ irc.german-freakz.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
