openSUSE Autoinstall December 2003

autoinstall@lists.opensuse.org

26 participants
36 discussions

DTD out of date?
by Holger Hellmuth 12 Dec '03

12 Dec '03

Could it be that the DTD is out of date? When I configure users with yast2 autoyast and store the xml-file, xmllint reports problems with <group> and <fullname>. And I checked the DTD myself. There is no 'fullname' at all and group is an element with subelements in the DTD, but a data element in the autoyast generated file (hope I'm not mixing up xml nomenclature here). Holger.

1 0

Backward compatibility in control files
by Fermín Galán 12 Dec '03

12 Dec '03

Hello, Which are the changes in the control file format (new tags, deprecated tags, new semantics for tags, etc.) from SuSE 8.1 to SuSE 8.2 to SuSE 9.0? Are they backward compatible (indeed, a control file for SuSE 8.1 works as a control file for SuSE 8.2 and SuSE 9.0? Thanks in advance! ------ Fermín

1 0

[suse-autoinstall] LVM config with AutoYAST (contd.)
by Schlabach, Torsten 12 Dec '03

12 Dec '03

Little update to this from myself: The problem seems to be that the tag <lvm_group> as a child of <raid_device> is ignored since SP3. This leads to the vg_create to try and create the volumes with device = "" (nothing) which cannot work. Q: How do I tell on what device the LVM group is to be created now? Given the fact that "LVM on software raid is not supported" how is this done with LVM on a plain harddisk? Regards, Torsten -----Ursprüngliche Nachricht----- Von: Schlabach, Torsten [mailto:Torsten.Schlabach@t-mobile.de] Gesendet am: Freitag, 12. Dezember 2003 12:03 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] LVM config with AutoYAST Dear list, we are using SLES 8 with SP3 and try to set up LVM with AutoYAST. The installer breaks with an error message saying: lvm vg_create invalid values Config snippet is below. It worked with non-SP3 SLES. Any ideas anyone? Regards, Torsten ---- <lvm config:type="list"> <lvm_group> <lvm_name>system</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>root</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>tmp</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> <lv> <lv_name>var</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>appl</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/appl/local</lv_mount> </lv> <lv> <lv_name>user1</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/users/local/user1</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH ----------------------------------------- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

LVM config with AutoYAST
by Schlabach, Torsten 12 Dec '03

12 Dec '03

Dear list, we are using SLES 8 with SP3 and try to set up LVM with AutoYAST. The installer breaks with an error message saying: lvm vg_create invalid values Config snippet is below. It worked with non-SP3 SLES. Any ideas anyone? Regards, Torsten ---- <lvm config:type="list"> <lvm_group> <lvm_name>system</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>root</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>tmp</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> <lv> <lv_name>var</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>appl</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/appl/local</lv_mount> </lv> <lv> <lv_name>user1</lv_name> <lv_size>2048mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/users/local/user1</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH -----------------------------------------

1 0

Install without documentation
by Togan Muftuoglu 11 Dec '03

11 Dec '03

Hi, Is there a way I can install all the rpms from the custom iso like the rpm --excludedocs command or do I have to recreate all the packages without documentation :-( and create the custom iso ? Thanks in advance -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://susefaq.sf.net

1 0

AutoYaST and firewall configuration
by David Carter 11 Dec '03

11 Dec '03

Hi everyone, I'm currently playing with AutoYaST on a scratch system, with a view to using SuSE 9.0+AutoYAST in place of Redhat 9+Kickstart on some of our servers. AutoYaST works rather nicely, but I'm having a couple of teething problems which is probably down to ignorance on my part. My test install environment is based on the GRUB boot floppy found at: ftp://ftp.suse.com/pub/people/nashif/autoinstall/ I'm looking at an install environment which uses TFTP for boot images and autoyast files but which uses manually configured IP addresses supplied by the grub and autoyast configurations. I don't trust DHCP on our network, simply because of the large numbers of different groups who run servers. Problem #1: Spurious DHCP requests ================================== Unless I switch off forceboot and reboot in the autoyast.xml file: <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">false</reboot> </mode> the system reboots and attempts a DHCP lookup on eth0 before setting up the static IP address which I have specified in the autoyast.xml file: <networking> ... <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>131.111.255.255</broadcast> <device>eth0</device> <ipaddr>131.111.11.209</ipaddr> <netmask>255.255.0.0</netmask> <network>131.111.0.0</network> <startmode>onboot</startmode> </interface> </interfaces> ... </networking> Is there another way of stopping the redundant DHCP request? At best this leads to a delay until the request times out. At worse the machine could end up with an invalid configuration. Problem #2: Firewall configuration ================================== /sbin/yast2 autoyast provides a screen for configurating a firewall which generates the following in autoyast.xml: <firewall> <fw_allow_fw_traceroute>yes</fw_allow_fw_traceroute> <fw_autoprotect_services>yes</fw_autoprotect_services> <fw_dev_ext>eth0</fw_dev_ext> <fw_dev_int></fw_dev_int> <fw_log_accept_all>no</fw_log_accept_all> <fw_log_accept_crit>yes</fw_log_accept_crit> <fw_log_drop_all>no</fw_log_drop_all> <fw_log_drop_crit>yes</fw_log_drop_crit> <fw_masq_nets></fw_masq_nets> <fw_masquerade>no</fw_masquerade> <fw_protect_from_internal>yes</fw_protect_from_internal> <fw_route>no</fw_route> <fw_services_ext_tcp>ssh</fw_services_ext_tcp> <start_firewall config:type="boolean">true</start_firewall> </firewall> The yast postinstall script which runs says "Setting up firewall", and there is various output in y2log which includes: 2003-12-08 12:38:45 <1> magenta-4(2667) [YCP] clients/autoinst_configure.ycp:105 Writing configuration for firewall However, /etc/sysconfig/SuSEfirewall2 doesn't appear to get updated: -rw-r--r-- 1 root root 26770 Dec 8 12:35 SuSEfirewall2 and iptables doesn't acquire any rules. Does autoyast support SuSEfirewall yet? It is conspicuous by its absence in the documentation provided at: http://www.suse.de/~nashif/autoinstall/9.0/html/index.html Thanks in advance for any answers. -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH.

3 3

What kicks up YaST2 at the end of a CD install ?
by David Clack 11 Dec '03

11 Dec '03

Hi, Can anyone tell me what kicks in the YaST2 configuration screens after a completed cd installation, root, user, video, etc. I need to get this to happen after an NFS autoinstallation. Thanks in advance Dave ____________________________________________________________ David Clack Sun Microsystems Senior Systems Engineer Desktop System Architect OSS OEM Software Sales 411 108th Ave. NE, Suite 600 Bellevue WA 98004 Direct : 425-369-2090 Cell: 206-265-1904 Fax: 425-369-0502 David.Clack(a)Sun.Com +++ Sent from a Sun Java Desktop System ++++

2 1

partitioning problems
by Holger Hellmuth 11 Dec '03

11 Dec '03

Hi, my problem ist that I'm getting an error in partitioning (with Suse9.0), but my autoinst.xml (supplied on floppy) seems to be correct. Here the autoinst.xml, which shows no problems with xmllint -valid -noout: ------------------------------- <?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"> <install> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">true</confirm> </mode> <mouse> <id>20_imps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> <packages config:type="list"> <package>kdeartwork3-sound-3.1.4-38</package> <package>suse-release-9.0-6</package> <package>myspell-german-20030301-45</package> <package>iptables-1.2.8-71</package> <package>hdparm-5.4-37</package> ... <package>docbook-toys-1.51.0-141</package> </packages> </software> </install> </profile> --------------------------- The error message "An error occured while trying to create partitioning plans" appears when suse tries to "Create partition plans". Since I already installed Suse9.0 on that machine, I'm sure that "/dev/hda" is correct (and partitioning is working in principle). The partitioning part is verbatim out of the documentation. I think the same error appeared also when the partitioning part was left out altogether, but I'm not sure. As a last resort I even deleted everything between <packages...> and </packages> to make sure the software part wasn't at fault, but to no avail. Any Ideas? Holger.

2 1

Apache2
by Gregory Baboolal 11 Dec '03

11 Dec '03

Hi, Upon installation of Suse 9.0 and selecting Apache2, and enabling the http server with perl, why is it not then possible to actually visit: localhost/cgi-perl/ i.e. the script alias doesn't seem to be active presumably (i think) because the if mod_perl.c(?) clause is not being executed? Greg.

2 1

Upgrading from 7.0 to 9.0
by C. Evangelinos 11 Dec '03

11 Dec '03

Hi - an old machine that I've set up and has been down for quite some time has recently come back up. It's running SuSE 7.1 and I need to upgrade it to a version for which uptodate patches are provided, preferably 9.0 (but any from 7.3 and above will be better than staying at 7.1). The problem is that the machine is remotely located and I cannot simply pop in a CD and try to upgrade. The people that can do that cannot do much else so we're in a sort of a bind. Basically what I need is a way to remotely upgrade a 7.1 system that is booted normally, connected via ssh and preferably using yast2 or yast. I've already downloaded the FTP version to a location on the hard disk of the system and tried to point both yast2 and yast to it and attempt the upgrade option of the menu (hoping that it can work in this manner though I'm not sure they are meant to by design). However the format of the files used for installation seems to have changed from 8.1 onwards and it complains that it can't find /suse/setup/descr/common.pkd I then downloaded the whole of SuSE 8.0 FTP version onto the disk of the system and tried to use yast/yast2 with it. yast2 seemed to work but the upgrade option actually failed to see that the 8.0 rpms were upgrades to the 7.1 and came up with 0 (zero) packages to update. yast refused to do anything useful early on because of the differences between the 7.1 and 8.0 distributions. So the questions are: a) Can a "live" remote update from 7.0 to 7.3 or above be done connected via ssh using yast/yast2 or is it a lost cause? b) Can the upgrade be done directly to 9.0? If so how? c) If the answers to (a) and (b) are negative, any ideas on what can be done apart from installing the new O/S on a new disk, configuring everything and sending it over there? Thanks for any help, Constantinos Evangelinos

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2003