[opensuse-autoinstall] SUMMARY: Init-scripts and nfs location

15 Dec 2006

      To summarize the answers and solution.

1: At the time that the init-scripts are fetched, the network is not
available. So you can not use <location>...</location> references with
nfs, http, ftp etc. Only with file.
 Anyone who says they have it working has probably brought the network
up in a previous script.

2: The following works.

    <scripts>
      <post-scripts config:type="list">
        <listentry>
          <filename>fetch-init.sh</filename>
          <interpreter>shell</interpreter>
          <source><![CDATA[
/etc/init.d/network start
/etc/init.d/portmap start
/bin/mount -r 192.168.1.1:/vol/source /mnt 
/bin/cp /mnt/initfile.sh /tmp
/bin/umount /mnt
/etc/init.d/portmap stop
/etc/init.d/network stop
]]></source>
        </listentry>
      </post-scripts>
      <init-scripts config:type="list">
        <listentry>
          <filename>initscript.sh</filename>
          <location>file:///tmp/initfile.sh</location>
        </listentry>
      </init-scripts>
    </scripts>

Notes:
1: The network has been configured at the point the postinstall runs (if
you are just using autoyast to configure it), so this works even with
dhcp, and DNS.
2: portmap is necessary for NFS. If you just want to use http or ftp,
then you just need the network. (curl is available in a minimal install,
wget is not)
3: The reason for putting it into tmp then using the init-script, is
that if there are no init-scripts defined, then autoyast will not put
the hook in to run them, even if there are scripts in
/var/adm/aytoinstall/init.d
4: Yes the syntax is file:///path/file. 2 slashes, the the full path
starting with a /.
5: What if you don't down the network? Probably nothing, but if you have
later scripts that configure the network, and it is already up, your
changes wont take affect.
6: Note that even your init scripts will not have the network up when
they run as of Sles10, sp1.
(http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html) So if your
init scripts need the network, you will have to bring it up in them.

Thanks all
-Andrew
...
-----Original Message-----
From: Andrew Laden [mailto:Andrew.Laden@tudor.com] 
Sent: Tuesday, December 12, 2006 3:26 PM
To: opensuse-autoinstall@opensuse.org
Subject: [opensuse-autoinstall] Init-scripts and nfs location
Using autoyast on Sles 9 SP3. pxebooting using dhcp.  
Installing over NFS, Autoyast file served up via NFS, so I 
know that all works fine.
Autoinstall all works fine. I get a fully installed ready to 
go system.
So now I am trying to use/configure some init scripts. I have 
two of them. One I have placed the source in the xml, and the 
other via NFS.
<scripts>
      <init-scripts config:type="list">
        <script>
          <filename>init-zeus_bootstrap</filename>
          <interpreter>shell</interpreter>
<location>nfs://192.168.1.1/vol/prod_LinuxInstall_grn_x/zeus/z
eus_bootst
rap</location>
        </script>
        <script>
          <filename>init-online-update.sh</filename>
          <interpreter>shell</interpreter>
          <source><![CDATA[
/usr/bin/online_update -s -u http://lx4-adm.grn.tudor.com/YOU 
-V > /var/tmp/online-update.out 2> /var/tmp/online-update.err 
]]></source>
        </script>
      </init-scripts>
    </scripts>
The one with source works fine. The other doesn't seem to work. So
1: Is the location paramter supported on Sles 9.3 for init scripts.
2: Is this section parsed and the files created at a time 
when the network is up, so that NFS is available?
3: Are there some log files that will help me. Since the 
script never runs, there is nothing in /var/adm/autoinstall. 
It looks like the script never gets copied from NFS and 
placed in there.
Thanks
-Andrew
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org
For additional commands, e-mail: 
opensuse-autoinstall+help@opensuse.org
-- 
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org