February 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Partitioning
by Urs Haberthuer 01 Mar '03

01 Mar '03

Dear Anas, I am still troubled with the same partitioning problem I have asked about in this mailing list before. I would be very much interested in the following option for autoyast2: If a disk is already partitioned (from a prevoius installation, for instance), I would like to instruct autoyast2 which partitions to format and which ones to leave untouched (without recreating any of the partitions) on this disk. It seems there is a manual solution to this problem suggested by Rasmus Borup Hansen by telling autoyast2 to interrupt the installation for a manual partitioning session. While this probably works fine (I didn't test it yet), it is difficult to be realized for a large farm of machines. Do you plan to add such an option in the next SuSE release or in an update for SuSE 8.1? Best regards Urs Haberthuer -- Urs Haberthuer Department of Biochemistry University of Zurich Winterthurerstrasse 190 CH - 8057 Zurich Phone: ++41 (0)1 635 55 92 Fax: ++41 (0)1 635 68 62 E-mail: atlantis(a)bioc.unizh.ch

2 1

FW: Live Eval CD wie?
by hb9irb 28 Feb '03

28 Feb '03

Hallo Leute, auf dem SuSE FTP server gibt es die möglichkeit das sogenannt "SuSE-8.1LiveEval-i386.iso" Herunterladen um die Evaluation Version ohne installation ausprobieren. Also ich habe diese Datei erfolgreich (ca. 650MB) auf dem local Festplatte gespeichert und spoeter habe ich versucht alles auf einem CD zu brennen, aber leider hat nicht geklappt. Die Brennsoftware ist NERO auf WinXP. Kann jemand mir erklären um diese bootfähig CD zu erstellen? HB9IRB Pasquale

1 0

partitioning problem
by Claude Arnold 28 Feb '03

28 Feb '03

Hi, I use autoyast (suse8.0 with yast2-modules-autoint-2.5.27-1) through the network. The client find the profile file and the Yast2 window shows me the steps. On the "prepare the hard disk" I see just a "0%" and Yast2 goes to the next step "installing packages". Even I don't set partitions (but define a drive and a device) in the profile file the partitioning is not perfomed automatically with the default values as mentioned in the manual. How can I see what's happend ? thanks, ------------- Claude Arnold Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4 Tél: 05.61.55.62.26 Fax: 05.61.55.82.00

1 0

Error: disk space exhausted
by Claude ARNOLD 26 Feb '03

26 Feb '03

Hi, With autoyast installation I have the following message: Error Disk space exhausted. It is certainly a partionning problem inherit by the *.xml config file. Is there a way to have some logs or informations on the partionning steps to see what happends ? If I do a "df" on the client I obtain: Filesystem 1k-blocks Used Available Use% Mounted on shmfs 55068 54320 748 99% / nfs_server:/tftpboot/suse80 10485436 4661160 5824276 45% /var/adm/mount /dev/loop0 77640 77640 0 100% /mounts/instsys With these informations can we see if the partionning performed ? Thanks for your help, Claude Arnold Laboratoire Emile Picard - UFR MIG Universite Paul Sabatier - 118, route de Narbonne 31062 TOULOUSE tel: +33 (0)5.61.55.62.26 Fax: +33 (0)5.61.55.82.00

2 1

couldn't find valid ramdisk image
by Claude Arnold 26 Feb '03

26 Feb '03

Sorry for the previous message it was send in a wrong subject... so again. Hello, I trie to install suse8.0 using autoyast throught the network. The steps I use are the following: 1. the server has a directory /tftpboot. 2. In this directory are the linux, initrd and syslinux.cfg files, these are extracted from the suse8.0/disks/bootdisk (copied from the CD's) file using mount -oloop. 3. In syslinux.cfg I put the following lines: ====================== default autoyast # default label autoyast kernel linux append console=ttyS0,9800 console tty initrd=initrd \ autoyast=nfs://nfs_server/tftpboot/suse80/install.xml \ install=nfs://nfs_server/tftpboot/suse80 verbose 1 ======================== 4. Next I create a netboot file using mknbi-linux (which comes from netboot package): mknbi-linux -a "linuxrc=auto rw ramdisk_size=65536" -r initrd linux netboot 5. I boot from client, it loads the netboot file and after some messages I have the following error message: ... RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 4048k freed Root-NFS: No NFS server availble, giving up ... is there a problem with the initrd file ? Can some one help me ? Thanks ------------- Claude Arnold Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4 Tél: 05.61.55.62.26 Fax: 05.61.55.82.00

2 2

Cloning Suse 8.1 Installation
by Joerg Friedrich 26 Feb '03

26 Feb '03

Hi! I have to install Suse 8.1 on 4 identical Servers. Yesterday I tried the autoinstallation from yast. I installed one machine, and selected the "Clone this machine" from yast/autoinstallation. But the installation failed, because it was not able to partition the Harddisks correctly. FYI. The machines have two 18GB SCSI-Harddisks, which are also identical (same manufacturer, same series). Hard disk layout should be: fdisk -l /dev/sda Disk /dev/sda: 255 heads, 63 sectors, 2231 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 1 131 1052226 fd Linux raid autodetect /dev/sda2 * 132 140 72292+ 83 Linux /dev/sda3 141 2231 16795957+ f Win95 Ext'd (LBA) /dev/sda5 141 663 4200966 fd Linux raid autodetect /dev/sda6 664 1186 4200966 fd Linux raid autodetect /dev/sda7 1187 2231 8393931 fd Linux raid autodetect sdb same. RAID layout should be four RAID1. md0: sda1/sdb1 md1: sda5/sdb5 md2: sda6/sdb6 md3: sda7/sdb7 I attached three files. clone.xml is the one, yast auto install created. autoinst.xml and autoinst2.xml are changed copies from clone.xml where I tried to fix the partition problem but failed. Can you help? -- Heute ist nicht alle Tage, ich komm' wieder, keine Frage!!! Joerg It is not well to be thought of as one who meekly submits to insolence and intimidation.

1 1

Changing the user to anonymous when doing an ftp install.
by Rowan Reid 25 Feb '03

25 Feb '03

For some reason whenever attempting to add additional packages to my SuSE8.0 release I get an error message stating the package could not be found or server error. In the path I'm noticing that it is not logging on as anonymouse. The path has been copy pasted below. I've also tried every variation of the path (noticing the double //) can anyone help ftp://rowan:*PASSWORD*@mirror.mcs.anl.gov//pub/suse/i386/8.0/suse/suse/z km1/km_freeswan-1.95_0.9.8-131.i386.rpm

2 2

SuSE Linux 8.1 Autoinst with YAST2 and the common.pkd file
by Orenchak, James 25 Feb '03

25 Feb '03

Hello, I have used Autoinst using NFS and FTP with SuSE Linux Version 7.1 a lot. It worked great. Now I'm starting to use YAST2 Autoinst to install SuSE Linux 8.1 on systems. The first problem I encountered was an error message that no software packages could be found when I tried to create the first control file. After reading about several fixes in this mailing list and installing them, that error disappeared. I copied all of the SuSE 8.1 CDs into one directory and then started the script create_package_descr to recreate the package database. I used the command without any parameters. I expected to see a file called common.pkd in the directory where I copied the CDs into after calling create_package_descr. I didn't find it. Is the file common.pkd no longer required? When yes, what should be in the file common.pkd? Mit freundlichen Grüßen / Best Regards James Orenchak

1 0

Disappearing packages
by Sven Thomsen 25 Feb '03

25 Feb '03

Hi, another day, another problem :-) I've got some "disappearing" packages. I've updated my repository with KDE3.1 packages, and some packages don't get copied to my autoinstall cd. Example: In my repository there is: # ls -l libart_lgpl-* -r--r--r-- 1 root root 64884 2003-02-22 11:39 libart_lgpl-2.3.10-75.rpm -r--r--r-- 1 root root 61610 2003-02-22 11:39 libart_lgpl-devel-2.3.10-75.rpm After calling create_package_descr I find in my packages-file: ##---------------------------------------- =Pkg: libart_lgpl 2.3.10 75 i586 +Req: ld-linux.so.2 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libm.so.6 libm.so.6(GLIBC_2.0) rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: libart_lgpl_2.so.2 -Prv: =Grp: System/GUI/GNOME =Lic: LGPL =Src: libart_lgpl 2.3.10 75 src =Tim: 1042148578 =Loc: 1 libart_lgpl-2.3.10-75.rpm =Siz: 64884 151539 ##---------------------------------------- =Pkg: libart_lgpl-devel 2.3.10 75 i586 +Req: /bin/sh rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: =Grp: System/GUI/GNOME =Lic: LGPL =Src: libart_lgpl 2.3.10 75 src =Tim: 1042148578 =Loc: 1 libart_lgpl-devel-2.3.10-75.rpm =Siz: 61610 195797 ##---------------------------------------- When I create a cd, yast2 seems to copy the file correctly: 2003-02-24 11:14:23 <1> tigerente(4758) [YCP] autoinstall/packageMgmt.ycp(createISO):325 Package to be copied: /export/media/suse_8.1//./suse/ i586/less-376-21.i586.rpm 2003-02-24 11:14:23 <1> tigerente(4758) [YCP] autoinstall/packageMgmt.ycp(createISO):325 Package to be copied: /export/media/suse_8.1//./suse/ i586/libart_lgpl-2.3.10-75.i586.rpm 2003-02-24 11:14:23 <1> tigerente(4758) [YCP] autoinstall/packageMgmt.ycp(createISO):325 Package to be copied: /export/media/suse_8.1//./suse/ i586/libcap-1.92-216.i586.rpm But, when I mount the created iso and look into i586: less-376-21.i586.rpm libcap-1.92-216.i586.rpm libgcc-3.2-36.i586.rpm libgimpprint-4.3.3-21.i586.rpm libjpeg-6.2.0-464.i586.rpm libogg-1.0-31.i586.rpm libpcap-0.7.1-46.i586.rpm libpng-1.2.4-58.i586.rpm libstdc++-3.2-36.i586.rpm libtiff-3.5.7-145.i586.rpm libvorbis-1.0-32.i586.rpm libxcrypt-1.1-44.i586.rpm liby2util-2.6.21-0.i586.rpm lilo-22.3.2-32.i586.rpm linux-atm-2.4.0-146.i586.rpm logdigest-0.1.1-95.i586.rpm logrotate-3.5.9-182.i586.rpm lsof-4.64-30.i586.rpm lukemftp-1.5-310.i586.rpm lvm-1.0.5-38.i586.rpm Same thing happens to liblcms, qt3 but not to kdebase3 et al. which have been updated, too... Mysterious, isn't it? Sven

2 1

Integration of KDE 3.1 Updates?
by Sven Thomsen 24 Feb '03

24 Feb '03

Hi, what's your favourite solution for including KDE3.1 updates in an autoinstallation? Greetings, Sven

2 3

sendmail nightmare on suse...
by redlineracerx 24 Feb '03

24 Feb '03

Hi there, Is there an rpm available for sendmail 8.12.7 for suse? Are the available rpm's for redhat compatible? Thanks, paul

1 0

Really frustrated ftp install help
by Rowan Reid 22 Feb '03

22 Feb '03

I recently did an ftp install of SuSE8.0 to make it faster I had previously downloaded the entire distru on a windows machine shared it then mounted the share n my ftp/pub folder. Install worked no prob. However now I wish to add a few aditional packages. However when I set up the source I get unable to mount source or if could not find file. I then used ftp.suse.com and a few other mirrors same prblem. Then I mounted the smb share localy on my drive /mnt/suse/ and I keep getting unable to mount source - this is with a harddrive install. I'm about to pull my hair out.

2 1

Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems
by herman gorter 21 Feb '03

21 Feb '03

Dear Thomas, Thanks for your patience! Down here is the result in xterm of your advise. Am I right, that we do have to get a link between libXm.so2 and libXm.so.3, but someway it does not work. Has it someting to do with permissions? I tried to find the files above and also "openmotif" in "find files" at look in: / ,but failed. So I could also not see if there are some wrong permissions. May be we could find the permissions in xterm, but I don't know how to do that. You seem to know a lot about Linux. I would appreciate if you could find some time to help me further out. kind regards, herman ________________________________________________________________________________ herman@linux:~> rpm -q openmotif openmotif-2.2.2-111 herman@linux:~> ln -s /usr/X11R6/lib/libXm.so3 /usr/X11R6/lib/libXm.so.2 ln: creating symbolic link `/usr/X11R6/lib/libXm.so.2' to `/usr/X11R6/lib/libXm.so3': Permission denied herman@linux:~> sux - Password: linux:~ # ln -s /usr/X11R6/lib/libXm.so3 /usr/X11R6/lib/libXm.so.2 linux:~ # rpm -Uhv /home/herman/Documents/opera-6.11-20021129.1-static-qt.i386.rpm error: failed dependencies: libXm.so.2 is needed by opera-6.11-20021129.1 linux:~ # ____________________________________________________________________________ >From: Thomas Mack <mack(a)ips.cs.tu-bs.de> >To: h_gorter(a)hotmail.com >Subject: Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems >Date: Wed, 19 Feb 2003 22:17:00 +0100 (MET) >Received: from infbssys.ips.cs.tu-bs.de ([134.169.32.1]) by >mc3-f2.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 19 Feb >2003 13:17:03 -0800 >Received: from infbsdb1.idb.cs.tu-bs.de (infbsdb1.idb.cs.tu-bs.de >[134.169.32.131])by infbssys.ips.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id >WAA26697for <h_gorter(a)hotmail.com>; Wed, 19 Feb 2003 22:17:01 +0100 >X-Message-Info: dHZMQeBBv44lPE7o4B5bAg== >Message-Id: <200302192117.WAA04167(a)infbsdb1.idb.cs.tu-bs.de> >Return-Path: mack(a)ips.cs.tu-bs.de >X-OriginalArrivalTime: 19 Feb 2003 21:17:03.0601 (UTC) >FILETIME=[3FA2A610:01C2D85C] > > >linux:~ # cd Documents rpm -Uhv opera-6.11-20021129.1-static-qt.i386.rpm > >-bash: cd: Documents: No such file or directory > >linux:~ # rpm -Uvh Documents/opera-6.11-20021129.1-static-qt.i386.rpm > >error: cannot open file >Documents/opera-6.11-20021129.1-static-qt.i386.rpm: > >No such file or directory > >linux:~ # rpm -Uhv > >/home/herman/Documents/opera-6.11-20021129.1-static-qt.i386.rpm > >error: failed dependencies: > > libXm.so.2 is needed by opera-6.11-20021129.1 > >linux:~ # > >_________________________________________________________________________________ > > >Ok, I forgot you are root, when installing, so it did not find the >directory in the first place. > >You need to have the package openmotif installed (I think), as this >package includes /usr/X11R6/lib/libXm.so.3 . If opera is not satisfied >with /usr/X11R6/lib/libXm.so.3 but rather likes to have libXm.so.2 >instead, you can try to create a link with the name of libXm.so.2 >pointing to libXm.so.3 . > >Firstly, you should see, if openmotif package is installed. As root user do >the following: > >rpm -q openmotif > >If you get something like "openmotif-2.2.2-111" as output, the package >is installed already. ONLY THEN, you would try do: > >ln -s /usr/X11R6/lib/libXm.so.3 /usr/X11R6/lib/libXm.so.2 > > >If the openmotif package is not yet installed, install that package from >your CD. > >Then you should retry to install opera. > >If there are other failed dependencies, you will have to install more >packages. > > >Thomas _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

2 1

Adding packages via ftp always fails.
by Rowan Reid 21 Feb '03

21 Feb '03

I recectly installed SuSE 8.0 via FTP. I am now trying to add the remaining kernel archive via YAST when I tried installing I selected the package but when it tried to install I get a cannot find file error. The error is below. This error seems to also be happening on my other server. Anyone else experience this ? <snippett> Package: ftp://rowan:*PASSWORD*@mirror.mcs.anl.gov//pub/suse/i386/8.0/suse/suse/z km1/km_freeswan-1.95_0.9.8-131.i386.rpm ³ ³ ³ ³ ³ ³ ³ returns an error: File not found on server or connection refused ³ ³ ³ ³ ³ ³ ³ You can skip this package, retry the download ³ ³ ³ ³ ³ ³ ³ or abort the installation. ³ ³ ³ ³ ³ ³ ³ [ Skip ] [Abort installation] [ Retry ]

1 0

Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems
by herman gorter 19 Feb '03

19 Feb '03

Dear Thomas, Thanks again for your kind advise and time! I did as you told me and I see, I get now the same problem as I had when I called Suse and they were so kind to help me by phone. There is the same failed dependency that I had with the original Suse Opera upgrade download. That's why Suse advised me then to download the static version. That's what I did as you can see, but there is still missing something... I don't know what, but unfortunately it still does not install the newest version of Opera! Down here you can see what xterm said. Do you have a further solution may-be? Do you think this might be called a bug in Suse 8.1? Thank you very much in advance, herman ______________________________________________________________________________ linux:~ # rpm -Uhv /home/herman/Documents/operaherman@linux:~> sux - -: unknown option linux:~ # Password: -bash: Password:: command not found linux:~ # linux:~ # rpm -Uhv /home/herman/Documents/opera6.11-20021129.1-static-qt.i386.rpm -bash: linux:~: command not found linux:~ # rpm -Uhv/home/herman/Documents/opera6.11-20021129.1-static-qt.i386.rpm -Uhv/home/herman/Documents/opera6.11-20021129.1-static-qt.i386.rpm: unknown option linux:~ # cd Documents -bash: cd: Documents: No such file or directory linux:~ # cd Documents rpm -Uhv opera-*.rpm -bash: cd: Documents: No such file or directory linux:~ # cd Documents rpm -Uhv opera-6.11-20021129.1-static-qt.i386.rpm -bash: cd: Documents: No such file or directory linux:~ # rpm -Uvh Documents/opera-6.11-20021129.1-static-qt.i386.rpm error: cannot open file Documents/opera-6.11-20021129.1-static-qt.i386.rpm: No such file or directory linux:~ # rpm -Uhv /home/herman/Documents/opera-6.11-20021129.1-static-qt.i386.rpm error: failed dependencies: libXm.so.2 is needed by opera-6.11-20021129.1 linux:~ # _________________________________________________________________________________ >From: Thomas Mack <mack(a)ips.cs.tu-bs.de> >To: "herman gorter" <h_gorter(a)hotmail.com> >Subject: Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems >Date: Wed, 19 Feb 2003 15:09:59 +0100 >MIME-Version: 1.0 >Received: from infbssys.ips.cs.tu-bs.de ([134.169.32.1]) by >mc6-f14.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 19 Feb >2003 06:10:02 -0800 >Received: from is38.idb.cs.tu-bs.de (is38.idb.cs.tu-bs.de >[134.169.32.148])by infbssys.ips.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id >PAA21779for <h_gorter(a)hotmail.com>; Wed, 19 Feb 2003 15:10:00 +0100 >Received: from is38.idb.cs.tu-bs.de (localhost [127.0.0.1])by >is38.idb.cs.tu-bs.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id >h1JE9x1l011614for <h_gorter(a)hotmail.com>; Wed, 19 Feb 2003 15:09:59 +0100 >Received: from localhost (localhost [[UNIX: localhost]])by >is38.idb.cs.tu-bs.de (8.12.3/8.12.3/Submit) id h1JE9xXJ011613for >h_gorter(a)hotmail.com; Wed, 19 Feb 2003 15:09:59 +0100 >X-Message-Info: dHZMQeBBv44lPE7o4B5bAg== >User-Agent: KMail/1.4.3 >References: <BAY2-F144qAP9APKtOo0003497d(a)hotmail.com> >In-Reply-To: <BAY2-F144qAP9APKtOo0003497d(a)hotmail.com> >Message-Id: <200302191509.59600.mack(a)ips.cs.tu-bs.de> >Return-Path: mack(a)ips.cs.tu-bs.de >X-OriginalArrivalTime: 19 Feb 2003 14:10:02.0786 (UTC) >FILETIME=[98708820:01C2D820] > >Am Mittwoch, 19. Februar 2003 14:31 schrieben Sie: > > Dear Thomas, > > > > Thanks for your kind advise. > > > > I know the static Opera upgradefile is in /home/herman/Documents. Down >here > > you can see what xterm says back now, if I type in the way you suggest. >Or > > do I make some stupid mistake...? > > >___________________________________________________________________________ > >You have directories on the command line in the same way as you have >them in some graphical programs. The directory given as ~ is the home >directory, which is /home/herman for you as user herman. > >There are at least choices, how you can manage your problem: >- You move you opera*.rpm file to your home directory and then: > rpm -Uhv opera-*.rpm > >- you go to the Documents directory on the command line: > > cd Documents > rpm -Uhv opera-*.rpm > >- you give the directory explicitely to rpm: > rpm -Uhv Documents/opera-*.rpm > >(or even with the complete path: > rpm -Uhv /home/herman/Documents/opera-*.rpm >) > >Thomas Mack >TU Braunschweig, Abt. Informationssysteme _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus

1 0

Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems
by herman gorter 19 Feb '03

19 Feb '03

Dear Thomas, Thanks for your kind advise. I know the static Opera upgradefile is in /home/herman/Documents. Down here you can see what xterm says back now, if I type in the way you suggest. Or do I make some stupid mistake...? ______________________________________________________________________________ herman@linux:~> sux - Password: linux:~ # rpm -U opera6.11-20021129.1-static-qt.i386.rpm error: cannot open file opera6.11-20021129.1-static-qt.i386.rpm: No such file or directory linux:~ # ______________________________________________________________________________ I am a dummie... I really don't know anymore how to get a more recent Operabrowser. Wished that the autoinstall in Yast2 worked better...! kind regards, herman >From: Thomas Mack <mack(a)ips.cs.tu-bs.de> >To: h_gorter(a)hotmail.com >Subject: Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems >Date: Wed, 19 Feb 2003 13:47:10 +0100 >MIME-Version: 1.0 >Received: from infbssys.ips.cs.tu-bs.de ([134.169.32.1]) by >mc7-f23.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 19 Feb >2003 04:47:13 -0800 >Received: from is38.idb.cs.tu-bs.de (is38.idb.cs.tu-bs.de >[134.169.32.148])by infbssys.ips.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id >NAA20720for <h_gorter(a)hotmail.com>; Wed, 19 Feb 2003 13:47:11 +0100 >Received: from is38.idb.cs.tu-bs.de (localhost [127.0.0.1])by >is38.idb.cs.tu-bs.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id >h1JClA1l011409for <h_gorter(a)hotmail.com>; Wed, 19 Feb 2003 13:47:10 +0100 >Received: from localhost (localhost [[UNIX: localhost]])by >is38.idb.cs.tu-bs.de (8.12.3/8.12.3/Submit) id h1JClACq011408for >h_gorter(a)hotmail.com; Wed, 19 Feb 2003 13:47:10 +0100 >X-Message-Info: dHZMQeBBv44lPE7o4B5bAg== >User-Agent: KMail/1.4.3 >References: <BAY2-DAV35gkJXrRjbD0000b5ff(a)hotmail.com> >In-Reply-To: <BAY2-DAV35gkJXrRjbD0000b5ff(a)hotmail.com> >Message-Id: <200302191347.10350.mack(a)ips.cs.tu-bs.de> >Return-Path: mack(a)ips.cs.tu-bs.de >X-OriginalArrivalTime: 19 Feb 2003 12:47:13.0437 (UTC) >FILETIME=[067A0CD0:01C2D815] > > > opera-6.11-20021129.1-static-qt.i386.rpm not installed in xterm. I type > > there in supermode: rpm - U opera-6.11-20021129.1-static-qt.i386.rpm > > >You have to type rpm -U opera*.rpm, NOT rpm - U opera*.rpm... > >There should not be a problem with this. Otherwise you will get some >more detailled error message from rpm. > >Thomas Mack >TU Braunschweig, Abt. Informationssysteme _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

1 0

Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems
by h_gorter＠hotmail.com 19 Feb '03

19 Feb '03

That the automated Yast2 installation has problems installing, because there is an original (older version) Operabrowser file on the DVD. greetings, herman ----- Original Message ----- Wrom: DMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJB To: <h_gorter(a)hotmail.com> Sent: Wednesday, February 19, 2003 12:00 PM Subject: Re: [suse-autoinstall] Suse 8.1 upgrade Operabrowser problems but, what has this question to do with the autoyast automated installation?!? Am Mittwoch, 19. Februar 2003 01:53 schrieb h_gorter(a)hotmail.com: > When I want to upgrade my Opera 6.3 that is included in the Linux Suse 8.1 > pack, I get problems. > > I have to install the download with Yast2, as Kpackage does not exist > anymore in the latest 8.1 version of Suse Linux. > The problem is, that with installing the upgrade 6.11 in Yast2, Yast2 asks > for the installation DVD. When I then click "Install" in the Yast2, it does > not install 6.11 but reinstalls the Opera 6.3 that is on the DVD. > > Another possibility is to install with xterm, but that does not reckognise > the downloded file...! So calling to Suse support, they advised me to > download the static version instead of the suse Linux version and then > install with xterm again. But for me xterm is pretty difficult. And that > does not work either. I get the downloaded upgradefile: > opera-6.11-20021129.1-static-qt.i386.rpm not installed in xterm. I type > there in supermode: rpm - U opera-6.11-20021129.1-static-qt.i386.rpm > > Does anyone know how to get in an easy way the newest version of the > Operabrowser in my Linux Suse 8.1 system? > > I have a similar problem with the newest version of Netscape. > > Thanks...! > herman

1 0

RE: [suse-autoinstall] automatically selecting smp kernel on cust om created autoinstall- cd
by RICHTER Jens NGLTS 19 Feb '03

19 Feb '03

OK, it works after updating the install system to autoyast2-installation-2.6.40-0. The original install system did not install any kernel, if no kernel package was mentioned in the software section of the autoinst.xml. With the new install system I do not have to specify the kernel package in my autoinst.xml, yast2 automatically selects the correct one. The patch description for 2.6.40 says it is possible to install an alternative kernel. How ist this done now ? Jens. > * RICHTER Jens NGLTS <Jens.Richter(a)framatome-anp.com> [Feb > 17. 2003 14:43]: > > Hi, > > > > i have a problem building a custom autoinstall cd based on SuSE 8.1. > > How can i convince autoinst to select the smp kernel when > installing a smp > > machine ? > > The custom cd should be able to hande up and smp machines alike. > > Is this possible ? > > Actually yast2 should automatically install an smp kernel if > SMP is detected! > grep /var/log/YaST2/y2log* for "Kernel determined" and let us > know what it > says. > > Anas > > > > Greetings Jens. > > > > > > ----------------------------------- > > Jens Richter > > Framatome ANP GmbH, NGLTS > > Mail: Jens.Richter(a)framatome-anp.com > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada >

1 0

post-scripts not executed
by Martin.Linten＠rzf.fin-nrw.de 19 Feb '03

19 Feb '03

Hallo! After the installation of suse 8.0 with autoyast2 I made several post-script modifications on the system, for example: <post-scripts config:type="list" > <script> <filename>gethosts.x</filename> <interpreter>shell</interpreter> <source> <![CDATA[#!/bin/sh mount -v -t nfs 130.11.6.52:/rzf/autoinst/config/files /mnt && \ echo "Old hosts" cat /etc/hosts cp -v /mnt/hosts /etc/hosts echo "New hosts" cat /etc/hosts umount -v /mnt]]> </source> </script> Now I tried to do the same with suse 8.1 and took the same xml files. The post scripts are not executed; I looked for an error message but found nothing. I tried to do some troubleshooting, but there are no files in /var/adm/autoinstall/logs or /var/adm/autoinstall/files etc. What could be the reason for this behaviour? Has anyone seen something similar? Please help & have a nice day, Martin

2 1

automatically selecting smp kernel on custom created autoinstall- cd
by RICHTER Jens NGLTS 19 Feb '03

19 Feb '03

Hi, i have a problem building a custom autoinstall cd based on SuSE 8.1. How can i convince autoinst to select the smp kernel when installing a smp machine ? The custom cd should be able to hande up and smp machines alike. Is this possible ? Greetings Jens. ----------------------------------- Jens Richter Framatome ANP GmbH, NGLTS Mail: Jens.Richter(a)framatome-anp.com

3 2

Suse 8.1 upgrade Operabrowser problems
by h_gorter＠hotmail.com 19 Feb '03

19 Feb '03

When I want to upgrade my Opera 6.3 that is included in the Linux Suse 8.1 pack, I get problems. I have to install the download with Yast2, as Kpackage does not exist anymore in the latest 8.1 version of Suse Linux. The problem is, that with installing the upgrade 6.11 in Yast2, Yast2 asks for the installation DVD. When I then click "Install" in the Yast2, it does not install 6.11 but reinstalls the Opera 6.3 that is on the DVD. Another possibility is to install with xterm, but that does not reckognise the downloded file...! So calling to Suse support, they advised me to download the static version instead of the suse Linux version and then install with xterm again. But for me xterm is pretty difficult. And that does not work either. I get the downloaded upgradefile: opera-6.11-20021129.1-static-qt.i386.rpm not installed in xterm. I type there in supermode: rpm - U opera-6.11-20021129.1-static-qt.i386.rpm Does anyone know how to get in an easy way the newest version of the Operabrowser in my Linux Suse 8.1 system? I have a similar problem with the newest version of Netscape. Thanks...! herman

1 0

Custom Selections
by Sven Thomsen 18 Feb '03

18 Feb '03

Hi, I'm having problems using my own package-selections: I've got a file named Sven.sel on my installation server located in /suse/setup/descr. ----- # SuSE-Linux-Package-Selection 3.0 -- (c) 2002 SuSE Linux AG # generated on Thu Sep 12 16:53:25 UTC 2002 =Ver: 3.0 =Sel: Sven =Sum: Sven =Cat: addon =Vis: true +Ins: SuSEfirewall2 aaa_base aaa_skel aaa_version acl ... ... ---- I've got the following lines in my xml-file: ---- ... <software> <addons config:type="list"/> <base>Sven</base> <packages config:type="list"> <package>harden_suse</package> <package>cups-client</package> <package>cups-libs</package> .... ---- Now, when I create a custom ISO-Image, I see in /var/log/YaST2/y2log: [wfm] PkgModuleFunctionsSelection.cc(SetSelectionString):286 Unknown selection 'Sven' What am I doing wrong? Sven

1 1

AW: [suse-autoinstall] Minimal Installation via http
by Prengel, Ralf 14 Feb '03

14 Feb '03

-----Ursprüngliche Nachricht----- Von: René Matthäi [mailto:matthaei@gmx.de] Gesendet: Donnerstag, 13. Februar 2003 17:45 An: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] Minimal Installation via http Brian Strand schrieb: > Prengel, Ralf wrote: > >> Autoyast works really fine here but I ve one problem. >> I m installing a minimal configuration via http. That works fine but >> after a reboot the http spurce isn t reachable any longer. >> It s clear that one or more packages are missing. >> Has anyone a hint which packages must be installed too. >> I tried several network-packages but it doesn t work. >> > I had a similar problem with minimal install which was solved by > adding the wget package; hopefully it will work for you too. Same here, too Thanks for all hints, wget was the solution.

1 0

Minimal Installation via http
by Prengel, Ralf 13 Feb '03

13 Feb '03

Autoyast works really fine here but I ve one problem. I m installing a minimal configuration via http. That works fine but after a reboot the http spurce isn t reachable any longer. It s clear that one or more packages are missing. Has anyone a hint which packages must be installed too. I tried several network-packages but it doesn t work. Thanks -- i.A. Ralf Prengel Customer Services Comline AG Dortmund/Germany Fon +49 231 97575-157 Fax +49 231 97575-257 EMail ralf.prengel(a)comline.de für Supportanfragen EMail support(a)comline.de Fon +49 231 97575-904 Fax +49 231 97575-905 Besuchen Sie uns auf der CeBIT 2003! Bei IBM in Halle 4, Stand A04 vom 12.-19. März 2003.

3 2

Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(
by Alejandro Gonzalez Madueno 12 Feb '03

12 Feb '03

Hi Anas First of all sorry for any kind of inconvenience is not my wishes I am in a process of a big customer migration to suse 80 professional using autoyast2. Just only in some servers, i have troubles during the partitionig phase of autoyast2, seems like the suse version is not able to re-read the partition table, even with the <initialize> tag included within the driver section. when the error occurs is shown a panel that indicates that the system has an invalid partition (re-try, abort, continue) if a hit the continue button the partitions are successfully formated and the suse installation progress but the lilo is no activated at the end of installation. please are you so kind to help me about that trouble ? Could be a good upgrade to autoyast2 allows to creates partitions with a 3rd utility like sfdisk included within a user scripts (another user-exit to autoyast :D ) I am working on this matter, I am reading the ycp autoyast programs to do that my self, but will be an unsopported hint or not :D Best Regards Subject: Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :( Hi Anas First of all thanks for your help I changes the xml as you explain in the attached note but without success: <partitioning config:type="list" > <drive> <initialize config:type="boolean">true</initialize> <device>/dev/rd/c0d0</device> <reuse>all</reuse> </drive> </partitioning> what is wrong ? resierfs and DAC960 modules are loaded before autoyast2 taking place. Best Regards ---------------------- Forwarded by Alejandro Gonzalez Madueno/Spain/IBM on 03/08/2003 12:07 PM --------------------------- Anas Nashif <nashif(a)suse.de> on 02/06/2003 04:03:45 AM To: Alejandro Gonzalez Madueno/Spain/IBM@IBMES cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :( * Alejandro Gonzalez Madueno <agonzalez(a)es.ibm.com> [Feb 05. 2003 17:20]: > > Hi Anas > > I added the tag <initialize config:type="boolean">true</initialize> > but no changes (is produced the same error). > > This system has a DAC960 hardware raid and the module is successfully > loaded > before autoyast2 excution. > > fdisk -l /dev/rd/c0d0 see successfuly the phisical disk > > bellow is exposed the whole xml file: > > <?xml version="1.0"?> > <!DOCTYPE profile SYSTEM "/usr/lib/YaST2/profile.dtd"> > <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" > http://www.suse.com/1.0/configns" > > <configure> > <runlevels> > <default>3</default> > </runlevels> > </configure> > <install> > <bootloader> > <activate config:type="boolean" >false</activate> > <linear config:type="boolean" >false</linear> > <location>mbr</location> > <parameters></parameters> > </bootloader> > <general> > <hwclock>localtime</hwclock> > <keyboard>spanish</keyboard> > <language>es_ES</language> > <mouse>probe</mouse> > <timezone>Europe/Madrid</timezone> > </general> > <initialize config:type="boolean">true</initialize> ^^^^^^^^^^^^^^^^ This goes into partitioning->drive > <partitioning config:type="list" > > <drive> > <device>/dev/rd/c0d0</device> > <reuse>all</reuse> > </drive> > </partitioning> > <report> > <confirm config:type="boolean" >false</confirm> > <errors> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </errors> > <messages> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </messages> > <warnings> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </warnings> > </report> > <software> > <addons config:type="list" /> > <base>standard</base> > </software> > </install> > </profile> > > > here attached the whole y2log: -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- 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 4

NFS based autoinstall from multiple sources...
by Frédéric Cros 10 Feb '03

10 Feb '03

Hi... I made my first attempt to use autoyast2 this week end and I'm still having some problems... Actually, I'm trying to find the "right" way of using it... Here's is what I am trying to do: I would like to setup an NFS autoinstall which lets me install the standard packages from the SuSE-8.1 DVD + some additional packages not included in SuSE-8.1. I decided to manage that by building a "custom" distribution directory which I called MGL-8.1 which contains the additional packages... I built MGL-8.1 by "duplicating" the structure of SuSE-8.1 and I believe it is correct as I can use it without problem with YaST2 as an additional distribution. I then organized the root of my NFS exported directory as indicated in the documentation (chapter 6) by creating the yast/order, etc... (See attachments...). When installing (booting a grub boot diskette with inst=IP://export the installation fails to locate the packages descr (from y2log, it is looking for ./suse/setup/descr). It seems that the content of the yast directory is just ignored (I can't find any mention of it in the logs) as the install does not find the SuSE-8.1 data. By the way, inst=IP://export/SuSE-8.1 works fine but, of course, does not handles my MGL-8.1 directory... Have I missed something??? Thanks in advance for any help... Fred. ----------------------------------------------------------------------- Frédéric Cros (fred(a)macguff.fr) http://www.macguff.fr Mac Guff Ligne Vox: +33 1 53 58 46 46 6, rue de la Cavalerie Fax: +33 1 53 58 46 47 75015 PARIS - FRANCE # yast/instorder: order of installation sources # # install 'ul' before 'sles8' # /yast/SuSE-8.1 /yast/MGL-8.1 #/ # yast/order: priority of installation sources # # source- product # description path /yast/MGL-8.1 /MGL-8.1 /yast/SuSE-8.1 /SuSE-8.1 #/ / This is the organisation of my NFS export directory: boot/ # copied from SuSE-8.1 content # copied from SuSE-8.1 media.1/ # copied from SuSE-8.1 profiles/ # where I store the intallation profiles... MGL-8.1/ # My custom directory media.1/ media # media ID (faked fom SuSE-8.1) content # content file, (faked fom SuSE-8.1) suse/ setup/ descr/ packages packages.DU packages.en SuSE-8.1/ # Pure SuSE DVD copy media.1/ media content suse/ setup/ descr/ *.sel packages packages.DU packages.en packages.de ... packages.pt yast/ instorder # instorder file order # order file MGL-8.1/ # symlink to ../MGL-8.1 SuSE-8.1/ # symlink to ../SuSE-8.1 NOTE: I tryed with both symlinks and full copies of MGL-8.1/ & SuSE-8.1/ but it made no difference...

1 0

PXE boot check script
by Frank Pascher 10 Feb '03

10 Feb '03

Hi, this is the script I use to check whether a pxe-file has been accesed or not. As soon a pxe-configuration has been served to a client the atime-value of the file is changed. After this happened the file can be deleted. Copy this script to a location you want and change it to be executable. Next set up a cron jop to run this script periodically. For example every 15 min. Have fun. frank #!/usr/bin/perl $logfile = "/var/log/pxecheck"; $dirname = "/tftpboot/pxelinux.cfg"; ($day,$mon,$year,$h,$min,$sec) = (localtime)[3,4,5,2,1,0]; open (logdatei,">> $logfile") ||die "cannot open logfile $logfile"; print logdatei "--------------------------------------------------------------------------- -----\n"; print logdatei "PXE-Directory : $dirname\n"; print logdatei "$day.",$mon+1,".", $year+1900," $h:$min:$sec\n"; opendir(d,$dirname); @content = sort(grep(!/(^\.\.?$)|(default)/,readdir(d))); closedir(d); while ($file = shift(@content)) { $file = "$dirname/$file"; ($mtime,$atime) = (stat $file)[9,8]; if ($atime > $mtime) { unlink($file); print logdatei "$file accessed deleted\n"; }else{ print logdatei "$file not accessed not deleted\n"; } } print logdatei "--------------------------------------------------------------------------- -----\n"; close (logdatei); +----------------------------------------------------------+ | Max-Planck-Institut für Radioastronomie | | Abt.1 (wissenschaftliche DV) | | | | Frank Pascher | +----------------------------------------------------------+ | Auf dem Huegel 69 Tel.: +49 (228) 525 359 | | 53121 Bonn Fax.: +49 (228) 535 229 | +----------------------------------------------------------+ | Email: mailto:fpascher@mpifr-bonn.mpg.de | | WWW: http://www.mpifr-bonn.mpg.de | | PGP Fingerprint: 13D1 8C86 57B3 2850 F158 4879 E5F3 7E20 | +----------------------------------------------------------+

1 0

rc.config and profiles. (SuSE 8.1)
by Scott Simmons 06 Feb '03

06 Feb '03

Ok I'm sneaking 2 question in on this one... First if the file rc.config is now directory how do I have an application point to the file that now doesn't exist? IE I'm trying to use Samsung Contact which is wanting to point to ect/rc.config for some of it's information. Second How do I edit the root profile, .bash_profile doesn't exist either? I'm just looking to add some directories to the PATH= Statement for root. It seems that Suse is very different in relation to files and there location, Any point in the right direction will be appreciated. Scott Simmons Holden Andrew Corp. ssimmons(a)holdenandrew.com

1 0

AW: [suse-autoinstall] autoinstall SLES8 [NFS repository / additi onal packages]
by Schmitt, Jochen 06 Feb '03

06 Feb '03

Hi, so I kept going as you told. I sucessfully copied the SLES and UL cds into the required directory and added the new nfs source in yast. Works! Then I put additional packages into /export/SLES8/sles8-i386/CD1/suse/i586 as someone else was told before. Then I run the following command hostname:/export/SLES8/sles8-i386/CD1/suse # /usr/lib/YaST2/bin/create_package_descr -d /export/SLES8/sles8-i386/CD1/suse -l english The output was as follows: using settings: datadirs: /export/SLES8/sles8-i386/CD1/suse languages: english output dir: ./setup/descr/ is not a directory: ignoring extra_provides: /usr/share/autoinstall/EXTRA_PROV ............... done processed 159 packages now recoding to UTF-8: packages packages.DU packages.en So, the two additional packages have benn recognized. But something seems to go wrong. When I start a yast and try to install these packages, they are not know. What about /usr/share/autoinstall/EXTRA_PROV may I change that directory ro my own needs? Can I use additional directories except e.g. i586, noarch, ... What does aotiyast expect to be in /usr/share/autoinstall/EXTRA_PROV? Regards, Jochen -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: 06 February 2003 03:25 An: Schmitt, Jochen Cc: 'suse-autoinstall(a)suse.com' Betreff: Re: [suse-autoinstall] autoinstall SLES8 [NFS repository / additional packages] * Schmitt, Jochen <Jochen.Schmitt(a)rewe.de> [Feb 03. 2003 18:19]: > Hi, > > I try to create one single NFS Source for autoinstallation and Yast for > installed systems. > I followed 6.1.3 in the autoyast manual. I can select my NFS repository in > "Change source of installation" but I am not able to search for packages. > There seems to be nothing in it. e.g. rsync. The system was installed > manually. > You have to add UL and SLES sources as different sources. For example, if you have followed the instruction in 6.1.3 you will have an NFS mounted directory with "ul" and "sles8" (might be with other names of course) sub-directories. You have to add those seperatly, i.e. first source will be <server ip>/exports/sles8/sles/CD1 and source 2 will be <server ip>/exports/sles8/ul/CD1 /exports/sles8 is where both UL and SLES have been copied as described in 6.1.3. > Where do I put additional packages (rpms) which came not with SLES8 or > update-packeges from the MW? You can put them in either SLES or UL, but make sure there are no duplicates and remove older versions. When adding new packages, you have to create the package database as described in in the manual for autoyast. Anas > > > Jochen > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Adding own/custom rpms
by Sven Thomsen 06 Feb '03

06 Feb '03

Hi there, I have trouble adding my own rpms for an automated installation. Has anyone succeded with this and can post the necesserary steps? - I've tried + adding my own directory besides i586/i686/noarch, named "sven" or "custom" + adding my rpms to the directories above + adding a i386 directory with my rpms - I've called /usr/lib/YaST2/bin/create_package_descr + packages, packages.DU get updated and I can see my packages in there But when I create an ISO-Image not a single rpm is copied to the generated structure in /tmp/YaST.... I'm using autoyast2-installation-2.6.40-0 and autoyast2-2.6.40-0. Where's my fault? Sven

3 7

Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(
by Alejandro Gonzalez Madueno 06 Feb '03

06 Feb '03

Hi Anas First of all thanks for your help I changes the xml as you explain in the attached note but without success: <partitioning config:type="list" > <drive> <initialize config:type="boolean">true</initialize> <device>/dev/rd/c0d0</device> <reuse>all</reuse> </drive> </partitioning> what is wrong ? resierfs and DAC960 modules are loaded before autoyast2 taking place. Best Regards ---------------------- Forwarded by Alejandro Gonzalez Madueno/Spain/IBM on 03/08/2003 12:07 PM --------------------------- Anas Nashif <nashif(a)suse.de> on 02/06/2003 04:03:45 AM To: Alejandro Gonzalez Madueno/Spain/IBM@IBMES cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :( * Alejandro Gonzalez Madueno <agonzalez(a)es.ibm.com> [Feb 05. 2003 17:20]: > > Hi Anas > > I added the tag <initialize config:type="boolean">true</initialize> > but no changes (is produced the same error). > > This system has a DAC960 hardware raid and the module is successfully > loaded > before autoyast2 excution. > > fdisk -l /dev/rd/c0d0 see successfuly the phisical disk > > bellow is exposed the whole xml file: > > <?xml version="1.0"?> > <!DOCTYPE profile SYSTEM "/usr/lib/YaST2/profile.dtd"> > <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" > http://www.suse.com/1.0/configns" > > <configure> > <runlevels> > <default>3</default> > </runlevels> > </configure> > <install> > <bootloader> > <activate config:type="boolean" >false</activate> > <linear config:type="boolean" >false</linear> > <location>mbr</location> > <parameters></parameters> > </bootloader> > <general> > <hwclock>localtime</hwclock> > <keyboard>spanish</keyboard> > <language>es_ES</language> > <mouse>probe</mouse> > <timezone>Europe/Madrid</timezone> > </general> > <initialize config:type="boolean">true</initialize> ^^^^^^^^^^^^^^^^ This goes into partitioning->drive > <partitioning config:type="list" > > <drive> > <device>/dev/rd/c0d0</device> > <reuse>all</reuse> > </drive> > </partitioning> > <report> > <confirm config:type="boolean" >false</confirm> > <errors> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </errors> > <messages> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </messages> > <warnings> > <log config:type="boolean" >true</log> > <show config:type="boolean" >true</show> > <timeout config:type="integer" >10</timeout> > </warnings> > </report> > <software> > <addons config:type="list" /> > <base>standard</base> > </software> > </install> > </profile> > > > here attached the whole y2log: -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

PXE loop
by Frank Pascher 06 Feb '03

06 Feb '03

Hi, I'm having a "small" problem concerning PXE installation. The installation and everything works fine But as it comes to a reboot of the machine the installation starts again. Ok that's still ok, because the pxe setup has to be changed to local boot for the client. But I don't want to do it by hand, cause for more than 200 clients it is a litle bit to much work. In the autoyast manual it is recommended to check the syslog for an initial transmitted RAM disk. The problem is that I can't find the appropriate line, even if I start the tftp-servecie with -v option. Could anyone give some advice, how to configure the tftpd and how to scan the syslog (example shell/perlscript ??)? Any help would be appreciated. cheers fp +----------------------------------------------------------+ | Max-Planck-Institut für Radioastronomie | | Abt.1 (wissenschaftliche DV) | | | | Frank Pascher | +----------------------------------------------------------+ | Auf dem Huegel 69 Tel.: +49 (228) 525 359 | | 53121 Bonn Fax.: +49 (228) 535 229 | +----------------------------------------------------------+ | Email: mailto:fpascher@mpifr-bonn.mpg.de | | WWW: http://www.mpifr-bonn.mpg.de | | PGP Fingerprint: 13D1 8C86 57B3 2850 F158 4879 E5F3 7E20 | +----------------------------------------------------------+

2 2

[suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(
by Alejandro Gonzalez Madueno 06 Feb '03

06 Feb '03

Sorry Anas :) I missed the y2log in the previous append 11:03:54 <1> linux(686) [YCP] clients/inst_prepdisk.ycp:523 partitioning .disk.rd.c0d0.partitio ns [$["delete":true, "fsid":5, "fstype":"Extended", "nr":1, "region":[0, 2212], "type":`extended, "ui_id": 1], $["delete":true, "fsid":131, "fstype":"Linux native", "nr":5, "region":[0, 653], "type":`logical, "ui_ id":2], $["create":true, "format":true, "fsid":131, "mount":"/boot", "nr":1, "region":[0, 3], "type":`prim ary, "used_fs":`ext2], $["create":true, "format":true, "fsid":130, "mount":"swap", "nr":2, "region":[3, 82 ], "type":`primary], $["create":true, "format":true, "fsid":131, "mount":"/", "nr":3, "region":[85, 2127], "type":`primary, "used_fs":`reiser]] 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):172 device '/rd/c0d0', cmd 'pa rtitions' 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(FdiskAccess):75 Head=255 Sector:63 Cyli nder:2212 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(SystemCmd):48 Konstruktor SystemCmd Us eTmp:1 Nr:0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(InitFile):103 File:"/tmp/YaST2.tdir/st p686_0_S" 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 5 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 1, start 1, end 3 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 1 to 83 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 2, start 4, end 85 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 2 to 82 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 3, start 86, end 2212 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 3 to 83 2003-02-05 11:04:01 <3> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(WritePartitionTable):544 Writing partit ion table failed 2003-02-05 11:04:01 <3> linux(686) [YCP] clients/inst_prepdisk.ycp:534 Oops, fdisk failed for device 2003-02-05 11:04:01 <3> linux(686) [Interpreter] clients/inst_prepdisk.ycp:540 Undefined function Storage: y2log lines 50-71/76 92% I tested the <initilize> tag set to "true" but does not work in another system that has /dev/hda is produced the same behaviour where is the fault ?

2 1

autoinstall SLES8 [NFS repository / additional packages]
by Schmitt, Jochen 06 Feb '03

06 Feb '03

Hi, I try to create one single NFS Source for autoinstallation and Yast for installed systems. I followed 6.1.3 in the autoyast manual. I can select my NFS repository in "Change source of installation" but I am not able to search for packages. There seems to be nothing in it. e.g. rsync. The system was installed manually. Where do I put additional packages (rpms) which came not with SLES8 or update-packeges from the MW? Jochen

2 1

RE: [suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(
by Alejandro Gonzalez Madueno 05 Feb '03

05 Feb '03

Sorry Anas :) I missed the y2log in the previous append 11:03:54 <1> linux(686) [YCP] clients/inst_prepdisk.ycp:523 partitioning .disk.rd.c0d0.partitio ns [$["delete":true, "fsid":5, "fstype":"Extended", "nr":1, "region":[0, 2212], "type":`extended, "ui_id": 1], $["delete":true, "fsid":131, "fstype":"Linux native", "nr":5, "region":[0, 653], "type":`logical, "ui_ id":2], $["create":true, "format":true, "fsid":131, "mount":"/boot", "nr":1, "region":[0, 3], "type":`prim ary, "used_fs":`ext2], $["create":true, "format":true, "fsid":130, "mount":"swap", "nr":2, "region":[3, 82 ], "type":`primary], $["create":true, "format":true, "fsid":131, "mount":"/", "nr":3, "region":[85, 2127], "type":`primary, "used_fs":`reiser]] 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):172 device '/rd/c0d0', cmd 'pa rtitions' 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(FdiskAccess):75 Head=255 Sector:63 Cyli nder:2212 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(SystemCmd):48 Konstruktor SystemCmd Us eTmp:1 Nr:0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] SystemCmd.cc(InitFile):103 File:"/tmp/YaST2.tdir/st p686_0_S" 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 5 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):270 deleting partition 1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 1, start 1, end 3 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 1 to 83 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 2, start 4, end 85 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:54 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 2 to 82 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):289 creating partition: type 5 , nr 3, start 86, end 2212 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):643 DelLast=0 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(NewPartitionStd):658 Ok=1 2003-02-05 11:03:55 <1> linux(686) [yast2-agent-fdisk] FdiskAgent.cc(Write):298 setting type of partition 3 to 83 2003-02-05 11:04:01 <3> linux(686) [yast2-agent-fdisk] FdiskAcc.cc(WritePartitionTable):544 Writing partit ion table failed 2003-02-05 11:04:01 <3> linux(686) [YCP] clients/inst_prepdisk.ycp:534 Oops, fdisk failed for device 2003-02-05 11:04:01 <3> linux(686) [Interpreter] clients/inst_prepdisk.ycp:540 Undefined function Storage: y2log lines 50-71/76 92% I tested the <initilize> tag set to "true" but does not work in another system that has /dev/hda is produced the same behaviour where is the fault ? Best Regards -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES8 / own and custom packages
by Schmitt, Jochen 05 Feb '03

05 Feb '03

Hi, so far I did not get an answer to my question before. Therefor I moved to another documentation for SLES8. As decribed in the SLES8 handbook I copied all the CDs into one directory, which is exported by NFS. Does anyone know where to put my own rpms? In i386 or i586? I did that. But the rebuild of the package database, as described in the SLES8 handbook on page 72 did not work. Regards, Jochen

1 0

[suse-autoinstall] re-read partition table HELP !!!!!!!!!!!!! :(
by Alejandro Gonzalez Madueno 04 Feb '03

04 Feb '03

-ct: re-read partition table HELP !!!!!!!!!!!!! :( G´day I have a trouble using autoyast2 from suse 8.0 professional version. First of all bellow is exposed my enviroment: ENVIROMENT ========== * suse 8.0 professional (with all patches applyed) * yast - 2.5.91 * yast2-module-autoinst-2.5.27rc3-0.noarch.rpm * 6GB IDE hard disk (exist primary linux partitions to destroy) XML === I wanna destroy the whole disk partitions. In order to do that I´m using this partition scheme: <partitioning config:type=list"> <drive> <device>/dev/hda</device> <reuse>all</reuse> </drive> </partitioning> When autoyast trates to creates the partitions in a unattended way (autoyast2), apears a message like: "The device /dev/hda has an invalid partition table. Set a valid one. This problem is reproduced also in a manual way, but i´m be able to fix the problem, using the re-read partiton table option located within the yast2 partitions expert menu. exist any unattended procedure to re-read the partitions table for suse 80 ? (without a system boots). right now suse 80 is a MUST in my organization and i couldn´t migrate to suse 8.1 Best Regards Alexander gonzalez

2 1

LVM over software RAID
by Brian Strand 04 Feb '03

04 Feb '03

Has an successfully gotten an autoinstall of LVM over software RAID? I can get sw RAID alone to work, but not LVM over sw RAID. I'm working from Suse 8.1 Professional (boxed). The configuration snippet follows at the end of this email. Note that this is a class I had been trying to merge with other profiles, so it is not a comlete autoinstall configuration. I get a single error when I run this through "xmllint --valid sw-raid.xml": sw-raid.xml:145: validity error: Element raid_device content doesn't follow the DTD Expecting (device_name , parity_algorithm , persistent_superblock , raid_level , chunk_size , mount , format , filesystem), got (device_name parity_algorithm persistent_superblock raid_level chunk_size mount format lvm_group ) </raid_device> ^ I had to put multiple logical_volumes elements in to get this far; it looks like there's a bug in the DTD (the following patch against autoyast2-installation-2.6.40-0 might fix it): --- /usr/share/YaST2/include/autoinstall/misc2.dtd.orig 2003-01-01 19:40:39.000000000 +0000 +++ /usr/share/YaST2/include/autoinstall/misc2.dtd 2003-02-04 20:50:57.000000000 +0000 @@ -20,7 +20,7 @@ <!ATTLIST inetd_services config:type CDATA #REQUIRED > -<!ELEMENT logical_volumes (lv)> +<!ELEMENT logical_volumes (lv+)> <!ATTLIST logical_volumes config:type CDATA #REQUIRED > I'm not sure how strictly (or if) the auto-installer follows the DTD, so I don't know if there are other fixes needed besides the DTD. In spite of this and a few other minor issues, I have to say I'm quite impressed with Suse's auto-install system; Anas has done a great job! (Especially as it appears to be a one-person show, judging from the traffic on this list.) Best regards, Brian sw-raid.xml: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd">  <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <lvm config:type="list"> <lvm_group> <lvm_name>switch</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>root</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>usr</lv_name> <lv_size>1800M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>usr-local</lv_name> <lv_size>200M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr/local</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>opt</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/opt</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>var</lv_name> <lv_size>2000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>home</lv_name> <lv_size>1000M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/home</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>tmp</lv_name> <lv_size>800M</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> </logical_volumes> <logical_volumes config:type="list"> <lv> <lv_name>tmp</lv_name> <lv_size>200M</lv_size> <lv_fs>swap</lv_fs> <lv_mount>/tmp</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hde</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_name>/dev/md0</raid_name> <size>100M</size> </partition> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdg</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_name>/dev/md0</raid_name> <size>100M</size> </partition> <partition> <format config:type="boolean">false</format> <mount/> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md0</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock>true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>4</chunk_size> <mount>/boot</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> </raid_device> <raid_device> <device_name>/dev/md1</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock>true</persistent_superblock> <raid_level>1</raid_level> <chunk_size>4</chunk_size> <mount/> <format config:type="boolean">false</format> <lvm_group>switch</lvm_group> </raid_device> </raid> </install> </profile>

2 1

corrupt files on Suse 8.1 DVD?
by Brian Strand 04 Feb '03

04 Feb '03

Has anyone else encountered corrupted files on the DVD version of Suse 8.1? The size of some files does not match that of the same files on the CD. The files I ran into included boot/root (DVD 7073792 bytes, CD 40628224 bytes) and the kernel RPMs suse/i586/k_*.i586.rpm. Hopefully if anyone else is having mysterious errors like "cannot execute /almost/any/file" and such during autoinstall (caused by a corrupt cramfs image file boot/root), this will save them some grief. I spent 6 hours chasing down this problem (I thought it was PXE booting that was causing the problems). Once I replaced the DVD files with the CD files, everything worked well (I have the DVD copied to an NFS-exported filesystem). Or perhaps my DVD or player is just messed up; unfortunately I only have one DVD drive operational at the moment, and only one DVD. Best regards, Brian

1 0

X11 configuration does not work after autoinstall
by Martin.Pelikan＠t-systems.com 04 Feb '03

04 Feb '03

Hi, I installed SuSE 8.0 with autoinstall from an NFS Server and it worked fine. The only problem is when I start to configure X11 (yast2 x11), the X server configuration starts and stops after a second again, I can't do any changes . yast x11 also doesn't work. When I install the System from DVD or CD (interactive) , i don't have any problems with the X11 configuration. Any ideas ? Thanks for help, Martin

1 0

Documentation for custom CD?
by Zacki 04 Feb '03

04 Feb '03

Hi there, on my search on the maillinglist for instructions or help to create a custom CD i found an articel from anas nashif about documentation. http://lists2.suse.com/archive/suse-autoinstall/2002-May/0005.html My first question, where can i find this one and mybe can someone send me the link. Then i found an article from Hella Breitkopf where she described to create an ISO-file manually but with SuSE 8.0. Now my second question, is it possible to do this for SuSE 8.1?. I've tried it but as you can see in a former mail it did not work. I have really done everything...my system is uptodate and i have the latest patch, do i need special packages? Uwe Maurer wrote that syslinux must be installed (i have allready installed but there was no success). Are there any other basic packages? Thanks in advance Greetings Zacki -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!

1 0

chroot scripts and mkinitrd
by Andy Wray 03 Feb '03

03 Feb '03

I'm trying to setup an unattended network install on a system with an LSI 53c1030 SCSI controller running the boot drive. There's a bug in the SuSE 8.1 installer (SuSE 8.1 is what I'm trying to install) that leaves the mptbase driver that is needed by the mptscsih driver out of the /etc/sysconfig/kernel file, and consequently it isn't included in the initrd, so on the first bootup, mptscsih fails to load and the system can't mount /. To fix this I thought I'd run a chroot script to update the /etc/sysconfig/kernel file. However, although this file appears to run (there's output in the /var/adm/autoinstall/logs directory), the /etc/sysconfig/kernel file remains unchanged. Of course, even if this worked, I'm not sure if it would fix the problem since I'm not sure if the chroot scripts run before or after mkinitrd. I've appended a portion of the autoyast installation file below. Can anyone help me with this? (The alternative I have right now is that there is a replacement mkinitrd on the SuSE ftp site provided as a diskette image, but this doesn't help much for an unattended network install. mkinitrd appears to be part of the aaa_base package, so I was thinking I could replace it in that package, but I'd rather not do that if possible). <scripts> <chroot-scripts config:type="list"> <script> <filename>fixinitrd.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh cat /mnt/etc/sysconfig/kernel #for debug sed 's/mptscsih/mptbase mptscsih/g' /mnt/etc/sysconfig/kernel > /mnt/etc/sysconfig/kernel.new cat /mnt/etc/sysconfig/kernel.new #for debug rm -f /mnt/etc/sysconfig/kernel mv /mnt/etc/sysconfig/kernel.new /mnt/etc/sysconfig/kernel cat /mnt/etc/sysconfig/kernel.new #for debug ]]> </source> </script> </chroot-scripts> </scripts> Thanks, --Andy

2 6