hello again last one for today This is my non-working <post-scripts> section. <post-scripts> <script> <filename>userinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh echo "AQUI ESTOY" > /tmp/aquivengo ]]> </source> </script> </post-scripts> DOUBTS: (he he, not working, why? :-)) what's the use of the <filename> subsection. If i am specifying the whole contents of the script, what do i need to provide a script name for? i was expecting to get a file /tmp/aquivengo in the target system containing the text "AQUI ESTOY" but the installation process i over, the file is not there. Any clue? thanks in advance Pablo Gomez
Hello Pablo, You wrote:
hello again
last one for today
This is my non-working <post-scripts> section.
<post-scripts> <script> <filename>userinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh echo "AQUI ESTOY" > /tmp/aquivengo ]]> </source> </script> </post-scripts>
DOUBTS:
(he he, not working, why? :-))
Have a look at the generated file. You will notice the empty first line. Placing "#!/bin/sh" on the first line should solve Your problem.
what's the use of the <filename> subsection. If i am specifying the whole contents of the script, what do i need to provide a script name for?
This is the name of the script in /var/adm/autoinstall/scripts.
i was expecting to get a file /tmp/aquivengo in the target system containing the text "AQUI ESTOY" but the installation process i over, the file is not there.
Any clue?
Look at /var/adm/autoinstall/logs/userinstall.sh Ciao, Carsten
Right!!!! you got it!!! Carsten Dumke wrote:
Hello Pablo,
You wrote:
hello again
last one for today
This is my non-working <post-scripts> section.
<post-scripts> <script> <filename>userinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh echo "AQUI ESTOY" > /tmp/aquivengo ]]> </source> </script> </post-scripts>
DOUBTS:
(he he, not working, why? :-))
Have a look at the generated file. You will notice the empty first line. Placing "#!/bin/sh" on the first line should solve Your problem.
This was exactly what happened. It seems that autoinstall fails without leaving any crumbs or clues. Some of the files under /var/adm/autoinstall are created when the process successes not when it fails so you are alone... except with the list :-) Thanks a lot. Now I can autoinstall my targets at last.
what's the use of the <filename> subsection. If i am specifying the whole contents of the script, what do i need to provide a script name for?
This is the name of the script in /var/adm/autoinstall/scripts.
i was expecting to get a file /tmp/aquivengo in the target system containing the text "AQUI ESTOY" but the installation process i over, the file is not there.
Any clue?
Look at /var/adm/autoinstall/logs/userinstall.sh
Ciao,
Carsten
Carsten Dumke wrote:
This is my non-working <post-scripts> section.
<post-scripts> <script> <filename>userinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh echo "AQUI ESTOY" > /tmp/aquivengo ]]> </source> </script> </post-scripts>
DOUBTS:
(he he, not working, why? :-))
Have a look at the generated file. You will notice the empty first line. Placing "#!/bin/sh" on the first line should solve Your problem.
This would have been significant if I would be calling the script as an executable, but thats not how it is called in autoyast. All scripts are called with /bin/sh -x <script name> 2&> <script name>.log So the first line and the magic #! are not really evaluated. Just test all variations, left aligned with CR and with CR and so on, all worked fine. So my guess is that the syntax and location of the script container was wrong. Anas
participants (3)
-
Anas Nashif -
Carsten Dumke -
Pablo Gomez