openSUSE Autoinstall February 2003

autoinstall@lists.opensuse.org

27 participants
42 discussions

by Urs Haberthuer

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

19 years, 2 months

FW: Live Eval CD wie?

by hb9irb

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

19 years, 2 months

partitioning problem

by Claude Arnold

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

19 years, 2 months

Error: disk space exhausted

by Claude ARNOLD

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

19 years, 2 months

couldn't find valid ramdisk image

by Claude Arnold

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

19 years, 2 months

Cloning Suse 8.1 Installation

by Joerg Friedrich

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.

19 years, 2 months

Changing the user to anonymous when doing an ftp install.

by Rowan Reid

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

19 years, 2 months

SuSE Linux 8.1 Autoinst with YAST2 and the common.pkd file

by Orenchak, James

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

19 years, 2 months

Disappearing packages

by Sven Thomsen

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

19 years, 2 months

Integration of KDE 3.1 Updates?

by Sven Thomsen

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

19 years, 2 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2003