AY in 9.1: List of bugs and feature requests
Hi Anas,
I give up with SuSE 9.1 because it seems to contain too many
bugs (including bugs in the installation process with yast,
which are not AY related (like system users not being created,
systems crashing when loading modules for non-existent
hardware etc.). It seems that neither the 2.6.5. kernel nor
the coldplug system are stable yet... I will try again with SuSE 9.2
Anyway, here's a list of bugs I found in AY 9.1 which perhaps can
be fixed before the release of 9.2.
And a feature request list :-)
This is just a concise summary of the things I wrote about
on the list in some other mails.
Bugs:
=====
- AY automatically adds scsi controller modules for initrd in
/etc/sysconfig/modules but fails to add the scsi_mod module
first. Even if one adds the scsi_mod via the profile, the controller
modules will be inserted first. Thus, the system will not be able to
boot from a scsi disk
- matching for "hostname" in rules.xml will not match the hostname but
the IP. The variable "hostname" in the AY environment contains the IP.
- chroot scripts can not be loaded with <location>nfs://</location>
since AY will mount the location on /mnt, where the just installed
system is already mountet, thus failing to copy the chroot scripts
into the installed system.
- profile.dtd does not include sysconfig.dtd
- bootloader.dtd is missing the kernel_parameters element
Feature wish-List:
==================
- chroot scripts should be executed as last thing, *after* the bootloader
config is written, so that it is e.g. possible to tweak the lilo.conf
just before rebooting.
- allow "<match>*</match>" to match against anything,
or let AY take a missing match as "always succeed" so that
one can e.g. just write
<rule>
<hostaddress>
</hostaddress>
<result>
<profile>@hostaddress@.xml</profile>
</result>
</rule>
to add a specific profile for every host with a single rule.
- allow to use variables via @ in the result part of a rule
when they were set in a custom script, i.e., allow
<rule>
<custom1>
<script>
<![CDATA[
#!/bin/sh
export myhostname=`grep HOSTNAME /var/lib/dhcpcd/dhcpcd-eth0.info | sed 's/HOSTNAME=//g'`
echo -n undefined
]]>
</script>
<match>undefined</match>
Hi, Frank Steiner wrote:
Hi Anas,
Feature wish-List: ================== - chroot scripts should be executed as last thing, *after* the bootloader config is written, so that it is e.g. possible to tweak the lilo.conf just before rebooting.
This is already possible: http://www.suse.de/~nashif/autoinstall/9.1/html/createprofile.scripts.html <snip> It is also possible to run the chroot scripts in the installed system by adding the boolean element chrooted. </snip> Anas
Best regards, Frank
Hi, Anas Nashif wrote:
Feature wish-List: ================== - chroot scripts should be executed as last thing, *after* the bootloader config is written, so that it is e.g. possible to tweak the lilo.conf just before rebooting.
This is already possible:
http://www.suse.de/~nashif/autoinstall/9.1/html/createprofile.scripts.html
<snip> It is also possible to run the chroot scripts in the installed system by adding the boolean element chrooted. </snip>
I might misunderstand that, but I though this is just the difference if I run the script in / or in chrooted /mnt? The web page says "Chroot scripts are executed ... and *before the boot loader is installed." Do you mean that the chroot flag changes that, i.e., the scripts with the "chrooted" flag are executed after the boot loader was installed? That's what I need so that I can patch the lilo.conf manually before rebooting. I will try with the chrooted flag to see if it makes the difference! cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
participants (2)
-
Anas Nashif
-
Frank Steiner