on Friday 08 January 2010 Stephen Dowdy wrote:
The first rule is an unconditional match on product (could be anything) to fake the equivalent of "#include <FOO.xml>" (i'm not sure if i can, or it's advisable to use a "<class>" here instead?)
a "matching always" rule is fine for that. You could put a class into the other XML snippets that pulls in the FOO.xml but I don't see a benefit in that.
I am initially testing this on a USB Key i built using 'mksusebootdisk'.
My understanding is that if i placed this rules file on the USB key's VFAT filesystem as '/cf/rules/rules.xml' and boot with:
linux autoyast=usb:///cf/ ZORKsite=site1 ZORKnode=ingest
The idea is correct but there is a problem because your installation source is on the the USB device. Autoyast tries to mount that device then and this fails because it's already mounted as readonly from the resolver (at least that would happen on SLES11 and IIRC it's the same on SLES10 SP3). Your /cf/ directory is on the installation source so you can use a fallback: autoyast=file:///cf/ As an alternative you can create a second partition on the USB stick that only contains the /cf/ directory. Then autoyast=usb:///cf/ works too. On openSUSE 11.3 and SLES11 SP1 that's fixed BTW.
I.E. is what i'm trying to do a correct and/or advisable way to use a rules file to parse the command line as the primary means of pulling the rest of the configurations into play?
yes, that's fine.
Secondarily, i wanted to test this stuff out using a virtual machine, but the virtual machine manager wants to be TOO helpful. Apparently, it will accept an "AutoYast" statement that can ONLY be a single profile file. (autoinst.xml), not a directory, therefore no rules can be run. What i tried, instead, was to create an ext2 disk image containing my autoyast setup, and put "autoyast=device:xvdc/cf" into the kernel line. Only the VM creation wizard sees the "autoyast" directive, pulls it from the kernel line, and then tries to handle it itself in the same way, and fails.
Is there a method of doing what i want using the standard SLES10 XEN virtual machine management functions so i can test this setup without having to venture down to the machine room with USB key in hand to find that something's still wrong?
Sorry, I'm not experienced with XEN. I use virtual box to test my autoyast stuff. But "device:xvdc/cf" is wrong anyway. Must be "device://xvdc/cf/"
Also, does the install "shell" support POSIX 'printf' instead of 'echo -n'?
yes it does -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org