openSUSE Autoinstall November 2004

autoinstall@lists.opensuse.org

37 participants
49 discussions

upgrading from 9.0 to 9.2
by Ryan Allen 08 Nov '04

08 Nov '04

Hi all, I'm trying to upgrade my autoyast setup from SUSE 9.0 to SUSE9.2. A few questions: 1) Is there an automatic way to import my autoyast.xml file? When I run the "check profile validity" command in the yast2 module, I get many many errors. I "opened" the 9.0 .xml file in the 9.2 GUI, then immediately saved it. Running diff between them showed many changes, but still many errors. Any suggestions? 2) There is no "make ISO" image in the yast2 autoyast module like 9.0 had. What is the easiest way to copy ONLY the required .rpm packages from the source tree and make an iso image? I need to get our standard server distribution to fit on one CD Thanks for your help, - Ryan

1 0

How implement the rules.xml in SLES9 autoyast?
by Jayesh Patel 05 Nov '04

05 Nov '04

Hi, I have been trying to auto install using auto yast SLES 9 and was not successful in using the Rules feature of autoyast. Here is my configuration 1) PXE configurations file. default linux prompt 1 timeout 72 label linux kernel vmlinuz-SLES9x86 append initrd=initrd-SLES9x86.img autoyast=nfs://<nfsserverip>/vol/stats/profiles install=nfs://<nfsserverip>/vol/stats/CDs 2) On the nfsserver, SLES 9 CD's are extracted under /vol/stats/CDs 3) On the nfsserver, the profile directory structure is as follows /vol/stats/profiles/rules/rules.xml /vol/stats/profiles/rules/autoinst_sles9.xml /vol/stats/profiles/autoinst_sles9.xml Note: Contents for /vol/stats/profiles/rules/autoinst_sles9.xml and /vol/stats/profiles/autoinst_sles9.xml are the same. 4) Contents of rules.xml are as below. <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <disksize> <match>/dev/hda 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>autoinst_sles9.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/sda 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>autoinst_sles9.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> With this setup the machine boots up and the autoinstall is not able to find the profile file and prompts for the profile file. On the prompt when I give the following path, the install processed and completes. nfs://<nfsserverip>/vol/stats/profiles/autoinst_sles9.xml What is it that I am doing wrong here, that the rules.xml method is not working? Jayesh Patel.

2 2

RE: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck]
by fraser_bailey＠agilent.com 05 Nov '04

05 Nov '04

That's odd. It works for me - I have exactly that syntax in my xml file. I don't have the services stuff. It might be that autoyast is becoming confused if the runlevels section also contains services setup directives. -----Original Message----- From: Stefan Voss [mailto:stefan.voss@itellium.com] Sent: Friday, November 05, 2004 10:13 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck] fraser_bailey(a)agilent.com schrieb: > It should be > > <runlevels> > <default>3</default> > </runlevels> > Yes, this is what the docs say, but it does not work for me (in 9.1 and 9.2). Yast shows that it wants to set runlevel 5. The logfile /var/log/Yast2/y2log suggests that a method/function runlevel_proposal is called despite the setting in the xml file. This proposal method comes up with runlevel 5. > -----Original Message----- > From: Stefan Voss [mailto:stefan.voss@itellium.com] > Sent: Friday, November 05, 2004 7:39 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] How to define services to enable or > disable? [FinanzIT: Viruscheck] > > > Martin Vidner schrieb: > > On Thu, Nov 04, 2004 at 12:53:26PM +0100, Hartmut.Dunker(a)finanzit.com > > wrote: > > > I'm using SLES 9. insserv works with my scripts. I've a workaround > > for the > > > autoinst.xml that works but I want to use the services syntax. > > > > It turns out to be a documentation error. The tag should not read > > <runlevels> but <runlevel>. > > I tried with > > <runlevel> > <default>3</default> > </runlevel> > > but autoyast (SuSE 9.2) still insists on runlevel 5. > According to the dtd file (/usr/share/autoinstall/dtd/runlevels.dtd) the > tag should be <runlevels>. Is the dtd file wrong, too? > > ~> cat /usr/share/autoinstall/dtd/runlevels.dtd > <?xml version="1.0" encoding="UTF-8"?> > <!ELEMENT runlevels (default?, services?)> > <!ELEMENT service (#PCDATA |service_name| service_status| service_start| > service_stop)*> > <!ELEMENT service_name (#PCDATA)> > <!ELEMENT service_status (#PCDATA)> > <!ELEMENT service_start (#PCDATA)> > <!ELEMENT service_stop (#PCDATA)> > <!ELEMENT services (service+)> > <!ATTLIST services > config:type CDATA #FIXED "list" > > > > > > > Anas, can you fix the docs please? > > > > > On Thu, Nov 04, 2004 at 08:39:18AM +0100, Hartmut.Dunker(a)finanzit.com > > > wrote: > > > > I tried to distribute own services in /etc/init.d and added a > > section to > > > my > > > > autoinst.xml to enable this services after installation. For > > comparison I > > > > added a section for disable a system service (xdm). This also is > > ignored > > > > and the service is enabled after installation. Where is the fault > > in my > > > > example? > > > > > > > > <configure> > > > > .... > > > > <runlevels> > > > > <default>3</default> > > > > <services config:type="list" > > > > > <service> > > > > <service_name>configure_system</service_name> > > > > <service_status>enable</service_status> > > > > </service> > > > > <service> > > > > <service_name>FIT_add_admin</service_name> > > > > <service_status>enable</service_status> > > > > </service> > > > > <service> > > > > <service_name>xdm</service_name> > > > > <service_status>disable</service_status> > > > > </service> > > > > </services> > > > > </runlevels> > > > > </configure> > > -- > > Martin Vidner, developer > > SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz > > Drahobejlova 27 tel:+420-296542373 > > 190 00 Praha 9, Czech Republic http://www.suse.cz > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > Regards, > Stefan Voss Regards, Stefan Voss -- Stefan Voss Mail: stefan.voss(a)itellium.com Tel.: +49 (0)201/ 727 7443 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Antwort: Re: [suse-autoinstall] How to define services to enable or disable?[FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 05 Nov '04

05 Nov '04

Hi, with <runlevel>...</runlevel> my probplem is solved under SLES 9 (based on SuSE 9.1). The runlevels.dtd seems to be the same as in SUSE 9.2. Greets Hartmut Stefan Voss <stefan.voss@itel An: suse-autoinstall(a)suse.com lium.com> Kopie: Thema: Re: [suse-autoinstall] How to define services to enable or disable?[FinanzIT: 05.11.2004 11:13 Viruscheck] fraser_bailey(a)agilent.com schrieb: > It should be > > <runlevels> > <default>3</default> > </runlevels> > Yes, this is what the docs say, but it does not work for me (in 9.1 and 9.2). Yast shows that it wants to set runlevel 5. The logfile /var/log/Yast2/y2log suggests that a method/function runlevel_proposal is called despite the setting in the xml file. This proposal method comes up with runlevel 5. > -----Original Message----- > From: Stefan Voss [mailto:stefan.voss@itellium.com] > Sent: Friday, November 05, 2004 7:39 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] How to define services to enable or > disable? [FinanzIT: Viruscheck] > > > Martin Vidner schrieb: > > On Thu, Nov 04, 2004 at 12:53:26PM +0100, Hartmut.Dunker(a)finanzit.com > > wrote: > > > I'm using SLES 9. insserv works with my scripts. I've a workaround > > for the > > > autoinst.xml that works but I want to use the services syntax. > > > > It turns out to be a documentation error. The tag should not read > > <runlevels> but <runlevel>. > > I tried with > > <runlevel> > <default>3</default> > </runlevel> > > but autoyast (SuSE 9.2) still insists on runlevel 5. > According to the dtd file (/usr/share/autoinstall/dtd/runlevels.dtd) the > tag should be <runlevels>. Is the dtd file wrong, too? > > ~> cat /usr/share/autoinstall/dtd/runlevels.dtd > <?xml version="1.0" encoding="UTF-8"?> > <!ELEMENT runlevels (default?, services?)> > <!ELEMENT service (#PCDATA |service_name| service_status| service_start| > service_stop)*> > <!ELEMENT service_name (#PCDATA)> > <!ELEMENT service_status (#PCDATA)> > <!ELEMENT service_start (#PCDATA)> > <!ELEMENT service_stop (#PCDATA)> > <!ELEMENT services (service+)> > <!ATTLIST services > config:type CDATA #FIXED "list" > > > > > > > Anas, can you fix the docs please? > > > > > On Thu, Nov 04, 2004 at 08:39:18AM +0100, Hartmut.Dunker(a)finanzit.com > > > wrote: > > > > I tried to distribute own services in /etc/init.d and added a > > section to > > > my > > > > autoinst.xml to enable this services after installation. For > > comparison I > > > > added a section for disable a system service (xdm). This also is > > ignored > > > > and the service is enabled after installation. Where is the fault > > in my > > > > example? > > > > > > > > <configure> > > > > .... > > > > <runlevels> > > > > <default>3</default> > > > > <services config:type="list" > > > > > <service> > > > > <service_name>configure_system</service_name> > > > > <service_status>enable</service_status> > > > > </service> > > > > <service> > > > > <service_name>FIT_add_admin</service_name> > > > > <service_status>enable</service_status> > > > > </service> > > > > <service> > > > > <service_name>xdm</service_name> > > > > <service_status>disable</service_status> > > > > </service> > > > > </services> > > > > </runlevels> > > > > </configure> > > -- > > Martin Vidner, developer > > SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz > > Drahobejlova 27 tel:+420-296542373 > > 190 00 Praha 9, Czech Republic http://www.suse.cz > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > Regards, > Stefan Voss Regards, Stefan Voss -- Stefan Voss Mail: stefan.voss(a)itellium.com Tel.: +49 (0)201/ 727 7443 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck]
by fraser_bailey＠agilent.com 05 Nov '04

05 Nov '04

It should be <runlevels> <default>3</default> </runlevels> -----Original Message----- From: Stefan Voss [mailto:stefan.voss@itellium.com] Sent: Friday, November 05, 2004 7:39 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck] Martin Vidner schrieb: > On Thu, Nov 04, 2004 at 12:53:26PM +0100, Hartmut.Dunker(a)finanzit.com > wrote: > > I'm using SLES 9. insserv works with my scripts. I've a workaround > for the > > autoinst.xml that works but I want to use the services syntax. > > It turns out to be a documentation error. The tag should not read > <runlevels> but <runlevel>. I tried with <runlevel> <default>3</default> </runlevel> but autoyast (SuSE 9.2) still insists on runlevel 5. According to the dtd file (/usr/share/autoinstall/dtd/runlevels.dtd) the tag should be <runlevels>. Is the dtd file wrong, too? ~> cat /usr/share/autoinstall/dtd/runlevels.dtd <?xml version="1.0" encoding="UTF-8"?> <!ELEMENT runlevels (default?, services?)> <!ELEMENT service (#PCDATA |service_name| service_status| service_start| service_stop)*> <!ELEMENT service_name (#PCDATA)> <!ELEMENT service_status (#PCDATA)> <!ELEMENT service_start (#PCDATA)> <!ELEMENT service_stop (#PCDATA)> <!ELEMENT services (service+)> <!ATTLIST services config:type CDATA #FIXED "list" > > > Anas, can you fix the docs please? > > > On Thu, Nov 04, 2004 at 08:39:18AM +0100, Hartmut.Dunker(a)finanzit.com > > wrote: > > > I tried to distribute own services in /etc/init.d and added a > section to > > my > > > autoinst.xml to enable this services after installation. For > comparison I > > > added a section for disable a system service (xdm). This also is > ignored > > > and the service is enabled after installation. Where is the fault > in my > > > example? > > > > > > <configure> > > > .... > > > <runlevels> > > > <default>3</default> > > > <services config:type="list" > > > > <service> > > > <service_name>configure_system</service_name> > > > <service_status>enable</service_status> > > > </service> > > > <service> > > > <service_name>FIT_add_admin</service_name> > > > <service_status>enable</service_status> > > > </service> > > > <service> > > > <service_name>xdm</service_name> > > > <service_status>disable</service_status> > > > </service> > > > </services> > > > </runlevels> > > > </configure> > -- > Martin Vidner, developer > SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz > Drahobejlova 27 tel:+420-296542373 > 190 00 Praha 9, Czech Republic http://www.suse.cz > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > Regards, Stefan Voss -- Stefan Voss Mail: stefan.voss(a)itellium.com Tel.: +49 (0)201/ 727 7443 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Antwort: Re: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 05 Nov '04

05 Nov '04

Hi Martin, I'm using SLES 9. insserv works with my scripts. I've a workaround for the autoinst.xml that works but I want to use the services syntax. My workaround: <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list"> <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh insserv configure_system insserv FIT_add_admin ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"/> </scripts> Greets Hartmut Martin Vidner <mvidner(a)suse.cz> An: Hartmut.Dunker(a)finanzit.com Kopie: suse-autoinstall(a)suse.com 04.11.2004 09:45 Thema: Re: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck] On Thu, Nov 04, 2004 at 08:39:18AM +0100, Hartmut.Dunker(a)finanzit.com wrote: > I tried to distribute own services in /etc/init.d and added a section to my > autoinst.xml to enable this services after installation. For comparison I > added a section for disable a system service (xdm). This also is ignored > and the service is enabled after installation. Where is the fault in my > example? > > <configure> > .... > <runlevels> > <default>3</default> > <services config:type="list" > > <service> > <service_name>configure_system</service_name> > <service_status>enable</service_status> > </service> > <service> > <service_name>FIT_add_admin</service_name> > <service_status>enable</service_status> > </service> > <service> > <service_name>xdm</service_name> > <service_status>disable</service_status> > </service> > </services> > </runlevels> > </configure> Hi Hartmut, what release are you using? So did your own services get enabled? If not, does "insserv FIT_add_admin" succeed in a running system? -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz

3 2

Newbie requires help with autoinstall on 9.0 - no display!
by mark＠atoneassociates.com 04 Nov '04

04 Nov '04

Hi - I am a newbie to linux so please forgive my ignorance. I recently tried to install 9.0 on to my machine. Its set up as dual boot with windows 98. The windows works fine (well as god as it normally does). When I boot into Linux everything works fine I think but when I am meant to get a login screen the monitor goes blank and the on light flashes like the computer isn't communicating with it anymore. The computer still seems to work bcasue if I hit any key I get some sort of repsonse but I still can't see anything. During the installation I had a warning message about the graphics card an Nvidia. I read some stuff and saw that I need to download different drivers. The problem is of course that I don't have a system to work on (at least I don't know how to access it wihtout the monitor!). Can anyone help please? Do I need to reinstall differently? Thanks for your patience, Mark

2 1

How to define services to enable or disable?
by Hartmut.Dunker＠finanzit.com 04 Nov '04

04 Nov '04

Hi all, I tried to distribute own services in /etc/init.d and added a section to my autoinst.xml to enable this services after installation. For comparison I added a section for disable a system service (xdm). This also is ignored and the service is enabled after installation. Where is the fault in my example? <configure> .... <runlevels> <default>3</default> <services config:type="list" > <service> <service_name>configure_system</service_name> <service_status>enable</service_status> </service> <service> <service_name>FIT_add_admin</service_name> <service_status>enable</service_status> </service> <service> <service_name>xdm</service_name> <service_status>disable</service_status> </service> </services> </runlevels> </configure> Greets Hartmut

3 2

Keeping partitions and differences between 9.1 -> 9.2
by Henrik Schmidt 02 Nov '04

02 Nov '04

Using 9.1 I have four primary partitions swap, root, /export/opt and /export/home. I want to keep /export/home at all costs and keep the configuration size/type of the others for 9.2. What do I have to change (see below) ? I notice the following changes from 9.1 to 9.2 : reiserfs has already to be loaded with pxelinux.cfg. There is no <addon>MINIMAL</addon> in 9.2 Any more pitfalls ? My current setup to install 9.1 on virgin disk : <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/opt</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall November 2004