June 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Help required in creating custom selection package
by Pramodh G N 16 Jun '03

16 Jun '03

Hi all, I am trying to build a customized SUSE distribution with a set of rpm's which is different from the default SLES distribution. I have gone through the documentation but it doesn't clearly say how to create a *.sel file without using any of the .sel files provided by the SLES CD. My requirement is to create a distribution depending on the customers requirement and generate a my.sel file, using which a distribution will be created. can somebody point out the steps to be followed for accomplishing this task. Thanks in Advance Pramodh **************************Disclaimer************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ***************************************************************************

1 0

merging classes without AutoYaST
by Michal Kubecek 15 Jun '03

15 Jun '03

Is it possible to merge class files into a control file "manually", ie without AutoYaST? I tried to use xsltproc and XSLT stylesheet I found in /usr/share/autoinstall/xslt/merge.xslt. xsltproc cannot find DTD files since the paths in XML headers are /usr/share/autoinstall but DTD files are in /usr/share/autoinstall/dtd. Even after linking DTD's into /usr/share/autoinstall the result looks different from what I get with AutoYaST. Michal Kubecek

2 1

Re: [suse-autoinstall] error .. packages not available during iso creation
by Richard Bos 14 Jun '03

14 Jun '03

Op donderdag 12 juni 2003 23:38, schreef sytse: > repository in autoyast means the place where your XML files will be stored. > > Did you do the 'change source of installation' in yast2? After changing the "source of installation" in yast package manager most of the pkgs were found. May I state that the verbosity of the error msg is not enough, should this be considered as a bug (perhaps the documentation should say something about it)? Shouldn't it be possible to provide the source of installation via "autoinstall -> file -> preferences -> "source of installation", this would intuitive. At this moment I selected Minimal.sel for the packages, in the process of creating the ISO 2 pkgs are missing. There is however no list with pkgs that are missing, not in yast on screen neither in the log file. I found a file called .../log/YaST2/badlist, that states that k_athlon should be removed from the list.source of installation [1]. How can I determine which pkgs are missing, I have mapped the Minimal.sel file with the packages file as well as with the installed rpms (and vice versa), but so clause sofar. Is this a bug too, or do I overlook something trivial?? I just continued here creating the iso. Yast stated it was about to write iso image (small window). There is however no progress meter (I know now), it was just doing nothing.... I aborted the process after minutes of waiting. Analysis of the log file revealed that there was lack of disk space. Which is very well possible as my /tmp filesystem is only 100MB. No problem, I extended the filesystem with lvm to 850 MB and started the ISO process once more. This time it finished successfully. May I propose that yast-autoinstall checks the disk space availability at some smart points? E.g. during the rpm copy process, after writing the iso skeleton, and before the creation of the iso image? In my case with the Minimal.sel selection 2x 210 MB is necessary. BTW: and it possible to link the rpms into the skeleton directory. This would save a lot of diskspace and is probably faster too... (With the default package selection more than 850 MB is needed to create the iso skeleton, so I should extend /tmp once more). I hope not to offend anyone, with this feedback! I just noticed these things and though to let you (most likely Anas ;) know. > On Thursday 12 June 2003 23:32, Richard Bos wrote: > > Op donderdag 12 juni 2003 22:57, schreef Richard Bos: > > > in the process of creating an iso image, autoyast checks the package > > > availality, in my case this check fails. That's probably due to an > > > incorrect repository setup. Can someone enlighten me, what the correct > > > setup should be. The error message I get is "498 packages not > > > available". > > > > > > I just choose a "default" system, no other pkgs have been added. > > > > Forgot to mention that I use SuSE-8.2. The system is installed from CD. > > The repository has been set to ....suse82/base/ as well as > > suse82/base/suse using "File -> prefereneces". -- Richard Bos Without a home the journey is endless [1] badlist: linux01:/var/log/YaST2 # cat badlist 2 packages failed Name: k_deflt Edition: 2.4.20-62 From-Input-List: yes Conflicts-With: k_athlon conflicts with k_deflt, k_deflt conflicts with k_athlon Remove-To-Solve-Conflict: k_athlon Name: k_smp Edition: 2.4.20-62 From-Input-List: yes Conflicts-With: k_athlon conflicts with k_smp, k_smp conflicts with k_athlon Remove-To-Solve-Conflict: k_athlon y2log: 2003-06-13 11:52:49 <3> hvslinux01(7918) [Interpreter] autoinstall/iso.ycp:157 [WFM] variable tok is not declared 2003-06-13 11:52:49 <3> hvslinux01(7918) [Interpreter] autoinstall/iso.ycp:157 [WFM] variable tok is not declared 2003-06-13 11:52:58 <3> hvslinux01(7918) [Interpreter] modules/HTML.ycp:116 cant add this type to string 2003-06-13 11:52:58 <3> hvslinux01(7918) [Interpreter] modules/HTML.ycp:116 cant add this type to string

4 8

pxelinux.0
by Florian Letz 14 Jun '03

14 Jun '03

Hi, I read the script again and again, but I didn't get it. Where do you get the file pxelinux.0 from? And what does it contain? With friendly greetings. Flo

2 1

Documentation Issues
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi everybody, last few days I had some nasty problems with the configuration in autoinst.xml. The major problem was that some part of the documentation is false or inactual. I used the Book "AutoYast2 Automatic Linux Installation und Configuration with YaST2" Revision 0.9. So be aware always to use the newest documentation available, which is right now Version 1.1! By the way, how often are there changes in xml tags? In 0.9 it was e.g. <network> now it is <networking>. Is there a validating parser, which can validate autoinst.xml? Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

3 2

Antwort: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM Update
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi, Sorry. Last script had some bugs and was posted without many tests. Here is the update. Any comments are greatly appreciated. <scripts> <pre-scripts config:type="list"> <script> <filename>/vgremove.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ insmod lvm-mod vgscan vgs=`echo /dev/vg_*` for vg in $vgs do if [ -d $vg ] then vgchange -a y $vg lvs=`ls $vg` for lv in $lvs do i=`basename $lv` if [ $lv != "group" ] then lvremove -f $vg/$lv fi done vgchange -a n $vg vgremove $vg done ]]> </source> </script> </pre-scripts> </scripts> Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- Diese Mitteilung sowie eventuelle Anhänge sind vertraulich und können privilegiert oder auf andere Weise gegen Weitergabe geschützt sein. Sollten Sie nicht der beabsichtigte Empfänger sein, bitte rufen oder mailen Sie den Absender an und löschen Sie diese Mitteilung sowie eventuelle Anhänge aus Ihrem System. Sind Sie nicht der beabsichtigte Empfänger, dürfen Sie diese Mitteilung bzw. die Anhänge weder kopieren noch an andere Personen weitergeben.

2 1

SuSE-8.2 & autoinstall
by Mikhail Terekhov 13 Jun '03

13 Jun '03

Hi, I'm trying to learn autoyast on my up to date SuSE-8.2 box and currently I'm stuck with the following problems: 1. When I save my configuration in a file, yast puts wrong path to the profile.dtd. It puts <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> instead of <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> If I correct this path then xmllint complains: my_clone_printer_only.xml:6: validity error: No declaration for attribute type of element cups_installation <cups_installation config:type="integer">0</cups_installation> ^ my_clone_printer_only.xml:6: validity error: No declaration for element cups_installation <cups_installation config:type="integer">0</cups_installation> ^ my_clone_printer_only.xml:7: validity error: No declaration for attribute type of element database <database config:type="symbol">foomatic</database> ^ my_clone_printer_only.xml:7: validity error: No declaration for element database <database config:type="symbol">foomatic</database> ^ my_clone_printer_only.xml:11: validity error: No declaration for attribute type of element accepting <accepting config:type="boolean">true</accepting> .... .... 2. When I try to clone my system and select to clone only printer settings and save to a file then yast clones and writes to the file everything - software, network, printers, e.t.c. But when I select to clone everyting including software it clones and saves all but software. Please help. What am I missing there? Regards, Mikhail

3 5

Re: [suse-autoinstall] User and Groups
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Thanks for this hint. Unfortunately I'am using SLES8 and it seems that it doesn't support these tags. Anybody any experiences with <groups>. Which version of autoyast do I need. Is there an update for SLES8. Thanks in advance. Have a nice weekend. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

User and Groups
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi, I wan't to create Users and Groups at the end of installation. But each of these users must have his own primary group with a customized gid. I never found a tag to create groups. Isn't there any? Thanks for help. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

2 1

Re: [suse-autoinstall] Updating YaST2 in installation repository
by Helge C. Rutz 13 Jun '03

13 Jun '03

Hello, can you please describe how to force already installed systems to use the new packages from the updated repository? As long as the clients use there old lokal package desriptions, I run into source not found errors when trying to install additional packages that were updated. Thanks Helge Rutz University of Karlsruhe Anas Nashif wrote > >Hi, > > >Yes, It is just as you described below. > > >Anas > > >Fermín Galán wrote: >> Hello everyone, >> >> I have read in the online documentation >> available that bugs of the autoinstallation >> system (enable_3d, password in clear text, ...) >> can be solved updating yast2 related >> RPMs (yast2, autoyast2, yast2-x11, etc). >> >> I would like to know wheter the updating processes >> is as simple as the addition of customized packages: >> delete the old RPM file in the repository, copy the >> updated one to the same directory (noarch, i586, >> etc.) and runing >> >> cd <repository>/suse >> /usr/lib/YaST2/bin/create_package_descr >> >> to update the packet database. >> >> I'm using/installing SuSE 8.1. >> >> Thanks in advance! >> >> ------- >> Fermín >> fermin.galan(a)agora-2000.com >> Agora Systems, S.A. >>

1 0