June 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Confirm
by Robison, Jonathon (M.) 10 Jun '03

10 Jun '03

Can anyone tell me where and how to place the "Confirm" setting in my autoinst.xml in order to cause the confirmation screen to come up before final execution? I want folks to be able to confirm/change their partitioning setup, but still get my correct package set, etc. Jonathon M. Robison Linux Integration Analyst Strategic Infrastructure Engineering Ford Motor Company 1000 Republic Dr., Ste. 600 Allen Park, MI 48101-3614 313-323-9529

2 1

Installation over http with another port than 80
by Tobias_Mucke＠mn.man.de 10 Jun '03

10 Jun '03

Hi everybody, is it possible to install over http with another port than 80? Thanks in advance. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

Antwort: Re: [suse-autoinstall] Autoyast under SLES8 (my autoinst.xml in ASCII)
by Tobias_Mucke＠mn.man.de 10 Jun '03

10 Jun '03

<?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config ="http://www.suse.com/1.0/configns"> <install> <general> <language>en_US</language> <keyboard> <keymap>german</keymap> </keyboard> <clock> <timezone>Europe/Berlin</timezone> <hwclock>localtime</hwclock> </clock> <mouse> <id>00_ps2</id> </mouse> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">true</reboot> </mode> </general> <init> <domain>mn.man.de</domain> <gateway>151.136.122.1</gateway> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # language: en_EN keytable: de-lat1-nd display color instmode: nfs server: 151.136.130.67 serverdir: /opt/export/install/sles8/i386/autoinstall install: nfs://151.136.130.67/opt/export/install/sles8/i386/autoinstall netdevice: eth0 hostip: 151.136.122.73 netmask: 255.255.254.0 gateway: 151.136.122.1 nameserver: 151.136.128.18 domain: mn.man.de # end_linuxrc_conf # Do not remove the above comment #]]> </info_file> <instmode>nfs</instmode> <ip>151.136.122.73</ip> <nameserver>151.136.128.18</nameserver> <netmask>255.255.254.0</netmask> <profile_protocol>file</profile_protocol> <server>151.136.130.67</server> <serverdir>/opt/export/install/sles8/i386/autoinstall</serverdir> <textmode config:type="boolean">false</textmode> <usedhcp config:type="boolean">false</usedhcp> </init> <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters>acpi=oldboot</kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>50M</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <partition_type>primary</partition_type> <size>16G</size> <lvm_group>vg_system</lvm_group> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>16G</size> </partition> <partition> <size>max</size> </partition> </partitions> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>vg_system</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lv_root</lv_name> <lv_size>1G</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lv_usr</lv_name> <lv_size>2G</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> <lv> <lv_name>lv_opt</lv_name> <lv_size>1G</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/opt</lv_mount> </lv> <lv> <lv_name>lv_var</lv_name> <lv_size>1G</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>lv_home</lv_name> <lv_size>512M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>lv_tmp</lv_name> <lv_size>512M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </warnings> </report> <software> <base>default</base> </software> </install> <configure> <network> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <hostname>mmicl006</hostname> <dns_domain>mn.man.de</dns_domain> <nameservers config:type="list"> <nameserver>151.136.128.18</nameserver> <nameserver>151.136.192.18</nameserver> <nameserver>151.136.42.131</nameserver> </nameservers> <searchlist config:type="list"> <search>mn.man.de</search> <search>mn-man.biz</search> <search>ed-man.biz</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <BOOTMODE>onboot</BOOTMODE> <BOOTPROTO>static</BOOTPROTO> <BROADCAST>151.136.123.255</BROADCAST> <IPADDR>151.136.122.73</IPADDR> <NETMASK>255.255.254.0</NETMASK> <NETWORK>151.136.122.0</NETWORK> <device>eth0</device> <module>bcm5700</module> <options></options> </interface> <interface> <BOOTMODE>onboot</BOOTMODE> <BOOTPROTO>static</BOOTPROTO> <BROADCAST>10.100.1.255</BROADCAST> <IPADDR>10.100.1.59</IPADDR> <NETMASK>255.255.255.0</NETMASK> <NETWORK>10.100.1.0</NETWORK> <device>eth1</device> <module>bcm5700</module> <options></options> </interface> </interfaces> <routing config:type="list"> <route> <destination>default</destination> <device></device> <gateway>151.136.122.1</gateway> <netmask>0.0.0.0</netmask> </route> </routing> </network> <security> <console_shutdown>ignore</console_shutdown> <cwd_in_root_path>no</cwd_in_root_path> <displaymanager_remote_access>no</displaymanager_remote_access> <encryption>des</encryption> <fail_delay>3</fail_delay> <faillog_enab>yes</faillog_enab> <gid_max>60000</gid_max> <gid_min>101</gid_min> <kdm_shutdown>root</kdm_shutdown> <lastlog_enab>yes</lastlog_enab> <obscure_checks_enab>yes</obscure_checks_enab> <pass_max_days>99999</pass_max_days> <pass_max_len>7</pass_max_len> <pass_min_days>0</pass_min_days> <pass_min_len>5</pass_min_len> <pass_warn_age>7</pass_warn_age> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>secure</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <uid_max>60000</uid_max> <uid_min>100</uid_min> </security> <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>XNTPD_INITIAL_NTPDATE</sysconfig_key> <sysconfig_path>xntp</sysconfig_path> <sysconfig_value>ntp1.mn.man.de</sysconfig_value> </sysconfig_entry> </sysconfig> <users config:type="list"> <user> <username>root</username> <encrypted config:type="boolean">true</encrypted> <user_password>IXu009/.msGNQ</user_password> </user> </users> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">86</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">55</min_vsync> </display> <monitor_device>TFT 1400FP</monitor_device> <monitor_vendor>DELL</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">true</start_x11> </x11> </configure> </profile> Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- Stefan Weigel <sw@global-linxs. An: Tobias_Mucke(a)mn.man.de de> Kopie: Thema: Re: [suse-autoinstall] Autoyast under SLES8 10.06.2003 11:52 Bitte antworten an sw Am Dienstag, 10. Juni 2003 08:17 schrieb Tobias_Mucke(a)mn.man.de: > Hi everybody, > > I am using SLES8 and try to install several nodes with that SuSE release. > Unfortunately I experienced some strange phenomenons (beside that lvm > problem last week) and I am wondering about a few marginal problems. > > 1. How can I install straight forward the SuSE Patch CDs during the initial > installation. I read that during a manuell installation that is possible by > booting from the latest patch CD. Is that right and can this be done by > Autoyast? If the SuSE Patch CD's contains only fresh RPM's, that it would be easy to copy the update RPM's in your tree, delete the old packages from there, and use create_package_descr to build the new descriptions. > 2. How can I avoid the license agreement at the beginning of the > installation? Have a look at: http://lists2.suse.com/archive/suse-autoinstall/2003-Apr/0061.html > 3. Why are the network devices not configured correctly at the end of the > installation? The first device eth0 is working, but eth1 doesn't get > configured. YaST2 says that none of the two interfaces are configured and > after a reboot eth0 remains also unconfigured. > Sorry, I don't have problems with this and can't help you with this point. > Since I am not sure that is my fault or a fault in my configuration, I > append my autoinst.xml. > > During autoinstallation I am booting from the SuSE SLES8 CD. The files info > and autoinst.xml are on a floppy. The CDs for installation are on a NFS > Server which was prepared like the SuSE docu described it for SLES8 and UL. > > Thanks for help again. > > > (See attached file: mmicl006_autoinst.xml) (See attached file: > mmicl006_info) > > Mit freundlichen Grüßen > > Tobias Mucke > > --------------------------------------------------------------------------- >----------------------- > > > MAN Nutzfahrzeuge AG > Informationssysteme Organisation (I) > Dachauer Straße 667 > D-80995 München > > Tel.: +49 (0) 89 1580 5269 > Mail-Adresse: Tobias_Mucke(a)mn.man.de > Internet-Adresse: http://www.man-trucks.com > --------------------------------------------------------------------------- >----------------------- This message and any attachments are confidential > and may be privileged or otherwise protected from disclosure. If you are > not the intended recipient, please telephone or email the sender and delete > this message and any attachment from your system. If you are not the > intended recipient, you must not copy this message or attachment or > disclose the contents to any other person. -- __________________________________________ stefan weigel administration global linxs gmbh knowledge interaction romanstrasse 16 80639 munich - germany www.global-linxs.com tel.: +49(0)89. 189 336- 61 fax.: +49(0)89. 189 336- 99 email: sw(a)global-linxs.com __________________________________________ This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

Autoyast under SLES8
by Tobias_Mucke＠mn.man.de 10 Jun '03

10 Jun '03

Hi everybody, I am using SLES8 and try to install several nodes with that SuSE release. Unfortunately I experienced some strange phenomenons (beside that lvm problem last week) and I am wondering about a few marginal problems. 1. How can I install straight forward the SuSE Patch CDs during the initial installation. I read that during a manuell installation that is possible by booting from the latest patch CD. Is that right and can this be done by Autoyast? 2. How can I avoid the license agreement at the beginning of the installation? 3. Why are the network devices not configured correctly at the end of the installation? The first device eth0 is working, but eth1 doesn't get configured. YaST2 says that none of the two interfaces are configured and after a reboot eth0 remains also unconfigured. Since I am not sure that is my fault or a fault in my configuration, I append my autoinst.xml. During autoinstallation I am booting from the SuSE SLES8 CD. The files info and autoinst.xml are on a floppy. The CDs for installation are on a NFS Server which was prepared like the SuSE docu described it for SLES8 and UL. Thanks for help again. (See attached file: mmicl006_autoinst.xml) (See attached file: mmicl006_info) Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

Antwort: Re: [suse-autoinstall] Autoyast and LVM
by Tobias_Mucke＠mn.man.de 10 Jun '03

10 Jun '03

Hi, I am using SLES8. Thanks for help with that prescript. I'll try that. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- Anas Nashif <nashif(a)suse.de> An: Tobias_Mucke(a)mn.man.de Kopie: suse-autoinstall(a)suse.com 06.06.2003 18:35 Thema: Re: [suse-autoinstall] Autoyast and LVM Hi, What release are using? 8.1? SLES? 8.2? Anas Tobias_Mucke(a)mn.man.de wrote: > Hi everybody, > > I'm using Autoyast and LVM together successfully during the first > installation. But when I try a second installation on the same node, yast2 > says that Volume Groups allready exist and doesn't format the lvols. > > Can I force YaST to create pvs ignoring that they are already in a vg? > > Thanks for help. > > > > Mit freundlichen Grüßen > > Tobias Mucke > > -------------------------------------------------------------------------------------------------- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

RE: [suse-autoinstall] Automated Install 8.2
by Berge, Harry ten 10 Jun '03

10 Jun '03

Forget ALICE. It can be done with autoyast. Please look at the documentation on http://www.suse.de/~nashif/autoinstall/ In the documentation you can also find information for migration from Kickstart. Success! Regards Harry > -----Original Message----- > From: Gyorda [SMTP:suse@gyorda.com] > Sent: Monday, June 09, 2003 5:50 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Automated Install 8.2 > > I'm trying to duplicate many servers to one that I have already built with > 8.2. Does anyone have instructions on setting up ALICE? Unfortunately > I'm > not very familiar yet with SUSE. (came from a Red Hat world with > kickstart) > > Much appreciative > Mike > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Automated Install 8.2
by Gyorda 09 Jun '03

09 Jun '03

I'm trying to duplicate many servers to one that I have already built with 8.2. Does anyone have instructions on setting up ALICE? Unfortunately I'm not very familiar yet with SUSE. (came from a Red Hat world with kickstart) Much appreciative Mike

1 0

Autoyast and LVM
by Tobias_Mucke＠mn.man.de 09 Jun '03

09 Jun '03

Hi everybody, I'm using Autoyast and LVM together successfully during the first installation. But when I try a second installation on the same node, yast2 says that Volume Groups allready exist and doesn't format the lvols. Can I force YaST to create pvs ignoring that they are already in a vg? Thanks for help. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

5 4

more on files-scripts
by Pablo Gomez 05 Jun '03

05 Jun '03

hello again it seems that - at least on my setup - files are created in advance than scripts runned. Is there any way to control it? thanks in advance Pablo Gomez

2 1

scripts
by Pablo Gomez 05 Jun '03

05 Jun '03

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

3 3