Uwe, Thanks for responding... Uwe Gansert wrote, On 01/11/2010 02:06 AM:
on Friday 08 January 2010 Stephen Dowdy wrote: ... 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.
Oops, my fault. I had an extraneous "_" in a file name that i'd renamed (e.g. the rule was pulling in ZORK_base.xml, and i'd renamed the file ZORKbase.xml). AFAICT, using the <rule> bit for unconditional inclusion is more desireable than putting in <class> stuff in each potential conditionally included profile bit. I just presume that "rules.xml" can't have any "class" directives in it, so using the wildcard match is "the way to go?"
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.
It does work, but i have to diddle it a bit. It initially fails with something like "Make sure install media is in Disk 1" (can't recall exactly.). All i have to do is hit "[BACK]", then proceed through the selection for Language and Keyboard, then "Setup or Install System", then select "Hard Disk" and then the partition for the USB key, then it works fine. But from what i'm reading, "file:///cf/" should "just work" as expected? I'll give that a try. Thanks for the tip on the secondary partition, that's useful to know.
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/"
I think i just mistyped, but the SLES XEN virtual machine manager still tries to "help" too much and keeps me from being able to specify the autoyast stuff. I guess i'll give up on that for now. If i find time later, i'll check out virtualbox.
Also, does the install "shell" support POSIX 'printf' instead of 'echo -n'? yes it does Great.
I'm now at the next problem, but i'll post a new thread to keep this from getting too complicated. --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy@ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org