From Thomas.Necker@marconi.com Mon Dec 1 16:04:24 2003 From: Thomas Necker To: autoinstall@lists.opensuse.org Subject: Merging classes Date: Mon, 01 Dec 2003 16:04:24 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2233481113943761679==" --===============2233481113943761679== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi I have a problem merging classe with YaST in SuSE 9.0. If I have the following file 0 udp /usr/sbin/in.tftpd tftp xinetd 0 true /tftpboot and merged with the following file using AutoYaST 0 tcp /usr/sbin/in.fingerd finger xinetd 0 The resulting file was 0 tcp /usr/sbin/in.fingerd finger xinetd 0 true /tftpboot So the xinetd configuration for the tftp server is not contained in the result. Why? Thanks, Thomas --===============2233481113943761679==-- From nashif@suse.de Tue Dec 2 04:17:16 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Merging classes Date: Tue, 02 Dec 2003 04:17:16 +0000 Message-ID: <3FCC11A0.4050508@suse.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0225042948369063006==" --===============0225042948369063006== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Thomas Necker wrote: > Hi > > I have a problem merging classe with YaST in SuSE 9.0. > > If I have the following file > > > > xmlns:config="http://www.suse.com/1.0/configns"> > > > 0 > > > udp > > /usr/sbin/in.tftpd > tftp > > > xinetd > 0 > > > true > /tftpboot > > > > > and merged with the following file using AutoYaST > > > > xmlns:config="http://www.suse.com/1.0/configns"> > > > 0 > > > tcp > > /usr/sbin/in.fingerd > finger > > > xinetd > 0 > > > > > The resulting file was > > > > xmlns:config="http://www.suse.com/1.0/configns"> > > > 0 > > > tcp > > /usr/sbin/in.fingerd > finger > > > xinetd > 0 > > > true > /tftpboot > > > > > So the xinetd configuration for the tftp server is not contained in the > result. Why? It is merged, one configuration did overwrite the other one, however, to have both list entries, you dont want to merge the "conf" enteries. This is a general problem with lists, it cant be handled automatically. Sometimes you want the whole configuration in a list to be replaces, in this case you want them to be "added". The merge style sheet can handle this, however only for one element in 9.0. See /usr/share/autoinstall/xslt/merge.xslt the parameter is dontmerge. In /usr/share/YaST2/modules/AutoinstClass.ycp line 67 dontmerge is set to "addon" which is for the package selections, if you change that to "conf" it will not merge the conf files in the examples above. I fixed that for upcoming releases to handle some more dontmerge parameters which can be configured by the user... Anas > > Thanks, > Thomas > --===============0225042948369063006==-- From nashif@suse.de Tue Dec 2 04:17:19 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Integrate a 3rd party module into an autoyast configuration Date: Tue, 02 Dec 2003 04:17:19 +0000 Message-ID: <3FCC11DC.1030206@suse.de> In-Reply-To: <41071631DA193B4B923CA3A9783207B20485C61A@cvx09abnlw.BN.DeTeMobil.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4955682911174838806==" --===============4955682911174838806== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Schlabach, Torsten wrote: > Dear list, >=20 > we have some machines that require a vendor supplied kernel module for thei= r RAID controller. >=20 > How could we integrate such a module into an autoyast installation? >=20 > P.S.: Bear with me if this has been asked before, but I was not able to fin= d any _searchable_ archive of this list. Take a look at ftp://ftp.suse.com/pub/people/hvogel/Update-Media-HOWTO/index.html Anas >=20 > ----------------------------------------- > Torsten Schlabach > +49 228 936 34735 > torsten.schlabach(a)t-mobile.de > T-Mobile Deutschland GmbH > ----------------------------------------- >=20 >=20 --===============4955682911174838806==-- From nashif@suse.de Tue Dec 2 04:18:55 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Q: Installation repository from SP3 CD images Date: Tue, 02 Dec 2003 04:18:55 +0000 Message-ID: <3FCC12A9.1060107@suse.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2254867642232078971==" --===============2254867642232078971== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Harald.Milz(a)computacenter.com wrote: > Hi, > > does anyone have a detailed instruction how to build an installation > repository for SP3 (2 CDs - which is which???) using the ISO images > directly, i.e. without copying everything to a filesystem? I can't see how > the available documentation applies to the set now... TIA! Again, i am not sure it will work with NFS, with http or ftp it might work with loop mounted images. Take a look at this draft i am working on: www.suse.de/~nashif/multiplesource-sa.pdf Anas > > Mit freundlichen Gruessen - Best regards > > Harald Milz --===============2254867642232078971==-- From nashif@suse.de Tue Dec 2 04:19:49 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] strange behaviour yast2 in graphical mode Date: Tue, 02 Dec 2003 04:19:49 +0000 Message-ID: <3FCC12E0.7080309@suse.de> In-Reply-To: <8C6ADF4772B7D511A3E40008C7BB878A014E5837@chopin.hitt.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0547851944453539432==" --===============0547851944453539432== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi, Is that SLES8/ SuSE 8.1? Anas Berge, Harry ten wrote: > Hi, > > When autoinstalling I have the strange situation that yast2 crashes out of > the install when it is running in graphical mode. In a few cases I got even > a kernel panic! > If I install the machine in text mode everything is fine. Has someone got a > clue? I > > >>Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, >> > > H.J. ten Berge > Test & Integration > --===============0547851944453539432==-- From nashif@suse.de Tue Dec 2 04:20:36 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] create_package_descr Date: Tue, 02 Dec 2003 04:20:36 +0000 Message-ID: <3FCC130F.7050905@suse.de> In-Reply-To: <20031126205457.GA21959@schiele.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6125372668247760653==" --===============6125372668247760653== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Robert Schiele wrote: > On Fri, Nov 21, 2003 at 02:15:01PM -0700, Eric Whiting wrote: > >>With suse 8.x I used: >> >>/usr/lib/YaST2/bin/create_package_descr >> >>to update an install tree with latest patches. >> >>Has this utility been removed? > > > No, it is just in /usr/bin/ now. and in autoyast2-utils package. Anas > > Robert > --===============6125372668247760653==-- From berge@hitt.nl Tue Dec 2 07:36:23 2003 From: "Berge, Harry ten" To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] strange behaviour yast2 in graphical mode Date: Tue, 02 Dec 2003 07:36:23 +0000 Message-ID: <8C6ADF4772B7D511A3E40008C7BB878A014E586C@chopin.hitt.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7107834683269496960==" --===============7107834683269496960== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Nope. It's a 8.2 Pro. Regards Harry > Hi, > Is that SLES8/ SuSE 8.1? > > Anas > > Berge, Harry ten wrote: > > Hi, > > > > When autoinstalling I have the strange situation that yast2 > crashes out of > > the install when it is running in graphical mode. In a few > cases I got even > > a kernel panic! > > If I install the machine in text mode everything is fine. > Has someone got a > > clue? I > > > > > >>Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > >> > > > > H.J. ten Berge > > Test & Integration > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > --===============7107834683269496960==-- From dpc22@cam.ac.uk Mon Dec 8 17:15:42 2003 From: David Carter To: autoinstall@lists.opensuse.org Subject: AutoYaST and firewall configuration Date: Mon, 08 Dec 2003 17:15:42 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0599964276469566791==" --===============0599964276469566791== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi everyone, I'm currently playing with AutoYaST on a scratch system, with a view to using SuSE 9.0+AutoYAST in place of Redhat 9+Kickstart on some of our servers. AutoYaST works rather nicely, but I'm having a couple of teething problems which is probably down to ignorance on my part. My test install environment is based on the GRUB boot floppy found at: ftp://ftp.suse.com/pub/people/nashif/autoinstall/ I'm looking at an install environment which uses TFTP for boot images and autoyast files but which uses manually configured IP addresses supplied by the grub and autoyast configurations. I don't trust DHCP on our network, simply because of the large numbers of different groups who run servers. Problem #1: Spurious DHCP requests ================================== Unless I switch off forceboot and reboot in the autoyast.xml file: true false false the system reboots and attempts a DHCP lookup on eth0 before setting up the static IP address which I have specified in the autoyast.xml file: ... static 131.111.255.255 eth0 131.111.11.209 255.255.0.0 131.111.0.0 onboot ... Is there another way of stopping the redundant DHCP request? At best this leads to a delay until the request times out. At worse the machine could end up with an invalid configuration. Problem #2: Firewall configuration ================================== /sbin/yast2 autoyast provides a screen for configurating a firewall which generates the following in autoyast.xml: yes yes eth0 no yes no yes no yes no ssh true The yast postinstall script which runs says "Setting up firewall", and there is various output in y2log which includes: 2003-12-08 12:38:45 <1> magenta-4(2667) [YCP] clients/autoinst_configure.ycp:105 Writing configuration for firewall However, /etc/sysconfig/SuSEfirewall2 doesn't appear to get updated: -rw-r--r-- 1 root root 26770 Dec 8 12:35 SuSEfirewall2 and iptables doesn't acquire any rules. Does autoyast support SuSEfirewall yet? It is conspicuous by its absence in the documentation provided at: http://www.suse.de/~nashif/autoinstall/9.0/html/index.html Thanks in advance for any answers. -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH. --===============0599964276469566791==-- From David.Clack@Sun.COM Tue Dec 9 22:29:03 2003 From: David Clack To: autoinstall@lists.opensuse.org Subject: What kicks up YaST2 at the end of a CD install ? Date: Tue, 09 Dec 2003 22:29:03 +0000 Message-ID: <1071008654.2742.37.camel@JDS.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5240680034830511798==" --===============5240680034830511798== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, Can anyone tell me what kicks in the YaST2 configuration screens after a completed cd installation, root, user, video, etc. I need to get this to happen after an NFS autoinstallation. Thanks in advance Dave ____________________________________________________________ David Clack Sun Microsystems Senior Systems Engineer Desktop System Architect OSS OEM Software Sales 411 108th Ave. NE, Suite 600 Bellevue WA 98004 Direct : 425-369-2090 Cell: 206-265-1904 Fax: 425-369-0502 David.Clack(a)Sun.Com +++ Sent from a Sun Java Desktop System ++++ --===============5240680034830511798==-- From hellmuth@ira.uka.de Tue Dec 9 22:36:24 2003 From: Holger Hellmuth To: autoinstall@lists.opensuse.org Subject: partitioning problems Date: Tue, 09 Dec 2003 22:36:24 +0000 Message-ID: <3FD64E55.1040002@ira.uka.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9115538008272468503==" --===============9115538008272468503== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, my problem ist that I'm getting an error in partitioning (with Suse9.0), but my autoinst.xml (supplied on floppy) seems to be correct. Here the autoinst.xml, which shows no problems with xmllint -valid -noout: ------------------------------- localtime Europe/Berlin german en_US true 20_imps2 /dev/hda all Minimal kdeartwork3-sound-3.1.4-38 suse-release-9.0-6 myspell-german-20030301-45 iptables-1.2.8-71 hdparm-5.4-37 ... docbook-toys-1.51.0-141 --------------------------- The error message "An error occured while trying to create partitioning plans" appears when suse tries to "Create partition plans". Since I already installed Suse9.0 on that machine, I'm sure that "/dev/hda" is correct (and partitioning is working in principle). The partitioning part is verbatim out of the documentation. I think the same error appeared also when the partitioning part was left out altogether, but I'm not sure. As a last resort I even deleted everything between and to make sure the software part wasn't at fault, but to no avail. Any Ideas? Holger. --===============9115538008272468503==-- From jwest49@earthlink.net Wed Dec 10 05:25:35 2003 From: Gregory Baboolal To: autoinstall@lists.opensuse.org Subject: Apache2 Date: Wed, 10 Dec 2003 05:25:35 +0000 Message-ID: <1071033965.2943.4.camel@home.linux> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9135038677401608100==" --===============9135038677401608100== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, Upon installation of Suse 9.0 and selecting Apache2, and enabling the http server with perl, why is it not then possible to actually visit: localhost/cgi-perl/ i.e. the script alias doesn't seem to be active presumably (i think) because the if mod_perl.c(?) clause is not being executed? Greg. --===============9135038677401608100==-- From ce107@dam.brown.edu Thu Dec 11 01:09:54 2003 From: "C. Evangelinos" To: autoinstall@lists.opensuse.org Subject: Upgrading from 7.0 to 9.0 Date: Thu, 11 Dec 2003 01:09:54 +0000 Message-ID: <200312110105.hBB15kZ17486@fritz.dam.brown.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1607017745994175253==" --===============1607017745994175253== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi - an old machine that I've set up and has been down for quite some time has recently come back up. It's running SuSE 7.1 and I need to upgrade it to a version for which uptodate patches are provided, preferably 9.0 (but any from 7.3 and above will be better than staying at 7.1). The problem is that the machine is remotely located and I cannot simply pop in a CD and try to upgrade. The people that can do that cannot do much else so we're in a sort of a bind. Basically what I need is a way to remotely upgrade a 7.1 system that is booted normally, connected via ssh and preferably using yast2 or yast. I've already downloaded the FTP version to a location on the hard disk of the system and tried to point both yast2 and yast to it and attempt the upgrade option of the menu (hoping that it can work in this manner though I'm not sure they are meant to by design). However the format of the files used for installation seems to have changed from 8.1 onwards and it complains that it can't find /suse/setup/descr/common.pkd I then downloaded the whole of SuSE 8.0 FTP version onto the disk of the system and tried to use yast/yast2 with it. yast2 seemed to work but the upgrade option actually failed to see that the 8.0 rpms were upgrades to the 7.1 and came up with 0 (zero) packages to update. yast refused to do anything useful early on because of the differences between the 7.1 and 8.0 distributions. So the questions are: a) Can a "live" remote update from 7.0 to 7.3 or above be done connected via ssh using yast/yast2 or is it a lost cause? b) Can the upgrade be done directly to 9.0? If so how? c) If the answers to (a) and (b) are negative, any ideas on what can be done apart from installing the new O/S on a new disk, configuring everything and sending it over there? Thanks for any help, Constantinos Evangelinos --===============1607017745994175253==-- From nashif@suse.de Thu Dec 11 01:19:27 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] SWAT (Samba Web Admnistration Tool) installation with Yast2, SuSe 8.2 Date: Thu, 11 Dec 2003 01:19:27 +0000 Message-ID: <3FD7C61A.2000303@suse.de> In-Reply-To: <200310031844.32214.yvon.nedonchelle@wanadoo.fr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4875628407394701546==" --===============4875628407394701546== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable This is the wrong list for such questions. please repost on a general list. Anas Yvon Nedonchelle wrote: > Hello. > I have installed the Samba packages supplied with SuSe 8.2, using Yast2. > Samba works fine but SWAT is not usable.=20 > When calling http://localhost:901 from Konqueror, the answer is : Impossibl= e=20 > to connect to localhost (port 901). >=20 > Looks funny because I had no problem with older version of SuSe. > The various files involved, /etc/inedt, /etc/services look fine. > What should I do to obtain SWAT ? >=20 > Thanks --===============4875628407394701546==-- From nashif@suse.de Thu Dec 11 01:24:48 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Upgrading from 7.0 to 9.0 Date: Thu, 11 Dec 2003 01:24:48 +0000 Message-ID: <3FD7C6AD.2080207@suse.de> In-Reply-To: <200312110105.hBB15kZ17486@fritz.dam.brown.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6035493228218360086==" --===============6035493228218360086== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit This is the wrong list for such questions. please repost on a general list. And short answer to your question: Update from 7.0 to 9.0 can only be done if you boot into 9.0 using the CDs or any other boot media, live update is not possible, especially due to different versions of rpm, yast and others. Anas C. Evangelinos wrote: > Hi - an old machine that I've set up and has been down for quite some > time has recently come back up. It's running SuSE 7.1 and I need to > upgrade it to a version for which uptodate patches are provided, > preferably 9.0 (but any from 7.3 and above will be better than staying > at 7.1). The problem is that the machine is remotely located and I > cannot simply pop in a CD and try to upgrade. The people that can do > that cannot do much else so we're in a sort of a bind. > > Basically what I need is a way to remotely upgrade a 7.1 system that > is booted normally, connected via ssh and preferably using yast2 or > yast. I've already downloaded the FTP version to a location on the > hard disk of the system and tried to point both yast2 and yast to it > and attempt the upgrade option of the menu (hoping that it can work in > this manner though I'm not sure they are meant to by design). However > the format of the files used for installation seems to have changed > from 8.1 onwards and it complains that it can't find > /suse/setup/descr/common.pkd > I then downloaded the whole of SuSE 8.0 FTP version onto the disk of > the system and tried to use yast/yast2 with it. yast2 seemed to work > but the upgrade option actually failed to see that the 8.0 rpms were > upgrades to the 7.1 and came up with 0 (zero) packages to update. yast > refused to do anything useful early on because of the differences > between the 7.1 and 8.0 distributions. > > So the questions are: > a) Can a "live" remote update from 7.0 to 7.3 or above be done > connected via ssh using yast/yast2 or is it a lost cause? > b) Can the upgrade be done directly to 9.0? If so how? > c) If the answers to (a) and (b) are negative, any ideas on what can > be done apart from installing the new O/S on a new disk, configuring > everything and sending it over there? > > Thanks for any help, > > Constantinos Evangelinos > --===============6035493228218360086==-- From nashif@suse.de Thu Dec 11 01:24:52 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Apache2 Date: Thu, 11 Dec 2003 01:24:52 +0000 Message-ID: <3FD7C724.6080503@suse.de> In-Reply-To: <1071033965.2943.4.camel@home.linux> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1893882194923258276==" --===============1893882194923258276== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit This is the wrong list for such questions. please repost on a general list. Anas Gregory Baboolal wrote: > Hi, > > Upon installation of Suse 9.0 and selecting Apache2, and enabling the > http server with perl, why is it not then possible to actually visit: > > localhost/cgi-perl/ > > i.e. the script alias doesn't seem to be active presumably (i think) > because the if mod_perl.c(?) clause is not being executed? > > Greg. > > --===============1893882194923258276==-- From nashif@suse.de Thu Dec 11 01:24:54 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] partitioning problems Date: Thu, 11 Dec 2003 01:24:54 +0000 Message-ID: <3FD7C751.3030508@suse.de> In-Reply-To: <3FD64E55.1040002@ira.uka.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7460660879930331871==" --===============7460660879930331871== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Holger, Without the log files, there is no way we can identify why partitioning is failing. Anas Holger Hellmuth wrote: > Hi, > my problem ist that I'm getting an error in partitioning (with Suse9.0), > but my autoinst.xml (supplied on floppy) seems to be correct. > > Here the autoinst.xml, which shows no problems with xmllint -valid -noout: > ------------------------------- > > > xmlns:config="http://www.suse.com/1.0 > /configns"> > > > > localtime > Europe/Berlin > > > german > > en_US > > true > > > 20_imps2 > > > > > /dev/hda > all > > > > Minimal > > > > kdeartwork3-sound-3.1.4-38 > suse-release-9.0-6 > myspell-german-20030301-45 > iptables-1.2.8-71 > hdparm-5.4-37 > ... > docbook-toys-1.51.0-141 > > > > > > --------------------------- > > The error message "An error occured while trying to create partitioning > plans" appears when suse tries to "Create partition plans". > > Since I already installed Suse9.0 on that machine, I'm sure that > "/dev/hda" is correct (and partitioning is working in principle). The > partitioning part is verbatim out of the documentation. > > I think the same error appeared also when the partitioning part was left > out altogether, but I'm not sure. > > As a last resort I even deleted everything between and > to make sure the software part wasn't at fault, but to no avail. > > Any Ideas? > > Holger. > > > > > > --===============7460660879930331871==-- From nashif@suse.de Thu Dec 11 01:25:46 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] What kicks up YaST2 at the end of a CD install ? Date: Thu, 11 Dec 2003 01:25:46 +0000 Message-ID: <3FD7C793.8010406@suse.de> In-Reply-To: <1071008654.2742.37.camel@JDS.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1225255163804100964==" --===============1225255163804100964== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit David Clack wrote: > Hi, > > Can anyone tell me what kicks in the YaST2 configuration screens after > a completed cd installation, root, user, video, etc. > > I need to get this to happen after an NFS autoinstallation. > See /etc/init.d/boot If the file /var/lib/YaST2/runme_at_boot exists, yast2 is started Anas > Thanks in advance > Dave > ____________________________________________________________ ... > > +++ Sent from a Sun Java Desktop System ++++ > --===============1225255163804100964==-- From nashif@suse.de Thu Dec 11 01:36:05 2003 From: Anas Nashif To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] AutoYaST and firewall configuration Date: Thu, 11 Dec 2003 01:36:05 +0000 Message-ID: <3FD7C9FB.20503@suse.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2398489754043474759==" --===============2398489754043474759== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit David Carter wrote: > Hi everyone, > > I'm currently playing with AutoYaST on a scratch system, with a view to > using SuSE 9.0+AutoYAST in place of Redhat 9+Kickstart on some of our > servers. AutoYaST works rather nicely, but I'm having a couple of teething > problems which is probably down to ignorance on my part. > > My test install environment is based on the GRUB boot floppy found at: > > ftp://ftp.suse.com/pub/people/nashif/autoinstall/ And in 9.0 documentation there is a section describing how to create such a boot floppy using the latest GRUB from 9.0... > > I'm looking at an install environment which uses TFTP for boot images and > autoyast files but which uses manually configured IP addresses supplied by > the grub and autoyast configurations. I don't trust DHCP on our network, > simply because of the large numbers of different groups who run servers. > > Problem #1: Spurious DHCP requests > ================================== > > Unless I switch off forceboot and reboot in the autoyast.xml file: > > > true > false > false > > > the system reboots and attempts a DHCP lookup on eth0 before setting up > the static IP address which I have specified in the autoyast.xml file: > > > ... > > > static > 131.111.255.255 > eth0 > 131.111.11.209 > 255.255.0.0 > 131.111.0.0 > onboot > > > ... > > > Is there another way of stopping the redundant DHCP request? At best this > leads to a delay until the request times out. At worse the machine could > end up with an invalid configuration. > Hmm, this should not happen. Can you check the file /var/lib/YaST2/install.inf and see if the network values you have supplied are present there! > Problem #2: Firewall configuration > ================================== > > /sbin/yast2 autoyast provides a screen for configurating a firewall > which generates the following in autoyast.xml: > > > yes > yes > eth0 > > no > yes > no > yes > > no > yes > no > ssh > true > > > > The yast postinstall script which runs says "Setting up firewall", and > there is various output in y2log which includes: > > 2003-12-08 12:38:45 <1> magenta-4(2667) [YCP] > clients/autoinst_configure.ycp:105 > Writing configuration for firewall > > However, /etc/sysconfig/SuSEfirewall2 doesn't appear to get updated: > > -rw-r--r-- 1 root root 26770 Dec 8 12:35 SuSEfirewall2 > > and iptables doesn't acquire any rules. Does autoyast support SuSEfirewall > yet? It is conspicuous by its absence in the documentation provided at: > > http://www.suse.de/~nashif/autoinstall/9.0/html/index.html > Ok, I might need to run a test install and see what exactly happens there.. Anas > Thanks in advance for any answers. > --===============2398489754043474759==-- From dpc22@cam.ac.uk Thu Dec 11 11:14:45 2003 From: David Carter To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] AutoYaST and firewall configuration Date: Thu, 11 Dec 2003 11:14:45 +0000 Message-ID: In-Reply-To: <3FD7C9FB.20503@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3343600404904374379==" --===============3343600404904374379== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Wed, 10 Dec 2003, Anas Nashif wrote: > > Is there another way of stopping the redundant DHCP request? At best this > > leads to a delay until the request times out. At worse the machine could > > end up with an invalid configuration. > > > Hmm, this should not happen. Can you check the file > /var/lib/YaST2/install.inf > and see if the network values you have supplied are present there! menu.lst on GRUB floppy includes: title autoinstall ifconfig --address=131.111.11.209 --server=131.111.10.90 root (nd) kernel (nd)/suse/linux \ hostip=131.111.11.209 netmask=255.255.0.0 \ gateway=131.111.11.62 nameserver=131.111.8.42 \ install=nfs://131.111.8.10/linux/suse/i386/9.0 \ autoyast=tftp://131.111.10.90/suse/autoyast.xml \ textmode=1 initrd (nd)/suse/initrd /var/lib/YaST2/install.inf on installed system includes: NetConfig: static Netdevice: eth0 NetUniqueID: 7EWs.weGuQ9ywYPF IP: 131.111.11.209 Hostname: 131.111.11.209 Broadcast: 131.111.255.255 Network: 131.111.0.0 Netmask: 255.255.0.0 Gateway: 131.111.11.62 Nameserver: 131.111.8.42 Server: 131.111.8.10 /var/log/messages right after first reboot: Dec 8 12:38:16 linux dhcpcd[2782]: broadcasting DHCP_DISCOVER Dec 8 12:38:26 linux dhcpcd[2782]: timed out waiting for a valid DHCP server response /etc/sysconfig/network/ifcfg-eth0 is created a few seconds later by the autoinst postinstall script: -rw-r--r-- 1 root root 160 2003-12-08 12:38:41.000000000 +0000 /etc/sysconfig/network/ifcfg-eth0 and contains: BOOTPROTO='static' BROADCAST='131.111.255.255' IPADDR='131.111.11.209' NETMASK='255.255.0.0' NETWORK='131.111.0.0' STARTMODE='onboot' UNIQUE='7EWs.weGuQ9ywYPF' ifcfg-eth0 doesn't exist before that point in time. -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH. --===============3343600404904374379==-- From leen.meyer@home.nl Thu Dec 11 14:49:44 2003 From: Leendert Meyer To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] AutoYaST and firewall configuration Date: Thu, 11 Dec 2003 14:49:44 +0000 Message-ID: <200312111549.40567.leen.meyer@home.nl> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2987440950829146083==" --===============2987440950829146083== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Op Thursday 11 December 2003 12:14, schreef David Carter: DC> On Wed, 10 Dec 2003, Anas Nashif wrote: DC> DC> > > Is there another way of stopping the redundant DHCP request? At best this DC> > > leads to a delay until the request times out. At worse the machine could DC> > > end up with an invalid configuration. DC> > > DC> > Hmm, this should not happen. Can you check the file DC> > /var/lib/YaST2/install.inf DC> > and see if the network values you have supplied are present there! DC> DC> menu.lst on GRUB floppy includes: DC> DC> title autoinstall DC> ifconfig --address=131.111.11.209 --server=131.111.10.90 DC> root (nd) DC> kernel (nd)/suse/linux \ DC> hostip=131.111.11.209 netmask=255.255.0.0 \ DC> gateway=131.111.11.62 nameserver=131.111.8.42 \ DC> install=nfs://131.111.8.10/linux/suse/i386/9.0 \ DC> autoyast=tftp://131.111.10.90/suse/autoyast.xml \ DC> textmode=1 DC> initrd (nd)/suse/initrd DC> DC> /var/lib/YaST2/install.inf on installed system includes: DC> DC> NetConfig: static DC> Netdevice: eth0 DC> NetUniqueID: 7EWs.weGuQ9ywYPF DC> IP: 131.111.11.209 DC> Hostname: 131.111.11.209 DC> Broadcast: 131.111.255.255 DC> Network: 131.111.0.0 DC> Netmask: 255.255.0.0 DC> Gateway: 131.111.11.62 DC> Nameserver: 131.111.8.42 DC> Server: 131.111.8.10 DC> DC> /var/log/messages right after first reboot: DC> DC> Dec 8 12:38:16 linux dhcpcd[2782]: broadcasting DHCP_DISCOVER DC> Dec 8 12:38:26 linux dhcpcd[2782]: DC> timed out waiting for a valid DHCP server response What is in the DHCP server logs about this DHCP request? I had a similar problem in my small home network (2 pc's), where the dhcp lease was not released just before the first reboot. Obviously the freshly installed OS can *not* now that there already is a lease waiting for it. My solution was to stop the dhcp-server, remove the lease, and start the dhcp-server again. Any scripts run during installation before the first reboot are run in a chrooted environment, and thus cannot influence the install program. Cheers, Leen --===============2987440950829146083==-- From toganm@dinamizm.com Thu Dec 11 15:10:32 2003 From: Togan Muftuoglu To: autoinstall@lists.opensuse.org Subject: Install without documentation Date: Thu, 11 Dec 2003 15:10:32 +0000 Message-ID: <20031211151038.GD213@dinamizm.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4086510689476463921==" --===============4086510689476463921== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, Is there a way I can install all the rpms from the custom iso like the rpm --excludedocs command or do I have to recreate all the packages without documentation :-( and create the custom iso ? Thanks in advance -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://susefaq.sf.net --===============4086510689476463921==-- From Torsten.Schlabach@t-mobile.de Fri Dec 12 11:03:34 2003 From: "Schlabach, Torsten" To: autoinstall@lists.opensuse.org Subject: LVM config with AutoYAST Date: Fri, 12 Dec 2003 11:03:34 +0000 Message-ID: <41071631DA193B4B923CA3A9783207B20485C6B4@cvx09abnlw.BN.DeTeMobil.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4361451355803318526==" --===============4361451355803318526== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Dear list, we are using SLES 8 with SP3 and try to set up LVM with AutoYAST. The installer breaks with an error message saying: lvm vg_create invalid values Config snippet is below. It worked with non-SP3 SLES. Any ideas anyone? Regards, Torsten ---- system 4M root 2048mb reiser / tmp 2048mb reiser /tmp var 2048mb reiser /var appl 2048mb reiser /appl/local user1 2048mb reiser /users/local/user1 ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH ----------------------------------------- --===============4361451355803318526==-- From Torsten.Schlabach@t-mobile.de Fri Dec 12 11:37:10 2003 From: "Schlabach, Torsten" To: autoinstall@lists.opensuse.org Subject: [suse-autoinstall] LVM config with AutoYAST (contd.) Date: Fri, 12 Dec 2003 11:37:10 +0000 Message-ID: <41071631DA193B4B923CA3A9783207B20485C6B5@cvx09abnlw.BN.DeTeMobil.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7729033439591354663==" --===============7729033439591354663== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Little update to this from myself: The problem seems to be that the tag as a child of = is ignored since SP3. This leads to the vg_create to try and create the volum= es with device =3D "" (nothing) which cannot work. Q: How do I tell on what device the LVM group is to be created now? Given the fact that "LVM on software raid is not supported" how is this done = with LVM on a plain harddisk? Regards, Torsten -----Urspr=C3=BCngliche Nachricht----- Von: Schlabach, Torsten [mailto:Torsten.Schlabach(a)t-mobile.de] Gesendet am: Freitag, 12. Dezember 2003 12:03 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] LVM config with AutoYAST Dear list, we are using SLES 8 with SP3 and try to set up LVM with AutoYAST. The installer breaks with an error message saying: lvm vg_create invalid values Config snippet is below. It worked with non-SP3 SLES. Any ideas anyone? Regards, Torsten ---- system 4M root 2048mb reiser / tmp 2048mb reiser /tmp var 2048mb reiser /var appl 2048mb reiser /appl/local user1 2048mb reiser /users/local/user1 ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH ----------------------------------------- --=20 To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com --===============7729033439591354663==-- From fermin.galan@agora-2000.com Fri Dec 12 14:40:48 2003 From: =?utf-8?q?Ferm=C3=ADn_Gal=C3=A1n?= To: autoinstall@lists.opensuse.org Subject: NIS configuration DHCP learning control in control file Date: Fri, 12 Dec 2003 14:40:48 +0000 Message-ID: <20031212144046.F2792783CE@agora-2000.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6484215013981335615==" --===============6484215013981335615== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, What is the tag of the control file that sets the value of DHCLIENT_MODIFY_NIS_CONF DHCLIENT_SET_DOMAINNAME variables in the /etc/sysconfig/network/dhcp file in the installed system? Thanks in advance! ------- Fermín --===============6484215013981335615==-- From fermin.galan@agora-2000.com Fri Dec 12 14:43:57 2003 From: =?utf-8?q?Ferm=C3=ADn_Gal=C3=A1n?= To: autoinstall@lists.opensuse.org Subject: Backward compatibility in control files Date: Fri, 12 Dec 2003 14:43:57 +0000 Message-ID: <20031212144355.D8EF3783CE@agora-2000.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3353725740321598308==" --===============3353725740321598308== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, Which are the changes in the control file format (new tags, deprecated tags, new semantics for tags, etc.) from SuSE 8.1 to SuSE 8.2 to SuSE 9.0? Are they backward compatible (indeed, a control file for SuSE 8.1 works as a control file for SuSE 8.2 and SuSE 9.0? Thanks in advance! ------ Fermín --===============3353725740321598308==-- From hellmuth@ira.uka.de Fri Dec 12 15:58:37 2003 From: Holger Hellmuth To: autoinstall@lists.opensuse.org Subject: DTD out of date? Date: Fri, 12 Dec 2003 15:58:37 +0000 Message-ID: <3FD9E52D.8010602@ira.uka.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0737987071440714623==" --===============0737987071440714623== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Could it be that the DTD is out of date? When I configure users with yast2 autoyast and store the xml-file, xmllint reports problems with and . And I checked the DTD myself. There is no 'fullname' at all and group is an element with subelements in the DTD, but a data element in the autoyast generated file (hope I'm not mixing up xml nomenclature here). Holger. --===============0737987071440714623==-- From hellmuth@ira.uka.de Fri Dec 12 15:59:24 2003 From: Holger Hellmuth To: autoinstall@lists.opensuse.org Subject: DTD out of date? Forgot to mention Date: Fri, 12 Dec 2003 15:59:24 +0000 Message-ID: <3FD9E5CE.2000205@ira.uka.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0041721044168840752==" --===============0041721044168840752== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sorry, forgot to mention, I'm talking about Suse 9.0 autoyast and Suse 9.0 DTD. Holger. --===============0041721044168840752==-- From hellmuth@ira.uka.de Fri Dec 12 16:17:20 2003 From: Holger Hellmuth To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Backward compatibility in control files Date: Fri, 12 Dec 2003 16:17:20 +0000 Message-ID: <3FD9E932.3040301@ira.uka.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3961439517780012841==" --===============3961439517780012841== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Fermín Galán wrote: > Are they backward compatible (indeed, a control file for SuSE 8.1 works as a > control file for SuSE 8.2 and SuSE 9.0? No. My old 8.1 autoinst.xml didn't work with 9.0. As an example: german became german Holger. --===============3961439517780012841==-- From jrobiso2@ford.com Fri Dec 12 18:48:50 2003 From: "Robison, Jonathon (M.)" To: autoinstall@lists.opensuse.org Subject: krb5 and dns Date: Fri, 12 Dec 2003 18:48:50 +0000 Message-ID: <1071254914.11876.21.camel@jrobiso2.fsic.ford.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4714861526936135340==" --===============4714861526936135340== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Does anyone know how to sett krb5 (especially pam_krb5) to determine it's KDC= using SRV records in DNS? The SuSE manuals talk a lot about the fact that it= can be done, and they show you how to set up the DHCP server to spit out SRV= records, but nothing about how to set the CLIENTS up to use them! And of course I need to automate this into my autoyast build process. --Jonathon Robison=20 --===============4714861526936135340==-- From dbrowett@coquitlam.ca Fri Dec 12 21:25:56 2003 From: "Browett, Darren" To: autoinstall@lists.opensuse.org Subject: SLES 8 - SP3 Date: Fri, 12 Dec 2003 21:25:56 +0000 Message-ID: <8423DAC11EF82D469CF20CE341CC4EDF02328131@EXCHANGE.private.coquitlam.bc.ca> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7789114110985913729==" --===============7789114110985913729== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi there, I downloaded the SP3 iso files from the web site, burned them to disk,then using yast2 applied the patch set to my installation. The strange thing is, it didn't ask for CD 2 !, I then inserted Disk 2 into the CD and tried to apply the patch set, but it wouldn't accept disk 2 Why would I not need to use CD 2 ? Thanks Darren ------------------------------------------------------------------------ -------------------------------------------------- Darren Browett P.Eng This message was transmitted Data Administrator using 100% recycled electrons Information and Communication Technology City of Coquitlam P:(604)927 - 3614 E:dbrowett(a)coquitlam.ca ------------------------------------------------------------------------ --------------------------------------------------- --===============7789114110985913729==-- From mhagebris@ipdynamics.com Fri Dec 12 21:51:35 2003 From: Magnus Hagebris To: autoinstall@lists.opensuse.org Subject: k_smp4G missing from created SUSE9.0 ISO image Date: Fri, 12 Dec 2003 21:51:35 +0000 Message-ID: <1071265880.17369.90.camel@heimdal.ipdynamics.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4782367878450382234==" --===============4782367878450382234== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit My created ISO image does only contain the k_deflt, k_athlon and k_smp kernels. Where is the k_smp4G kernel? Is this a bug in the autoinstall iso creation? I created a patched source tree;the description files look good and properly includes the k_smp4G kernel. It just doesn't get added to the ISO. During install YaST complains about not finding the k_smp4G kernel on the cd... Install works perfectly fine on systems not using the k_smp4G kernel. Any work-around for this? Or tips... Thanks, Magnus --===============4782367878450382234==-- From mhagebris@ipdynamics.com Sat Dec 13 01:24:25 2003 From: Magnus Hagebris To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] k_smp4G missing from created SUSE9.0 ISO image - SOLVED Date: Sat, 13 Dec 2003 01:24:25 +0000 Message-ID: <1071278661.17369.158.camel@heimdal.ipdynamics.com> In-Reply-To: <1071265880.17369.90.camel@heimdal.ipdynamics.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0821837229589240529==" --===============0821837229589240529== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Never mind I just patched the file /usr/share/YaST2/include/autoinstall/iso.ycp and changed: packages =union (packages, ["k_deflt", "k_athlon", "k_smp"]); to: packages =union (packages, ["k_deflt", "k_athlon", "k_smp", "k_smp4G"]); Rebuilt the CD and all was fine... :-) Any reason you didn't added k_smp4G Anas? Cheers, Magnus On Fri, 2003-12-12 at 13:51, Magnus Hagebris wrote: > My created ISO image does only contain the k_deflt, k_athlon and k_smp > kernels. Where is the k_smp4G kernel? Is this a bug in the autoinstall > iso creation? > > I created a patched source tree;the description files look good and > properly includes the k_smp4G kernel. It just doesn't get added to the > ISO. > > During install YaST complains about not finding the k_smp4G kernel on > the cd... Install works perfectly fine on systems not using the k_smp4G > kernel. > > Any work-around for this? Or tips... > > Thanks, > Magnus > --===============0821837229589240529==-- From mvidner@suse.cz Mon Dec 15 09:11:44 2003 From: Martin Vidner To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] NIS configuration DHCP learning control in control file Date: Mon, 15 Dec 2003 09:11:44 +0000 Message-ID: <20031215091137.GB28781@valkyrie.suse.cz> In-Reply-To: <20031212144046.F2792783CE@agora-2000.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7316546055134227131==" --===============7316546055134227131== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Fri, Dec 12, 2003 at 03:40:45PM +0100, Fermín Galán wrote: > What is the tag of the control file that sets the value of > > DHCLIENT_MODIFY_NIS_CONF > DHCLIENT_SET_DOMAINNAME > > variables in the /etc/sysconfig/network/dhcp file in the installed system? It is "nis_by_dhcp". -- 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 --===============7316546055134227131==-- From Alfred.Isele@fujitsu-siemens.com Mon Dec 15 09:17:42 2003 From: Alfred Isele To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] SLES 8 - SP3 Date: Mon, 15 Dec 2003 09:17:42 +0000 Message-ID: <3.0.6.32.20031215101342.00ae4e10@athen> In-Reply-To: <8423DAC11EF82D469CF20CE341CC4EDF02328131@EXCHANGE.private. coquitlam.bc.ca> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9171682445742871539==" --===============9171682445742871539== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, As far as I know, CD2 does contain the sources. Regards Alfred At 13:25 12.12.03 -0800, Browett, Darren wrote: >Hi there, > >I downloaded the SP3 iso files from the web site, burned them to >disk,then using yast2 >applied the patch set to my installation. > >The strange thing is, it didn't ask for CD 2 !, I then inserted Disk 2 >into the CD and tried >to apply the patch set, but it wouldn't accept disk 2 > >Why would I not need to use CD 2 ? > >Thanks > >Darren > >------------------------------------------------------------------------ >-------------------------------------------------- >Darren Browett P.Eng This >message was transmitted >Data Administrator using >100% recycled electrons >Information and Communication Technology >City of Coquitlam >P:(604)927 - 3614 >E:dbrowett(a)coquitlam.ca >------------------------------------------------------------------------ >--------------------------------------------------- > > > > --===============9171682445742871539==-- From fermin.galan@agora-2000.com Mon Dec 15 11:18:21 2003 From: =?utf-8?q?Ferm=C3=ADn_Gal=C3=A1n?= To: autoinstall@lists.opensuse.org Subject: create_package_descr questions Date: Mon, 15 Dec 2003 11:18:21 +0000 Message-ID: <20031215111817.209D178404@agora-2000.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8755339865500748388==" --===============8755339865500748388== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, I have a pair of questions about the package database creation process (performed by create_package_descr script): 1. Can be used the same script for all SuSE versions (SuSE 8.1, SuSE 8.2 and SuSE 9.0) or each version have its own script file (in the autoyas2 package that comes with the version)? 2. Is create_package_descr a stand-alone program? (It seems that it uses the file /usr/share/autoinstall/EXTRA_PROV) Thanks in advance! ------- Fermín --===============8755339865500748388==-- From SP@jndata.dk Mon Dec 15 12:15:46 2003 From: Stefan Pahrmann To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] Backward compatibility in control files Date: Mon, 15 Dec 2003 12:15:46 +0000 Message-ID: <50244C3F1C9F574C87613B927E155BD40641A1@SJN00020.jndata.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6758002210872150744==" --===============6758002210872150744== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Is there some official documentation about the changes in the control-files from 8.2 to 9.0? I've heard some rumors that they aren't compatible, but I haven't found any official statement (or a reason for this changes) yet. Somebody in here, who know more about it? -Stefan -----Original Message----- From: Holger Hellmuth [mailto:hellmuth(a)ira.uka.de] Sent: 12. december 2003 17:14 To: suse-autoinstall Subject: Re: [suse-autoinstall] Backward compatibility in control files Fermín Galán wrote: > Are they backward compatible (indeed, a control file for SuSE 8.1 > works as a control file for SuSE 8.2 and SuSE 9.0? No. My old 8.1 autoinst.xml didn't work with 9.0. As an example: german became german Holger. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com --===============6758002210872150744==-- From fermin.galan@agora-2000.com Mon Dec 15 14:16:35 2003 From: =?utf-8?q?Ferm=C3=ADn_Gal=C3=A1n?= To: autoinstall@lists.opensuse.org Subject: RE: [suse-autoinstall] Backward compatibility in control files Date: Mon, 15 Dec 2003 14:16:35 +0000 Message-ID: <20031215141632.A0EBD7840F@agora-2000.com> In-Reply-To: <50244C3F1C9F574C87613B927E155BD40641A1@SJN00020.jndata.local> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8724518551964989245==" --===============8724518551964989245== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit So there is backward compatibility from SuSE 8.1 to SuSE 8.2 but there isn't from SuSE (8.1|8.2) to SuSE 9.0. It's right? Thanks! ------ Fermín -----Mensaje original----- De: Stefan Pahrmann [mailto:SP(a)jndata.dk] Enviado el: lunes, 15 de diciembre de 2003 12:50 Para: suse-autoinstall Asunto: RE: [suse-autoinstall] Backward compatibility in control files Is there some official documentation about the changes in the control-files from 8.2 to 9.0? I've heard some rumors that they aren't compatible, but I haven't found any official statement (or a reason for this changes) yet. Somebody in here, who know more about it? -Stefan -----Original Message----- From: Holger Hellmuth [mailto:hellmuth(a)ira.uka.de] Sent: 12. december 2003 17:14 To: suse-autoinstall Subject: Re: [suse-autoinstall] Backward compatibility in control files Fermín Galán wrote: > Are they backward compatible (indeed, a control file for SuSE 8.1 > works as a control file for SuSE 8.2 and SuSE 9.0? No. My old 8.1 autoinst.xml didn't work with 9.0. As an example: german became german Holger. -- 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 --===============8724518551964989245==-- From ewhiting@amis.com Mon Dec 15 14:52:39 2003 From: Eric Whiting To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] create_package_descr questions Date: Mon, 15 Dec 2003 14:52:39 +0000 Message-ID: <3FDDC498.1C652C59@amis.com> In-Reply-To: <20031215111817.209D178404@agora-2000.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1836999075980296373==" --===============1836999075980296373== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit I tried the create_package_descr script from suse 9.0 on my 8.2 tree -- it caused problems... I still haven't fixed that 8.2 tree. I'm guessing we have to use the create_package_descr from 8.2 to update a 8.2 install tree. That will be a little harder. eric Fermín Galán wrote: > > Hello, > > I have a pair of questions about the package database creation process > (performed by create_package_descr script): > > 1. Can be used the same script for all SuSE versions (SuSE 8.1, SuSE 8.2 and > SuSE 9.0) or each version have its own script file (in the autoyas2 package > that comes with the version)? > > 2. Is create_package_descr a stand-alone program? (It seems that it uses the > file /usr/share/autoinstall/EXTRA_PROV) > > Thanks in advance! > > ------- > Fermín > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com --===============1836999075980296373==-- From Martin.Moeser.external@fujitsu-siemens.com Wed Dec 17 10:27:09 2003 From: Martin =?utf-8?q?M=C3=B6ser?= To: autoinstall@lists.opensuse.org Subject: No Kernel installed Date: Wed, 17 Dec 2003 10:27:09 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1062538957468482215==" --===============1062538957468482215== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi List, since we build our custom-CD's (SLES8) with SP3, there will be no kernel inst= alled by autoyast. As a result, all modules are missing, and /boot is almost = empty, no boot-image or initrd in there. So the network interfaces don't work= and the reboot fails because of the missing vmlinuz. We use a machine with two processors and therefore we need an smp-kernel inst= alled which worked fine BEFORE we put the SP3-Packages into the repository. T= he needed kernel was detected and installed automatically. Any ideas? Regards, Martin M=C3=B6ser --=20 Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ --===============1062538957468482215==-- From erich.titl@think.ch Fri Dec 19 12:28:33 2003 From: Erich Titl To: autoinstall@lists.opensuse.org Subject: Online update failure Date: Fri, 19 Dec 2003 12:28:33 +0000 Message-ID: <5.1.1.6.0.20031219132721.00ae28c8@luna.think.ch> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6466508589318074078==" --===============6466508589318074078== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi I have a SuSE 7.3 which I'd like to update using the online update. Whenever = I try to access _any_of the preconfigured FTP servers I get the following err= or. This is with english as user language. Another 7.3 with German language g= ets the update descriptions fine... =C2=A6 =C2=A6Starting download of patch descriptions from ftp.leo.org. = =C2=A6 =C2=A6 =C2=A6 =C2=A6Connected = =C2=A6 =C2=A6 =C2=A6 =C2=A6failed : File not found on server = =C2=A6 =C2=A6 =C2=A6 =C2=A6Disconnected = =C2=A6 =C2=A6 =C2=A6=C2=A6information. =C2=A6=C2=A6 +-----------------------------------------------= ----------+ =C2=A6 =C2=A6 =C2=A6=C2=A6 =C2=A6 Can't get the patches from server. = =C2=A6 =C2=A6 =C2=A6 =C2=A6=C2=A6 =C2=A6 Please try to get patches from another S= uSE FTP server. =C2=A6 =C2=A6 =C2=A6 =C2=A6=C2=A6 =C2=A6 [OK] = =C2=A6 =C2=A6 =C2=A6 =C2=A6=C2=A6 +-----------------------------------------------= ----------+ =20 Could anyone please tell me where to look Thanks Erich Titl THINK=20 P=C3=BCntenstrasse 39=20 8143 Stallikon=20 mailto:erich.titl(a)think.ch=20 PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --===============6466508589318074078==-- From erich.titl@think.ch Fri Dec 19 12:31:48 2003 From: Erich Titl To: autoinstall@lists.opensuse.org Subject: [ more info ] Online update failure Date: Fri, 19 Dec 2003 12:31:48 +0000 Message-ID: <5.1.1.6.0.20031219132959.03dc8cc0@luna.think.ch> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6003898489400798021==" --===============6003898489400798021== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi This is the failed FTP request, apparently the release 7.3 is missing in the = path 14:11:59.650803 castor.granella-holding.ch.42952 > ftp.leo.org.ftp: P 29:89(6= 0) ack 2536 win 5840 (DF) 0x0000 4500 0070 134f 4000 4006 d276 c0a8 c863 E..p.O(a).@..v...c 0x0010 839f 4817 a7c8 0015 5382 4bdc ca27 e0c9 ..H.....S.K..'.. 0x0020 8018 16d0 32e5 0000 0101 080a 17cc 58dd ....2.........X. 0x0030 07b8 f9f5 4357 4420 2f70 7562 2f63 6f6d ....CWD./pub/com 0x0040 702f 6f73 2f75 6e69 782f 6c69 6e75 782f p/os/unix/linux/ 0x0050 7375 7365 2f73 7573 652f 6933 3836 2f75 suse/suse/i386/u 0x0060 7064 6174 652f 2f70 6174 6368 6573 0d0a pdate//patches.. Where is the path for the online update defined? Erich Titl THINK=20 P=C3=BCntenstrasse 39=20 8143 Stallikon=20 mailto:erich.titl(a)think.ch=20 PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --===============6003898489400798021==-- From Darin.Perusich@cognigencorp.com Mon Dec 22 15:30:49 2003 From: Darin Perusich To: autoinstall@lists.opensuse.org Subject: pxe boot fails. Date: Mon, 22 Dec 2003 15:30:49 +0000 Message-ID: <3FE70C80.7040806@cognigencorp.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6424226615103718487==" --===============6424226615103718487== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit hello, i'm trying to get my autoinstall to boot only using the syslinux pxelinux.0 image and not have to rely on etherboot. i already have etherboot working fine i just want to see if i can get pxe working by itself. where i'm running into a problem is when the system tries to load initrd, it starts loading but i then get a "Boot failed, press any key to retry, or wait to reset...". any thoughts on what might be causing this? i'm using linux and initrd from the suse9 pro cd /boot/loader. dhcpd.conf for this host. host host1 { filename "/pxelinux.0"; fixed-address 172.16.0.223; hardware ethernet 00:07:E9:5D:8C:7B; next-server 172.16.0.16; } pxelinux.cfg/AC1000DF default linux label linux kernel linux append load_ramdisk=1 initrd=initrd install=nfs://172.16.0.9/suse/ autoyast=nfs://172.16.0.16/export/configs/host1.xml thanks -- Darin Perusich Unix Systems Administrator Cognigen Corp. darinper(a)cognigencorp.com --===============6424226615103718487==-- From linux@andac.it Tue Dec 23 09:20:29 2003 From: Account for mailing list To: autoinstall@lists.opensuse.org Subject: wlan0/eth0 wireless help Date: Tue, 23 Dec 2003 09:20:29 +0000 Message-ID: <20031223093407.21604.qmail@cinzia> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0765862838207079425==" --===============0765862838207079425== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections. Any ideas? Thanks Andrea --===============0765862838207079425==-- From linux@andac.it Tue Dec 23 09:52:29 2003 From: Account for mailing list To: autoinstall@lists.opensuse.org Subject: wlan0/eth0 wireless help Date: Tue, 23 Dec 2003 09:52:29 +0000 Message-ID: <20031223100536.21684.qmail@cinzia> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2474772378856124545==" --===============2474772378856124545== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections. Any ideas? Thanks Andrea --===============2474772378856124545==-- From Harald.Milz@computacenter.com Mon Dec 29 12:30:51 2003 From: Harald.Milz@computacenter.com To: autoinstall@lists.opensuse.org Subject: SuSE 9.0 PXE boot problem Date: Mon, 29 Dec 2003 12:30:51 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2923816495858049789==" --===============2923816495858049789== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, since my notebook's CD-ROM drive is dying slowly I tried to install SuSE Linux 9.0 Prof. from my existing PXE/DHCP/TFTP server which already has working configs for 8.0 and 8.2: label 8.0 kernel kernel-8.0 append initrd=initrd-8.0 acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-8.0" label 8.2 kernel kernel-8.2 append initrd=initrd-8.2 acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-8.2" As usual, copied boot/loader/linux and boot/loader/initrd to /tftpboot and added a config entry to pxelinux.cfg/default: label 9.0 kernel kernel-9.0 append initrd=initrd-9.0 ramdisk_size=65536 showopts ide=nodma acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-9.0" which, apart from some additional options taken from the CD isolinux.cfg file, are identical to the ones above. The additional options don't change any of the descibed behaviour, which is: - notebook boots via pxelinux just fine, I get my text menu, enter 9.0 - kernel unpacks, and ... - the screen is an 80x25 chaos of ASCII characters with various attributes, like blink, etc. Machine stops. Nothing happens. It looks as if the kernel was unpacked into the EGA video memory region at segment b800. Any clue what happens? Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 --===============2923816495858049789==-- From linux@andac.it Mon Dec 29 12:47:01 2003 From: Account for mailing list To: autoinstall@lists.opensuse.org Subject: wireless NIC/DSL Date: Mon, 29 Dec 2003 12:47:01 +0000 Message-ID: <20031229130050.9307.qmail@cinzia> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2452274683330495782==" --===============2452274683330495782== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to use wireless NIC to connect DSL modem. With Any other distributions is possible to use wireless PCMCIA because any NIC PCMCIA is named ethX Any ideas ? Thanks Andrea --===============2452274683330495782==-- From linux@andac.it Mon Dec 29 13:00:48 2003 From: Account for mailing list To: autoinstall@lists.opensuse.org Subject: Crossover/Dreamweaver Date: Mon, 29 Dec 2003 13:00:48 +0000 Message-ID: <20031229131418.9355.qmail@cinzia> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7502862460483320601==" --===============7502862460483320601== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I installed Suse 9.0 and last Crossover Office to use DreamweaverMX ... but I got avery kind of error. I installed Crossover/Dreamweaver without errors but I can't run DMX ... in first time I got "missing MFC42.DLL" after if I launch it from windows folder it told me that I need to configure the keyboard .... someone could help me? Thanks in advance. Andrea --===============7502862460483320601==-- From hubba@unixcook.com Mon Dec 29 22:32:55 2003 From: Hubertus Haniel To: autoinstall@lists.opensuse.org Subject: Re: [suse-autoinstall] Crossover/Dreamweaver Date: Mon, 29 Dec 2003 22:32:55 +0000 Message-ID: In-Reply-To: <20031229131418.9355.qmail@cinzia> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1524944031735421206==" --===============1524944031735421206== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Mon, 29 Dec 2003, Account for mailing list wrote: > Date: Mon, 29 Dec 2003 14:14:18 +0100 > From: Account for mailing list > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Crossover/Dreamweaver > > > Hi, > I installed Suse 9.0 and last Crossover Office to use DreamweaverMX ... but > I got avery kind of error. I installed Crossover/Dreamweaver without errors > but I can't run DMX ... in first time I got "missing MFC42.DLL" after if I > launch it from windows folder it told me that I need to configure the > keyboard .... > I suggest you try the forums supplied by codeweavers to resolve this issue If you bought the product online via their website you should be able to use the same login to access the forums as you used to download the product. This mailing list deals only with issues with SuSE's automatic installation via autoyast. In regards to your postings about wireless and ADSL I suggest you check the SuSE website for a more adequate mailing list like suse-linux(a)suse.com or suse-linux-e(a)suse.com with a little bit more info about your problem. I configured my wirleless card as wlan0 via yast with an IP address and it talks quite happely to my ADSL router which also has an IP address. Best regards Hubba --===============1524944031735421206==-- From sullivan@mathcom.com Tue Dec 30 16:54:42 2003 From: Steve Sullivan To: autoinstall@lists.opensuse.org Subject: yast2 doesn't start Date: Tue, 30 Dec 2003 16:54:42 +0000 Message-ID: <20031230165117.DF0915F6CA@helix.mathcom.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0349774745703424240==" --===============0349774745703424240== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I'm running Suse 9 professional on a Pentium. When I login as root yast works fine. But when I login as me and try ... xhost + GreenButton / system / yast Get password popup for command: /sbin/yast2; enter password Nothing happens. Yast2 never starts. Meanwhile /var/log/messages shows: Dec 30 09:49:02 helix su: (to root) sullivan on /dev/pts/4 Dec 30 09:49:02 helix su: pam_unix2: session started for user root, service su Dec 30 09:49:02 helix su: pam_unix2: session finished for user root, service = su Dec 30 09:49:02 helix su: (to root) sullivan on /dev/pts/4 Dec 30 09:49:02 helix su: pam_unix2: session started for user root, service su Dec 30 09:49:03 helix su: pam_unix2: session finished for user root, service = su Why can't I start yast2 this way? Many thanks, Steve =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Steve Sullivan sullivan(a)mathcom.com Mathcom Solutions Inc.: Custom Software Development. * Mathematical optimization, simulation, and modeling. * Database, data mining, information retrieval. * Java, XML, C++, Mathematica, Matlab, XSLT, XQuery, SOAP, RMI, ... http://www.mathcom.com 303-494-7115 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --===============0349774745703424240==--