On Wed, Sep 26, 2007 at 10:10:21PM +0100, Yan Fitterer wrote:

I don't think so. BUT: you can create an "info" file with that information (and the autoyast parameter, as well as other bits) and have that on a floppy or USB stick, if that helps.

Yeah, we did the same here for awhile. The unfortunate thing is that autoyast doesn't seem to actually parse the xml data until the main autoyast parts start, which are gotten via the mounted install area. We started running into truncated /proc/cmdline data here too because we use fairly long paths (can't really get around that due to our environment) and we pass several other things on the cmdline. Now we're ok because, as of at least SP1 for sles/sled10 + (and I patched our older kernels) the limit for cmdline was bumped from 256 characaters to 2048. We use pxe booting and mac addressed based files in order to pass host specific based info to the boot process, then edit or rm that file during the chroot script section. Setup is good enough now that I can run a menu driven script we have here, feed in a file consisting of hostname ip mac and power on whole racks of hosts (we have a lot of blades now) and have fully imaged hosts in a 1/2 hour or so. I've grown to love autoyast. :) -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Bob: "Ok, I'm goin'... but a swift kick in the ass isn't the solution to everything you know." Red: "I gotta disagree with you there Bob!" -- That 70's show -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org