April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Autoyast questions
by suse_list＠infineon.net 28 Apr '05

28 Apr '05

Hi, I managed to get most of the autoyast stuff to work with PXE boot, though there are a couple of questions and suggestions. With the release of Suse Pro 9.3 it seems that the yast autoinstall tool breaks the partitioning sizing in the autoyast config files. The question i have is i would like to enable that after the basic install on first boot one can get suse to check for online_updates, like one can do with installing from CD or installing via failsafe. Anyone have any ideas as to what to add to the autoyast config files? The other question, is there some way to determine in a post script the DHCP network information given and setting it to static on the machine? Please let me know thanks S.

2 1

Custom package installation using AutoYaST
by boopathy krishnamoorthy 28 Apr '05

28 Apr '05

Hi I had customised the installation using AutoYaST. For adding my own package to install using AutoYaST, i had created a directory "custom" under "install_root/suse/". # ls suse i586 custom noarch nosrc setup src x86_64 In the control.xml i added the following portion <software> <addons config:type="list"> . </addons> <packages config:type="list"> . . </packages> <extra_packages> <package_location> custom </package_location> <packages config:type="list"> <package>glibc</package> <package>libnscd</package> </packages> </extra_packages> </software> But after installation my packages doesn't get installed. And i don't know whether AutoYaST read's <extra_packages> portion. Give ur valuable points over this. And i want to know which file contains the list of packages that AutoYaST read from control.xml. ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

2 1

Custom CD for SLES9 x86_64
by Bernhard Duebi 28 Apr '05

28 Apr '05

Hello everybody, I try to create a custom CD for SLES9 x86_64. With Yast CD Creator I setup the hierarchy needed to install Linux. Then I put Enterprise Agents into a separate directory. These get installed by the postinstall script. Then I compiled everything with mkisofs. I can boot from the CD, there's a popup complaining that I try to install 32bit software on a 64bit hardware. In the Yast log file I can see that yast is doing some magic to avoid this messages. Is somebody willing to share this magic with me ? Sincerely Bernhard

2 1

Re: [suse-autoinstall] How can I regularly update the install rep ository?
by Michael Marion 27 Apr '05

27 Apr '05

On 26 Apr, Stephens, Bill {PBSG} wrote: > LABEL SUSE LINUX Version 9.1 Try changing the label.. I changed mine from SUSE CORE Version 9 to SUSE Updates > DESCRDIR /SUSE-updates/updates/setup/descr > DATADIR /SUSE-updates/updates And remove the preceeding / from the above paths.. I think they should be relative from the base of the path the content file is in. I.e. my content file is located at: <long path>/sles9/SUSE-Updates/content and the two lines are: DESCRDIR updates/setup/descr DATADIR updates Where the directory "updates" is directly under the SUSE-Updates path. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "The Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!" -- Matthew Sachs on Slashdot

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 27 Apr '05

27 Apr '05

Also, when I try adding the install source, I get the following error: Local Source Adding dir:///usr/suse9.1//SUSE-updates/ ERROR(InstSrc:E_no_instsrc_on_media) -----Original Message----- From: Stephens, Bill {PBSG} [mailto:Bill.Stephens@pbsg.com] Sent: Tue 4/26/2005 5:17 PM To: Michael Marion Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] How can I regularly update the install rep ository? Ok, I think I'm making some progress, but I can't seem to find the glue that brings it all together. I created a content file and media.1 directory, but it's still not installing. Here's what I have: Root content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-DVD-i386 DISTVERSION 9.1-0 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR suse/setup/descr DATADIR suse FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-UPDATE-i386 DISTVERSION 9.1-1 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR /SUSE-updates/updates/setup/descr DATADIR /SUSE-updates/updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates/media.1/media file: SuSE Linux AG 20040407221453 2 doublesided MEDIA1 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD INSTALLATION 32BIT MEDIA2 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD UPDATE 32BIT SUSE-updates/media.1/products file: /SUSE-updates SUSE-LINUX-UPDATES-i386 9.1 -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: Tue 4/26/2005 3:30 PM To: Bill.Stephens(a)pbsg.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install rep ository? On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons -- 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] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 26 Apr '05

26 Apr '05

Ok, I think I'm making some progress, but I can't seem to find the glue that brings it all together. I created a content file and media.1 directory, but it's still not installing. Here's what I have: Root content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-DVD-i386 DISTVERSION 9.1-0 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR suse/setup/descr DATADIR suse FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-UPDATE-i386 DISTVERSION 9.1-1 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR /SUSE-updates/updates/setup/descr DATADIR /SUSE-updates/updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates/media.1/media file: SuSE Linux AG 20040407221453 2 doublesided MEDIA1 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD INSTALLATION 32BIT MEDIA2 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD UPDATE 32BIT SUSE-updates/media.1/products file: /SUSE-updates SUSE-LINUX-UPDATES-i386 9.1 -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: Tue 4/26/2005 3:30 PM To: Bill.Stephens(a)pbsg.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install rep ository? On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons

1 0

Re: [suse-autoinstall] How can I regularly update the install rep ository?
by Michael Marion 26 Apr '05

26 Apr '05

On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons

1 0

Grub and packages on autoinstalls
by suse_list＠infineon.net 26 Apr '05

26 Apr '05

Hi, We seem to be experiencing some really strange things with SuSE 9.3 used in a build server. We purchased the SuSE 9.3 Proffessional (on box it says update edition). The problems we are experiencing is first, that when a system is installed and booted the first time we get a "Grub Harddisk Error", and system won't load. The only way to load is to go through booting failsafe and then telling it to boot the system. Having searched on google it seems to do something be grub getting confused with the disk. Booting from harddisk via PXE will fail also, as it can't find FS to boot from. The machine is a IBM Intellistation M Pro, (2.2Ghz Xeon), with a 100GB Western Digital IDE disk in it. Anyone have any ideas ? The other problem is that when we add customized packages and run the createpkg_descr script on the directory it seems to find it ok, but when we even add the package to the build profile, it doesn't seem to even install the package, but unlike SuSE 9.2 it doesn't fail either (stating it didn't find the package). Anyone have any ideas here? Please let us know Thanks S.

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 26 Apr '05

26 Apr '05

I must be screwing something fundamental up. The majority of doc I've found centered around SLES 8 and 9. I'm trying to do this with suse pro 9.1. I copied the DVD to my nfs mount source. When I boot my root dir structure looks like this: -r--r--r-- 1 root root 9129056 Apr 7 2004 ARCHIVES.gz -r--r--r-- 1 root root 17992 Apr 7 2004 COPYING -r--r--r-- 1 root root 25733 Apr 7 2004 COPYING.de -r--r--r-- 1 root root 1438 Apr 7 2004 COPYRIGHT -r--r--r-- 1 root root 1606 Apr 7 2004 COPYRIGHT.de -r--r--r-- 1 root root 3808102 Apr 7 2004 ChangeLog -r--r--r-- 1 root root 57276 Apr 7 2004 INDEX.gz -r--r--r-- 1 root root 363 Apr 7 2004 LIESMICH -r--r--r-- 1 root root 377 Apr 7 2004 LIESMICH.DOS -r--r--r-- 1 root root 356 Apr 7 2004 README -r--r--r-- 1 root root 370 Apr 7 2004 README.DOS drwxr-xr-x 3 root 500 4096 Apr 25 10:14 SUSE-updates -r--r--r-- 1 root root 2238 Apr 7 2004 SuSEgo.ico -r--r--r-- 1 root root 36 Apr 7 2004 autorun.inf dr-xr-xr-x 3 root root 4096 Apr 7 2004 boot -r--r--r-- 1 root root 592 Apr 7 2004 content -r--r--r-- 1 root root 21394 Apr 5 2004 control.xml -r--r--r-- 1 root root 273 Apr 26 09:50 directory.yast dr-xr-xr-x 3 root root 4096 Apr 7 2004 docu dr-xr-xr-x 20 root root 4096 Apr 7 2004 dosutils -r--r--r-- 1 root root 1694 Apr 7 2004 gpg-pubkey-3d25d3d9-36e12d04.asc -r--r--r-- 1 root root 2295 Apr 7 2004 gpg-pubkey-9c800aca-39eef481.asc -r--r--r-- 1 root root 105066 Apr 7 2004 ls-lR.gz dr-xr-xr-x 2 root root 4096 Apr 7 2004 media.1 -r--r--r-- 1 root root 2817 Apr 7 2004 pubring.gpg dr-xr-xr-x 6 root root 4096 Sep 20 2004 suse drwxr-xr-x 2 root root 4096 Apr 26 11:58 yast My yast directory contains the following order file: /SUSE-updates/ /SUSE-updates/ / / and instorder file: / /SUSE-updates/ I've run the create_package_descr script and confirmed that /SUSE-updates/updates/setup/descry/packages* files are there. When I run the install, none of the updated packages get picked up. What am I missing? I suspect the directory structure isn't set up correctly, but with 9.1 pro, I don't have a sles or core directory. Thanks, Bill Stephens -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, April 25, 2005 5:03 AM To: Richard Bos Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install repository? Richard Bos wrote: > Op woensdag 13 april 2005 23:56, schreef Michael Marion: >>Note that you have to remove conflicting old rpms too.. i.e. if you put >>something new in, like autofs-4.1.4, you have to remove autofs-4.1.3 before >>running the create_package_descr script. > > I don't think this is required, yast will determine what is newest version > available (making life much easier). > right. A much cleaner solution is to create a seperate source for updates usign the script I posted a while ago, this way you dont change the original SUSE sources.. Anas -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Network configuration with post install script.
by dbenisty＠free.fr 26 Apr '05

26 Apr '05

I'm trying to automate the network configuration on a post install script with autoyast. I cannot predict the number of ethernet card and the ones that will be used before the installation. So i wrote a script that ask the user all the network info, hostname, gateway etc . . . Actually the problem i have is when i want to use the ifcfg-eth-xxxxx file generated by autoyast when i put this : <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth2</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth3</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth4</device> <startmode>onboot</startmode> </interface> </interfaces> the file generated by autoyast have not the same content that when i use yast and give the same info. With autoyast i don't have a _nm_name=..... field on the ifcfg file and so i don't have the hwcfg-$_nm_name associated file created on /etc/sysconfig/hardware I could bypass that but it seems that i need this field to configure the bonding that i want to use on all my servers. By parsing the 'hwinfo --network' output i could generate by myself the ifcfg-xxx files & hwcfg-xxxx associated files but i'm not sure it's the way i should go. I simply cannot predict the number of card and associated driver before the install and so i cannot predict the final parameters before scanning the hardware and asking the user witch card he wanna use. So i cannot put those info on the autoyast xml file, that's why i doing that on a post instal script. So my question is, how can i automate the network configuration for various servers (i have i386 & ia64 arch) with autoyast & post install scripts ? something like that : card_list=`ls -A /sys/class/net | grep eth` choice=`kdialog --title "Bonding interfaces" --inputbox "Activate Bonding on ? (ethx ethy) :" "$card_list"` and then i ask all the network config for the bonding and i wanna be able to generate all the associated config files. i can find the info for generating the files with requests like : # the simple name here hwinfo --network | grep "Device File" | echo `awk '{print $3}'` # the driver here hwinfo --network | grep "Driver:" | awk '{print $2}' # The Driver # the pci-bus-xxxx string there hwinfo --network | grep "SysFS Device Link:" | awk '{print $4}' | grep -n devices | echo `awk -F/ '{print "pci-bus-"$NF}'` # the HW Adress hwinfo --network | grep "HW" | echo `awk '{print $3}'` # the unique id hwinfo --network | grep "Unique" | echo `awk '{print $3}'` if guess there are simple a way to do that, but i can't find it :) Greetings. Daniel

2 1