February 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

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