Mailinglist Archive: opensuse-autoinstall (124 mails)

[Brian Corriveau <bcorriveau@xxxxxxxx>]

On Wednesday 08 December 2004 11:29 pm, Frank Steiner wrote:

> That's actually what we do.  The important thing is just to remove
> the "INITRD_MODULES" line in /etc/sysconfig/kernel in a post script
> before AY writes the bootloader config. Because then AY will detect
> it does not need any initrd modules and not create an initrd.

I tried putting in a chroot postscript that runs before the bootloader is 
written, but the autoinstaller still seems to insist on writing out an 
initrd. In fact it has a nasty habit of locking up without any error messages 
when writing out the "boot manager" from time to time. My kernel boots and 
runs fine without an initrd so you can imagine this doesn't make me very 
happy to see that part mess up the install. The postscript puts a # in front 
of the INITRD_MODULES. When I log at the setup.log I can set that the post 
script ran and put the # in because I cat the file after modifying it. What 
is really strange is that the /etc/sysconfig/kernel in the installed system 
the line is uncommented and has a module in it. Is there something else I 
need to do to not build an initrd?

# cat setup.log
+ perl -pi -e s/INITRD_MODULES/#INITRD_MODULES/ /etc/sysconfig/kernel
+ head /etc/sysconfig/kernel
## Path:        System/Kernel
## Description:
## Type:        string
## Command:     /sbin/mkinitrd
#
# This variable contains the list of modules to be added to the initial
# ramdisk by calling the script "mk_initrd"
# (like drivers for scsi-controllers, for lvm or reiserfs)
#
#INITRD_MODULES=""
...

thanks
Brian