March 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Mutliple Installsources
by Martin Vogt 10 Mar '06

10 Mar '06

Hello list, OpenSuSE does not contain many multimedia applications. But there ist an addition Multimediadirectory for SUSE 10.x. ftp://packman.inode.at/suse/10.0/ Currently Im using this /proc/cmdline for autoyast: initrd=initrd_suse101b6_i386 vga=0x314 Insmod=e1000,bcm5700,e100,aic7xxx_old install=http://10.136.16.223/mysuse101/inst/CD1 autoyast=tftp://10.136.16.221/suse/autoyast-suse101-lvm.xml Is it possible to add a second installation resource during an autoyast installation? SLES9 for example had something like this: cat yast/order /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 Which tells yast to use more resources. Is a similiar mechanism supported with OpenSuSE? regards, Martin

2 1

Installation media in SLES9 SP3
by Radoslaw Sypianski XX (LI/EAB) 10 Mar '06

10 Mar '06

Hi During autoinstallation process (in chroot script) I would like to know from where (which device) the installation is going on. How to find out about it ? Regards, Radek

2 1

LSI Logic Megaraid and SLES 9 SP2 --- Uwe Gansert Help me Please :-)
by Rob Thompson 10 Mar '06

10 Mar '06

Hi, I am attempting to use autoyast to install SLES 9 SP2 on a new Dell 2850. I am using a .xml file for the partitioning and package selection and everything works fine until the first reboot. Upon rebooting, the server cannot find its' hard disks. The raid controller it is attempting to use is a megaraid. If I build this server by-hand using the SP2 cd's the install works and during boot it shows it is using the megaraid_mbox module. This is what is also listed in /etc/sysconfig/kernel. If I build using autoyast, then use a rescue cd to see the drives and mount / no megaraid module is present in /etc/sysconfig/kernel. My question is this: Can I force the autoyast installation to use the megaraid_mbox module? I have tried putting the following line in /tftp/pxelinux.cfg/default file label linux kernel linux append pci=noacpi ide=nodma barrier=off initrd=initrd ramdisk_size=65536 insmod=megaraid_mbox along with pointers to my NFS share and the xml file. Is this the correct way to add a module, or am I missing something else? Thanks, Rob Thompson

2 1

AutoYast LVM problem
by dbellis＠mmm.com 08 Mar '06

08 Mar '06

Hello, I am getting the following error during the partition phase of autoyast. LVM error lvremove -f -A n /dev/vg00/home /dev/sda1: open failed: No such device or address Here is my xml file. <?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> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mmm.com</domain> <hostname>servername</hostname> <nameservers config:type="list"> <nameserver>0.0.0.0</nameserver> <nameserver>0.0.0.0</nameserver> </nameservers> <searchlist config:type="list"> <search>mmm.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>0.0.0.0</broadcast> <device>eth-id-00:14:22:0e:7b:d0</device> <ipaddr>0.0.0.0</ipaddr> <netmask>255.255.255.0</netmask> <network>0.0.0.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> <options>Speed=100 Duplex=2</options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>0.0.0.0</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Central</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> </mode> <mouse> <id>22_exps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <partition_type>primary</partition_type> <mount>/boot</mount> <size>1GB</size> </partition> <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> <partition_type>primary</partition_type> <mount>swap</mount> <size>2GB</size> </partition> <partition> <create config:type="boolean">true</create> <lvm_group>vg00</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> </drive> <drive> <device>/dev/vg00</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <create config:type="boolean">true</create> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>home</lv_name> <mount>/home</mount> <size>2000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>opt</lv_name> <mount>/opt</mount> <size>4000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>root</lv_name> <mount>/</mount> <size>6000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>2000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>usr</lv_name> <mount>/usr</mount> <size>4000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>var</lv_name> <mount>/var</mount> <size>4000mb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Linux-Tools</addon> <addon>Basis-Sound</addon> <addon>X11</addon> <addon>Base-System</addon> <addon>Kde-Desktop</addon> <addon>YaST2</addon> <addon>auth</addon> <addon>Print-Server</addon> <addon>SuSE-Documentation</addon> </addons> <base>default</base> <packages config:type="list"> <package>clamav</package> <package>gmp</package> <package>ltrace</package> <package>sharutils</package> </packages> </software> </install> </profile> Any ideas or help would be greatly apprcieated! David Bellis

2 1

dynamic partition size
by Jochen Mueller 08 Mar '06

08 Mar '06

Hello, i am using autoyast (SLES9 SP3 and Suse 10, both using NFS) Installation on a lot of different systems. How could i size the partitions depending on disk-size and on memory size of the target System? For example: * the swap partition should be 1.5 times the size of the memory, but at least 1 gig and max. 8 gig. * the /home partition should be 20% of the disk drive but at least 50Gig Any ideas about this nice features ? Regads Jochen

2 1

Online updates offline
by Roger Oberholtzer 08 Mar '06

08 Mar '06

I have some SUSE 10 systems that are not able to access the internet. However, I would like them be kept up to date. Previously, I had an on-line system that I did updates on, keeping the downloaded files. Overall, this worked. The problem is that the kept files just grows and grows as there is no mechanism for getting rid of obsolete updates. It also requires that I keep an office computer in sync do this. Is there an easy way to maintain a local copy of the online update database? I guess I could mirror it. But then I get lots of things we never install. Any other interesting option? -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23

1 0

installing SP2 using autoyast
by jaiber john 07 Mar '06

07 Mar '06

Hello, I'm working on a software that lets user install SLES9 and the drivers required on a machine automatically. It does this by collecting essential user inputs and creating the autoyast.xml. This xml file is copied to a hard-disk location along with the vmlinux and initrd from CD1 to the hard-disk which is then made bootable by installing LILO (with kernel and initrd lines pointing to the files copied above). The linuxrc.config is modified within the initrd to set installation source as CD, etc. The following lines were added to linuxrc.config before re-creating the initrd: ------------------------------------------------------- AutoYast: file:///autoyast.xml Exec: modprobe ext3 InstMode: cd ------------------------------------------------------- On re-boot from hard-disk, it'd request SLES9 CD1,2,3,... and the OS would get installed. The drivers would get installed through post-install scripts. This techinique worked well for SLES9 but not with SP2. If I do the same with SP2 (i.e, copying the kernel, initrd from SP2 CD1 to hard-disk), on reboot, it requests for core SLES9 CD1 and then on, only SLES9 installation proceeds, the SP2 cds were not asked and hence they dont get installed. Are there any provision in linuxrc.config or info file to direct autoyast to install SP2 and hence request specifically for SP2 CD1 on reboot? -- Thanks <Jaiber John>

1 0

SLES9 SP2 autoyast installation
by jaiber john 07 Mar '06

07 Mar '06

Hello, Is there any specific entry I need to add to autoyast.xml to install SLES9 SP2? I ask this because when I install SP2 using the autoyast.xml I used for installing SLES9, the installer does not ask for CD2 and CD3 of SP2. Instead it completes using base SLES9 CDs itself. I need the updated kernel drivers in SP2 to get SATA controller detected. Thanks, Jaiber John

1 1

Chroot script: mounting dvdrom
by Radoslaw Sypianski XX (LI/EAB) 02 Mar '06

02 Mar '06

Hi I have to copy some files from installation media (dvd-rom in my case) after installation process, in chroot script. In SuSE Linux Prof. 9.3 there is no problem cause in that script I'm albe to find mounted iso9660 device and copy necessary files from there. But in SLES9 SP3 this method doesn't work - mount command in chroot script returns that there is no mounted iso9660 devices. Of course I can try to mount /dev/cdrom by default but it is not enough in case when there are 2 and more dvd drives - I don't know in which the installation media is. How to find out from which device the installation has been done ? Or maybe there is another way to solve that in SLES9 ? Regards, Radek

1 0

Changing Kernel in pxe install
by Reeves, Matthew J. 01 Mar '06

01 Mar '06

Classification: UNCLASSIFIED I'm trying to set up a pxe environment to install SuSE 9.0 on some Dell Poweredge 1850s. The kernel that comes with 9.0 doesn't support the raid controllers. I want to change the installing kernel to 2.4.32 so that the raid works. I can get the systems booting and linuxrc runs but it asks for a module disk then goes into manual mode. In the manual mode I can kick off a ftp install but after root is downloaded the system just goes back to the linuxrc menu. Is there an easy way to change the kernel? Thanks, Matt

3 2