October 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Output of post scripts
by Dennis Peere 19 Oct '05

19 Oct '05

Hi all, Can anyone tell me if there is any way to show some output of a post installation script to the console screen ? I'd like to show what scripts it is performing and show some results. Regards, Dennis _________________________________________________________________ Bescherm je Inbox: Phishing - hoe te herkennen, rapporteren en voorkomen http://www.msn.be/security/phishing/

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 19 Oct '05

19 Oct '05

Hi Ajay, 1) verify with ' xmllint ' any of your xml files. 2) Keep in mind that the rules.xml was an UNTESTed example. 3) Verfiy your directory structure and file security setting . No softlinks and what so ever. 4) I mentioned also the /var/log/Yast2 directory. You will find there the y2log* files . Search them for rules.xml. You will see what happens during parsing the rules.xml. 5) I hope that your 'global' xml does not contain any Swap info. Maybe it is a good idea to REMOVE any partition info from your 'global' xml file and put all partition information into your class files for the sake of simplity To make the point: a) verify that your rules.xml works as expected ( search in the log files ) If it works as aspected: b) Verify the the merging process / the merged xml file And maybe Uwe got an idea ? hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int >>> Ajay Mulwani <ajaymulwani(a)gmail.com> 19/10/05 15:25 >>> Hi Hans, 1. The class.xml file was missing that header and footer info which I added and restarted the install. It seems the swap is still not there !! 2. rules.xml : is exactly the same as you had mailed earlier. $ cat rules.xml <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh mem=$( cat /proc/meminfo | grep -i memtotal | awk '{ print $2 } ' } # Output is in kbytes echo -n $mem ]]> </script> <match>499999</match> <match_type>greater</match_type> </custom1> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>500000</match> <match_type>lower</match_type> </custom1> <profile>classes/smallswap.xml</profile> <continue config:type="boolean">true</continue> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> $ 3. /var/adm/autoinstall/cache/InstalledSystem.xml is certainly missing the swap partition info. 4. The latest documentation link seems to not working currently. Regards, Ajay

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 19 Oct '05

19 Oct '05

Hi Ajay 1) Even an class.xml file must contain the header and footer for an autoinstall XML File Example: ( I do not know if its valid or not ) <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> ... ... </autoinstall> So your example is missing them. The best is to take the lines from your autoinst.xml file 2) Have you checked your rules.xml Be carefull with the <continue config:type="boolean">false</continue> because my example is pretty simple ( It does not use AND or OR logic for rules ) and after that no rules are processed any further. so you might post also your rules.xml 3) Check the Yast-Log files ( I think you will find the log after installation at /var/log/Yast2 ) and also look at /var/adm/autoinstall/cache/InstalledSystem.xml because it should be your merged final control/autoinstall file. 4) Latest Documenation for autoyast http://www.suse.de/~ug/autoyast_doc/rulesandclass.htm hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int >>> Ajay Mulwani <ajaymulwani(a)gmail.com> 19/10/05 13:38 >>> Hello Hans, Thanks for the excellent info. I was testing this and configured my setup exactly the same way as mentioned in your example. The host on which I tried the installation is having more then 500MB RAM. Therefore I assumed largeswap.xml and autoinst.xml files should have been be merged to create the final control file. The contents of largeswap.xml file in my case are: $ cat largeswap.xml <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <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_type>primary</partition_type> <size>2000mb</size> </partition> $ ..... and rest everything is defined in autoinst.xml. However after installation was over I saw all the partitions except swap. Please let me know if I did anything wrong or misunderstood somewhere. Regards, Ajay

2 1

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Ajay Mulwani 19 Oct '05

19 Oct '05

Hello Hans, Thanks for the excellent info. I was testing this and configured my setup exactly the same way as mentioned in your example. The host on which I tried the installation is having more then 500MB RAM. Therefore I assumed largeswap.xml and autoinst.xml files should have been be merged to create the final control file. The contents of largeswap.xml file in my case are: $ cat largeswap.xml <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <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_type>primary</partition_type> <size>2000mb</size> </partition> $ ..... and rest everything is defined in autoinst.xml. However after installation was over I saw all the partitions except swap. Please let me know if I did anything wrong or misunderstood somewhere. Regards, Ajay

1 0

RE: [suse-autoinstall] Supplementary installation-sources and version numbers
by Marlier, Ian 18 Oct '05

18 Oct '05

I'd grab the .src RPM, and change the name of the package. Leave the deps and everything alone, but if it's got a different package name then it shouldn't be overwritten. (ie, call is drdb-lars-0.7.13-0) -----Original Message----- From: Lars Neyjahr [mailto:lars.neyjahr@bcc.de] Sent: Tue 9/27/2005 9:17 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Supplementary installation-sources and version numbers Hi there, I have a few questions about installation of different versions of RPM-packages during auto-install. I use an additional installation-source which was added by "installation_sources -ea ftp://..." and I'd like to install an older (by version-number) package from this source rather than from my local SuSE-mirror. Here is an example: drbd-0.8.0-3 <= original SuSE-package which I don't want drbd-0.7.13-0.ln.0 <= my own package which I want to install How can I install a specific version - 0.7.13-0.ln.0 in this case - if the original version number is higher and how do i prevent any following online-update from installing the newer version? Thanks in advance. Bye... ...Lars -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Ethernet aliases?
by Michael T. Halligan 18 Oct '05

18 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What's the best way to do an ethernet alias in a control file? Like creating an eth0:1 or eth0:2 device? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDVVj1wjCqooJyNAMRAtuvAKCv52ETl58JXg6Ijsu6crkbajukIACgtVwd U1B5HPiYjxugQqHAFjQPuNM= =PrBT -----END PGP SIGNATURE-----

1 0

Re: [suse-autoinstall] Network installation - kernel command line limitation
by Alexander Dubinin 18 Oct '05

18 Oct '05

Hi Hans-Joachim, all, No, there is :) Please, look at documentation for autoyast - PDF file, section 7.3.3, named "Combining linuxrc info file with YaST2 control file": - Cut - 3.3. Combining linuxrc info file with YaST2 control file If you choose to pass information to linuxrc using the info file, it is possible to integrate the keywords in the XML control file. In the case the file has to be accessible to linuxrc and has to be named info. Linuxrc will look for a string (start_linuxrc_conf in the control file which represents the beginning of the file. If it is found, it will parse the content starting from that string and will finish when the string end_linuxrc_conf is found. The options are stored in the control file in the following way: Example 7.2. Linxurc options in the control file .... <install> .... <init> <info_file> <![CDATA[ ## Don't remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> .... Note that the autoyast keyword must point to the same file, i.e. if it is on a floppy, then the protocol floppy has to be used. In other cases where the info file is stored in the initial ram-disk, the file option has to be used. - Cut - Recreation of initrd is not suitable - as I need to install SLES9 in many different locations (As I understand it's "Enterprize" Linux, isn't it? ;) and from different NFS servers. Even in one office, there are few LABs, located behind firewall, where addresses of NFS server are different. So, target is to have generated autoyast control file for different offices (Using CGI script and database with server names, NFS paths, partition layouts, etc.) and install SLES9 transparently for customers. And of course, there is no reason to recreate initrd image, used for PXE boot for each of hundred locations - it's crazy. 2005/10/18, Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int>: > > >>> Alexander Dubinin <adubinin(a)gmail.com> 17/10/05 22:22 >>> > >Does anybody have other ideas? Or maybe somebody know, how to make > >"info" section in control file working? > > There is no INFO section in the control file. > Add the file ' info ' into the initrc file what just means: > Unpack the file ( Its a cpio archiv conating a minimal linux bootkernel and modules afaik ) > Add the info file to it. > repack the the initrc and be happy. > > Sorry for the sort answer but its pretty late in germany. > > hth > Hajo No problems :) Anyway - thanks for try to help! -- Regards, Alexander Dubinin

1 0

Re: [suse-autoinstall] Network installation - kernel command line limitation
by Hans-Joachim Ehlers 17 Oct '05

17 Oct '05

>>> Alexander Dubinin <adubinin(a)gmail.com> 17/10/05 22:22 >>> >Does anybody have other ideas? Or maybe somebody know, how to make >"info" section in control file working? There is no INFO section in the control file. Add the file ' info ' into the initrc file what just means: Unpack the file ( Its a cpio archiv conating a minimal linux bootkernel and modules afaik ) Add the info file to it. repack the the initrc and be happy. Sorry for the sort answer but its pretty late in germany. hth Hajo

1 0

Network installation - kernel command line limitation
by Alexander Dubinin 17 Oct '05

17 Oct '05

Hi all, Recently I've found that pxelinux, supplied with SLES9 still have limitation with 255 characters in kernel command line. So, if you want to append "aytoyast=<URL> install=<NFS_PATH> <some_kernel_options>" - it's very easy fall out to some strange mode during installation... For example, I had "showopts" argument cut at first letter - as result "s" was added to kernel options... You can imagine result ;) As I understand, it's problem of pxelinux - it uses old boot protocol, instead of new one - 2.02 - which have no such limitation. Is there any workaround? I've tried to use "Combining linuxrc info file with YaST2 control file" - but not understand, how it supposed to work. When I've placed required section to control file, retrieved from CGI script, and removed "install=" option from kernel command line, it just not working. Seems like linuxrc don't know how to get it from HTTP... So, looks like there are 2 options left - rewrite pxelinux to support longer kernel command line, or make "info" section of control file working... Does anybody have other ideas? Or maybe somebody know, how to make "info" section in control file working? Any help will be _very_ appreciated! -- Regards, Alexander Dubinin

1 0

Loadlin 1.6C problem when installing Novell Linux Desktop 9
by Dennis Peere 14 Oct '05

14 Oct '05

Hi, I'm trying to perform an automated harddisk installation of NLD 9 but seem to have problems loading initrd with loadlin 1.6C. The original initrd deliverd on CD1 of NLD is 5706806 bytes and I think that's too big for loadlin 1.6C. When I boot in FREEDOS and start loadlin I use the following command LOADLIN LINUX initrd=INITRD ramdisk_size=65536 root=/dev/ram0 init=/linuxrc It ends with the following error message : RAMDISk: Compressed image found at block 0 Invalid compressed format (err=2) VFS: Mounted root (minix filesystem) readonly Freeing unused kernel memory: 212K freed I've tried the following commands, without success, to start loadlin : LOADLIN LINUX INITRD=INITRD ramdisk_size=65536 LOADLIN linux initrd=initrd init=/linuxrc LOADLIN linux initrd=initrd init=/linuxrc root=/dev/ram0 I've used the same loadlin version to install RedHat 8.0 and RHES 4 without any problems. Although I must say that the initrd.img's were smaller on RH (2711963 bytes for RH8 and 3092868 bytes for RHES4) If I boot from CD1 and start the installation, the following modules are loaded during installation : Module Size Used by reiserfs 241488 1 edd 9368 0 dm_snapshot 16796 0 dm_mod 50300 1 dm_snapshot multipath 7688 0 raid6 98576 0 raid5 20736 0 xor 15240 2 raid6,raid5 raid1 14848 0 raid0 8192 0 parport_pc 35520 0 parport 37832 1 parport_pc usb_storage 60096 0 uhci_hcd 29200 0 hid 40896 0 ehci_hcd 27908 0 usbcore 103644 6 usb_storage,uhci_hcd,hid,ehci_hcd ide_cd 36740 0 sg 35616 0 sr_mod 16292 0 sd_mod 20224 0 scsi_mod 108876 4 usb_storage,sg,sr_mod,sd_mod cdrom 36892 2 ide_cd,sr_mod cramfs 42868 1 vfat 14208 2 fat 43584 1 vfat af_packet 20872 0 nvram 8456 0 I've tried to mount the initrd (from the NLD cd's) and removed all modules that weren't loaded during the cd installation. The result was an initrd of 2056532 bytes When I started loadlin with that initrd I got the following error mesages with every module the kernel want to load : on VT3 insmod: error inserting '/modules/reiserfs.ko': -1 Invalid module format insmod: error inserting '/modules/eepro100.ko': -1 Invalid module format on VT4 ehci_hcd: disagrees about version of symbol struct_module uhci_hcd: disagrees about version of symbol struct_module After giving up on trying to find out what modules I needed to put in the initrd I started looking for an alternative program for loadlin that can mount the original initrd and found Tiny.exe => http://sourceforge.net/projects/gujin/ Used that with the following command : tiny.exe linux initrd root=/dev/ram0 ramdisk_size=65536 init=/linuxrc Error message : Kernel panic: No init found. Try passing init= option to kernel. linld.com => http://195.66.192.168/linux/linld/ Used that with the followinc command : linld.com image=linux initrd=initrd cl=nld.par nld.par includes : ramdisk_size=65536 install=hd://suse/nld/cd1 autoyast=file:///mounts/extra/autoinst.xml Error message : -1 Invalid module format for every module it wants to load. Hope someone can help me out :-( Regards, Dennis Peere _________________________________________________________________ Gratis bloggen op MSN Spaces http://spaces.msn.com/?mkt=nl-be

3 3