On Tue, Mar 16, 2010 at 18:23, Mike Coleman <tutufan@gmail.com> wrote:
On Tue, Mar 16, 2010 at 10:27 AM, Uwe Gansert <ug@suse.de> wrote:
yast2-runlevel package is installed?
That did it! Did I miss the doc on this? Is there any way to tell which packages I have to install to enable which sections?
I might be wrong, but i think this isn't in the docs (yet?).
Here's an example scripts section. I can send the whole thing if need be. For this, the script seems to have been unpacked into /var/adm/autoinstall, but there is no evidence that I can find (during the install or in the logs or the existence of the touched file) that it was run.
If the files are there, then I'd assume they were executed, too. Try turning on debugging, that way you'll have an additional /var/adm/autoinstall/scripts/<scriptname>-run with "set -x"-like debug output of the shellscript. For pre-scripts, note these are run *before* the target system is even mounted. So if you write anything anywhere, it doesn't mean it will end up in the target system. The example from the docs[0] for a pre-script is to edit the autoyast profile and reread it. Try something like that, too (because I can't think of anything else useful right now; well, if you have access to the webserver logs, you could put something useless like "wget http://pxe/script1-success" in there). When the post-script is run, the target system is available in /mnt, does your script write or touch something there? (This would explain why your touch in the third script does not show up in the target, you want to touch /mnt/post-install-test-2. Why the echo doesn't show up, I can't tell though.)
* The 'networking' block needs more documentation on how to set up static addresses.
It doesn't have to be elaborate. Just pasting in a second example showing a simple static IP case would get us about 70% there...
I found one of my vmware home-clickups and documentation for it. What i did was this: ---------- 8< ---------- == Network == === IP === * network devices -> network settings -> edit -> overview * add -> next -> statically assigned ip address -> ip address "172.16.98.123", subnet mask "255.255.255.0" -> next -> ok === Route === * network devices -> network settings -> edit -> routing -> default gateway "172.16.98.254" -> ok === Hostname / DNS / resolv.conf === * network devices -> network settings -> edit -> hostname/dns * hostname "new-and-shiny", domain "tengrand" * name server 1 "172.16.98.65", name server 2 "172.16.98.193" * domain search "tengrand" (might be set automatically by dhcp/installer anyway) -> ok ---------- >8 ---------- And it resulted in this xml snippet (the relevant part should be <interfaces> and maybe <routing>) ---------- 8< ---------- <networking> <dhcp_options> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <domain>tengrand</domain> <hostname>new-and-shiny</hostname> <nameservers config:type="list"> <nameserver>172.16.98.65</nameserver> <nameserver>172.16.98.193</nameserver> </nameservers> <resolv_conf_policy>auto</resolv_conf_policy> <searchlist config:type="list"> <search>tengrand</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>172.16.98.123</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>172.16.98.254</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> ---------- >8 ----------
Regarding static adresses, if your machine gets the "right" IP during install, like via boot parameter "hostip=a.b.c.d", you can use <keep_install_network> (as in our config).
Unfortunately, we don't have that here. I was ultimately able to figure this out by using 'yast' to generate sections of the file which I could then tweak...
Yeah, we did the same in the beginning: Click together a bit of stuff we knew we'd need, then get the file under version control and edit it with our favorite text editors from there. tty, 686f6c6d 0: http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#pre-install.s... -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org