February 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

rules.xml example using custom rules?
by Voss Stefan 04 Feb '04

04 Feb '04

Hi, has anybody an examples rules.xml that uses custom1-5 rules? We want to determine the machine specific configuration (hostname, IP address settings) via rules. According to rules.dtd such a rule could look like this <rule> <custom1> <script>/path/to/some/script.sh</script> <match>machine1</match> <match_type>equal</match_type> </custom> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> Is it correct that <script> contains a script path or does it contain the script body like the following? <rule> <custom1> <script> <![CDATA[ #!/bin/sh # Try to determine value of boot parameter $machine=$(cat /proc/cmdline | grep "name=") echo $machine ]]> </script> <match>machine1</match> <match_type>equal</match_type> </custom> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> Regards, Stefan Voss

1 0

WG: [suse-autoinstall] Problems customizing an install CD
by Lenz, Fabian 04 Feb '04

04 Feb '04

Your first problem: on the first cd, in the directory /boot/loader/ is the isolinux.cfg (SuSE 9.0). default linux # hard disk label harddisk kernel linux append SLX=0x202 showopts # install label linux kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts acpi=off <----------- add this! Your third problem: in /suse/setup/descr/ is the file packages! =Ver: 2.0 ##---------------------------------------- =Pkg: 3ddiag 0.703 159 i586 +Req: /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/sh ld-linux.so.2 libc.so.6 libc.so.6(GLIBC_2.0) libhd.so.7 rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: 3ddiag = 0.703-159 -Prv: =Grp: System/Base =Lic: GPL =Src: 3ddiag 0.703 159 src =Tim: 1064411185 =Loc: 1 3ddiag-0.703-159.i586.rpm <---------------------- Loc: 1 means the package is on CD 1! =Siz: 27266 50861 change all Loc : X to Loc: 1 if you have all +Aut: packages on one cd! Stefan Dirsch <sndirsch(a)suse.de> -Aut: ##---------------------------------------- =Pkg: BASS 20030801 50 i586 +Req: scummvm timidity ... ... ... ... -----Ursprüngliche Nachricht----- Von: steven.cardinal(a)adheris.com [mailto:steven.cardinal@adheris.com] Gesendet: Donnerstag, 29. Januar 2004 16:10 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Problems customizing an install CD I'm new to both SuSE and Autoyast. I've read through the autoinstall docs on the Suse site and find that I don't seem to know enough about autoyast in the first place to figure out what they are telling me. Here's what I've done and the problems I am having: I created a directory /SUSE9 and copied (cp -a /mnt/* /SUSE9/) all 5 CDs into this directory. I setup Yast to use this as a repository (I already used Yast update to patch this machine, so my yast utilities should be the latest available). I found that, using the GUI to select my source directory, if it appends a trailing / to the path (/SUSE9/) - it is not seen as a valid source. Finally figured that out and got autoyast to see the directory as well. I created a config for a server I am building. I used the Minimal+X11 selection plus added dhcp and bind. I setup some user accounts, etc. Everything seemed fine (the disks on this compaq dl360 show as /dev/ida/c0d0 so I had to hand-edit my config file afterwards). I then chose to build an ISO based on this config. It said it found all the necessary files and created an iso file, which I burned to media. First problem I had was that the compaq seems to have acpi issues, so I had to boot the cd with "linux acpi=off". Is there a way to configure autoyast to add those parameters by default? This CD will be used to rebuild the system should it die for some reason (hard drive crash or something) - it would be easier to hand off to my support people if they had very few ways of generating problems ;-) Second, I had an error installing grub (in the config file I told it to use the MBR and to replace what is there) The error was 'File not found'. I chose to reconfigure and retry and it worked ok - not sure if this is a problem with this particular machine or in my config. Any ideas? Next, it rebooted and went to install packages, but it suddenly couldn't find most of my packages and started prompting me for CD2. Shouldn't the 'Create ISO' setup the necessary paths in the iso image so that it works? Is there something I have to configure elsewhere? Once I get past this I'll hack away at adding extra packages (samba3, etc). I haven't had any luck getting autoyast to recognize my custom .sel file (it can't open any of my CD-provided .sel files either, so I don't understand how it works) Also, autoupdate pulls down patch.rpm files. Is there a way to apply these to my source directory so that my final build cd is patched already? Thanks Steve Oh, is there any plan to make the mailing list archives searchable? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

typos in autoinstall FAQ
by Hal Wine 03 Feb '04

03 Feb '04

Anas, Thanks for the FAQ -- it's helping me move forward on SLES installation server setup... There are some typos in the example code for 2.5 (HTTP loopback mount of ISO images): printf "/SP3\t/SP3" > yast/order printf "/SLES\t/SLES" > yast/order printf "/UL/CD1\t/UL/CD1" >> yast/order printf "/unitedlinux-i386/CD1\t/unitedlinux-i386/CD1" > yast/instorder printf "/sles8-i386/CD1\t/sles8-i386/CD1" >> yast/instorder printf "/SP3\t/SP3" > yast/instorder first, there is a missing '>' in the second and the last line. second, either the command needs be changed to 'echo -e', or '\n' needs to be added to the end of the strings. third, I'm not sure that the sets of data match. This is the only place I've seen different naming conventions used in the same pair of order/instorder files. The 'order' file refers to '/SLES', and the 'instorder' file refers to '/sles8-i386/CD1' finally, I _think_ to match the directory structure earlier in the example, the correct refernce to SP3 should be '/SP3/CD1' I'm not sure about the last two, as even with with (and without) those changes, I still can't get sles8 sp3 to install via HTTP. --Hal

1 1

Re: [suse-autoinstall] example for sles8 + sp3 install server setup?
by Joachim Jordan 02 Feb '04

02 Feb '04

Hi everyone, it works for me to it that way. I added the SP3 just as another source to the installation tree. Here is my script i'm using to setup the distribution: ------------------------------------------------------- #!/bin/sh # Script to setup SLES netinstall source if [ $# -lt 1 ] then echo "Please provide the path of the new driver as parameter!" exit 1 fi cd $1 # check if in correct directory! if [ ! -f suse/CD1/content ] then echo "Error: Looks like wrong directory!" exit 1 fi # remove previous configurations if [ -d yast ] then rm -r yast fi if [ -d boot ] then rm -r boot fi if [ -d media.1 ] then rm -r media.1 fi if [ -f content ] then rm content fi if [ -f driverupdate ] then rm driverupdate fi # Now we have to move some data around to make this # a multiple source directory # # first we copy the order directory described above. mkdir yast cp suse/CD1/content yast/ cp suse/CD1/content . # Then the boot directory with the installation image cp -a suse/CD1/boot . # The content file and the media directory cp -a suse/CD1/media.1 . if [ -f media.1/info.txt ] then rm media.1/info.txt fi # Now we copy the description files from SLES to the order directory as # described earlier. mkdir -p yast/suse/suse/setup/descr cp -a suse/CD1/suse/setup/descr yast/suse/suse/setup cp suse/CD1/content yast/suse/ cp -a suse/CD1/media.1 yast/suse/ cp -a suse/CD2/media.2 yast/suse/ cp -a suse/CD3/media.3 yast/suse/ # Same applies for supplementary mkdir -p yast/sup/suse/setup/descr cp -a supplementary/CD1/suse/setup/descr yast/sup/suse/setup cp supplementary/CD1/content yast/sup/ cp -a supplementary/CD1/media.1 yast/sup/ cp -a supplementary/CD2/media.2 yast/sup/ # Do the same for Service Pack 3 mkdir -p yast/sp3/suse/setup/descr cp -LRp sp3/CD1/suse/setup/descr yast/sp3/suse/setup cp sp3/CD1/content yast/sp3/ cp -a sp3/CD1/media.1 yast/sp3/ cp -a sp3/CD2/media.2 yast/sp3/ # overwrite the old file in the boot directory with new ones cp -a sp3/CD1/boot . # copy driverupdate file cp sp3/CD1/driverupdate . # Do the same for Addons mkdir -p yast/ad/addons/setup/descr cp -a Addons/addons/setup/descr yast/ad/addons/setup cp Addons/content yast/ad/ cp -a Addons/media.1 yast/ad/ # We are almost done.. # Now we'll adapt the order files. # Fields of the order files are TAB delimited cat << EOF > yast/order /yast/ad Addons /yast/sp3 sp3/CD1 /yast/suse suse/CD1 /yast/sup supplementary/CD1 EOF cat << EOF > yast/instorder /yast/sup /yast/suse /yast/sp3 /yast/ad EOF # final stuff #cp ../Code/root/root.neu boot/root chown -R wwwrun:nogroup . # End ------------------------------------------------------------------- I even added another source for my own packages. For that i reused the content and media.1 files from the SLES distribution and changed them. I'm using HTTP as installation protocol and this is for an Power PC based installation for JS20 blades. But it is more or less the same for Intel. Just one thing about the SP3, to get all the Yast fixes included in the installation process( for example necessary for HTTP support, HTTP is broken in the SLES8 and fixed with the code in the SP3), you have to copy the driverupdate file to the root of your new multi source distribution(or if you use NFS, you can also copy the subdirectory containing all from the CD to the root). For me, the driverupdate file does not work. If i use it, yast dies in the middle of the installation with an segfault. If i copy all files from the driverupdate file into the root file manually, it works. Best regards, Joachim Jordan Linux IT Architect, EMEA Linux Center of Competence IBM Laboratories, Dept.3300, Schoenaicherstr.220, D 71032 Boeblingen, Germany Sametime/e-mail: jordanj(a)de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232 Hal Wine <hal(a)reactivity.c To: suse-autoinstall(a)suse.com om> cc: Subject: [suse-autoinstall] example for sles8 + sp3 install server setup? 13.01.2004 18:32 Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3? I followed Anas' example laytout for my original installation server setup. I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source. If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct? Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs. Thanks, --Hal -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

Install Problem
by Ryan Simmons 02 Feb '04

02 Feb '04

I have SuSE Linux 8.2 Professional that I have installed before on this computer. However, I was redoing my harddrive and repartioning it more to my liking, so I wiped it clean and began to reinstall various OS's on my comp. When I boot up from the SuSE CD OR DVD I can only get as far as selecting which install to do. Such as Installation, Installation-Safe Settings, Installation- ACPI Enabled, Manual Installation, etc., etc. After I select which one(I've tried each one) all I get is a blue line on the left of my screen and a mashed up, mostly grayish lines at the top of my screen. If I start hitting enter or other buttons, I can see the gray lines switch around like it is going through options, it's just not displayed where a human can tell what is going on. I have not changed my display card or drivers or anything really, exept upgrading my RAM a little. But the memory test says that all my RAM is fine. Since I have installed this before on my computer without this problem, I've been trying to figure out what is different now than before. But I can't think of anything. Has anyone had this problem? Or any ideas on what's wrong? Ryan Dell Dimension 8200 Pentium 4 2.4GHz 1 GB RDRAM 128MB NVIDIA GeForce4 Ti 4600 Tv out _________________________________________________________________ Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1

2 1

Next Bug with autoyast and SP3?
by Hans Kamm 01 Feb '04

01 Feb '04

Hi, how many bugs have autoyast? over 100?. Situation. Booting from SP3-CD with control-file and install-files on nfs. lilo wouldn't install (I' see noting interesting in the log. I think the new kernel is missing.) With SP 2a-CD it works! Hans _________________________________________________________________ Schützen Sie Ihren Posteingang vor unerwünschten E-Mails. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt Hotmail-Junk-Filter aktivieren!

1 0