Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Helmut@Hullen.de (Helmut Hullen)
Newsgroups: alt.os.linux.slackware,comp.os.linux.misc
Subject: Re: why must initrd 'track' vmlinuz ?
Date: 03 Apr 2011 17:15:00 +0200
Organization: Hullen BS
Lines: 23
Message-ID: <Bj8mn+ei1uB@helmut.hullen.de>
References: <in9tpo$cns$1@dont-email.me> <ina2ct$tuh$1@news.xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Trace: individual.net 70DZ4v2gtQbfrPWDrEot5QrNcwyTew7JUiD+BX3asqoFUBfHZ5
Cancel-Lock: sha1:9F0QxelCA6q5skpeE3EICQB0DE4=
User-Agent: OpenXP/4.10.7372 (Win32) (i386)
Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:585

Hallo, Douglas,

Du meintest am 03.04.11:

>> OK, perhaps the initrd & vmlinuz must be 'created together' since
>> the driver routines don't have standard locations .. and initrd must
>> be 'linked' to vmlinuz ?

[...]

> The "modular" kernel requires an initrd.

No - "that depends".

You can build a kernel with some "built in" modules for booting into  
runlevel 1, and all the modules only needed in higher runlevels (6  
excluded) can be loaded without the help of an init-ramdisk.

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".