openSUSE Autoinstall July 2003

autoinstall@lists.opensuse.org

28 participants
58 discussions

Problem after creating new package db
by Daniel Bertolo 09 Jul '03

09 Jul '03

Hi I would like to update my repository with some updated RPMs. As described in the autoyast howto, I run "/usr/lib/YaST2/bin/create_package_descr -d /install/suse -l german -l english". The package describtions will be created and stored in "./setup/descr". But when I would like to configure the packages in autoyast, hundreds of dependencies failed, starting with "missing /bin/awk; missing /bin/bash" etc. The only way I found to fix it was to recopy the repository from the DVDs. But then I still have the old packages. What do I do wrong? By the way: What is the best way in order to keep the repository up-to-date. Is there a way that the clients always boot over the network in order to check for updates? I would like the clients to do the following during boot: - Boot over network using PXE - Check if there is a local linux installation - If no -> install - If yes -> compare the installed packages to the repository - If there are updates -> install the updated packages -> local boot - If there are no updates -> local boot This is what the SuSE Smart Client Framework does. But how do I implant this? There is no howto and the consultants I know do not want to tell me how to do it unless they can do it. Thanks for help. Daniel Bertolo

1 0

WG: configure nsswitch.conf
by Daniel Bertolo 08 Jul '03

08 Jul '03

Hi I set up an autoinstall server using pxe-boot. For authentication I use LDAP. Unfortunately, if LDAP-client is configured in autoyast, the local users are not available anymore (e.g. root). I found the problem in the nsswitch.conf file. There are the following entries: passwd: ldap group: ldap But there should be "ldap files" instead. How can this be configured during the autoinstall process? Thanks, Daniel

2 1

AW: [suse-autoinstall] Adding custom RPMs to an NFS install setup
by Michael.Regner＠dbv-winterthur.de 08 Jul '03

08 Jul '03

Hello Anas, you told to use create_package_descr after creating a directory structure like given in you tgz file. But I don´t know how to use this tool. Can you please give short description? ThanX Michael Regner -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Dienstag, 8. Juli 2003 07:33 An: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] Adding custom RPMs to an NFS install setup Marc Christensen wrote: > Anas, > > Thanks for the great info.... > > [snip] > > >>Using the above names, the order files would have the follwing >>configuration: >> >># cat yast/instorder >>/UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 >>/CustomPackages /CustomPackages >>/SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 >>/ / > > > > I have set up these files before according to the pdf that I mentioned > before but it did not mention the / entry. Is it nessasery? > No, not really, if it works for you. "/" is needed in cases one copied a source directly into the root of the export. > [snip] > >>Now you can add packages as you wish to the CustomPackages >>repository. Dont forget to run the create_package_descr script when >>updating or adding new packages. > > > > Now, do these new packages get installed automaticaly? Or does the user > need to do something to get them installed? If not, is there a way to > get them installed without user intervention? > You have to add them in the software resource. Otherwise yast2 will just not install them, just like any other package. An alternative is to add them to a selection, but one should avoid changing the default selections cause those are tested and work fine. > And just for my information, does SuSE 8.2 folow the same method for NFS > installs as SLES or SuSE 8.1? 8.2 actually does not follow this method. 8.2 should follow this, although 8.2 is not a multi-source release. Anas > > Thanks much. > > -- > Marc Christensen > http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=9502 > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

changing autofs to autofs4 in default.sel doesn't work
by Fermín Galán 07 Jul '03

07 Jul '03

Hello everyone! I'm trying to change the default automounter package that is instaled by default, from "autofs" to "autofs4". I suppose that the way to do so is changing in default.sel (in the server repository) the line with "autofs" to "autofs4" (I also have re-create the packages database with create_pakage_descr, although I don't know whether this is really needed after changing .sel files). But this doesn't work! The old "autofs" is installed, not the desired "autofs4". Somebody knows what is the cause or how to solve the problem? Thanks in advance! ------------ Fermín

1 0

Error while installing addtional Packages
by silverio.santos＠equant.com 04 Jul '03

04 Jul '03

Hi, I am trying to create an ISO-image using the configuration of a system whose configuration I extracted using AutoYaST's clone-function. First I copied the content of the CDs into a folder on the HDD, created an i386 folder below suse, copied the additional package into it and left create_package_descr do its job. Then I created the iso-file, wrote the CD and booted the target-system successfully from it. While installation on the target-system the following appears while configuring software selections: "Error while configuring software selections" and exits to the text-linuxrc. The package has been copied onto the CD into the i386-folder, so the package-description was obviously correct. The package name in the .xml-file has been created by the clone-function on the template-system. Removing this additional package's <package>-entry from the .xml-file provides a fully working automatic installation. On one hand the ISO-file-creation identifies and uses the correct file. On the other hand it looks to me like AutoYaST-Installation is unable to find the filename that is assigned to the package name. May this supposition be correct and if so how can I find the correct "short name" of the package to be installed? But maybe there is another explanation... Thanks and best regards Silvério Santos

1 0

parsing control file
by Robert Alonso 03 Jul '03

03 Jul '03

Has anyone else experienced this? I've got my info file set to point to a directory. Hence, yast should look for the control file first by hex IP address and then 'default'. Well, I forgot to symlink the control file with default, so it couldn't find a control file. So up comes a prompt asking me to explicitly name the file. I enter the name and it begins to process it, but dies when creating partition plans saying that there is an error with the partition plans - please check the syntax of the control file. I tried a few times with the same result. However, when I created 'default' and linked it to the exact same file, it works. So the bug appears to be that although it prompts the user to explicitly name the control file, it doesn't actually process it. If you have any hints or info, please let me know. Thanks, Robert p.s. I also tried explicitly naming the control file in the info file, and that works fine.

2 1

Problems with autoinstalling on server with FC-HBA
by BLassen＠haitec.de 03 Jul '03

03 Jul '03

Dear list ... I'm having severe problems with using autoyast to install SL 8.2 on my servers. I've set up an environment as the one in the document by Anas Nashif That means I'm using DHCP, TFTP and NSF to distribute the kernel initrd and the controlfile The distribution part is working flawless, but it seems as if the partioning is goinig awry somehow. The servers I'm using dont have any local disks but get them through a FC SAN. IThey start up without any problems , load the kernel and initrd, start the HW detection and seem to load all the drivers that are needed. But when it comes to start installing thr packets an errormessage is thrown that states that there is no space left on the HD This is definitly not true, because I've just initialized it -> meaning its absolutly empty Has anybody a clue why this is happening or how I can get more information what is going wrong ? TIA Bengt

2 2

XFree not configured
by Leandro Gelasi 02 Jul '03

02 Jul '03

Hi to all. I am trying to create custom installation disks (for network install) to be used on varius pc in our net. All seem fine, but the installation process fails to configure X11 subsytem on the test computer. The newly installed system starts at runlevel 5, but Kdm doesn't start because XF86Config is wrong. I think the problem is my VGA adapter (S3 Trio3d), sax2 can't correctly recognize it, altought 'xf86config' can be successfully used to set it up correctly. I also tried with another card (an old Cirrus Logic PCI) with no success. At this point I can't try it with other hardware. Any hints? TIA LG -- Leandro Gelasi Servizio supporto utenti Linux Email: supporto.linux(At)uniroma1(punto)it Home Page: http://linuxhelp.uniroma1.it Università di Roma "La Sapienza" - C.I.T.I.Co.R.D. Centro Interateneo per le Tecnologie dell'Informazione e la Comunicazione nella Ricerca e nella Didattica

1 0

reread partitions
by Lars Stavholm 02 Jul '03

02 Jul '03

Hi all, does anyone know of a way to make autoyast reread the partition table(s) after (or at the end of) a pre-script execution? I'm trying to remove the current partitions, if any, using "parted", which succeeds. However, I'm guessing that autoyast already has a pretty good idea of the current partition plan based on a partition table(s) read prior to my usage of "parted"? R/Lars S

2 4

remote-boot with TCP/IP BOOT-PROM (BOOTIX)
by tom＠korsika-camp.de 02 Jul '03

02 Jul '03

hey, i've got a nic with an tcp/ip boot-prom (bootix), which requires exactly one bootdisk-image. is there any possibility to create such a disk, merging the existing boot- and modules-disks from the first suse-cd? just using the image of the normal bootdisk, requires to insert the modules-disks. but i cant see any way to get them from tftp-server. any ideas? thanks for your answers Tom

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall July 2003