Mailinglist Archive: opensuse-autoinstall (70 mails)
| < Previous | Next > |
AutoYaST - Not skipping second stage (SuSE 10.1)?
- From: "Justin McCormick" <jlmccorm@xxxxxxxxx>
- Date: Sun, 3 Dec 2006 07:25:00 +0000 (UTC)
- Message-id: <864e11300612022121j30b420e1o2d8fc4a960dfce1f@xxxxxxxxxxxxxx>
Hello folks! I'm developing a provisioning system, and am trying to fully
automate the install of SuSE as a part of the system.... I need the install
to be 100% automated, from booting up, doing the install, and then booting
the system. Needs to be completely a hands off install.... and I've setup a
very basic config file as a test, but for some reason it does not skip the
second stage of the install. I've searched around to no avail, maybe I am
missing something?
A second thing, unrelated to the second stage of the install that I've
noticed, is for some reason when the first stage of the install finishes,
the system reboots but it seems to hang on trying to boot. Never loads a
kernel, never says anything at all actually after the initial BIOS screens.
Could that be an issue with not specifying or setting up a bootloader in the
config file? Or any other ideas?
Any help would be greatly appreciated!
- Justin (jlmccorm at gmail dot com)
Below is the autoyast.xml file I'm using: (For SuSE 10.1)
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="
http://www.suse.com/1.0/configns">
<general>
<signature-handling>
<accept_unsigned_file
config:type="boolean">true</accept_unsigned_file>
<accept_file_without_checksum
config:type="boolean">true</accept_file_without_checksum>
<accept_verification_failed
config:type="boolean">true</accept_verification_failed>
<accept_unknown_gpg_key
config:type="boolean">true</accept_unknown_gpg_key>
</signature-handling>
<mode>
<halt config:type="boolean">false</halt>
<onfirm config:type="boolean">false</confirm>
<second_stage config:type="boolean">false</second_stage>
</mode>
</general>
<partitioning config:type="list">
<drive>
<use>all</use>
</drive>
</partitioning>
<software>
<base>Minimal</base>
<packages config:type="list">
<package>tftp</package>
</packages>
</software>
<networking>
<dns>
<dhcp_hostname config:type="boolean">true</dhcp_hostname>
<dhcp_resolv config:type="boolean">true</dhcp_resolv>
<domain>local</domain>
<hostname>linux</hostname>
</dns>
</networking>
<users config:type="list">
<user>
<encrypted config:type="boolean">false</encrypted>
<username>root</username>
<user_password>myunsafeplaintextpw</user_password>
<forename/>
<surname/>
</user>
<user>
<encrypted config:type="boolean">false</encrypted>
<username>myuser</username>
<user_password>myotherunsafepw</user_password>
<forename/>
<surname/>
</user>
</users>
<scripts>
<chroot-scripts config:type="list">
<script>
<chrooted
config:type="boolean">true</chrooted>
<filename>kspost</filename>
<interpreter>shell</interpreter>
<source>
<![CDATA[
#/bin/sh
echo "get finished_suse_01-00-02-55-57-1b-bf" | /usr/bin/tftp 192.168.0.3 &
sleep 1
killall tftp
]]>
</source>
</script>
</chroot-scripts>
</scripts>
</profile>
automate the install of SuSE as a part of the system.... I need the install
to be 100% automated, from booting up, doing the install, and then booting
the system. Needs to be completely a hands off install.... and I've setup a
very basic config file as a test, but for some reason it does not skip the
second stage of the install. I've searched around to no avail, maybe I am
missing something?
A second thing, unrelated to the second stage of the install that I've
noticed, is for some reason when the first stage of the install finishes,
the system reboots but it seems to hang on trying to boot. Never loads a
kernel, never says anything at all actually after the initial BIOS screens.
Could that be an issue with not specifying or setting up a bootloader in the
config file? Or any other ideas?
Any help would be greatly appreciated!
- Justin (jlmccorm at gmail dot com)
Below is the autoyast.xml file I'm using: (For SuSE 10.1)
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="
http://www.suse.com/1.0/configns">
<general>
<signature-handling>
<accept_unsigned_file
config:type="boolean">true</accept_unsigned_file>
<accept_file_without_checksum
config:type="boolean">true</accept_file_without_checksum>
<accept_verification_failed
config:type="boolean">true</accept_verification_failed>
<accept_unknown_gpg_key
config:type="boolean">true</accept_unknown_gpg_key>
</signature-handling>
<mode>
<halt config:type="boolean">false</halt>
<onfirm config:type="boolean">false</confirm>
<second_stage config:type="boolean">false</second_stage>
</mode>
</general>
<partitioning config:type="list">
<drive>
<use>all</use>
</drive>
</partitioning>
<software>
<base>Minimal</base>
<packages config:type="list">
<package>tftp</package>
</packages>
</software>
<networking>
<dns>
<dhcp_hostname config:type="boolean">true</dhcp_hostname>
<dhcp_resolv config:type="boolean">true</dhcp_resolv>
<domain>local</domain>
<hostname>linux</hostname>
</dns>
</networking>
<users config:type="list">
<user>
<encrypted config:type="boolean">false</encrypted>
<username>root</username>
<user_password>myunsafeplaintextpw</user_password>
<forename/>
<surname/>
</user>
<user>
<encrypted config:type="boolean">false</encrypted>
<username>myuser</username>
<user_password>myotherunsafepw</user_password>
<forename/>
<surname/>
</user>
</users>
<scripts>
<chroot-scripts config:type="list">
<script>
<chrooted
config:type="boolean">true</chrooted>
<filename>kspost</filename>
<interpreter>shell</interpreter>
<source>
<![CDATA[
#/bin/sh
echo "get finished_suse_01-00-02-55-57-1b-bf" | /usr/bin/tftp 192.168.0.3 &
sleep 1
killall tftp
]]>
</source>
</script>
</chroot-scripts>
</scripts>
</profile>
| < Previous | Next > |