November 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 07 Dec '04

07 Dec '04

Hi Anas, Thanks for the help. I've made all the fixes you and Marcin Kurc suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

3 6

Updating Installation Source
by Thomas Mieslinger 30 Nov '04

30 Nov '04

Hello List, I have the Problem that the bcm5721 network chip is not supported out of the box by SLES 8. I can install SLES 8 with a patched initrd, but after the reboot the default kernel 2.4.18-138 is activ and it doesn't know anything about that chip. How do I change the network driver after the installation and before the reboot? regards Thomas -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com

2 2

Re: confirm subscribe to suse-autoinstall@suse.com
by Günther J. Niederwimmer 30 Nov '04

30 Nov '04

Am Dienstag, 30. November 2004 12:36 schrieb suse-autoinstall-help(a)suse.com: > Hi! This is the ezmlm program. I'm managing the > suse-autoinstall(a)suse.com mailing list. > > I'm working for my owner, who can be reached > at suse-autoinstall-owner(a)suse.com. > > To confirm that you would like > > gjn(a)gjn.priv.at > > added to the suse-autoinstall mailing list, please send > an empty reply to this address: > > > suse-autoinstall-sc.1101814617.idnkhbdfnolmckgiedip-gjn=gjn.priv.at(a)suse.co >m > > Usually, this happens when you just hit the "reply" button. > If this does not work, simply copy the address and paste it into > the "To:" field of a new message. > > or click here: > mailto:suse-autoinstall-sc.1101814617.idnkhbdfnolmckgiedip-gjn=gjn.priv.at >@suse.com > > This confirmation serves two purposes. First, it verifies that I am able > to get mail through to you. Second, it protects you in case someone > forges a subscription request in your name. > > > --- Administrative commands for the suse-autoinstall list --- > > I can handle administrative requests automatically. Please > do not send them to the list address! Instead, send > your message to the correct command address: > > For help and a description of available commands, send a message to: > <suse-autoinstall-help(a)suse.com> > > To subscribe to the list, send a message to: > <suse-autoinstall-subscribe(a)suse.com> > > To remove your address from the list, just send a message to > the address in the ``List-Unsubscribe'' header of any list > message. If you haven't changed addresses since subscribing, > you can also send a message to: > <suse-autoinstall-unsubscribe(a)suse.com> > > For addition or removal of addresses, I'll send a confirmation > message to that address. When you receive it, simply reply to it > to complete the transaction. > > If you need to get in touch with the human owner of this list, > please send a message to: > > <suse-autoinstall-owner(a)suse.com> > > Please include a FORWARDED list message with ALL HEADERS intact > to make it easier to help you. > > --- Enclosed is a copy of the request I received. > > Return-Path: <gjn(a)gjn.priv.at> > Received: (qmail 24269 invoked from network); 30 Nov 2004 11:36:57 -0000 > Received: from unknown (HELO hermes.suse.de) (195.135.221.8) > by 0 with SMTP; 30 Nov 2004 11:36:57 -0000 > Received: from scanhost.suse.de (scanhost.suse.de [149.44.160.36]) > by hermes.suse.de (Postfix) with ESMTP id 06B928E886 > for <suse-autoinstall-subscribe(a)lists.suse.com>; Tue, 30 Nov 2004 12:36:57 > +0100 (CET) Received: from hermes.suse.de ([149.44.160.1]) > by scanhost.suse.de (scanhost [149.44.160.36]) (amavisd-new, port 10025) > with ESMTP id 18445-05 for <suse-autoinstall-subscribe(a)lists.suse.com>; > Tue, 30 Nov 2004 12:36:55 +0100 (CET) > Received: from Cantor.suse.de (news.suse.de [195.135.220.2]) > (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) > (No client certificate requested) > by hermes.suse.de (Postfix) with ESMTP id CDDE710FAD5 > for <suse-autoinstall-subscribe(a)suse.com>; Tue, 30 Nov 2004 12:36:55 +0100 > (CET) Received: from smtp.gjn.priv.at > (81-223-23-209.goesting.xdsl-line.inode.at [81.223.23.209]) by > Cantor.suse.de (Postfix) with ESMTP id 99E011196E69 > for <suse-autoinstall-subscribe(a)suse.com>; Tue, 30 Nov 2004 12:36:55 +0100 > (CET) Received: from localhost (bbs.gjn.priv.at.loc [127.0.0.1]) > by smtp.gjn.priv.at (Postfix) with ESMTP id 2C32258DD > for <suse-autoinstall-subscribe(a)suse.com>; Tue, 30 Nov 2004 12:37:36 +0100 > (CET) Received: from smtp.gjn.priv.at ([127.0.0.1]) > by localhost (bbs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP > id 02918-08 for <suse-autoinstall-subscribe(a)suse.com>; > Tue, 30 Nov 2004 12:37:34 +0100 (CET) > Received: from techz.gjn.priv.at.loc (techz.gjn.priv.at.loc > [192.168.100.100]) by smtp.gjn.priv.at (Postfix) with ESMTP id 2781358D9 > for <suse-autoinstall-subscribe(a)suse.com>; Tue, 30 Nov 2004 12:37:34 +0100 > (CET) From: "=?utf-8?q?G=C3=BCnther_J=2E?= Niederwimmer" <gjn(a)gjn.priv.at> > To: suse-autoinstall-subscribe(a)suse.com > Subject: subscribe > Date: Tue, 30 Nov 2004 12:37:33 +0100 > User-Agent: KMail/1.7.1 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > Message-Id: <200411301237.33967.gjn(a)gjn.priv.at> > X-Virus-Scanned: by amavisd-new at scanhost.suse.de > X-Spam-Status: No, hits=-0.9 tagged_above=-20.0 required=5.0 tests=BAYES_30 > X-Spam-Level: > > > =2D-=20 > MfG / Regards > G=C3=BCnther J. Niederwimmer -- MfG / Regards Günther J. Niederwimmer

1 0

Re: confirm unsubscribe from suse-autoinstall@suse.com
by Günther J. Niederwimmer 30 Nov '04

30 Nov '04

Am Dienstag, 30. November 2004 12:32 schrieb suse-autoinstall-help(a)suse.com: > Hi! This is the ezmlm program. I'm managing the > suse-autoinstall(a)suse.com mailing list. > > I'm working for my owner, who can be reached > at suse-autoinstall-owner(a)suse.com. > > To confirm that you would like > > guenther(a)gjn.priv.at > > removed from the suse-autoinstall mailing list, please send an empty reply > to this address: > > > suse-autoinstall-uc.1101814371.aoiaecbmjleopbfkoohn-guenther=gjn.priv.at@su >se.com > > Usually, this happens when you just hit the "reply" button. > If this does not work, simply copy the address and paste it into > the "To:" field of a new message. > > or click here: > mailto:suse-autoinstall-uc.1101814371.aoiaecbmjleopbfkoohn-guenther=gjn.pr >iv.at(a)suse.com > > I haven't checked whether your address is currently on the mailing list. > To see what address you used to subscribe, look at the messages you are > receiving from the mailing list. Each message has your address hidden > inside its return path; for example, mary(a)xdd.ff.com receives messages > with return path: > <suse-autoinstall-return-<number>-mary=xdd.ff.com(a)suse.com. > > > --- Administrative commands for the suse-autoinstall list --- > > I can handle administrative requests automatically. Please > do not send them to the list address! Instead, send > your message to the correct command address: > > For help and a description of available commands, send a message to: > <suse-autoinstall-help(a)suse.com> > > To subscribe to the list, send a message to: > <suse-autoinstall-subscribe(a)suse.com> > > To remove your address from the list, just send a message to > the address in the ``List-Unsubscribe'' header of any list > message. If you haven't changed addresses since subscribing, > you can also send a message to: > <suse-autoinstall-unsubscribe(a)suse.com> > > For addition or removal of addresses, I'll send a confirmation > message to that address. When you receive it, simply reply to it > to complete the transaction. > > If you need to get in touch with the human owner of this list, > please send a message to: > > <suse-autoinstall-owner(a)suse.com> > > Please include a FORWARDED list message with ALL HEADERS intact > to make it easier to help you. > > --- Enclosed is a copy of the request I received. > > Return-Path: <guenther(a)gjn.priv.at> > Received: (qmail 20329 invoked from network); 30 Nov 2004 11:32:51 -0000 > Received: from unknown (HELO hermes.suse.de) (195.135.221.8) > by 0 with SMTP; 30 Nov 2004 11:32:51 -0000 > Received: from scanhost.suse.de (scanhost.suse.de [149.44.160.36]) > by hermes.suse.de (Postfix) with ESMTP id 126F010FAA5 > for <suse-autoinstall-unsubscribe(a)lists.suse.com>; Tue, 30 Nov 2004 > 12:32:51 +0100 (CET) Received: from hermes.suse.de ([149.44.160.1]) > by scanhost.suse.de (scanhost [149.44.160.36]) (amavisd-new, port 10025) > with ESMTP id 16646-08 for <suse-autoinstall-unsubscribe(a)lists.suse.com>; > Tue, 30 Nov 2004 12:32:48 +0100 (CET) > Received: from Cantor.suse.de (mail-ex.suse.de [195.135.220.2]) > (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) > (No client certificate requested) > by hermes.suse.de (Postfix) with ESMTP id A021A10FAD5 > for <suse-autoinstall-unsubscribe(a)suse.com>; Tue, 30 Nov 2004 12:32:48 > +0100 (CET) Received: from smtp.gjn.priv.at > (81-223-23-209.goesting.xdsl-line.inode.at [81.223.23.209]) by > Cantor.suse.de (Postfix) with ESMTP id 2525D1196C7B > for <suse-autoinstall-unsubscribe(a)suse.com>; Tue, 30 Nov 2004 12:32:48 > +0100 (CET) Received: from localhost (bbs.gjn.priv.at.loc [127.0.0.1]) > by smtp.gjn.priv.at (Postfix) with ESMTP id B7CBF58DA > for <suse-autoinstall-unsubscribe(a)suse.com>; Tue, 30 Nov 2004 12:33:25 > +0100 (CET) Received: from smtp.gjn.priv.at ([127.0.0.1]) > by localhost (bbs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP > id 02918-06 for <suse-autoinstall-unsubscribe(a)suse.com>; > Tue, 30 Nov 2004 12:33:20 +0100 (CET) > Received: from techz.gjn.priv.at.loc (techz.gjn.priv.at.loc > [192.168.100.100]) by smtp.gjn.priv.at (Postfix) with ESMTP id 29A6158D8 > for <suse-autoinstall-unsubscribe(a)suse.com>; Tue, 30 Nov 2004 12:33:19 > +0100 (CET) From: "=?utf-8?q?G=C3=BCnther_J=2E?= Niederwimmer" > <guenther(a)gjn.priv.at> To: suse-autoinstall-unsubscribe(a)suse.com > Subject: unsubscribe > Date: Tue, 30 Nov 2004 12:33:19 +0100 > User-Agent: KMail/1.7.1 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > Message-Id: <200411301233.19192.guenther(a)gjn.priv.at> > X-Virus-Scanned: by amavisd-new at scanhost.suse.de > X-Spam-Status: No, hits=-1.5 tagged_above=-20.0 required=5.0 tests=BAYES_01 > X-Spam-Level: > > > =2D-=20 > MfG / Regards > G=C3=BCnther J. Niederwimmer -- MfG / Regards Günther J. Niederwimmer

1 0

Problem with autoinstalling X11, dhcp-hostname, local users and Log-Problem
by Oliver Osburg 29 Nov '04

29 Nov '04

Hi there, excuse my previous posting in german. I forgot, that this list prefers english. I have the following problem with autoyast: After being almost finished with the cloning of some R51 Thinkpads, I got the following Problem: a) The Hostname ist not setup correctly b) X11 is not configured, though there are enties in the config-file (see below) c) user are not added It seems to me, as if the entire <configure> section is ignored. Software selection and configuration of the boot-loader works, nevertheless. The section looks like the following: ---snip--- <configure> <groups config:type="list"> <group> <groupname>video</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>audio</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>dialout</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>uucp</groupname> <userlist>user2,user4,user2,user1</userlist> </group> </groups> <networking> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <device>eth0</device> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>coling.uni-jena.de</domain> <hostname>dhcp</hostname> <nameservers config:type="list"> <nameserver>141.35.1.16</nameserver> </nameservers> <searchlist config:type="list"> <search>coling.uni-jena.de</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user3</fullname> <gid>100</gid> <home>/home/user4</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1002</uid> <user_password>PASS</user_password> <username>user4</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user2</fullname> <gid>100</gid> <home>/home/user2</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1001</uid> <user_password>PASS</user_password> <username>user2</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user1</fullname> <gid>100</gid> <home>/home/user1</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>PASS</user_password> <username>user1</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user2</fullname> <gid>100</gid> <home>/home/user2</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1003</uid> <user_password>PASS</user_password> <username>user2</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname>root</fullname> <gid>0</gid> <home>/root</home> <password_settings> <expire></expire> <flag></flag> <inact></inact> <max>10000</max> <min>0</min> <warn></warn> </password_settings> <shell>/bin/bash</shell> <uid>0</uid> <user_password>PASS</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">true</enable_3d> <monitor> <display> <frequency config:type="integer">75</frequency> <height config:type="integer">1050</height> <width config:type="integer">1400</width> </display> <monitor_device>1400X1050@75HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <window_manager>kde</window_manager> </x11> </configure> ---snap--- As I read before, the file is parsed and partly understood and exectued. But the <configure> section does not work. Oh, yes: If I add an preinstallation script, that works. The other sections are ignored all the time. I do not find any relevant information in the logs: ---snip--- 2004-11-29 14:07:05 <5> linux(997) [ui-ncurses] YNCursesUI.cc(idleLoop):163 idleLoop error in select() (9) 2004-11-29 14:07:05 <5> linux(997) [ui-ncurses] YNCursesUI.cc(idleLoop):163 idleLoop error in select() (9) ---snap--- more than 90% of the logs are made up by this line. I use Suse Professional 9.1, and I tried in with and without patches and upgrades. No change occured. What did happen here? kind regards, Oliver Osburg -- - Oliver Osburg - System Architect JULIE Group Jena University - email: o.osburg(a)uni-jena.de phone: +493641 9 44 324 note : All above is my opinion unless specified otherwise. 9:30, Computing Center: Mainserver died. Hairdo okay.

1 0

X11, dhcp-hostname und Log Problem mit autoyast
by Oliver Osburg 29 Nov '04

29 Nov '04

Hallo zusammen, Ich habe folgendes Problem mit autoyast: Nachdem ich fast fertig war mit dem Clonen von Thinkpads, ergeben sich aus bislang ungeklärter Ursache folgende Probleme: a) Der dhcp Hostname wird nicht korrekt gesetzt b) X11 wird nicht mehr konfiguriert, geht aber trotzdem in Runlevel 5. c) User werden nicht mehr angelegt. Es sieht so aus, als ob die gesamte <configure> section einfach ignoriert wird. Die Section sieht so aus: ---snip--- <configure> <groups config:type="list"> <group> <groupname>video</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>audio</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>dialout</groupname> <userlist>user2,user4,user2,user1</userlist> </group> <group> <groupname>uucp</groupname> <userlist>user2,user4,user2,user1</userlist> </group> </groups> <networking> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <device>eth0</device> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>coling.uni-jena.de</domain> <hostname>dhcp</hostname> <nameservers config:type="list"> <nameserver>141.35.1.16</nameserver> </nameservers> <searchlist config:type="list"> <search>coling.uni-jena.de</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user3</fullname> <gid>100</gid> <home>/home/user4</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1002</uid> <user_password>PASS</user_password> <username>user4</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user2</fullname> <gid>100</gid> <home>/home/user2</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1001</uid> <user_password>PASS</user_password> <username>user2</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user1</fullname> <gid>100</gid> <home>/home/user1</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>PASS</user_password> <username>user1</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname> user2</fullname> <gid>100</gid> <home>/home/user2</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1003</uid> <user_password>PASS</user_password> <username>user2</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname>root</fullname> <gid>0</gid> <home>/root</home> <password_settings> <expire></expire> <flag></flag> <inact></inact> <max>10000</max> <min>0</min> <warn></warn> </password_settings> <shell>/bin/bash</shell> <uid>0</uid> <user_password>PASS</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">true</enable_3d> <monitor> <display> <frequency config:type="integer">75</frequency> <height config:type="integer">1050</height> <width config:type="integer">1400</width> </display> <monitor_device>1400X1050@75HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <window_manager>kde</window_manager> </x11> </configure> ---snap--- Software selection funktioniert, auch Partitionierung fuktioniert wunderbar. Am seltsamsten: ich hatte auch ein pre-script drin, welches auch in der configure-section drin ist...das ging auch. Das oben genannte aber nie. Ich finde auch keine richtig aussagefähigen Logs, ausser jenem hier: ---snip--- 2004-11-29 14:07:05 <5> linux(997) [ui-ncurses] YNCursesUI.cc(idleLoop):163 idleLoop error in select() (9) 2004-11-29 14:07:05 <5> linux(997) [ui-ncurses] YNCursesUI.cc(idleLoop):163 idleLoop error in select() (9) ---snap--- Aber mir sagt das nichts... Ich verwender SuSE 9.1 Professional. Herzliche Grüße: Oliver Osburg -- - user1 - System Architect JULIE Group Jena University - email: o.user1(a)uni-jena.de phone: +493641 9 44 324 note : All above is my opinion unless specified otherwise. 9:30, Computing Center: Mainserver died. Hairdo okay.

1 0

Supportanfrage
by Harald Piasecki 28 Nov '04

28 Nov '04

Registriecode: 43937023212632 Benutzerkennung:harald01 Passwort:vfhqgs Sehr geehrte Damen und Herren, ich habe SUSE 9.2 aufgespielt, und seitdem habe ich Probleme mit meinem CDROM- Laufwerk in der Bedienebene KONQUEROR! folgende Fehlermeldungen werden angezeigt: Ordner /media/cdrom läßt sich nicht öffnen!! Ausserdem beim einbinden in die Bedienoberfläche Kdesktop wird folgendes angezeigt: Nur root kann /dev/cdrom von /media/cdrom unmounten!! Frage : wo liegt hier der Fehler? (ich habe schon 2x ein UP-Date vorgenommen, Original CD von SUSE) Eine kleine Anmerkung: es ist nicht sehr hilfreich nur Literaturhinweise o.ä. zu schicken, unter einem SUPPORT verstehe ich etwas anderes!! Vielen Dank! Mit freundlichen Grüssen Harald Piasecki

1 0

RE: [suse-autoinstall] customizing initrd
by Thomas Mieslinger 26 Nov '04

26 Nov '04

> Well I think the problem is that during uncompression I get this message. > > root@deinst01> gzip -d initrd.gz > > gzip: initrd.gz: decompression OK, trailing garbage ignored > > when I recompress this file it is smaller than the original and > doesn't boot anymore. > > What is that "trailing garbage ignored"? > > regards Thomas > -- > GLS IT Services > Thomas Mieslinger > GLS Germany Str. 1-7 fon: +49 6677 17 463 > 36286 Neuenstein fax: +49 6677 17 111 > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > <fraser_bailey(a)agilent.com> schrieb am 25.11.2004 20:09:57: > > > That should work, but you need to gzip -9c because otherwise the > > initrd can't be uncompressed. > > > > -----Original Message----- > > From: Thomas Mieslinger [mailto:Thomas.Mieslinger@gls-itservices.com] > > Sent: Thursday, November 25, 2004 7:08 PM > > To: suse-autoinstall(a)suse.com > > Subject: [suse-autoinstall] customizing initrd > > > > > > > > > > > > > > Hello List, > > > > I need to update the content of the 5mb initrd file that resides on the > > tftpserver. gunziping, mounting minix fs changing it and gzipping it > > doesn't do the trick. > > > > How does suse/novell create this file? > > > > Thanks in advance > > > > Thomas > > -- > > GLS IT Services > > Thomas Mieslinger > > GLS Germany Str. 1-7 fon: +49 6677 17 463 > > 36286 Neuenstein fax: +49 6677 17 111 > > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >

4 6

SuSE 9.1 vnc install.
by Miro B. 26 Nov '04

26 Nov '04

Hi List. I am having trouble with SuSE 9.1 vnc authentication! It works fine on our local network, but when trying to do a vnc install an a remote computer, the vnc authentication fails! The Tightvnc applet starts up fine but the password is contantly rejected! I am getting a error message that says something like this: "error vncpassword.arg" Here is a snippet from the info file. -----------------------snip----------------------------------------- PROMPT 1 DEFAULT install TIMEOUT 50 label install KERNEL img/suse9.1/linux append install=<instdir> ip=<hostip> netm=<netmask> ramdisk_size=60000 initrd=<path to initrd> root=/dev/ram3 vga=788 vnc=1 vncpassword=somepass --------------snip-------------------------------------------- Thanks in advance. Miro B.

1 0

customizing initrd
by Thomas Mieslinger 25 Nov '04

25 Nov '04

Hello List, I need to update the content of the 5mb initrd file that resides on the tftpserver. gunziping, mounting minix fs changing it and gzipping it doesn't do the trick. How does suse/novell create this file? Thanks in advance Thomas -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com

2 1

RE: [suse-autoinstall] customizing initrd
by fraser_bailey＠agilent.com 25 Nov '04

25 Nov '04

That should work, but you need to gzip -9c because otherwise the initrd can't be uncompressed. -----Original Message----- From: Thomas Mieslinger [mailto:Thomas.Mieslinger@gls-itservices.com] Sent: Thursday, November 25, 2004 7:08 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] customizing initrd Hello List, I need to update the content of the 5mb initrd file that resides on the tftpserver. gunziping, mounting minix fs changing it and gzipping it doesn't do the trick. How does suse/novell create this file? Thanks in advance Thomas -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com -- 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] Install using FTP
by Robert Morrow 25 Nov '04

25 Nov '04

I have tried many combinations with that. I have tried with the trailing / and also tried to use a . to indicate current directory. I try to take a look at the install.inf file but it passes so quickly I am not able to get the information I need. could you give me a sample syntax you would use? The install account drops directly into the directory where it is installing from so there will be no FTP://server/"dir". could that be the problem? Robert Morrow >>> Anas Nashif <nashif(a)suse.de> 11/23/04 9:34 PM >>> Try having the complete URL in "install" with trailing slash and remove installdir. You can try those options directly on the command line till it works. You can also install manually and when yast2 starts switch to the console and look into the file /etc/install.inf and see what the install URL is like, which you can use in the info file for automated installation. Anas Robert Morrow wrote: > I have set up an autointall and it works fine when I have it set up with > NFS. I created an info file with all the information need to log into > the server. But it tells me it can not find the instalation source. If > i manualy go threw the steps i can use the same ftp to install it. here > is the info file > > InstMode: ftp > install: ftp://**********.kumc.edu > username: ******** > password: ***************** > InstallDir: / > netdevice: eth0 > server: *******.kumc.edu > usedhcp: 0 > netmask: 255.255.255.0 > gateway: 10.13.6.1 > autoyast: floppy > > > If anyone has any comments I could use the help. > Thanks > Robert Morrow > > >

2 1

Antwort: Re: [suse-autoinstall] Prob with multiple sles8 baseddistributionson one cdrom [FinanzIT: Viruscheck]
by Markus.Steinfelder＠finanzit.com 25 Nov '04

25 Nov '04

Anas Nashif <nashif(a)suse.de> An: Markus.Steinfelder(a)finanzit.com Kopie: suse-autoinstall(a)suse.com 23.11.2004 03:42 Thema: Re: [suse-autoinstall] Prob with multiple sles8 based distributionson one cdrom [FinanzIT: Viruscheck] Markus.Steinfelder(a)finanzit.com wrote: > Hi, > > I want to install multiple sles8 based distributions form one cdrom/dvd. I > have created an image with the following layout: > > ../boot > ../boot/loader > ../media.1 > ../pf > ../pf/serv1 > ../pf/serv1/suse > ../pf/serv1/suse/i386 > ../pf/serv1/suse/i586 > ../pf/serv1/suse/i686 > ../pf/serv1/suse/noarch > ../pf/serv1/suse/setup > ../pf/serv1/suse/setup/descr > ../pf/serv1/boot > ../pf/serv1/media.1 > ../pf/serv2 > ../pf/serv2/suse > ../pf/serv2/suse/i386 > ../pf/serv2/suse/i586 > ../pf/serv2/suse/i686 > ../pf/serv2/suse/noarch > ../pf/serv2/suse/setup > ../pf/serv2/suse/setup/descr > ../pf/serv2/boot > ../pf/serv2/media.1 > > serv1 and serv2 have different incompatible software stacks. So I have two > complete copies of distributions parallel on the cdrom but only one > bootloader.... > > When I run autoyast via tftboot/nfs everythings works fine using the > following isolinux.cfg: > DEFAULT serv1 > DISPLAY /pxelinux.cfg/msg > TIMEOUT 150 > PROMPT 1 > # srv1 > label srv1 > kernel linux > append initrd=initrd install=nfs://192.168.0.1/pf/serv1 > autoyast=nfs://192.168.0.1/pf/serv1/autoinst.serv1.xml textmode=1 > # srv2 > label srv2 > kernel linux > append initrd=initrd install=nfs://192.168.0.1/pf/serv2 > autoyast=nfs://192.168.0.1/pf/serv2/autoinst.serv2.xml textmode=1 > > When I run autoyast from cdrom with the following isolinux.cfg > DEFAULT serv1 > DISPLAY msg > TIMEOUT 150 > PROMPT 1 > # srv1 > label srv1 > kernel linux > append initrd=initrd install=cdrom:/ > autoyast=device://sr0/pf/serv1/autoinst.serv1.xml textmode=1 > # srv2 > label srv2 > kernel linux > append initrd=initrd install=cdrom:/ > autoyast=device://sr0/pf/serv2/autoinst.serv2.xml textmode=1 > > I get the Error "Fehler bei der Konfiguration der Sofware Auswahl". Some > tests have shown that autoyast wants to read the sel-files and the packages > file from /suse/setup/descr instead of /pf/serv1/suse/setup/descr (If I > copied one version of it to the /suse/setup/descr directory, autoyast works > fine). I think the problem is in the install parameter and autoyast can't > find the special "root-directory" of the distribution but I havn't found > any documentation about it. Where are the differences between cdrom and nfs > installation? > Beside the fact that mutiple products on one CDs does not work, although it is actually implemented, but was never tested, you boot parameter cant make it work. How do you expect yast to know where the packages are when you specify install=cdrom:/ in both cases? YaST knows nothing about /pf/serv1 and /pf/serv2 Anas Anas, I have tried several install-parameter-combinations (i.e. install=device:/.., install=cdrom:/pf...) but they don't work as I hope... Also an install-path relative to the autoinst.xml-file doesn't work. I havn't found a complete list/documentation of install parameters in the AutoYaST guide. Is there a documentation about this paramter available? Markus

2 1

Install using FTP
by Robert Morrow 23 Nov '04

23 Nov '04

I have set up an autointall and it works fine when I have it set up with NFS. I created an info file with all the information need to log into the server. But it tells me it can not find the instalation source. If i manualy go threw the steps i can use the same ftp to install it. here is the info file InstMode: ftp install: ftp://**********.kumc.edu username: ******** password: ***************** InstallDir: / netdevice: eth0 server: kumc-ldm.kumc.edu usedhcp: 0 netmask: 255.255.255.0 gateway: 10.13.6.1 autoyast: floppy If anyone has any comments I could use the help. Thanks Robert Morrow

1 0

BUG: Incorrect runlevel-entry created with the autoyast tool?
by Hans Kamm 23 Nov '04

23 Nov '04

Hi, I think there is a bug in the yast autoinstall-tool to create the autoinst.xml. This code will be created (using 2.9.45-0.2). <runlevel> <default>3</default> </runlevel> Shouldn't it be: <runlevels> <default>3</default> </runlevels> as mentioned in the documentation and runlevels.dtd. For a long time I mentioned here a bug with the DTD-file (http://lists2.suse.com/archive/suse-autoinstall/2004-Aug/0068.html). As far as I know the patch is not avaible in any rpm-file? Greets Hans _________________________________________________________________ Die rote Karte für lästige E-Mails. MSN Hotmail mit Junk-Mail-Filter. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt kostenlos anmelden!

2 1

Boot.iso for SuSE 9.2
by Alexander.Gehrig＠rsd.rohde-schwarz.com 23 Nov '04

23 Nov '04

Hi All! Where i can get the boot.iso for SuSE 9.2? Of course i can use the first CD of the SuSE 9.2 ... but the size is much larger than only a cd with the boot needed files only. For SuSE 9.1 i can get this file form the SuSE ftp server. - Where i can find the file for SuSE 9.2? Thanks! Bye Alexander

1 0

Problem setting up the partition table
by Eric Schwartz 23 Nov '04

23 Nov '04

Hello all, I'm setting up a SUSE autoinstallation environment for the first time, and things are going relatively smoothly, EXCEPT... when it comes time to set up the partition table, autoyast complains that it can't set up the swap space on /dev/hda5. This is perplexing, since I only specified three partitions, including the swap space. I've included the pertinent part of the xml config file below. Any tips would be greatly appreciated! Thanks, Eric Schwartz. <partitioning config:type=list> <drive> <device>/dev/hda</device> <initialize config:type=boolean>true</initialize> <partitions config:type=list> <partition> <crypt>twofish256</crypt> <filesystem config:type=symbol>ext3</filesystem> <format config:type=boolean>true</format> <loop_fs config:type=boolean>false</loop_fs> <mount>/boot</mount> <partition_id config:type=integer>131</partition_id> <partition_type>primary</partition_type> <size>40M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type=symbol>swap</filesystem> <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> <size>350MB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type=symbol>ext3</filesystem> <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_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>1,2,3</use> </drive> </partitioning>

3 2

Prob with multiple sles8 based distributions on one cdrom [FinanzIT: Viruscheck]
by Markus.Steinfelder＠finanzit.com 23 Nov '04

23 Nov '04

Hi, I want to install multiple sles8 based distributions form one cdrom/dvd. I have created an image with the following layout: ../boot ../boot/loader ../media.1 ../pf ../pf/serv1 ../pf/serv1/suse ../pf/serv1/suse/i386 ../pf/serv1/suse/i586 ../pf/serv1/suse/i686 ../pf/serv1/suse/noarch ../pf/serv1/suse/setup ../pf/serv1/suse/setup/descr ../pf/serv1/boot ../pf/serv1/media.1 ../pf/serv2 ../pf/serv2/suse ../pf/serv2/suse/i386 ../pf/serv2/suse/i586 ../pf/serv2/suse/i686 ../pf/serv2/suse/noarch ../pf/serv2/suse/setup ../pf/serv2/suse/setup/descr ../pf/serv2/boot ../pf/serv2/media.1 serv1 and serv2 have different incompatible software stacks. So I have two complete copies of distributions parallel on the cdrom but only one bootloader.... When I run autoyast via tftboot/nfs everythings works fine using the following isolinux.cfg: DEFAULT serv1 DISPLAY /pxelinux.cfg/msg TIMEOUT 150 PROMPT 1 # srv1 label srv1 kernel linux append initrd=initrd install=nfs://192.168.0.1/pf/serv1 autoyast=nfs://192.168.0.1/pf/serv1/autoinst.serv1.xml textmode=1 # srv2 label srv2 kernel linux append initrd=initrd install=nfs://192.168.0.1/pf/serv2 autoyast=nfs://192.168.0.1/pf/serv2/autoinst.serv2.xml textmode=1 When I run autoyast from cdrom with the following isolinux.cfg DEFAULT serv1 DISPLAY msg TIMEOUT 150 PROMPT 1 # srv1 label srv1 kernel linux append initrd=initrd install=cdrom:/ autoyast=device://sr0/pf/serv1/autoinst.serv1.xml textmode=1 # srv2 label srv2 kernel linux append initrd=initrd install=cdrom:/ autoyast=device://sr0/pf/serv2/autoinst.serv2.xml textmode=1 I get the Error "Fehler bei der Konfiguration der Sofware Auswahl". Some tests have shown that autoyast wants to read the sel-files and the packages file from /suse/setup/descr instead of /pf/serv1/suse/setup/descr (If I copied one version of it to the /suse/setup/descr directory, autoyast works fine). I think the problem is in the install parameter and autoyast can't find the special "root-directory" of the distribution but I havn't found any documentation about it. Where are the differences between cdrom and nfs installation? Greets Markus Steinfelder

2 1

rescue system with remote access
by Benjamin Indermühle 19 Nov '04

19 Nov '04

This might not be the right mailing list, but i can try. I am developing a rootServer system for our company. We will offer SuSE with on those machines. The autoinstall task was quite easy to implement, i dont have big problems with it at all. My question is about the rescue system which comes with suse. Which I also would like to offer. Is there a way to tell it, to configure the network interface and ssh for example. I havent found rearly any documention on the repair system. and nothing on how to pass parameters to it, while starting it. thanks a lot for your help Benjamin Indermühle -- *~*~* *~*~* We are connecting the world ! *~*~* *~*~* SolNet - Internet Solution Provider Bechburgstrasse 29, 4528 Zuchwil, Switzerland Phone: +41 32 686 82 82, Fax: +41 32 685 96 13 WWW: http://www.solnet.ch - E-Mail:ib@solnet.ch *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~*~*

1 0

SuSE 9.2 DVD on x86_64
by Egan Ford 19 Nov '04

19 Nov '04

What do I need in my .xml file to tell SuSE 9.2 autoyast to install the x86_64 binaries on x86_64 boxes? Currently it is installing the 32bit code. Thanks.

3 3

lan configuration
by Michael Shannon 18 Nov '04

18 Nov '04

Is there a way to configure lan interfaces from a scriptable cli tool instead of using yast? Neither the ncurses or x11 versions of yast seem to be very script friendly. We have tools that configure dns, ntp and mail configurations based on the ip address of the host, so what I'd really like to do is something right along these lines: a) Write a tool that enters the ip address/netmask and default route of eth0 (and the corresponding files in /etc/sysconfig/network). b) Call the tool we already use to configure dns/ntp/mail Having to run "yast lan" is awfully time consuming when all we really need is the interface up to finish the rest of our configuration. I know I can configure the interfaces with ifconfig and the routes with route, but those utilities don't write out the results to /etc/sysconfig/network/* Our machines get installed on a dhcp network in staging then get moved to a different network once everything but the network is configured. Thanks, -m

1 0

RE: lan configuration
by Michael Shannon 18 Nov '04

18 Nov '04

Scripting this was much easier than I had anticipated, thanks for playing :-) -m ________________________________ From: Michael Shannon Sent: Thursday, November 18, 2004 8:23 AM To: 'suse-autoinstall(a)suse.com' Subject: lan configuration Is there a way to configure lan interfaces from a scriptable cli tool instead of using yast? Neither the ncurses or x11 versions of yast seem to be very script friendly. We have tools that configure dns, ntp and mail configurations based on the ip address of the host, so what I'd really like to do is something right along these lines: a) Write a tool that enters the ip address/netmask and default route of eth0 (and the corresponding files in /etc/sysconfig/network). b) Call the tool we already use to configure dns/ntp/mail Having to run "yast lan" is awfully time consuming when all we really need is the interface up to finish the rest of our configuration. I know I can configure the interfaces with ifconfig and the routes with route, but those utilities don't write out the results to /etc/sysconfig/network/* Our machines get installed on a dhcp network in staging then get moved to a different network once everything but the network is configured. Thanks, -m

1 0

suse-autoinstall-unsubscribe-jbarnoh=tunku.uady.mx@suse.com
by ISC. Jesús Alfredo Barreiro noh 16 Nov '04

16 Nov '04

-----Mensaje original----- De: Anas Nashif [mailto:nashif@suse.de] Enviado el: Sunday, November 14, 2004 10:03 AM Para: suse-autoinstall(a)suse.com Asunto: Re: [suse-autoinstall] adding install sources on the command line Anas Nashif wrote: > not sure about YOU, but the regular installation sources can be added > using the following utility: > > # installation_sources -h > installation_sources: invalid option -- h > Usage: > installation_sources [-e] -a url Add source at given URL. > -e Enable source. > installation_sources -s Show all available sources. > > > For my own use I wrote a small script to add and remove sources using > the above utility, especially SLES9 network sources, take a look at > > http://www.suse.com/~nashif/add-source.sh > Should be http://www.suse.com/~nashif/add-sources.sh Anas > > Anas > > > > Michael Shannon wrote: > >> >> >> >> >> Is there a way to add and remove install and you sources on the command >> line? >> >> >> >> Something like >> >> >> >> yast inst_source server1/core9 server1/sles9 server1/otherstuff >> >> yast you_server servername >> >> yast you_server -remove server >> >> >> >> Thanks, >> >> >> >> -m >> >> >> >> > -- 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] Can not find source
by fraser_bailey＠agilent.com 16 Nov '04

16 Nov '04

How do you provide the info file on the cd? See http://lists2.suse.com/archive/suse-autoinstall/2004-Oct/0071.html for how to add the info file to a cd. -----Original Message----- From: Robert Morrow [mailto:rmorrow@kumc.edu] Sent: Monday, November 15, 2004 8:43 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Can not find source I created a autoinst.xml file and every time I try to boot to it, I get an error:" Could not find the SUSE Linux Enterprise Sever 9 installation source". I am booting to the cd so I have tried to specify it with an info file but still do not have any luck. Robert Morrow -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Can not find source
by Robert Morrow 15 Nov '04

15 Nov '04

I created a autoinst.xml file and every time I try to boot to it, I get an error:" Could not find the SUSE Linux Enterprise Sever 9 installation source". I am booting to the cd so I have tried to specify it with an info file but still do not have any luck. Robert Morrow

1 0

online_update breaks
by m.frerichs 15 Nov '04

15 Nov '04

Hallo, after autoinstallation of SuSE 9.1 64 bit , I would like to install all security and recommended Patches with online_update. In the past the following commands succeeded: online_update -u ftp://ftp.suse.com/pub/suse -d -s -V to download patches online_update -u ftp://ftp.suse.com/pub/suse - k security online_update -u ftp://ftp.suse.com/pub/suse security to install patches Now online_update hangs and window is locked always at the same patch freeradius displaying special characters: /var/lib/YaST2/you/mnt/i386/update/9.1/rpm/i586 is not installed online_update -u ftp://ftp.suse.com/pub/suse -d -s -V -k recommended Types of patches to be installed: recommended Server URL: ftp://ftp.suse.com/pub/suse Server Name: Directory File: Path 0: ./x86_64/update/9.1/patches Patches: fetchmsttfonts (Optional): Download Microsoft(r) TrueType Core Fonts ..... gpdf (Security): Ein GNOME-PDF-Betrachter RPM: gpdf 0.112.1-26.5 x86_64 (installed: 0.112.1-26.3 [older]) freeradius (Security): Ein Ã¤uÃ By the way installing a special patch never succeeded: online_update -u ftp://ftp.suse.com/pub/suse --product popt --> ERROR(Media:file not found)[Couldn't cd to popt] Thanks for your answers and improvements +----------------------------------------------------------------------+ | Marianne Frerichs | | Zentralinstitut fuer Angewandte Mathematik | | Forschungszentrum Juelich GmbH | | D-52425 Juelich | | Phone: +49 02461 61-1466 | | Email: M.Frerichsfz-juelich.de Fax: +49 02461 61-6656 | +----------------------------------------------------------------------+

1 0

Antwort: Re: [suse-autoinstall] How do I prevent re-install? [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 15 Nov '04

15 Nov '04

Hi, why not create a default entry in the /tftpboot/pxelinux.cfg/[IP address] for booting from local disc and another entry for installation? The same way suse does it on the installation medium. Greets Hartmut Aaron Amauba <aapa20032003@yah An: Dave Thacker <dthacker(a)omnihotels.com>, suse-autoinstall(a)suse.com oo.com> Kopie: Thema: Re: [suse-autoinstall] How do I prevent re-install? [FinanzIT: Viruscheck] 12.11.2004 17:54 This is not a clean way, but what I do is to move the config file from /tftpboot/pxelinux.cfg/[IP address] to another name (I chose [ip Address] _local). that way the machine will boot from local disk. I just run a script when I want to install a machine that 1st moves the config file to /tftpboot/pxelinux.cfg/[IP address], then after some time (10 min) renames the file to something that will not be found. Im sure there is a cleaner way to do this ..... Dave Thacker <dthacker(a)omnihotels.com> wrote: Goal: Unnattended install of SUSE 9.1 using autoyast2. I've successfully done a minimal installation using auto-yast on SuSE 9.1. After the client finished install, it rebooted. It's set to boot from PXE so it started up the entire install process. and started to install again. I have false set in the config file. In chapter 4 of the docs it states: "Change starting from SUSE Linux 9.1/SLES9 The reboot property in the mode resource was used to force a reboot after initial system setup and before the system is rebooted for the first time. Currently after initial installation all systems must reboot, which makes thes option obsolete." Given that a reboot is inevitable, how do I stop a perpetual install loop? DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

adding install sources on the command line
by Michael Shannon 14 Nov '04

14 Nov '04

Is there a way to add and remove install and you sources on the command line? Something like yast inst_source server1/core9 server1/sles9 server1/otherstuff yast you_server servername yast you_server -remove server Thanks, -m

2 2

Multi CD install cd reboots and re-installs after first CD
by Dave Thacker 14 Nov '04

14 Nov '04

Goal: Unattended install of SUSE 9.1 I'm able to do a successful minimal install of SUSE 9.1. I've added the gcc group to the software list to verify that I have my archive cataloged correctly. After installing CD 1, the client machine reboots and starts the install process all over again. (variation of perpetual install loop I reported earlier today) How do I get autoyast to read the next CD? More importantly, how do I stop the client from rebooting? Has anyone done a multi-cd install successfully on SUSE 9.1? DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)

2 1

How do I prevent re-install?
by Dave Thacker 13 Nov '04

13 Nov '04

Goal: Unnattended install of SUSE 9.1 using autoyast2. I've successfully done a minimal installation using auto-yast on SuSE 9.1. After the client finished install, it rebooted. It's set to boot from PXE so it started up the entire install process. and started to install again. I have <forceboot config:type="boolean">false</forceboot> set in the config file. In chapter 4 of the docs it states: "Change starting from SUSE Linux 9.1/SLES9 The reboot property in the mode resource was used to force a reboot after initial system setup and before the system is rebooted for the first time. Currently after initial installation all systems must reboot, which makes thes option obsolete." Given that a reboot is inevitable, how do I stop a perpetual install loop? DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)

3 2

How to set up PXE server?
by Hugo 12 Nov '04

12 Nov '04

Hello! I asked this on another SuSE list and I was directed here. I tried to search the archives as well as google for the answers, but I really can't find any good tutorial or how to. Here is my problem: I have an old laptop without CD-drive. It really needs a new install and doing it from floppy isn't really a option. But it can boot from the network. Two uses for that computer (dual boot): 1) general web - for this I was planning SuSE (400MHz Celeron, with 128Mb) 2) Kids' CD-roms for my kid - I could not get these running with wine... so it means either win98 or win2k. The installed (and broken) OS is Win98, but I have original installation CD for both windows. I have found that PXE is something connected to a DHCP server. But the first problem is that I already have a DHCP server on my network (NAP box). I was planning on using my SuSE 9.1 pro for suplying the installations for the laptop, so how do I do this? Next problem is the windows... The only guides that I have seen involve booting linux... although not very throughout help for that either. I'd like to start the windows or SuSE 9.1 installation over the network. How do I prepare the installation CD's for this? I'm also planning to install my little old Norton Ghost 2003 for backup in which ever windows ends up working better with the CD-roms. Restoring the image means booting from floppy (which I can do when I get them installed in the first place) but it would be much nicer if I could boot that floppy from the network also (i.e. when the win98 gets messed up, just boot from the net and reinstall the image for win98.) I believe that I should be able to do this with SuSE 9.1... but how? -- HG

2 2

Keeping partitions with SuSE 9.2
by Andreas Haupt 12 Nov '04

12 Nov '04

Hello, when upgrading a host to a newer SuSE version I used the partitioning feature "Using existing mount table" with SuSE 9.1. This is explained under: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Partitioning.… With AutoYast in SuSE 9.2 this does not work any more. Yast complains with "Error: No proposal" under "Partitioning" when it shows the installation summary before the real installation. Has this feature been dismissed or is there a different syntax now? Thanks in advance Andreas -- | Andreas Haupt | E-Mail: andreas.haupt(a)hmi.de | Hahn-Meitner-Institut (DN) | WWW: | Glienicker Straße 100 | Phone: +49/30/8062-2597 | 14109 Berlin | Fax: +49/30/8062-2096

1 0

dtd problems on SLES9 PPC
by Frank Steiner 11 Nov '04

11 Nov '04

Hi, I'm installing SLES 9 on IBM pSeries (power4 cpus). I first installed it manually and grepped the xml files from cloning the machine to build a general installation. Two proplems arise: 1) That's what cloning the machine and saving the profile gives me for the bootloader: <bootloader> <activate config:type="boolean">true</activate> <board_type>chrp</board_type> <default>linux</default> <loader_device>/dev/sda1</loader_device> <loader_type>ppc</loader_type> <location>custom</location> <of_defaultdevice config:type="boolean">true</of_defaultdevice> <prep_boot_partition>/dev/sda1</prep_boot_partition> </bootloader> However, checking the file with nsgml and the dtd files from the autoyast2-installation.rpm tells me: nsgmls:profiles/part_hal_keep.xml:7:28:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:7:37:E: element "activate" undefined nsgmls:profiles/part_hal_keep.xml:8:17:E: element "board_type" undefined nsgmls:profiles/part_hal_keep.xml:9:14:E: document type does not allow element "default" here nsgmls:profiles/part_hal_keep.xml:13:36:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:13:45:E: element "of_defaultdevice" undefined nsgmls:profiles/part_hal_keep.xml:14:26:E: element "prep_boot_partition" undefined I ignore it because the xml file works for installing further machines, but I guess the dtd files should be corrected. 2) For checking the profiles while writing them, I copied the dtd files to a path relative to my profiles. My autoyast dir that I pass to autoyast has the structure rules/ profiles/ dtd/ where rules/ contains rules.xml. All my manually written profiles as well as the rules.xml start with <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> which works well when I check my files with nsgml. For installing, I use a rules.xml with: <rule> <arch> <match>ppc64</match> <match_type>exact</match_type> </arch> <result> <profile>profiles/lmuppc.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <hostaddress> <match>141.84.1.134</match> <match_type>exact</match_type> </hostaddress> <result> <profile>profiles/part_hal_keep.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> where both of the profiles containt the "../dtd.." stuff. When I run the installation with this rules.xml, I get an error message /tmp/YaST2-.../rules/profiles/lmuppc.xml:2: warning: failed to load external entity "/tmp/YaST2-.../rules/dtd/profile.dtd" <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> Likely, the dtd file were not copied over to the /tmp/YaST2-.../rules/ dir. But, this error does not occur if I put the contents of part_hal_keep.xml into lmuppc.xml and work with only one profile in rules.xml! Then the whole installation runs through. Thus, only when using more than one profile in rules.xml, it fails. Any thoughts? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

RE: [suse-autoinstall] upgrading from 9.0 to 9.2
by Ryan Allen 11 Nov '04

11 Nov '04

> -----Original Message----- > From: Thomas Schweikle [mailto:tps@vr-web.de] > Sent: Wednesday, November 10, 2004 1:50 AM > To: Ryan Allen > Subject: Re: [suse-autoinstall] upgrading from 9.0 to 9.2 > > Ryan Allen schrieb: > > > > > I'm quite lost. It currently appears that we cannot upgrade from 9.0 > to > > 9.2. I've set up the system to PXE boot, and transfer the files to the > > client with HTTP. The HTTP log on the 9.2 PXE/install server is > > reporting the following: > > > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not exist: /srv/www/htdocs/suse/media.1/info.txt > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not exist: /srv/www/htdocs/suse/part.info > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not > > exist: /srv/www/htdocs/suse/driverupdate > > > > And it's right, those files do not exist. What are the secrets for > > getting autoinstall running on 9.2?? > > These Files exist on DVD an CDROM. Try copying them from there. > > -- > Thomas This is incorrect. The three files listed above are not included in the 9.2 media. They are not on the CDs or the DVDs. I appears that autoinstall is completely broken with 9.2. I have not heard from anybody on this list that has info on 9.2. Perhaps I am the only one who has tried it? Anas?? Thanks, -- Ryan

2 1

evms
by Edward Tast 10 Nov '04

10 Nov '04

Hello, Does anyone know if it is possible to setup evms with autoinstall? If so, can you please provide an example or point me in the right direction? Thanks much.....

1 0

RE: [suse-autoinstall] upgrading from 9.0 to 9.2
by Ryan Allen 09 Nov '04

09 Nov '04

Just wondering if anybody got this message.... I'm quite lost. It currently appears that we cannot upgrade from 9.0 to 9.2. I've set up the system to PXE boot, and transfer the files to the client with HTTP. The HTTP log on the 9.2 PXE/install server is reporting the following: [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/media.1/info.txt [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/part.info [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/driverupdate And it's right, those files do not exist. What are the secrets for getting autoinstall running on 9.2?? Thanks! -- Ryan > -----Original Message----- > From: Ryan Allen [mailto:r.allen@f5.com] > Sent: Monday, November 08, 2004 12:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] upgrading from 9.0 to 9.2 > > > > 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

Resolving dependencies
by Dave Thacker 09 Nov '04

09 Nov '04

Greetings list! We're about to embark on an adventure using autoyast2 on 10 new servers. Some of these servers will run heartbeat and/or ultramonkey, which requre changes from the default kernel. Once I've created an autoyast config, is there a way to test it for dependencies? If not, how can I capture the results of a working install and import them into autoyast2? TIA DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)

1 0

Re: [suse-autoinstall] New Stupid user Questions
by Robert Morrow 09 Nov '04

09 Nov '04

I have tryed to remove all executable permitions of the file and it still does not work... >>> Johannes Klug <Johannes.Klug(a)dreger.de> 11/09/04 7:52 AM >>> "Robert Morrow" <rmorrow(a)kumc.edu> wrote on 08.11.2004 15:46:07: > I have been put incharge of setting up an auto-install for 30 + > machines. I have does this befor using the autoyast utility and never > editing the xml at all. But as i am trying to do it again I can not seem > to get the install to read my autoinst.xml file. I am running Suse > Enterprise 9.1. > > Robert Morrow Hello Robert, check permissions of autoinst.xml. If it's executable, yast won't read it. I had this problem after carrying my xml file to another using a floppy disk. Regards, Johannes Klug

1 0

New Stupid user Questions
by Robert Morrow 09 Nov '04

09 Nov '04

I have been put incharge of setting up an auto-install for 30 + machines. I have does this befor using the autoyast utility and never editing the xml at all. But as i am trying to do it again I can not seem to get the install to read my autoinst.xml file. I am running Suse Enterprise 9.1. Robert Morrow

2 1

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