April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

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

x11 - sax2
by Peter Guyan 26 Apr '05

26 Apr '05

Hi My newbie-question: In a classroom with six identical machines i try to netinstall with pxe and autoyast2 under suse9.2. I set up one machine and create a profile with it. All works fine until after the first boot, where I just get a text based login. I have to login as root, run SaX2 and init 5 to test and complete. On the "master"-machine X11 works fine. After reading some messages in the archive i suppose, that autoyast2 can't install X11. Is this correct? There were some hints on a very basic installation with VESA, which I also tried to setup - without success. Can someone give me an example of a post-install-script to setup SaX2, because my attempts did not work. Thanks. Peter

2 1

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

25 Apr '05

On 13 Apr, Luca Pacor wrote: > I am asking myself whether it would be possible to online_update the > autoinstall repository: it would be nice to be able to install new > machines using an up-to-date repository reducing this way the install > time ... > I am using SuSE 9.2 You could regularly pull down updates into your own update path, and use that. I created a SUSE-Updates tree at the same level as my SUSE-CORE and SUSE-SLES paths, and put updates into there. Then use create_package_descr to make the descr files. i.e. under sles9/SUSE-Updates/updates I have dirs for i586, x86_64, noarch and setup I put the rpms into the right paths based on arch, then cd into sles9/SUSE-Updates/updates and run: /opt/kde3/share/apps/krpmview/create_package_descr -d . That creates the files under setup: cornholio updates {1229}$ find setup/ setup/ setup/descr setup/descr/packages setup/descr/packages.DU setup/descr/packages.en 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. You could setup a tree like this and rsync in new packages when you get them, and even remove older ones if you script well enough. I do it by hand since we have to test all new changes and stuff here before we push them out into our compute farm. You also have to have the order and instorder files setup to see that path, mine are: cornholio sles9 {1234}$ cat yast/order /SUSE-Updates /SUSE-Updates /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 cornholio sles9 {1235}$ cat yast/instorder /SUSE-CORE-Version-9/CD1 /SUSE-Updates /SUSE-SLES-Version-9/CD1 When you start a new install, or use yast to point to the Updates path, you'll know pretty quickly if it's seen as valid or not. I've used this setup to add in a lot of things we needed that weren't stock in sles9, or just to update packages. I added openafs, updated autofs with direct map support, updated kernel (mostly for autofs patches), etc. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Jerry and George describe wedgies to Elaine] Elaine: "Boys are sick!" Jerry: "Well what do girls do?" Elaine: "We just tease someone until they develop an eating disorder." ==> Seinfeld.

4 3

auto updating install tree
by Ashe Canvar 25 Apr '05

25 Apr '05

Hi all, I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive. The issue I am not clear about is as follows: - I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126 - if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server. - What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required. Is there any way to accomplish this ? How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual. I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization. Thanks!

2 1

Autoinstall and Root-Password
by Daniel Spannbauer 25 Apr '05

25 Apr '05

Hello, I'm a novice in Installing with autoyast. I try a lot at this time. I have some trouble with installig SuSE 9.2 with autoyast. Problem1: The User "root" has no password, I try to fix it with: <window_manager>kde</window_manager> </x11> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted>true</encrypted> <forename/> <surname/> </user> </users> </configure> After this the User "root" has a password but I can*t login as root. Must the password in the config-File be Plain Text? Problem2: The Installation gives an Error-Message. "Wrong LDAP-Config". This Message comes with or without an Ldap-Entry in the config-File. Has anybody the same Problems? Greetings Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de

4 4

autoinstall of OES novell components
by Victor Billings 25 Apr '05

25 Apr '05

Sorry if this has been answered previously, I have done a rudimentary search of the archive and found no answers. I have used autoinstall in the past and been quite pleased. But now I am trying to do an autoinstall of the Novell components of OES. While I can get the packages to install correctly, the YaST configuration is a complete mystery. The Novell components all show up in my software addons section ie; <addon>novell-base</addon> <addon>novell-eDirectory</addon> correctly, but I do not have the respective configuration of those components. I have been unable to find a UI in Autoinstall for the configuration of the novell components. Is this currently possible via autoinstall? Thanks, Victor

2 1

SuSE 9.0 Mount From a Post-Install Script "only root can do that"
by Ragnar Skaret 23 Apr '05

23 Apr '05

Hi, I use SuSE 9.0 professional CD version as installation source. I'm trying to run a mount within a post script but as reported earlier it fails with "mount: only root can do that" Here is the result log from post.sh.log: ----------------------- + id uid=0(root) gid=0(root) + whoami root + mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda3 on /data type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) + ls -l total 156 drwxr-xr-x 2 bin bin 4096 2005-04-01 11:42 bin drwxr-xr-x 3 root root 4096 2005-04-01 11:42 boot drwxr-xr-x 3 root root 4096 2005-04-01 11:38 data drwxr-xr-x 31 root root 73728 2005-04-01 11:44 dev drwxr-xr-x 43 root root 4096 2005-04-01 11:45 etc drwxr-xr-x 3 root root 4096 2005-04-01 11:45 home drwxr-xr-x 8 root root 4096 2005-04-01 11:41 lib drwx------ 2 root root 16384 2005-04-01 11:38 lost+found drwxr-xr-x 5 root root 4096 2005-04-01 11:45 media drwxr-xr-x 2 root root 4096 2003-09-23 18:02 mnt drwxr-xr-x 3 root root 4096 2005-04-01 11:39 opt dr-xr-xr-x 49 root root 0 2005-04-01 11:43 proc drwx------ 5 root root 4096 2005-04-01 11:45 root drwxr-xr-x 3 daemon daemon 8192 2005-04-01 11:41 sbin drwxr-xr-x 4 root root 4096 2005-04-01 11:39 srv drwxrwxrwt 7 root root 4096 2005-04-01 11:45 tmp drwxr-xr-x 12 root root 4096 2005-04-01 11:39 usr drwxr-xr-x 13 root root 4096 2005-04-01 11:39 var + mount -a 192.168.113.107:/data1/SuSE90 /mnt mount: only root can do that + cd /mnt/post_scripts/ /var/adm/autoinstall/scripts/post.sh: line 9: cd: /mnt/post_scripts/: No such file or directory + cp php-4.3.4.tar.gz /tmp ----------------------- When the installation is finished I executed command "mount" and then the installation media was mounted (nfs) but it was not mounted at this point of the installation process Is the post scripts executed "between" first boot and the installation of the remaining RPMs? (Since I'm using a CD version as installation media, the CD1 is installed then a boot is performed and then the remaining CDs are installed) Is there a fix for this problem anywhere? Should I provide more logs? Any help is much appreciated This is part of my autoyast xml: <scripts> <post-scripts config:type="list" > <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh id whoami mount ls -l mount -a 192.168.113.107:/data1/SuSE90 /mnt cd /mnt/post_scripts/ cp php-4.3.4.tar.gz /tmp ]]> </source> </script> </post-scripts> </scripts> Regards Ragnar Skaret ------------------------------------------------------------ Få din egen @start.no-adresse gratis på http://www.start.no/

1 0

Autoyast file(s)
by suse_list 22 Apr '05

22 Apr '05

Hi, I was wondering a few things about the YAST autoinstall config files. I have setup the rules file correctly and all seems to work. Now what i would like to do is to split up the config files so that the <software> section is in a separate file and can be included in different config files. Basically i want custom configurations only for partitioning trees, and the rest to be modular. Another question is, how would i set it up in the config files that when it installs it also runs online updates as well and configures it to do auto-online updates from a specified server? Please let me know Thanks Sascha

2 1

multiple ethernet interfaces causes duplicate host records in the /etc/hosts file?
by deet 22 Apr '05

22 Apr '05

Hello. I am using autoyast/sles9. I just started building hosts with more than 1 physical ethernet interface which resulted in some surprising entries in the /etc/hosts file. here is the snippet of my control.xml file that pertains to the hosts networking setup. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <domain>atl.company.com</domain> <hostname>app01</hostname> <nameservers config:type="list"> <nameserver>172.17.9.25</nameserver> </nameservers> <searchlist config:type="list"> <search>atl.company.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <startmode>onboot</startmode> <broadcast>172.17.177.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>172.17.177.54</ipaddr> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>onboot</startmode> <broadcast>10.170.3.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>10.170.3.21</ipaddr> </interface> </interfaces> The resulting hosts file has these 2 entries. 10.170.3.21 app01.atl.company.com 172.17.177.54 app01.atl.company.com app01 The question is. Why is the line "10.170.3.21 app01.atl.company.com" being added to the /etc/hosts file? If I cannot stop this from occuring can I at least control the name that gets associated with the 2nd interface so I might end up with 10.170.3.21 eth1-app01.atl.company.com or something like that? TIA. Deet.

2 1

rules.xml and profiles question - howto define variable in rules.xml
by deet 19 Apr '05

19 Apr '05

Hello. We are running SLES9 and use autoyast to perform our client installations. I'm trying to get my installation environment to the point where I can build machines which have a hostname set and non dhcp ip's for eth0/eth1 with various routes entries. I've now been able to kind of get a working understanding of using rules.xml and profiles (mainly through reading postings from this list). So i've got this rule working which grabs the appropriated domain profile (extra domains removed for readability). The domain profile basically has all the general high level settings that apply to hosts in a domain. But then I need to be able to incorporate each host specific profile which contains host specific entries such as hostname/ip address/gateway/static routes/etc. <rule> <domain> <match>ca.company.net</match> <match_type>exact</match_type> </domain> <result> <profile>sles9.ca.cfg</profile> <continue config:type="boolean">true</continue> </result> </rule> But now I'm trying to configure the host specific profile. I realized I could add in and rule for every single host that I'm installing which would do the following but I dont like the idea of having to edit the rules file for every single host that I install. <rule> <mac> <operator>and</operator> <match>00093f10cc32</match> <match_type>exact</match_type> </mac> <result> <result> <profile>host42.ca.company.net.xml</profile> </result> </rule> Ideally I would like to see something where I have a catch all rule for all hosts which ends in a match and the resulting profile it looks for is an xml file that I have created which would be something like <mac_address>.xml or <ip_address>.xml. I've seen a posting from Anas that I could use some notation like <profile>profile-@mac@.xml</profile> But I dont know how to set that "mac" variable within the rule. Would I do a custom rule to do this and if so how would I do it? If I'm running a custom script do I embed it in the xml or have a path to a script that gets executed? I would really appreciate any pointers or tips on this topic as I feel if I can get over this last hurdle I will have a fairly portable autoyast structure that I can propogate to our various sites without much modification. If anyone would be able to include any custom rule examples I would be very greatful. Thanks for your help! Derek.

2 1

Re: [suse-autoinstall] Custom install source for yast in SLES9
by Michael Marion 15 Apr '05

15 Apr '05

On 15 Apr, Campbell, Fraser wrote: > Can anyone point me to documentation on this? Are there tools to help set > this up? Not sure on full docs, But I created a media.1 dir and a content file. So I have: SUSE-Updates/ /updates/ /i586/ /noarch/ /setup/ /x86_64/ /media1/ /directory.yast /info.txt /media /products /content Content is (Created by slightly modifying the one that came with sles9): PRODUCT SUSE Updates VERSION 9 DISTPRODUCT SUSE-Linux-SLES-x86-64 DISTVERSION 9-0 BASEPRODUCT SUSE CORE BASEVERSION 9 YOUTYPE business YOUPATH x86_64/update/SUSE-SLES/9 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/x86_64/SUSE-SLES/9/release-notes.rpm ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch DEFAULTBASE x86_64 REQUIRES sles-release-9 LINGUAS de en LABEL SUSE Updates LABEL.de SUSE SLES in der Version 9 DESCRDIR updates/setup/descr DATADIR updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles ====== In media.1.. directory.yast is: info.txt media products ====== info.txt is just a direct copy from the sles9 media.1 ====== media is: SuSE Linux AG 20040702194312 1 ====== Products is: / SUSE-Updates-x86-64 9 ====== I don't know which are completely required, but I was just copying files from sles9 and editing them as I saw fit.. and I'd keep trying to add the path as an install source until it worked. And it worked with the above. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com The needs of the many outweigh the needs of the few, or the one. That's from Trek. Pretty cool, huh? -- Dennis Miller

1 0

Custom install source for yast in SLES9
by Campbell, Fraser 15 Apr '05

15 Apr '05

Hi, I have a directory tree like this: Mypackages____ i386 |__ i586 |__ i686 |__ noarch |__ setup__descr The directory Mypackages/setup/descr contains files packages, packages.DU and packages.en ... the files were generated with the following command: cd Mypackages && create_package_descr -x path/EXTRA_PROV_FILE_FROM_SLES9CD1 When I export this source with NFS to an existing SLES9 server I get the message "There is no product information available at the given location. If you expected to address a product, return and enter the correct location." Can anyone point me to documentation on this? Are there tools to help set this up? Thanks, Fraser

1 0

HOWTO: SLES9: create a DVD with alle packages and the newest service pack?
by Hans Kamm 14 Apr '05

14 Apr '05

Hi, is there a way to create a new install-media with alle packages plus the newest service pack with some updates? Regards, Hans _________________________________________________________________ Eine für alle. MSN Suche. http://search.msn.de Finden statt suchen!

1 0

partition error with 9.3,, part II
by Henrik Schmidt 14 Apr '05

14 Apr '05

I checked the y2log more carefully and found an entry ["auto_added"=true] for a /boot ext2 partition. Now I understand why it fails as I already created 4 primary partitions using all space [swap,/,/export/opt,/export/home]. Why is this auto added, it wasn't with 9.2 and /boot happily lived on my root partition ? How can I disable this auto addition, I just don't want it ? Thanks Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

Re: [suse-autoinstall] Problems donwloading driverupdate-SLES8
by Michael Marion 13 Apr '05

13 Apr '05

On 7 Apr, Ivor Terret wrote: > GET //distro/SLES_8_0_IA32/UL/CD1/content HTTP/1.0" 200 587 Looks like your content file is linked to the content file on the first UnitedLinux cd, when it should be linked to the content file on the sles8 specifc cd. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Jerry and George describe wedgies to Elaine] Elaine: "Boys are sick!" Jerry: "Well what do girls do?" Elaine: "We just tease someone until they develop an eating disorder." ==> Seinfeld.

1 0

Re: [suse-autoinstall] UpdateDir:
by Michael Marion 13 Apr '05

13 Apr '05

On 6 Apr, Radzai, Bridgette A. wrote: > Can someone tell me what the UpdateDir: parameter in used for in the > linuxrc.config file? It is a default parameter and is set to > /linux/suse/i386-sles9 Well, in my sp1 image, that directory has: ls linux/suse/x86_64-sles9/ dud.config inst-sys y2update in it. dud.config has info on the SP: cornholio x86_64-sles9 {1195}$ cat dud.config UpdateName: Service Pack 1 UpdateID: 7cbcbaef9f9d4490 UpdatePriority: 100 inst-sys has a few updated binaries/libs, probably to override those on the root image from the SLES9 initial release: cornholio x86_64-sles9 {1201}$ find inst-sys/ inst-sys/ inst-sys/sbin inst-sys/sbin/save_y2logs inst-sys/usr inst-sys/usr/lib64 inst-sys/usr/lib64/YaST2 inst-sys/usr/lib64/YaST2/plugin inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so.2 inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so.2.0.0 inst-sys/usr/lib64/libhd.so.8 inst-sys/usr/lib64/libhd.so.8.78 and y2update has a bunch of udpated yast scripts.. or at least I think that's what they are. Obviously I'm on an x86_64 host too. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living #$*% out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

1 0

partition error with 9.3
by Henrik Schmidt 13 Apr '05

13 Apr '05

I'm using autoyast with pxeboot. I get "Error while configuring partitions" with a setup that worked with 9.2. What's new with 9.3 ? I noticed that I had to manually agree to the license, how to skip this automatically ? Where can I read about autoyast changes from 9.2 to 9.3 ? I checked /var/log/YaST2/y2log but couldn't find an error message. Any help ? I want to preserve partition 4 and format the rest with reiserfs. --------------- partition setup ------------------------ <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/opt</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> ---------------------------------------------------------- -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

How can I regularly update the install repository?
by Luca Pacor 13 Apr '05

13 Apr '05

Hello everybody, I am asking myself whether it would be possible to online_update the autoinstall repository: it would be nice to be able to install new machines using an up-to-date repository reducing this way the install time ... I am using SuSE 9.2 Any hint would be greatly appreciated. Many thanks in advance Luca

1 0

Re: [suse-autoinstall] Installing 64-bit software on 64-bit computer
by Steffen Winterfeldt 13 Apr '05

13 Apr '05

Hi, [getting rid of boot loader 64 bit check on SL 9.1+] the correct way is to remove the 'notice <N>' line from isolinux.cfg/syslinux.cfg. N is a bitmask, currently these bits are defined: 0: wrong side of a two-sided dvd 1: enable 64bit check 2: software is 64bit 3: is dvd 4: software is 32+64bit (Needs bit 1 set, too!) (9.2+) 5: default install source is slp (9.3+) Steffen

1 0

can not create an 64 bit auto-install with a 32-bit system (can not select 64-bit packages)
by Marco Manngatter 13 Apr '05

13 Apr '05

hello, i have a 32-bit system(SuSE 9.2 Professional) installed, can i create an auto-install for a 64-bit system with my 32-bit system? (i can not select any 64-bit package, only 32-bit packages) OR i must install a 64-bit system to create a 64-bit auto-install(to select 64-bit packages)? thx marco manngatter

1 0

Mountpoints missing in clone.xml/SLES8
by Oliver Schweikert 12 Apr '05

12 Apr '05

Hi all, when i create a clone of my SLES 8 system, the mount points are missing for cciss devices (autoyast2-2.6.46-3). I figured out that the function findMountpoint() in AIClone.ycp assumes, that e.g. the 1. partition of /dev/hda is associated to /dev/hda1, which is correct, but for the file /dev/cciss/c0d0 the 1. partition is /dev/cciss/c0d0p1 (the "p" makes the difference). Maybe using the device major/minor numbers will be a solution. Because i have not the skills to do it on my own in a acceptabe length of time, i would be glad if a fix would be available. Regards, Oliver

1 0