Debian did not use initrd per default with 2.2.x. Was it possible ? Actually you cannot define a default boot configuration with aboot.conf. You just define several boot scenarios, identified by the first number in the line: 0, 1, 2 etc. You choose a specific scenario at the SRM console:
boot dka0 -flags 0 or boot dka0 -flags 1 or boot dka0 -flags l The flags are passed over to aboot. So "-flags l" will let aboot display the configured scenarios and give you a command line. Ionut On Tue, Jul 15, 2003 at 01:28:13PM +0200, [EMAIL PROTECTED] wrote: > > You have to pass the path to the initrd image. aboot.conf here: > > ok, I think I'm understanding the boot process more now. Just in case, I > want to make a second boot configuration with the old kernel. While I have > vmlinuz-2.2.20-generic in /boot, I can't find any initrd but the new ones. > Did 2.2.20 not use an initrd? Or did it get deleted while installing the new > kernel-image? > Another question is, how can I select another boot-configuration at boot > time? I configured aboot to automatically boot vmlinuz... > > Lars > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- *************** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you * can do anything the computer is able to do."