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

scripts and files
by Pablo Gomez 04 Jun '03

04 Jun '03

Hello again after following some list contributors advice, none of these sections work for me. In the target /var/adm/autoinstall/cache/installedSystem.xml it seems as if it had to work: [...] <scripts> <post-scripts> <script> <filename>userinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh echo "# " >> /etc/fstab echo "# AQUI ESTOY" >> /etc/fstab echo "# " >> /etc/fstab ]]> </source> </script> </post-scripts> </scripts> [...] Someone told me to surround the <post-scripts> part with a <scripts> structure, but this is not documented anywhere. Anyhow, it doesn't work either, cut the <scripts> apart or let them stay. Is there any possibility of tracing what is supossed it's automatically done with this? thanks in advance! PG

2 1

chroot scripts
by Pablo Gomez 04 Jun '03

04 Jun '03

hello i have a doubt about chroot scripts. what are them for? are them chroot executed in the target filesystem mounted under /var/adm or whatever? could someone post any interesting or useful application case? thanks in advance. Pablo Gomez

2 1

Kernel is not installed with empty <packages> tag
by Fermín Galán 04 Jun '03

04 Jun '03

Hello everyone, I'm using the following control file to perform a SuSE 8.1 autoinstallation: <?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"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>demo-zone.com</domain> <hostname>praga</hostname> <nameservers config:type="list"> <nameserver></nameserver> </nameservers> <searchlist config:type="list"> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <broadcast></broadcast> <device>eth0</device> <ipaddr></ipaddr> <netmask></netmask> <network></network> <options></options> <remote_ipaddr></remote_ipaddr> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway></gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <runlevels> <default>5</default> <services config:type="list"/> </runlevels> <scripts> <post-scripts config:type="list"> </post-scripts> <pre-scripts config:type="list"/> </scripts> <users config:type="list"> <user> <encrypted config:type="boolean">false</encrypted> <user_password>changeme</user_password> <username>root</username> </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">false</enable_3d> <monitor> <display> <frequency config:type="integer">75</frequency> <height config:type="integer">768</height> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">75</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">50</min_vsync> <width config:type="integer">1024</width> </display> <monitor_device>1024X768@75HZ</monitor_device> <monitor_vendor> VESA</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">true</start_x11> </x11> </configure> <install> <bootloader> <write_bootloader config:type="boolean">true</write_bootloader> <lba_support config:type="boolean">true</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Madrid</timezone> </clock> <keyboard> <keymap>spanish</keymap> </keyboard> <language>es_ES</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>probe</id> </mouse> </general> <partitioning config:type="list" > <drive> <device>/dev/hda</device> <use>all</use> </drive> </partitioning> <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">false</show> <timeout config:type="integer">10</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">false</show> <timeout config:type="integer">10</timeout> </warnings> </report> <software> <addons config:type="list"> <addon>Kde</addon> </addons> <base>Minimal+X11</base> <packages config:type="list"> </packages> </software> </install> </profile> However, when installation finishes, there is no kernel installed under /boot (the k_deftl package is not installed). I have discovered that removing <packages config:type="list"> </packages> of the control file, the installation works fine with the kernel installed. It seems autoyast2 doen't like an empty <packages> list. Somebody have experienced similar behaviour? What is the cause? Maybe an autoyast2 bug? Thanks in advance, -------- Fermín Agora Systems, S.A.

1 0

Re: [suse-autoinstall] scripts
by ahmed＠mindspring.com 03 Jun '03

03 Jun '03

I've found that you have to have the <![CDATA[ tag left aligned, along with every other piece of text that you want to run in a script. Finish off the last line with >>] on the same line, or left aligned For example, your script should look like <![CDATA[ #!/bin/sh echo "AQUI ESTOY" > /tmp/aquivengo ]]> Hope this helps </source> </script> </post-scripts> -------Original Message------- From: Pablo Gomez <pgomez(a)arrakis.es> Sent: 06/03/03 06:16 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] scripts > > 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

LVM
by Regner Michael 03 Jun '03

03 Jun '03

Hi , I am trying to install our maschines using autoyast. And I want to setup the system disk using LVM. Therefore, I got some questions. Is it possible to put /boot in the control of LVM. Same question for / . Has somebody a working autoinst.xml for this purpose ? All I got, is a error during the install process. I need the <partitioning> and the <lvm_config> stanza. I tried to use the example out of " AutoYast2: Automatic Linux Installation and Configuration with YaST2 by Anas Nashif Copyright © 2002 SuSE Linux AG Revision History Revision $Id: autoyast2.xml,v 1.4.2.1 2002/10/31 02:00:42 nashif Exp $ 2002/ Version 1.1 " but, this did not work, ...or I was too stupid to understand exactly that to do. BTW: I using SuSE Pro 8.2 at the moment, but I am waiting for a box SLES 8. Are there great differences ? ThanX Michael Regner

1 0

Re: [suse-autoinstall] files section
by Pablo Gomez 03 Jun '03

03 Jun '03

Hello, Stefan unfortunately :-) the xml syntax is ok as reported with xmllint, in fact, the whole autoinstall works fine except some parts without any complaint. I am trying your own excerpt to check results. Thanks again Stefan Weigel wrote: >Hi! >I also had problems with the files section. Try to check with > >xmllint autoinst.xml > >if the syntax is correct. Here an working example from my autoinst.xml: > ><?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"> > <configure> > <files config:type="list"> > <file> > <file_contents> ><![CDATA[ ># a test file >]]> > </file_contents> > <file_path>/tmp/test1</file_path> > </file> > <file> > <file_contents> ><![CDATA[ ># a second test file >]]> > </file_contents> > <file_path>/tmp/test2</file_path> > </file> > </files> >.. > </configure> ></profile> > >Greetings > >Stefan > > >Am Dienstag, 3. Juni 2003 09:37 schrieb Pablo Gomez: > > >>hello >> >>i was wondering if this <files> section is correct and why it does not work >> >> >> <files> >> <config_file> >> <file_path>/tmp/test.txt</file_path> >> <file_contents> >> <![CDATA[some content]]> >> </file_contents> >> </config_file> >> </files> >> >> >>i am expecting from it to create a file named test.txt under the /tmp >>directory in the installed system just containing "some content" in it >>but fails. >> >>I am trying to (auto) install SuSE8.2 with update floppy and expect to >>set up standard config files using this method. >> >>any suggestions? thanks in advance. >> >>Pablo Gomez >> >> > > >

1 0

files section
by Pablo Gomez 03 Jun '03

03 Jun '03

hello i was wondering if this <files> section is correct and why it does not work <files> <config_file> <file_path>/tmp/test.txt</file_path> <file_contents> <![CDATA[some content]]> </file_contents> </config_file> </files> i am expecting from it to create a file named test.txt under the /tmp directory in the installed system just containing "some content" in it but fails. I am trying to (auto) install SuSE8.2 with update floppy and expect to set up standard config files using this method. any suggestions? thanks in advance. Pablo Gomez

1 0

autoinst.xml not found
by Leandro Gelasi 03 Jun '03

03 Jun '03

Hi to all. I'm trying to realize a custom boot cd for automating network installation of SuSE 8.2. I created autoinst.xml (with autoyast2) and copied it on the root directory of SuSE boot cd (as found on SuSE ftp). I copied boot cd on /tmp/test_cd, then modified /tmp/test_cd/boot/loader/isolinux.cfg this way: ------------------------ default auto1 # autoinstall label auto1 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=file:/autoinst.xml install=ftp://my_suse_ftp_mirror/pub/suse_mirror/8.2/ ip=192.168.17.2 netmask=255.255.255.0 gateway=192.168.17.1 # hard disk label harddisk kernel linux append SLX=0x202 showopts < unmodified part> ------------------- I recreated cd image with: mkisofs -o prova1.iso -b boot/loader/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table /tmp/test_cd and burned it successfully. The boot process starts correctly and I can reach YaST2 screen. After a while YaST2 complains about the lack of autoinst.xml and there is no way for me to make it read from the CD. Identical problem if I try to read it from floppy (modifying or not the "autoyast=..." boot option). Any hints? TIA LG -- Leandro Gelasi Servizio supporto utenti Linux Email: supporto.linux(At)uniroma1(punto)it Home Page: http://linuxhelp.uniroma1.it Università di Roma "La Sapienza" - C.I.T.I.Co.R.D. Centro Interateneo per le Tecnologie dell'Informazione e la Comunicazione nella Ricerca e nella Didattica

1 0

Keeping partitions
by Urs Haberthuer 03 Jun '03

03 Jun '03

Hi All, I tested extensively the patch for keeping partitions. To apply the patch I used the method that modifies the cramfs image in the installation repository (script to do so is provided by Anas Nashif, http://www.suse.de/~nashif/autoinstall/y2update/). After this, keeping partitions works fine as described in the documentation. Best, Urs -- Urs Haberthuer Department of Biochemistry University of Zurich Winterthurerstrasse 190 CH - 8057 Zurich Phone: ++41 (0)1 635 55 92 Fax: ++41 (0)1 635 68 62 E-mail: atlantis(a)bioc.unizh.ch

1 0

sles 8 RAID in autoyast
by Nate Faerber 02 Jun '03

02 Jun '03

Hi, I am having a lot of trouble getting autoyast to install a raid configuration. I have tried several methods from the "documentation" and mailing-lists but I still get errors regarding the size of '/' and '/var' (basically, the raid arrays are not being set up properly). This is SLES 8 on an Opteron system. I have even tried installing manually then using yast2 to create a clone.xml. Using the clone.xml untouched on the same system results in a "Preparting the RAID system failed" error. Here is the partitioning and raid portion of my control file: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>80mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>2040mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_name>/dev/md2</raid_name> <size>6000mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">5</partition_nr> <raid_name>/dev/md3</raid_name> <size>1020mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md4</raid_name> <size>10gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdb</device> <partitions config:type="list"> <partition> <format config:type="boolean">true</format> <mount>/bootmirror</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>80mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>2040mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_name>/dev/md2</raid_name> <size>6000mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">5</partition_nr> <raid_name>/dev/md3</raid_name> <size>1020mb</size> </partition> <partition> <format config:type="boolean">false</format> <mount /> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md4</raid_name> <size>10gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md1</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>64</chunk_size> <mount>swap</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> </raid_device> <raid_device> <device_name>/dev/md2</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>64</chunk_size> <mount>/</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> </raid_device> <raid_device> <device_name>/dev/md3</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>64</chunk_size> <mount>/var</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> </raid_device> <raid_device> <device_name>/dev/md4</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>64</chunk_size> <mount>/home</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> </raid_device> </raid> thanks -nate

2 3

autoyast2: rebooting
by Berge, Harry ten 02 Jun '03

02 Jun '03

Hi, I'm new to this list so forgive me if I ask for obvious thingz... I'm wondering if it's possible to *NOT* have autoyast2 reboot after the initial installation. I remember SuSE 7.3 only re-initting but 8.2 does a complete reboot. Can I prevent this? I've 'fooled around' with the reboot/forceboot flags but the behaviour is the same... Anyone a clue? > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test Engineer HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

Updating YaST2 in installation repository
by Fermín Galán 02 Jun '03

02 Jun '03

Hello everyone, I have read in the online documentation available that bugs of the autoinstallation system (enable_3d, password in clear text, ...) can be solved updating yast2 related RPMs (yast2, autoyast2, yast2-x11, etc). I would like to know wheter the updating processes is as simple as the addition of customized packages: delete the old RPM file in the repository, copy the updated one to the same directory (noarch, i586, etc.) and runing cd <repository>/suse /usr/lib/YaST2/bin/create_package_descr to update the packet database. I'm using/installing SuSE 8.1. Thanks in advance! ------- Fermín fermin.galan(a)agora-2000.com Agora Systems, S.A.

2 1

Problems adding fstab Options
by Joachim.Tork＠gad.de 02 Jun '03

02 Jun '03

Hello, I'm using SLES Autoinstallation. I tell autoyast to use acl, see below ... <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>data=ordered,acl</fstopt> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <size>max</size> ... Unfortunetly that does not work. Can anybody help ? Best regards Joachim

2 1

grub as default
by Jochen Schaefer 02 Jun '03

02 Jun '03

Hi Anas, is it possible to set up grub as default bootloader with autoyast, even if ones selects lvm and/or softwareraid for sles8? In sles8 induced the selection of lvm or softwareraid to an installation of lilo. greetings Jochen -- Jochen Schäfer SuSE Linux AG Geschäftsstelle Rhein-Ruhr Marie-Curie-Straße 11-17 D-53757 St. Augustin E-Mail: jochen.schaefer(a)suse.de

2 1