June 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

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