RE: [suse-autoinstall] Autoyast SLES9 with network and root passw ord at prompt
Jean-Paul,
I use autoyast procedure [...] my goal is to include the configuration of ethernet interfaces and root password during the installation process... What's the code to include in my autoinst.xml file for enabling these purposes please ?
I'd prefer "yast2 autoyast" to setup the XML-File, but however
this would be an example for a static configuration:
<networking>
<dns>
Gunreben, Peter (Peter) a écrit : Hi, I clarify my goal : I don't want to fix root password and network interfaces configuration; I wish have these modules to appear like a "normal" installation and query the user to set these parameters (these parameters are site specific, all of the others things are common and automatised). I have tested static configuration and it works but it's not a good thing for deploying many servers without DHCP. Thanks for answers, Regards, Jean-Paul.
Jean-Paul,
I use autoyast procedure [...] my goal is to include the configuration of ethernet interfaces and root password during the installation process... What's the code to include in my autoinst.xml file for enabling these purposes please ?
I'd prefer "yast2 autoyast" to setup the XML-File, but however this would be an example for a static configuration:
<networking> <dns>
false false <domain>YOUR_DOMAIN_NAME</domain> <hostname>YOUR_HOST_NAME</hostname> <nameservers config:type="list"> <nameserver>YOUR_NAMESERVER_1</nameserver> <nameserver>YOUR_NAMESERVER_2</nameserver> </nameservers> <searchlist config:type="list"> <search>YOUR_DNS_SEARCH_PREFIX</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>YOUR_BROADCAST_ADDRESS</broadcast> <device>eth0</device> <ipaddr>YOUR_IP_ADDRESS</ipaddr> <name>Ethernet Network Card</name> <netmask>YOUR_NETMASK</netmask> <network>YOUR_NETWORK_IP_ADDRESS</network> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"><device>static-0</device> <module>YOUR_ETH0_KERNEL_MODULE</module> <options>YOUR_OPTIONS_FOR_THE_ETH0_KERNEL_MODULE</options> </modules> <routing>false <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>YOUR_GATEWAY</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking>=======
<users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname>root</fullname> <gid>0</gid> <home>/root</home>
<max>10000</max> <min>0</min> <shell>/bin/bash</shell> <uid>0</uid>ENCRYPTED_PASSPHRASE_COMES_HERE <username>root</username> </user> </users>===== Regards, Peter.
-- Jean-Paul Cheney
On Mon, 14 Nov 2005, Jean-Paul Cheney wrote:
Gunreben, Peter (Peter) a écrit :
Hi,
I clarify my goal : I don't want to fix root password and network interfaces configuration; I wish have these modules to appear like a "normal" installation and query the user to set these parameters (these parameters are site specific, all of the others things are common and automatised). I have tested static configuration and it works but it's not a good thing for deploying many servers without DHCP.
You need a static ip address at two stages. http://forgeftp.novell.com//yast/doc/SL10.0/autoinstall/invoking_autoinst.ht... documents "hostip" and various other boot-time parameters. After that I'd consider simply running "yast2 network" and "passwd" from an init.d script that 'insserv -r' itself at the end. I haven't tested, but there's no reason why it shouldn't work. -BT -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 Support: system@mi.uib.no Contact: teknisk@mi.uib.no Direct: bjornts@mi.uib.no
participants (3)
-
Bjorn Tore Sund -
Gunreben, Peter (Peter) -
Jean-Paul Cheney