Am Fre, 2002-08-09 um 15.20 schrieb Anas Nashif:

* bernd.ronecker@t-online.de <bernd.ronecker@t-online.de> [Aug 08. 2002 11:24]:

...

Hi,

I need to resize my ramdisk blocksize in order to boot the new installed linux. In the xml file under <bootloader>you can add <kernel_parameters>value</kernel_parameters>. For "value" I use: ramdisk_blocksize=1024 which works fine at the lilo prompt. Which further depencies are there or what kind of sysntax should I use for the kernel parameters tag? For any hints I would be happy,

syntax is free text, i.e <kernel_parameters>key=value key=value</kernel_parameters>

Anas

...

Thanx Bernd

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada

Well, that what I've done. But it doesn't work. I found out, that the lilo.conf of the new installed system contains a value: append = " ramdisk_blocksize=4096 .... ". Why did YAST2 do this entry? The syslinux.cfg on my bootdisk contains this value as well. I did this because I couldn't get cramfs to work with a ramdisk blocksize of 1024 so I had to make my initrd with a blocksize of 4096. This all works pretty well until the new installed system boots.The ramdisk value is wrong and "Kernel Panic" appears unless I use my kernel parameter at the lilo prompt: ramdisk_blocksize=1024 . How Can I get that append line out of that lilo.conf without doing anything manually :-). Regards, Bernd