July 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] Xserver configuration
by Martin Schmiderer 17 Jul '03

17 Jul '03

Am Donnerstag, 17. Juli 2003 15:52 schrieb Thomas Mack: > Am Donnerstag 17 Juli 2003 14:44 schrieb Martin Schmiderer: > > Hello *, > > > > i am trying to use autoyast to install a lot of clients automaticly. That > > works fine without configure X11, but i will configure the xserver by > > autoyast and the default runlevel must be 5! > > How can i do this ??? > > Ein Beispiel aus einer 8.2 Konfiguration (yast2->Sonstiges->Automatische > Installation und dann konfigurieren): > > > <?xml version="1.0"?> > <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> > <profile xmlns="http://www.suse.com/1.0/yast2ns" > xmlns:config="http://www.suse.com/1.0/configns"> > <configure> > <x11> > <color_depth config:type="integer">16</color_depth> > <configure_x11 config:type="boolean">true</configure_x11> > <display_manager>kdm</display_manager> > <enable_3d config:type="boolean">true</enable_3d> > <monitor> > <display> > <frequency config:type="integer">75</frequency> > <height config:type="integer">1200</height> > <max_hsync config:type="integer">95</max_hsync> > <max_vsync config:type="integer">82</max_vsync> > <min_hsync config:type="integer">30</min_hsync> > <min_vsync config:type="integer">58</min_vsync> > <width config:type="integer">1600</width> > </display> > <monitor_device>1600X1200@75HZ</monitor_device> > <monitor_vendor> LCD</monitor_vendor> > </monitor> > <resolution>1152x864</resolution> > <start_x11 config:type="boolean">true</start_x11> > <window_manager>kde</window_manager> > </x11> > </configure> > </profile> > > > Im Grunde spezifiziert man nur den Monitor und die Auflösung, sagt noch, ob > man > 3D etc. haben möchte, und das war es dann auch schon. Der Rest wird > automatisch > gemacht. > > Wir haben bei uns XF86Config Dateien vorkonfiguriert, die wir dann in einem > post-script nach /etc/X11 kopieren. Das kann sich auch empfehlen, wenn das > autoyast alleine keine vernünftige X-Konfiguration hinbekommt. > > Im Grunde dürfte die Konfiguration mit Yast2 unter einem lauffähigen 8.2 > die einfachste und schnellste Lösung zu sein. Die individuellen Anpassungen > kann man dann anschließend auf einfache Weise hinzustricken. > > > Thomas Mack > TU Braunschweig, Abt. Informationssysteme Hi Thomas, vielen Dank fuer die Hilfe! Das funktioniert prima. regards Martin -- ________________________________creating IT solutions Martin Schmiderer science + computing ag System Administration Hagellocher Weg 71-75 phone +49 7071 9457 225 72070 Tuebingen, Germany fax +49 7071 9457 211 www.science-computing.de

1 0

Xserver configuration
by Martin Schmiderer 17 Jul '03

17 Jul '03

Hello *, i am trying to use autoyast to install a lot of clients automaticly. That works fine without configure X11, but i will configure the xserver by autoyast and the default runlevel must be 5! How can i do this ??? regards Martin -- ________________________________creating IT solutions Martin Schmiderer science + computing ag System Administration Hagellocher Weg 71-75 phone +49 7071 9457 225 72070 Tuebingen, Germany fax +49 7071 9457 211 www.science-computing.de

1 0

Re: [suse-autoinstall] rpm update errors
by Ricardo Kleemann 16 Jul '03

16 Jul '03

Thank you. But if yast can take care of the dependency problems, how should I go about installing the updates? Should I use a command other than "online_update" to perform the installs? Because that command is encountering errors when I try to install (with -i) Ricardo ----- Original Message Follows ----- > Op woensdag 16 juli 2003 16:58, schreef Ricardo Kleemann: > > Hello, > > > > I use the online_update script via cron to download > > packages, and then I use it manually to install > packages. > > > Recently, updates to apache2 were downloaded, but > > running online_update -i returns an error when trying to > > update apache. > > > > So then I decided to try updating apache manually via > > rpm, here are the errors: > > > > # rpm -Uvh apache2-2.0.46-3.i586.rpm > > error: failed dependencies: > > libapr0 = 2.0.46 is needed by apache2-2.0.46-3 > > apache2 = 2.0.44 is needed by > > apache2-devel-2.0.44-38 > > apache_mmn_20020903_0 is needed by > > apache2-prefork-2.0.44-38 > > apache_mmn_20020903_0 is needed by > > apache2-mod_perl-1.99_08-29 > > > > # rpm -Uvh apache2-devel-2.0.46-3.i586.rpm > > error: failed dependencies: > > apache2 = 2.0.46 is needed by > apache2-devel-2.0.46-3 > > It looks like you downloaded and are installing a patch > rpm that misses some patch rpms that have been released > before the ones mentioned above. This can be solved by > obtaining the full rpm and install that one instead. The > dependency you see above is of another nature that yast > can take care off. > > -- > Richard Bos > Without a home the journey is endless > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com For additional > commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

rpm update errors
by Ricardo Kleemann 16 Jul '03

16 Jul '03

Hello, I use the online_update script via cron to download packages, and then I use it manually to install packages. Recently, updates to apache2 were downloaded, but running online_update -i returns an error when trying to update apache. So then I decided to try updating apache manually via rpm, here are the errors: # rpm -Uvh apache2-2.0.46-3.i586.rpm error: failed dependencies: libapr0 = 2.0.46 is needed by apache2-2.0.46-3 apache2 = 2.0.44 is needed by apache2-devel-2.0.44-38 apache_mmn_20020903_0 is needed by apache2-prefork-2.0.44-38 apache_mmn_20020903_0 is needed by apache2-mod_perl-1.99_08-29 # rpm -Uvh apache2-devel-2.0.46-3.i586.rpm error: failed dependencies: apache2 = 2.0.46 is needed by apache2-devel-2.0.46-3 I know how to manually go, one by one, and install the necessary packages in order to get around the dependency problems. But doesn't YasT2 provide a way to automatically take care of that? That's one of the purposes of using an auto-install program, so I don't have to worry about the dependency issues... Another question, I see a kernel update was downloaded recently. What is the recommended procedure for upgrading the kernel? Will the online_update script take care of that automatically, including any grub changes or do I need to do something myself? Thanks for your help. Ricardo

2 1

Problems with the first console (tty0)
by BLassen＠haitec.de 16 Jul '03

16 Jul '03

Hello list ... I´ve come across somthing weired, and I´m not to shure where the problem comes from. When I install a minimal Setup direcctly from the CD it works perfect. But when i use the autoyast tool i get trouble with the first console (tty0) It shows two login prompts It looks like this : - Welcome to SuSE Linux bla bla (tty1) - -server login: - Welcome to SuSE Linux bla bla (tty0) - -server login:(flashing cursor) When i enter anything for a user name to log in on the first console it echos back some of the characters of the username. After that i´m propted to enter the password, but everything i´m entering is considered as false. If i switch to the second console there is no problem at all with logging on ... Has anybody come across something like that ? Bengt Lassen HAITEC AG Lyonerstraße 11a 60528 Frankfurt Tel.: +49-(0)69 - 6 65 61-0 Mobil.: +49-(0)179 - 39 14 656 Fax.: +49-(0)69 - 6 65 61-400 mailto: blassen(a)haitec.de http://www.haitec.de

1 0

Patches
by Michael.Regner＠dbv-winterthur.de 15 Jul '03

15 Jul '03

Hello, I am trying to setup a SLES 8 using autoyast for servers. Using the original software coming on CD, the installation using autoyast works quite well. But I have no idea how to deal with the patch rpm files from the web. Should I copy them into the /install/sles/CD1 or /install/ul/CD[1,2,3] directory and run the create_package_descr ? Or what is the best way the install the new packages from the begin using using autoyast ? Or must I install the original software and after that perform an update ? How should I deal with the patches in generell ? I dont want to make a online update using the internet. What is the best way to keep a lot of servers up to date ? ThanX Michael

3 3

autoyast network installating without specifiying server IP address
by Fermín Galán 15 Jul '03

15 Jul '03

Hello, To specify where lives control file for an unattended SuSE 8.1 network installation, a switch is used. For example: autoyast=nfs://192.168.1.30/suse_profiles/ Note that the IP of the NFS server have to be staticly set in the switch. Is there any way of installing without specifing server IP address via DHPC? The fact is that programs as grub are capable of getting files without static server IP address configuration, so I wonder if autoyast can. Thanks in advance! ------------ Fermín

1 0

Keep clients updated
by Daniel Bertolo 11 Jul '03

11 Jul '03

Hello I would like to keep auto-installed clients updated, but without a user input. Can yast be configured to check for updates on boot? And what would be the best way to provide an update repository? Shall I mirror a SuSE-update-folder? Someone told me to use apt4rpm. What shall I prefer? YOU or atp4rpm? Thanks Daniel Bertolo

1 0

Re: [SLE] adding menu entires from an RPM install???
by Marc Christensen 11 Jul '03

11 Jul '03

Well, I ran into another snag. This is really upsetting. I have desktop menu entries for the RPMs that I have built in /etc/opt/gnome/SuSE/System/Configuration/myapp.desktop /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/Configuration/myapp.desktop /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/Settings/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/System/Configuration/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/System/myapp.desktop (as stated in a previous followup). This works well when installed on an existing system. However, when these RPMs are installed during a network install, the entries are missing! linux:~ # rpm -V myapp missing /etc/opt/gnome/SuSE/System/Configuration/myapp.desktop missing /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/Configuration/myapp.desktop missing /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/Settings/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/System/Configuration/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/System/myapp.desktop linux:~ # How do I work with the [SuSE] system to get menu entries in KDE and gnome?!#$%?!!! -- Marc C. Marc Christensen wrote: > Hi Eveyone, > > I have made an RPM for SLES 8 and need to add an entry to eveyone's > desktop (kicker) and gnome desktop menus. How do I do that? > > In my RPM, I have placed it here: > > /opt/kde3/share/applnk/System/myapp.desktop > > and > > /opt/gnome/share/apps/System/myapp.desktop > > I have not checked to see if the gnome desktop link actualy gets entered > however, the KDE one does not. It does appear here: > > K -> Configure Panel -> Add -> Button -> System -> myapp > > This is not where I want it to go. I need it here: > > K -> System -> myapp > > > How do I do this? > > Thanks > > -- > Marc C. -- Marc Christensen http://www.mecworks.com

1 0

Adding custom RPMs to an NFS install setup
by Marc Christensen 10 Jul '03

10 Jul '03

Hello everyone. I've set up an NFS install for SLES 8 & SuSE 8.1 according to chapter 6 ofAutoYast2 guide: http://www.suse.de/~nashif/autoinstall/8.1/autoyast2.pdf I am unclear how to modify this setup to install custom RPMs that I have created and need installed on workstations. Anyone done this? Thanks.

2 4

Re: [suse-autoinstall] Adding custom RPMs to an NFS install setup
by Anas Nashif 10 Jul '03

10 Jul '03

Richard Bos wrote: > > > I'm doing it differently using suse-8.2, that I'll explain below. In my case > everytime after I run create_package_descr I need to refresh the installed > source by deleting and adding the source using yast that points to my > autoinstall source. That's because the cache /var/adm/YaST/InstSrcManager is > not updated with the info/files created by create_package_descr. Am I doing > something wrong or is it a bug? > Neither, this is the way it should go. If you put some packages on system and use the script, it does not imply that you also want to use the source for the running system., unless its the same version of course, you might need to do it. > My update method in short: > a update directory mirrors some directories from ftp.suse.com > renamed the suse dir to base > created a new dir called latest > linked this dir (latest) so suse > a script now links in the most recent packages from the update and base > directories into the latest directory (right format). After that the > create_package_descr is called. > Yast should actually be able to take the latest version if the same package exists with 2 versions. But this is not clean anyways. Anas

2 1

autoinstall when using two drives
by Debbie Velarde 09 Jul '03

09 Jul '03

I am trying to use AutoYast2 to install a system with two hard drives. I am using SLES8. I want to destroy all existing partitions on both drives and then create the following: sda: /boot, /swap, / (using default values) sdb: /data (which takes up the entire second drive) When I add the information to the partition section of the autoinstall.xml file, I get the following error: "Partition '/data' needs 2.00 MB more disk space. Please deselect some packages." Then if I click "OK", it continues with the installation and then returns another error: "Could not format /dev/sdb5" Here is the partition section of my latest autoinstall.xml: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">true</format> <mount>/data</mount> <filesystem config:type="symbol">jfs</filesystem> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> </drive> </partitioning> Has anyone else seen this problem or know what I am doing incorrectly? Thanks, Debora

2 4

Re: [suse-autoinstall] autoinstall when using two drives
by Anas Nashif 09 Jul '03

09 Jul '03

Hi, According to the log files, yast can only see /dev/sda, no /dev/sdb!! /dev/sda is SCSI, 33.90 GB, /dev/sda, LSILOGIC-1030 IM But there is no mention of /dev/sdb, might be a kernel module problem, although mptscsih is loaded... What happens when you try to install manually? Anas Debbie Velarde wrote: > Anas, > > I've attached all the files in /var/log/YaST2/. > > I will also try changing the size of / to "max" and will send out another > email shortly. > > Thanks, > Debora > > On Wed, 9 Jul 2003, Anas Nashif wrote: > > >>Hi, >>Can you please send me the log files from /var/log/YaST2/*. >> >>Something else I have just noticed, the size of partitions other than >>boot on swap cant be given as "auto". So the size of the root partition >>must be set to "max". But this might not have an effect in your case >>cause the error is about /data. >> >>I have just tried the same configuration you sent, and it works for me, >>so logs will be appreciated.. >> >> >>Anas >> >> >> >>Debbie Velarde wrote: >> >>>Hi Anas, >>> >>>Thanks for replying so quickly. I tried replacing both of the >>><reuse>all</reuse> lines with <use>all</use>. >>>But I am still getting the same error. >>>Any more ideas? >>> >>>On Wed, 9 Jul 2003, Anas Nashif wrote: >>> >>> >>> >>>>Hi, >>>> >>>>Debbie Velarde wrote: >>>> >>>> >>>>>I am trying to use AutoYast2 to install a system with two hard drives. >>>>>I am using SLES8. >>>>>I want to destroy all existing partitions on both drives and then create >>>>>the following: >>>>>sda: /boot, /swap, / (using default values) >>>>>sdb: /data (which takes up the entire second drive) >>>>> >>>>>When I add the information to the partition section of the autoinstall.xml >>>>>file, I get the following error: >>>>>"Partition '/data' needs 2.00 MB more disk space. Please deselect some >>>>>packages." >>>>>Then if I click "OK", it continues with the installation and then returns >>>>>another error: >>>>>"Could not format /dev/sdb5" >>>>> >>>>> >>>>>Here is the partition section of my latest autoinstall.xml: >>>>> <partitioning config:type="list"> >>>>> <drive> >>>>> <device>/dev/sda</device> >>>>> <reuse>all</reuse> >>>> >>>>Try <use>all</use> instead. >>>> >>>> >>>> >>>>Anas >>>> >>>> >>>>-- >>>>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 >> >> > >>

1 0

RE: [suse-autoinstall] Problem after creating new package db
by Berge, Harry ten 09 Jul '03

09 Jul '03

This is almost the 'default' problem when you do a 'create_package_descr'. What you must do is a create_package_descr -d /install/suse -l german -l english -x /usr/share/autoinstall/EXTRA_PROV This will do the works! Regards Harry > -----Original Message----- > From: Daniel Bertolo [SMTP:daniel.bertolo@kinderheim-buehl.ch] > Sent: Wednesday, July 09, 2003 9:31 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Problem after creating new package db > > 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 > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

AW: [suse-autoinstall] Problem after creating new package db
by Daniel Bertolo 09 Jul '03

09 Jul '03

> -----Ursprüngliche Nachricht----- > Von: Richard Bos [mailto:richard.bos@xs4all.nl] > Gesendet: Mittwoch, 9. Juli 2003 10:39 > An: Daniel Bertolo > Betreff: Re: [suse-autoinstall] Problem after creating new package db > > On Wednesday 09 July 2003 09:31, Daniel Bertolo wrote: > > 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? > > What SuSE version? > Did you include the EXTRA_PROV file, located in /usr/share/autoinstall/ SL 8.2. Yes, I include the EXTRA_PROV file (for a Java-RPM). This worked before. The problem I described appears if I replace an original RPM in the repository (in my case, I replaced yast2-ldap-client-2.7.6 with yast2-ldap-client-2.7.7). Afterwards, I do the create_package_descr and the new descriptions will be written to /install/suse/setup/descr/packages[.lang]. When I open yast2 and click on "add software" for the local machine, all dependencies are good and the updated packages are shown. But as soon as I run "yast2 autoyast" and configure the package selections, hundreds of dependencies fail. But the new packages are shown, too. What do I do wrong. Should I better let the original repository as is and use EXTRA_PROV also for updates? > > > 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 > > Is this during installation or operation? > I do this with apt. Just put "apt-rpm -y upgrade" in the boot sequence > and in > a crontab (n case the system is not booted) and the system will be kept up > to > date nicely. You can create a local apt repository with apt4rpm. As > spinoff > of that tool you can keep your installation package up to date keep easily > as > well (only a ver small additional script is needed). > I would like to put this in the boot-sequence in order to update the clients during boot. I will have a look for a apt-howto on the net. Guess there are some, aren't there? But thank you for the idea. > -- > Richard Bos

1 0

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