May 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 16 Jun '05

16 Jun '05

Jiri Srain wrote: > Hi Mike! > > Dne pondělí 30 květen 2005 10:26 jste napsal(a): > >>Jiri Srain wrote: >> >>>Dne pondělí 30 květen 2005 09:59 jste napsal(a): > > >>>>SLES10 seems a bit too far on the horizon. This is the first system >>>>we're trying to install using autoyast with SLES9. >>> >>>It is not issue of autoinstallatino only - plain installatino is affected >>>as well. >> >>but there at least you have the option of checking the initrd before you >>boot. I tried with adding "boot confirm true" (can't remember the exact >>syntax) in autoinst.xml but that option didn't seem to have any effect >>as the machine booted automatically right after installation finished. > > > Don't know, pass the question to the list. > > >>I would be happy if I had the chance to alter the MKINITRD and create a >>correct initrd _before_ the initial reboot, as we're not really looking >>for fully-automated setups. >>Any idea on why this might not work? > > > No, no idea. I didn't know about this option before. That's (or rather was) the option in autoinst.xml: <install> <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> </mode> According to autoyast documentation here http://www.suse.de/~nashif/autoinstall/9.1/autoyast.pdf it has been dropped for SuSE9.1/SLES9. >>>It is not possible to add all modules which are in info file to initrd - >>>because it would put there a lot of modules which are not needed. >>> >>> >>>>Where does the MKINITRD variable get set? Which file would I have to >>>>look into to tweak it myself? >>> >>>/usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be >>>recompiled by 'ycpc -c Initrd.ycp'. >> >>thanks for the pointer. I'll look into it tomorrow when I'm on site. > > > If you just want to update sysconfig and recreated initrd before the reboot, > the probably easiest would be to add to /usr/share/YaST2/clients/inst_finish > just after bootloader is installed eg. > > Popup::Message (_("Update the inirdd now")); > > This will show you message after bootloader is saved and you can switch to the > console to change anything you want to. > > Just remember that you have to change the file in the installation system > (which is stored on CD1 in /boot/root). It is cramfs image. that sounds like a good workaround, thanks.

3 2

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 30 May '05

30 May '05

Hi Jiri Jiri Srain wrote: > Hi Mike! > > Dne pondělí 30 květen 2005 09:59 jste napsal(a): > >>Jiri >> >>I think this is a major problem for all machines with more than one HBA. >>autoinst would work or not depending on the PCI ID which makes it quite >>unpredictable (i.e. you'd have to check PCI slot ordering and adapt >>accordingly before starting installation). > > > It is not for all of them, only for some. It may happen that the modules are > loaded in the same order as they are saved to sysconfig - but this is > unpredictable. this is exactly the problem I have. If we wanted to upgrade a number of machines from SLES8 to SLES9 we'd have to check each and every one of them on the hardware level. >>SLES10 seems a bit too far on the horizon. This is the first system >>we're trying to install using autoyast with SLES9. > > > It is not issue of autoinstallatino only - plain installatino is affected as > well. but there at least you have the option of checking the initrd before you boot. I tried with adding "boot confirm true" (can't remember the exact syntax) in autoinst.xml but that option didn't seem to have any effect as the machine booted automatically right after installation finished. I would be happy if I had the chance to alter the MKINITRD and create a correct initrd _before_ the initial reboot, as we're not really looking for fully-automated setups. Any idea on why this might not work? >>Wouldn't it be possible to just add the detected modules _after_ the >>ones explicitely defined in the info file? This way all the modules >>needed for the installation get loaded and any additional (detected) >>modules as well. > > > Wouldn't it be possible to set the modules to info file in the different > order? This should solve the problem for this particular machine. not really. The number of devices on the qla2300 might change over time and then I'd have to use scsidev or devlabel to get consistent device names. We haven't figured out yet which one of the two (scsidev or devlabel) to use. Hitachi (SAN) wants us to go with devlabel, SuSE with scsidev. I'd prefer to have / on /dev/sda3 on all the machines. > It is not possible to add all modules which are in info file to initrd - > because it would put there a lot of modules which are not needed. > > >>Where does the MKINITRD variable get set? Which file would I have to >>look into to tweak it myself? > > > /usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be recompiled > by 'ycpc -c Initrd.ycp'. thanks for the pointer. I'll look into it tomorrow when I'm on site. >>Mike >> >>Jiri Srain wrote: >> >>>Hi! >>> >>>To /etc/sysconfig/kernel, the modules are written in the order the >>>respective adapters are detected. The order the modules were loaded for >>>installation is not used. The reason was that the list of modules needed >>>for installation contains moduels which are not needed in inird of the >>>running system (eg. network card if installing from network). >>> >>>I want to fix it at least for SLES10 (to try to keep the order of the >>>modules during first stage but not modules which are not needed into >>>initrd) >>> >>>Dne sobota 28 květen 2005 00:26 Michael Steinmann napsal(a): >>> >>>>I'm having problems with SLES9 SP1 autoinst on a machine with two >>>>qla2300 and one megaraid controller. >>>> >>>>In my info file I've got: >>>>insmod: megaraid >>>>insmod: qla2300 >>>> >>>>and the drivers load in that order, giving me /dev/sda on the first disk >>>>on the megaraid controller which is what I want. >>>> >>>>But, autoinst would always add the qla2300 to the beginning of the >>>>MKINITRD variable in /etc/sysconfig/kernel before building the initrd. >>>>As the qla2300 gets added at the *beginning* this leads to a initrd >>>>linuxrc that always loads qla2300 before megaraid. >>>>When the machine boots using the initrd built by autoinst the devices >>>>are not in the same order as during the install. >>>> >>>>When qla gets loaded via info file, the MKINITRD looks like this: >>>>"qla2300 megaraid qla2300" >>>> >>>>when it doesn't get loaded by 'insmod: qla2300' in info file: >>>>"qla2300 megaraid" >>>> >>>>Why would autoinst insist on putting qla2300 in the initrd? And why at >>>>the beginning of the list? >>>> >>>>Shouldn't the order the modules get added to the initrd honor the order >>>>given in the info file? >>>> >>>>Mike > >

1 0

initrd module load order not following info file
by Michael Steinmann 30 May '05

30 May '05

I'm having problems with SLES9 SP1 autoinst on a machine with two qla2300 and one megaraid controller. In my info file I've got: insmod: megaraid insmod: qla2300 and the drivers load in that order, giving me /dev/sda on the first disk on the megaraid controller which is what I want. But, autoinst would always add the qla2300 to the beginning of the MKINITRD variable in /etc/sysconfig/kernel before building the initrd. As the qla2300 gets added at the *beginning* this leads to a initrd linuxrc that always loads qla2300 before megaraid. When the machine boots using the initrd built by autoinst the devices are not in the same order as during the install. When qla gets loaded via info file, the MKINITRD looks like this: "qla2300 megaraid qla2300" when it doesn't get loaded by 'insmod: qla2300' in info file: "qla2300 megaraid" Why would autoinst insist on putting qla2300 in the initrd? And why at the beginning of the list? Shouldn't the order the modules get added to the initrd honor the order given in the info file? Mike

2 1

Problem with swap space on Suse 9.1 installation
by Paulo Coelho 29 May '05

29 May '05

Hello, I’m trying to install Suse 9.1 on a very old machine (a Pentium 133Mhz w/ 48Mb of RAM and two Maxtor hard drives, one with 1.2Gb and another with 1.5Gb) Since my CD-ROM doesn’t seem to read recordable CDs, I’ve been trying a network installation (I’ve downloaded the installation directory into another PC on my LAN that’s acting as FTP server). I’ve created the three boot floppy disks and I’m booting my machine from floppy. I can configure my network card using the appropriate modules disk. When I first tried to install, it told me there was not enough memory and had to create some swap space. I then used the rescue disk to try to do something about it. I used fdisk and set up these partitions: /dev/hda1 – Linux /dev/hda2 – Linux Swap /dev/hdc1 – Linux Then I did a mkswap –c /dev/hda2 and the swapon /dev/hda2 The swap has 280Mbytes. I rebooted the machine and started the installation process. Once again it said I had to create swap space, and I went to a console terminal and did the swapon /dev/hda2 command – no errors. This seamed to have worked, because it started to download the installation image. It was all going well until it needed to use the swap space. I can see activity on the hard drive, but the download stops and the installation hangs. No error messages that I can see. Can anyone help me on this one? I have very little experience with Linux, I’m probably doing something wrong… Thank you! Paulo -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.2.0 - Release Date: 27-05-2005

1 0

RE: [suse-autoinstall] Network Installation Problems
by Paul Anthony Rae (QC/EMC) 27 May '05

27 May '05

As it turns out it was a corrupted control.xml in the source tree. Thanks to those who sent their suggestions and advice! Paul -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 19, 2005 5:33 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Well I am still battling with this issue. I still get big red "Error in Installation" trying to do an autoinstall over the network. Possible issues: 1) I have no DNS server on my little private network where I am attempting the install. Is this a problem? 2) Control file validity checks out ok, but maybe there is something busted? What kinds of problems might lead to 'Error in Installation" just after control file download, assuming the control file is sane? Below is the last version of the control file I have been using. Any weirdnesses I am missing? Paul <?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> <runlevel> <default>3</default> </runlevel> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Pacific</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>ignore</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <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_type>primary</partition_type> <size>13.9GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>Swap</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">131</partition_id> <size>12GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/opt</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <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>Base-System</addon> <addon>YaST2</addon> </addons> <base>Minimal</base> </software> </install> </profile> -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 10, 2005 11:32 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Excluding a package, or proper dependency resolution
by Dax Kelson 25 May '05

25 May '05

I'm having a problem of having two conflicting packages being installed. Both "imap" and "cyrus-imapd". Apparently "imap" is coming from either "base" one of the "addons" listed, and then when I manually specify cyrus-imapd as a "package" the conflict occurs. How can I still use my defined list of "addons", yet not have imap installed? Here is my config snippet: <software> <base>default</base> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Fonts</addon> <addon>Games</addon> <addon>Gnome</addon> <addon>Gnome-Devel</addon> <addon>Hacker</addon> <addon>Java</addon> <addon>Kde</addon> <addon>Kde-Desktop</addon> <addon>Kde-Devel</addon> <addon>Kernel-Devel</addon> <addon>LAMP2</addon> <addon>LDAP-Server</addon> <addon>Laptop</addon> <addon>Latex</addon> <addon>Min</addon> <addon>Mobile</addon> <addon>Multimedia</addon> <addon>Network</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>Tcl-Development</addon> <addon>Voip</addon> <addon>X11</addon> <addon>Xen</addon> </addons> <packages config:type="list"> <package>autoyast2-utils</package> <package>SDL-devel</package> <package>finger-server</package> <package>mozilla-mail</package> <package>ncftp</package> <package>pdksh</package> <package>talk-server</package> <package>telnet-server</package> <package>postgresql-server</package> <package>lvm2</package> <package>cyrus-imapd</package> </packages> </software> A workaround is to just "rpm -e imap" in a postinstall script, but I was hoping for a cleaner solution. Thanks in advance. Dax Kelson Guru Labs

2 1

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Daniel Fitzner 25 May '05

25 May '05

I use as bootcd the sles8 sp3 cd, so normally this could not be the problem. thx and best regards --- Uwe Gansert <ug(a)suse.de> schrieb: > On Tuesday 24 May 2005 13:44, Daniel Fitzner wrote: > > > I checked the logfile and the following entries > should be a hint for the > > problem: > > okay, I see. > > > 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] > CurlAgent.cc(Execute):252 > > Data: 2005-05-24 04:26:42 <1> linux(1397) > [ag_curl] > > CurlAgent.cc(Execute):253 Output: > /tmp/YaST2-01397/autoinst.xml 2005-05-24 > > 04:26:42 <3> linux(1397) [Interpreter] :0 Couldn't > find an agent to handle > > '.get_mac' 2005-05-24 04:26:42 <3> linux(1397) > [Interpreter] > > the .get_mac agent came with a service pack. I think > it's SLES8 Service Pack > 3. So you have to use that one and not a plain > SLES8. > > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 > Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: > +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

Integrating scsi modul in autoyast installation
by FITZ MAILING 24 May '05

24 May '05

Hello guys, maybe someone of you tried the same, like I am doing now since 1 week. I have a server with a scsi controller, that is not supported by the standard kernel of suse. If I a the modul manual at the installation everything works. But I want to use autoyast. The FAQ of autoyast points to http://ftp.softnet.tuc.gr/pub/linux/suse/people/hvogel/Update-Media-HOWTO/U… for this. So I created the directory linux/suse/i386-sles8 with the subdirectories install and module in my HTTP-Repository and also at my bootcd (SLES8 SP3), but nothing works, the module could not be loaded. Any hints or suggestions how to deal with this problem??? thanks ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

3 2

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Uwe Gansert 24 May '05

24 May '05

On Tuesday 24 May 2005 13:44, Daniel Fitzner wrote: > I checked the logfile and the following entries should be a hint for the > problem: okay, I see. > 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] CurlAgent.cc(Execute):252 > Data: 2005-05-24 04:26:42 <1> linux(1397) [ag_curl] > CurlAgent.cc(Execute):253 Output: /tmp/YaST2-01397/autoinst.xml 2005-05-24 > 04:26:42 <3> linux(1397) [Interpreter] :0 Couldn't find an agent to handle > '.get_mac' 2005-05-24 04:26:42 <3> linux(1397) [Interpreter] the .get_mac agent came with a service pack. I think it's SLES8 Service Pack 3. So you have to use that one and not a plain SLES8. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

1 0

Problem creating valid autoyast.xml file (SuSE 9.3) [Virus checked]
by Matthias.Eble＠kaufland.de 24 May '05

24 May '05

Hi autoinstall list, I've got a problem creating autoyast xml files on a HP-BL20pg3 server (SuSE 9.3). The result of the creation of the xml file doesn't seem to be valid at all. Here are the steps I did 1. started yast/yast2: chose misc -> autoinstallation I got an empty set of basic settings. 2. create the reference file: Tools ->Create Reference Profile. 3. chose system services (runlevel) only - for simplicity 4. create... looks good up to then 5. let's check the result: Tools-> check validity.. Without DTD: OK With DTD: /tmp/YaST2-15489-tNCLVw/valid.xml:12: element device_map: validity error : No declaration for attribute type of element device_map <device_map config:type="list"> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:14: element firmware: validity error : No declaration for element firmware <firmware>(hd0)</firmware> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:15: element linux: validity error : No declaration for element linux <linux>/dev/cciss/c0d0</linux> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:16: element device_map_entry: validity error : No declaration for element device_map_entry </device_map_entry> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:17: element device_map: validity error : No declaration for element device_map </device_map> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:83: element bootloader: validity error : Element bootloader content does not follow the DTD, expecting (activate? , global? , initrd_modules? , loader_device? , loader_type? , location? , repl_mbr? , sections?), got (activate device_map global initrd_modules loader_device loader_type location repl_mbr sections ) </bootloader> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:103: element keep_partition_fsys: validity error : No declaration for attribute type of element keep_partition_fsys <keep_partition_fsys config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:104: element keep_partition_id: validity error : No declaration for attribute type of element keep_partition_id <keep_partition_id config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:105: element keep_partition_num: validity error : No declaration for attribute type of element keep_partition_num <keep_partition_num config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:105: element keep_partition_num: validity error : No declaration for element keep_partition_num <keep_partition_num config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:109: element filesystem_id: validity error : No declaration for attribute type of element filesystem_id <filesystem_id config:type="integer">131</filesystem_id> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:109: element filesystem_id: validity error : No declaration for element filesystem_id <filesystem_id config:type="integer">131</filesystem_id> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:118: element size: validity error : No declaration for attribute type of element size <size config:type="integer">100270081</size> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:119: element partition: validity error : Element partition content does not follow the DTD, expecting (create | crypt | crypt_fs | crypt_key | filesystem | format | fs_options | fstopt | grow | label | loop_fs | lv_name | lvm_group | maxsize | mount | mountby | noauto | partition_id | partition_nr | partition_type | raid_name | raid_options | raid_type | region | size | usepart)*, got (filesystem filesystem_id format mount partition_id partition_nr region size ) </partition> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:121: element filesystem_id: validity error : No declaration for attribute type of element filesystem_id <filesystem_id config:type="integer">142</filesystem_id> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:121: element filesystem_id: validity error : No declaration for element filesystem_id <filesystem_id config:type="integer">142</filesystem_id> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:129: element size: validity error : No declaration for attribute type of element size <size config:type="integer">72716697601</size> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:130: element partition: validity error : Element partition content does not follow the DTD, expecting (create | crypt | crypt_fs | crypt_key | filesystem | format | fs_options | fstopt | grow | label | loop_fs | lv_name | lvm_group | maxsize | mount | mountby | noauto | partition_id | partition_nr | partition_type | raid_name | raid_options | raid_type | region | size | usepart)*, got (filesystem_id lvm_group partition_id partition_nr region size ) </partition> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:133: element drive: validity error : Element drive content does not follow the DTD, expecting (device? , initialize? , is_lvm_vg? , partitions? , pesize? , use?), got (device keep_partition_fsys keep_partition_id keep_partition_num partitions use ) </drive> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:137: element keep_partition_fsys: validity error : No declaration for attribute type of element keep_partition_fsys <keep_partition_fsys config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:138: element keep_partition_id: validity error : No declaration for attribute type of element keep_partition_id <keep_partition_id config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:139: element keep_partition_num: validity error : No declaration for attribute type of element keep_partition_num <keep_partition_num config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:139: element keep_partition_num: validity error : No declaration for element keep_partition_num <keep_partition_num config:type="list"/> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:140: element lvm2: validity error : No declaration for element lvm2 <lvm2 config:type="boolean">true</lvm2> ^ /tmp/YaST2-15489-tNCLVw/valid.xml:217: element drive: validity error : Element drive content does not follow the DTD, expecting (device? , initialize? , is_lvm_vg? , partitions? , pesize? , use?), got (device is_lvm_vg keep_partition_fsys keep_partition_id keep_partition_num lvm2 partitions pesize use ) </drive> ^ What was wrong? This is the first thing i do with this system after the fresh installation. df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg00-lv_root 5.0G 162M 4.6G 4% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/cciss/c0d0p1 99M 8.2M 86M 9% /boot /dev/mapper/vg00-lv_home 1008M 33M 925M 4% /home /dev/mapper/vg00-lv_tmp 1008M 33M 925M 4% /tmp /dev/mapper/vg00-lv_usr 2.0G 613M 1.3G 32% /usr /dev/mapper/vg00-lv_var 2.0G 71M 1.8G 4% /var We have been using autoyast for about one year now. But it has never given us the impression of being in productive state. The dialogs to create a control file manually seem to be kinda unready, too. - The dialog inserts mount points for LVM, swap or md partitions by default and accepts them. - File -> new shows no impact - created a dummy partition maually without the crypt option being checked: <partition> <crypt>twofish256</crypt> ... I don't know the internals, perhaps I'm wrong, but.. maybe you can tell me - Configuring my partition setup after generating a reference file isn't possible. The left bar tells me sth about a table to the right. Unfortunately there is no table to the right - there is no problem, when start with an empty setup. Did you experience problems like this, too? I clouldn't find any patches up to now. Is there a way to tell yast to create a xml file on installation time, like kickstart? Thanks for your hints Matthias

3 8

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Daniel Fitzner 20 May '05

20 May '05

> hmm. Referring to: > http://yast.suse.com/autoinstall/sles8/html/invoking.html#Invoking.HTTP > > The MAC address feature was not in SLES8. Since > there were no rules either in > SLES8, at the moment the only chance for you that I > see is to configure your > dhcp server to send different IPs to different MAC > adresses. > So the questions is, why the MAC address feature is documented in http://yast.suse.com/autoinstall/sles8/autoyast2-sles8.pdf???? thx and best regards ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Daniel Fitzner 20 May '05

20 May '05

Hi, you are right, I changed this behaviour. Now the client makes also a get for default, but still not for the macadresse: 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET //SuSE/xml//C0A8D3A7 HTTP/1.1" 404 301 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0A8D3A HTTP/1.1" 404 299 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0A8D3 HTTP/1.1" 404 298 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0A8D HTTP/1.1" 404 297 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0A8 HTTP/1.1" 404 296 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0A HTTP/1.1" 404 295 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C0 HTTP/1.1" 404 294 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//C HTTP/1.1" 404 293 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml// HTTP/1.1" 403 296 "-" "-" 192.168.211.167 - - [20/May/2005:13:28:16 +0200] "GET /SuSE/xml//default HTTP/1.1" 404 299 "-" "-" thx and best regards --- Uwe Gansert <ug(a)suse.de> schrieb: > On Friday 20 May 2005 11:29, Daniel Fitzner wrote: > > > Here is the part of my accesslog (apache): > > > > [19/May/2005:14:04:33 +0200] "GET /SuSE/xml// > HTTP/1.1" 200 1288 "-" "-" > > I don't like this last line because it's a > successfull GET request. I guess > your webserver has answered with the index.html in > this case or with a > directory listing (depends on how your webserver is > configured). Delete the > index.html and/or don't allow directory listing. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 > Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: > +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

Re: [suse-autoinstall] SLES8 Retrieving Controlfile via http
by Daniel Fitzner 20 May '05

20 May '05

Hi Uwe, I have in my logfile only gets for the hexadecimal version of the client ip. But because I want to use the same ip for all clients at the first stage of the autoyast installation, I cannot differ the clients. So the macaddress would be a nice and only working feature. Here is the part of my accesslog (apache): 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET //SuSE/xml//C0A8D3A7 HTTP/1.1" 404 301 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0A8D3A HTTP/1.1" 404 299 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0A8D3 HTTP/1.1" 404 298 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0A8D HTTP/1.1" 404 297 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0A8 HTTP/1.1" 404 296 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0A HTTP/1.1" 404 295 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C0 HTTP/1.1" 404 294 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml//C HTTP/1.1" 404 293 "-" "-" 192.168.211.167 - - [19/May/2005:14:04:33 +0200] "GET /SuSE/xml// HTTP/1.1" 200 1288 "-" "-" thx and best regards --- Uwe Gansert <ug(a)suse.de> schrieb: > On Thursday 19 May 2005 16:48, Daniel Fitzner wrote: > > > I want to use the mac-feature, but I can see in > the logfiles from the > > webserver, that autoyast only tries the > hexadecimal presentation of the > > ipaddress and not the mac adress and also not the > file default. > > > > Has anyone the same experience?? > > Maybe you have a file like "C" or "C0" or something > like that in your document > root of the webserver? > If not, paste that part of the access.log please. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 > Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: > +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

RE: [suse-autoinstall] Network Installation Problems
by Paul Anthony Rae (QC/EMC) 19 May '05

19 May '05

Well I am still battling with this issue. I still get big red "Error in Installation" trying to do an autoinstall over the network. Possible issues: 1) I have no DNS server on my little private network where I am attempting the install. Is this a problem? 2) Control file validity checks out ok, but maybe there is something busted? What kinds of problems might lead to 'Error in Installation" just after control file download, assuming the control file is sane? Below is the last version of the control file I have been using. Any weirdnesses I am missing? Paul <?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> <runlevel> <default>3</default> </runlevel> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Pacific</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>ignore</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <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_type>primary</partition_type> <size>13.9GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>Swap</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">131</partition_id> <size>12GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/opt</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <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>Base-System</addon> <addon>YaST2</addon> </addons> <base>Minimal</base> </software> </install> </profile> -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 10, 2005 11:32 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

User Defined Partitioning
by Kai Streubel 19 May '05

19 May '05

Hello People, i am working with Suse AutoInstallation for a quite long time now, and i need a possibility to make user defined changes during autoinstall, especially for the partitioning. Is there a way to be asked for partioning instead of using the rules defined in the xml? Thank you, Kai

2 1

SLES8 Retrieving Controlfile via http
by Daniel Fitzner 19 May '05

19 May '05

Hello, according to the following documentation (http://yast.suse.com/autoinstall/sles8/autoyast2-sles8.pdf) about getting the controlfile : > If only the path prefix variable is defined, YaST2 will fetch the control file from the specified location in > the following way: >1. First, it will search for the control file using its own IP address in upper case hexadecimal, e.g. >192.0.2.91 -> C000025B. >2. If that file is not found, it will remove one hex digit and try again. This action is repeated till the >file with the correct name is found. Ultimately, it will try looking for a file with the MAC address >of the clients as the file name (mac should have the following syntax: 0080C8F6484C) and if not >found a file named default (in lower case). >As an example, for 192.0.2.91, the HTTP client will try: >C000025B >C000025 >C00002 >C0000 >C000 >C00 >C0 >C >0080C8F6484C >default I want to use the mac-feature, but I can see in the logfiles from the webserver, that autoyast only tries the hexadecimal presentation of the ipaddress and not the mac adress and also not the file default. Has anyone the same experience?? thx and best regards ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

2 1

Which you/yast files contain the Product description?
by Robert Cummins 19 May '05

19 May '05

I have a case where a machine is running SLES 9.0 and need to be updated. When I try to run yast2 then select "online update", there is no information about the architecture or product installed. Where does yast/you get that information?

1 0

disable abort button
by Lee Hartley 18 May '05

18 May '05

I need to keep users from interrupting the install. I would like to simply disable the abort button and ability to ctrl-atl-del during the install (unless some secret combo is pressed). I have seen posts for disabling consoles. I have not seen any info on disabling functionality in the graphical side. I would also be ok with locking the keyboard (with an unlock code for admins). I have seen that others are interested in this as well, but I have not found a solution. Any thoughts or pointers would be great. Even info on what controls these features in the install env.. Thanks!

1 0

PXE install on Fujitsu Siemens Scaleo T A64XP35 (fwd)
by Volkmar Glauche 17 May '05

17 May '05

... apologies for cross-posting this, but perhaps someone on this list can give some advice or has solved the problem below. ---------- Forwarded message ---------- Date: Tue, 10 May 2005 20:08:43 +0200 (CEST) From: Volkmar Glauche <volkmar.glauche(a)uniklinik-freiburg.de> To: suse-amd64(a)suse.com Subject: [suse-amd64] PXE install on Fujitsu Siemens Scaleo T A64XP35 Hi, I am trying to do a PXE install of SuSE Linux Professional on a Fujitsu Siemens Scaleo T A64XP35 box. However, it does seem to have problems initializing the network card after PXE. I have tried the following scenarios: 1) Boot from DVD with install=nfs://myserver/mydir. This works fine, the network card gets its IP over DHCP and starts the download. Yast detects the card as Asus CK804 (apparently using the forcedeth driver?). 2) Boot from the PXE PROM of the network card. This downloads the kernel (linux64 from the DVD) and initrd (initrd64 from DVD) and starts booting. The network card sends a DHCPDISCOVER 2 or 3 times, but does not answer the DHCPOFFER from the DHCP server. Thus it times out on mounting the installation source and I get into linuxrc. However, I did not have any luck to activate the network card manually, either. Any ideas? -- Volkmar Glauche - Department of Neurology volkmar.glauche(a)uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

3 4

Re: [suse-autoinstall] Custom CD for SLES9 x86_64
by Steffen Winterfeldt 17 May '05

17 May '05

Sorry for the late reply, I'm just back from vacation. On Sat, 30 Apr 2005, Bernhard Duebi wrote: > On Thu, 2005-04-28 at 10:17, Steffen Winterfeldt wrote: > > On Thu, 28 Apr 2005, Bernhard Duebi wrote: > > > > > 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 ? > > > > http://lists.suse.com/archive/suse-autoinstall/2005-Apr/0029.html > > sounds great, does it mean that I can create a CD which contains both > archs and the installer decides which packages to install ? Yes. But only with SL >= 9.2 (not SLES9). > If yes, is there a howto somewhere ? Not that I'm aware of. But on our 'normal' DVD it works this way: the bootloader appends '64' to the kernel and initrd names on 64-bit machines (if bit 4 is set in 'notice' in isolinux.cfg). You must ensure that initrd64 points to a 64-bit installation system (linuxrc.config has an entry in our initrd64 setting it to 'root64'). I think that's about all the black magic. Steffen

1 0

AutoYast DVD 32/64-Bit
by Petros.Stavrakakis＠br-automation.com 17 May '05

17 May '05

Hi, I'm using SuSE 9.3 on a 32bit-System. I have created an SuSE 9.3-AutoYast DVD with all the needed packages for 32bit and 64bit architectures. DVD was made with mkisofs and burned with k3b. The installation of the 32bit version is going fine. Everything is in place and working. The 64bit installation fails a the very beginning of the bootprocess of the DVD with the following text "Kernel panic - not syncing: No init found. Try passing init= option to kernel." The boot-directory on the AutoYast-DVD is the same as on the normal SuSE 9.3-DVD. Nothing except the isolinux.cfg was altered. I added "netsetup=0 instmode=cd autoyast=default" to the isolinux.cfg. Are there any special options for the mkisofs-command to make it work for the 64bit-Arch? I found out that in the bootlogo the names for "linux" and "initrd" will be changed to "linux64" and "initrd64" with a suffix-option. (gfxboot) I don't know why a normal SuSE 9.3-DVD boots and installs fine in 64bit and my DVD does not, although the relevant files are unchanged. Somebody a clue? Mit freundlichen Grüßen, Petros Stavrakakis APROL-Systemintegration email: petros.stavrakakis(a)br-automation.com Bernecker +Rainer Industrie-Elektronik GmbH Niederlassung Essen An der Reichsbank 8 D-45127 Essen Tel.:+49 (0) 201 74777 - 0 Fax: +49 (0) 201 74777 - 999 http://www.aprol.com http://www.br-automation.com ###################################### The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ######################################

2 1

S.O.S. Kiez! Polizei schlaegt Alarm
by MVIDNER＠suse.cz 15 May '05

15 May '05

Lese selbst: http://bz.berlin1.de/archiv/041115_pdf/BZ041115_004_GB2IG556.1.htm

1 0

Re: [suse-autoinstall] partitioning SuSE Professional 9.3 keep partition
by Uwe Gansert 13 May '05

13 May '05

On Thursday 12 May 2005 14:46, Hoepfner, Enrico wrote: > the result is: > > /dev/hda1 9.1 GB - Extended 0 19589 > /dev/hda5 3.1 GB - Linux swap swap 0 6529 > /dev/hda6 3.1 GB F Linux nativ (ext2) / 6530 13059 > /dev/hda7 3.1 GB - Linux nativ /data1 13060 19589 > > seams like the parameter <create config:type="boolean">false</create> is > ignored now. if you specify the size correctly, then the partitions keep alive, because they are not formated. At the moment, this is the only way I see. So, add the correct <size> statement for each partition maybe <region> instead of <size> is even better. Maybe there is a better way but I can't find it and I don't understand the partitioning code in autoyast. The partitioning code will be rewritten completely and I hope to get rid of the old code until SLES10. We will see. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

2 1

Re: [suse-autoinstall] partitioning SuSE Professional 9.3 keep partition
by Uwe Gansert 12 May '05

12 May '05

On Thursday 12 May 2005 13:16, Hoepfner, Enrico wrote: > what i want is only to keep the partition 7. all other partition I don't > care about - this mean, that partition 5 (swap) and 6 (/) can be use as > they are - they must not create only format. The following Config-File was > working on SuSE 9.2, what goes wrong in SuSE 9.3 ? I hope the following forces autoyast to use your partition plan. Please try to add: > <partitioning config:type="list"> > <drive> <initialize config:type="boolean">true</initialize> > <device>/dev/hda</device> > <partitions config:type="list"> > <partition> > <mount>swap</mount> > <create config:type="boolean">false</create> > <format config:type="boolean">true</format> > <partition_nr config:type="integer">5</partition_nr> > </partition> > <partition> > <mount>/</mount> > <create config:type="boolean">false</create> > <format config:type="boolean">true</format> > <partition_nr config:type="integer">6</partition_nr> > <filesystem>ext3</filesystem> > </partition> > <partition> > <mount>/data1</mount> > <create config:type="boolean">false</create> > <format config:type="boolean">false</format> > <partition_nr config:type="integer">7</partition_nr> > <filesystem>ext3</filesystem> > </partition> > </partitions> > </drive> > </partitioning> let me know what happens then. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

2 1

suse 9.2 ftp installation error
by Kai Zhang 12 May '05

12 May '05

Cannot read package data from installation media. Media Error? Im installing Linux suse 9.2 via FTP. I downloaded boot.ioi from and burned it into a CD. I've got ADSL and disabled firewall. The installation gets as far as the install settings page then i recieve the above Error. Any help would be greatley appreciated.

1 0

Re: [suse-autoinstall] partitioning SuSE Professional 9.3 keep partition
by m.frerichs 12 May '05

12 May '05

I failed with all tests depending on the following XML-File to leave the size of all 4 partitions and to format the primary filesystems /boot, / and swap and to keep data on partition /private . Tests: 1) <create config:type="boolean">true</create> for partition 1-3 2) <create config:type="boolean">false</create> for partitition 1-4 3) without line <create config: 4) <size>max</size> for partition 3 , / But always during " System fuer automatische Installation vorbereiten" a window is opened with text : "Fehler bei der Konfiguration der Partitionen" xmllint does not notice any syntax-errors. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> <profile xmlns ="http://www.suse.com/1.0/yast2ns""http://www.suse.com/1.0/configns"> .... <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">ext2</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <mount>/boot</mount> <size>auto</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <mount>/</mount> <size>10gb</size> </partition> <partition> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <mount>/private</mount> </partition> </partitions> <prefer_remove config:type="boolean">true</prefer_remove> <keep_partition_num>4</keep_partition_num> </drive> </partitioning> ..... The same test-machine is previously autoinstalled with 9.3 with 4 formatted partitions with the following XML-File: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <size>auto</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <size>10gb</size> </partition> <partition> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/private</mount> <size>max</size> </partition> </partitions> </drive> </partitioning> Thanks for your help! M.Frerichs xmlns:config=

1 0

Re: [suse-autoinstall] partitioning SuSE Professional 9.3 keep partition
by Hoepfner, Enrico 12 May '05

12 May '05

Hi, tanks for your help!! now i understand the problem i little bit more. but i can see how the problem is to solve. what i want is only to keep the partition 7. all other partition I don't care about - this mean, that partition 5 (swap) and 6 (/) can be use as they are - they must not create only format. The following Config-File was working on SuSE 9.2, what goes wrong in SuSE 9.3 ? <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <mount>swap</mount> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <partition_nr config:type="integer">5</partition_nr> </partition> <partition> <mount>/</mount> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <partition_nr config:type="integer">6</partition_nr> <filesystem>ext3</filesystem> </partition> <partition> <mount>/data1</mount> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <partition_nr config:type="integer">7</partition_nr> <filesystem>ext3</filesystem> </partition> </partitions> </drive> </partitioning> the result in SuSE 9.3 is: /dev/hda1 9.4 GB 0 19589 /dev/hda2 0.4 MB swap 19587 19587 /dev/hda3 0.4 MB F / 19588 19588 /dev/hda4 0.4 MB /data1 19589 19589 /dev/hda5 376.5 MB swap 0 764 /dev/hda6 5.0 GB 765 11171 /dev/hda7 4.0 GB 11172 19589 seams like the parameter <mount> or <partition_nr> is not used. Thanks enrico Uwe Gansert wrote: > On Thursday 12 May 2005 10:31, Hoepfner, Enrico wrote: > > please don't reply to me directly. Always use the list, so that the mails get > archived for google and other people who'll have the same problem in the > future. > > >>the result is: >> >>/dev/hda1 9.4 GB - Extended - 0 19586 >>/dev/hda7 4.0 GB - Linux nativ - 11172 19586 >>/dev/hda8 5.0 GB F Linux nativ / 0 10405 >>/dev/hda9 376.5 MB F Linux swap swap 10406 11171 >> >>nearly correct - only mount from partititon 7 to /data1 is missing. (this >>not realy a problem) > > > okay, I just talked to our Storage expert and this partitioning is not > possible. What we see above is simply broken but autoyast expects it to be > like that. So the reality and what autoyast thinks are no longer in sync. :( > > >>"Die Partition /dev/hda8 konnte nicht formatiert werden. ..." > > > yes, that's what we expect, since there is no hda8 > After deleting hda5 and hda6, the old hda7 is the new hda5 - we can't change > that behaviour. Autoyast seems not to know that and just adds partitions at > the end - that's a bug. > > >>after aborted installation the partition are all destroyed!!!! > > > sorry, I hope you had a backup :) > well, at the moment it looks like it's not possible to do what you want to do > (keep logical partition nr.7 but delete partition 5 and 6). It would have > been possible to delete the logical partition at the end but not some in > between. > > I will do heavy changes in the partitioning code in the near future together > with the storage expert here at SUSE. > -- --------------- enrico hoepfner (+49) 0711/811-49394 hoepfner(a)fli.sh.de.bosch.com Robert Bosch GmbH, Abt. CD/AEF, PSF 30 02 40, D-70442 Stuttgart -------------------------------------------------------------------------

1 0

Re: [suse-autoinstall] sles9-s390 autoyast
by Stefan Leippert 12 May '05

12 May '05

Did anybody try autoyast on an s390(x) on an lpar ? Any idea where I can pass the autoyast=-parameter ? Thank you. Stefan Uwe Gansert <ug(a)suse.de> 12.05.2005 10:42 To Stefan Leippert/Germany/IBM@IBMDE cc Subject Re: [suse-autoinstall] sles9-s390 autoyast On Thursday 12 May 2005 10:32, you wrote: > Thank you for your fast reply. please don't reply to me directly. Always reply to the list (that will be archived and so in the future, other people with the same problem might find the answer in the archive). > then you can add "autoyast=ftp://servername/profile_name.xml" to the > linuxrc parameter list (that's where you configured the "install=nfs://...." > > Where do I have to insert this parameters ? Into > (boot/loader/isolinux.cfg)? http or ftp is fine. the problem is, I don't know anything about s390 and so it might be, that the installation workflow is another than on an i586 system. On i586, if you boot a CD for example, you'll get a menue with a prompt where you can add kernel parameters, installation source and stuff like that. There you have to add the autoyast parameter to. I don't know where to do that on a s390 system. > > You can manipulate the installation source, if you want that, > > I think I have to do that, or is there another way to tell yast to look > for the controlfile at another location. well, I told you. Use http or ftp for the control file. The problem is, I don't know where you can pass the "autoyast=" parameter on a s390 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

1 0

partitioning SuSE Professional 9.3 keep partition
by Hoepfner, Enrico 12 May '05

12 May '05

Hi, I've a problem to keep a partition by a new installaiton with autoyast (SuSE Professional 9.3). There is a logical partition /dev/hda7 mounted on /data1 wich i want to keep with all data on it. The oether logical partitions /dev/hda5 + /dev/hda6 should use for "/" and "swap". The strange is that my XML-config did exactly what i want in SuSE 9.2 but not in SuSE 9.3. What i have, before installation: /dev/hda Partition Size Mount FS Type /dev/hda1 extended partition /dev/hda5 376mb swap swap logical partition /dev/hda6 5gb / ext3 logical partition /dev/hda7 xx /data1 ext3 logical partition What i want is the following: /dev/hda Partition Size Mount Format FS Type /dev/hda1 extended partition /dev/hda5 auto swap F swap logical partition /dev/hda6 5gb / F ext3 logical partition /dev/hda7 xx /data1 -- logical partition (KEEP) My XML-configuration looks so: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <mount>/data1</mount> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <partition_nr config:type="integer">7</partition_nr> <filesystem config:type="symbol">ext3</filesystem> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <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">6</partition_nr> <size>5gb</size> </partition> <partition> <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_nr config:type="integer">5</partition_nr> <size>auto</size> </partition> </partitions> <use>5,6</use> </drive> </partitioning> What i get ist: Device F Typ MountP /dev/hda1 extended /dev/hda2 Linux /data1 /dev/hda5 swap swap /dev/hda6 Linux /dev/hda7 Linux My Question: What have i get wrong? How can I configure what I want (also with SuSE 9.3)? thanks enrico

3 7

sles9-s390 autoyast
by Stefan Leippert 12 May '05

12 May '05

Hello ! I am trying to install SLES-9 s390 with autoyast from our local install server on zSeries. I read the manual and tried to get it work, but maybe there are some basic understanding problems: I have a control file (written in XML, made by yast2 and parsed ok) where all necessary data is stored in (IP-Adresses, DASD-IDs, Partitioning, Package Selection etc.) The control file is on our local FTP-Server. On our installation server there are only ISO-Files of the installation CDs, which are mounted loopback (incl. SP1...). A simple remote installation with ssh with ramdisk, yast etc. works fine. It is not possible to use a CD-ROM or floppy for the control file. But I can make changes to the iso-files. Which file on the ISOs have to be changed to get the system to load my control-file for autoinstallation? Thank you for your help ! Stefan

2 1

Problems finding autoinst.xml on floppy
by Thorbjorn Jemander 11 May '05

11 May '05

Hello, I'm new to suse and yast2/autoyast. I've got suse professional 9.3 and want to install that on a number of machines. I've created an autoinst.xml file (from using "yast2 autoyast") that I've put on a 3.5" floppy (MSDOS formatted). The autoinst.xml file passes xmllint without comments, and it looks OK. The floppy does not contain any info file. The problem: I put in the DVD and the floppy and boot. Apparantly, the autoinst.xml file should be detected automatically and turn the installation into an automated one. However, it does not detect the file (it's spelled correctly, I've checked several times). I can see that the disk drive flashes its LED during the first phase of the installation, so it looks like it's at least trying to read the floppy. It does not find it, or at least thinks that something is wrong with it, since it always proceeds to manual install. If I explicitly specify autoyast=floppy, or autoyast=floppy://autoinst.xml (in the first installation screen) it also tries to read the floppy, but then I end up in the ncurses installer where I get the message "Could not find the SUSE Linux Installation Source, Activating manual setup program". What does that mean? I've tried with two different floppy disks, so that it's not the disk that is broken. The disk drive is working under normal suse (KDE) operation, so it does not seem like that that is broken either. What am I doing wrong? - Is a MSDOS-formatted floppy disk OK? - Is the content of the autoinst.xml file wrong? The XML syntax seems to be fine, but how can I tell whether the installer thinks that the contents makes no sense? How can I verify that the *installer* thinks the autoinst.xml file is OK? - Do I need an info file on the floppy? - Can't I do this floppy autoinstallation with the factory SuSE 9.3 CDs/DVDs? The autoinst.xml file: ----------------------------------8<----------- <?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> <groups config:type="list"> <group> <groupname>video</groupname> <userlist>tsslab</userlist> </group> <group> <groupname>dialout</groupname> <userlist>tsslab</userlist> </group> </groups> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.0.255</broadcast> <device>eth0</device> <ipaddr>192.168.0.20</ipaddr> <name>Ethernet Network Card</name> <netmask>255.255.255.0</netmask> <network>192.168.0.0</network> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <runlevel> <default>5</default> <services config:type="list"> <service> <service_name></service_name> </service> </services> </runlevel> <scripts> <post-scripts config:type="list"> <script> <filename>postinstall</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[echo "Postinstallation script is running!"]]></source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>preinstall</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[echo "Preinstallation script is running!"]]></source> </script> </pre-scripts> </scripts> <user_defaults> <expire></expire> <group>100</group> <groups>video,dialout</groups> <home>/home</home> <inactive>-1</inactive> <shell>/bin/bash</shell> <skel>/etc/skel</skel> </user_defaults> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname>tsslab</fullname> <gid>100</gid> <home>/home/tsslab</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>$2a$05$CdvjoC.h6A5UWVx1hVXMzu/eI9CdA467wf4YX.LDWaUNuicm Z1Ss2</user_password> <username>tsslab</username> </user> </users> <x11> <color_depth config:type="integer">24</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">82</max_hsync> <max_vsync config:type="integer">75</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">58</min_vsync> </display> <monitor_device>1280X1024@75HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1280x1024</resolution> <window_manager>kde</window_manager> </x11> </configure> <install> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Stockholm</timezone> </clock> <keyboard> <keymap>swedish</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fs_options> <opt_format> <option_blank config:type="boolean">true</option_blank> <option_str>--format</option_str> <option_value>auto</option_value> </opt_format> <opt_hash> <option_blank config:type="boolean">true</option_blank> <option_str>--hash</option_str> <option_value>auto</option_value> </opt_hash> </fs_options> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>30000</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>500</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">130</partition_id> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <addons config:type="list"> <addon>Basis-Sound</addon> <addon>Kde-Desktop</addon> <addon>Min</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>default</base> <packages config:type="list"> <package>ddd</package> <package>ethereal</package> <package>ethtool</package> <package>ipgrab</package> <package>iptraf</package> <package>netboot</package> <package>nttcp</package> <package>perl-Net-Telnet</package> <package>rinetd</package> <package>tcpd-devel</package> <package>trafmon</package> </packages> </software> </install> </profile> --------------->8-------------------------------- ________________________________________________ Dr. Thorbjörn Jemander, Senior/RT Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)epact.se, +46 13 465 58 67, www.epact.com

4 6

Wrong URL for CD2 with installations over nfs
by mayrs＠RZ.FH-Augsburg.DE 11 May '05

11 May '05

Hi I tried to use autoyast for SLES9 over nfs. After I pass SLES CD1, CORE CD1 and reach CORE CD2 I get an error "Insert Media SUSE CORE Version 9 CD 2 ERROR(Media: not attached)". The given URL for the media is nfs://10.128.1.20/local/software/suse/SLES9//core-i386/CD2 The same error for cd 3,4,5 Where does this double-slash between SLES9 and core-i386 come from? Thanks, Stefan Mayr

1 0

SuSE 9.3 install with updates
by Volkmar Glauche 10 May '05

10 May '05

Hi all, I am trying to set up a NFS repository for autoinstall of SuSE Professional 9.3. Problems arise when I try to integrate the latest updates using the scripts create_update_source.sh and create_package_descr (Anas: create_update_source.sh as published on the web does only work correctly when started in the root directory of the installation source, otherwise it doesn't find the original EXTRA_PROV file). But this is not the main problem: after including the updates as described and running create_package_descr, some packages fail to install with md5 checksum and other errors (both updated and original packages). However, this does not seem to be reproducible: I installed an AMD64/64bit which failed first on glibc from the original sources. Then I installed a XEON/32bit, again failure on the glibc. However, the same XEON, installing 64bit now, did not fail at glibc, but at some later point. Both the original source and the updates seem to be ok themselves. NFS installation from the vanilla sources and updating from the updated rpms works. Has anyone seen something similar? Might this be an NFS related issue (no relevant error logs on the NFS server side, though)? I can provide y2logs from the last install in case they would help debugging. -- Volkmar Glauche - Department of Neurology volkmar.glauche(a)uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg

1 0

RE: [suse-autoinstall] Network Installation Problems
by Paul Anthony Rae (QC/EMC) 10 May '05

10 May '05

Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Re: [suse-autoinstall] Network Installation Problems
by Michael Marion 09 May '05

09 May '05

On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Re: [suse-autoinstall] Customizing Package Selection and Network Setting
by Michael Marion 09 May '05

09 May '05

On 9 May, Akira Ijuin wrote: > For example, yast/autoyast will automatically install a predefined > set of RPMs when Print Server support is selected. How does one go > about modifying this predefined set? I _think_ that you can edit the .sel files under the SLES (the SLES disk, not UL) directory, under suse/setup/descr then rerun the create_package_descr program to rebuild the descr files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Customizing Package Selection and Network Setting
by Akira Ijuin 09 May '05

09 May '05

Hi, Does anybody have information on doing the following things on autoyast? This is on SLES9 for x86_64. 1. Change the RPM packages that are installed when installing any given installation packages defined by yast/autoyast? For example, yast/autoyast will automatically install a predefined set of RPMs when Print Server support is selected. How does one go about modifying this predefined set? Similarly, a minimal install is done when no extra install packages are selected. How does one go about defining what gets installed during minimal install? 2. Force a network interface to full duplex during installation with autoyast? Also, how is this done during regular bootup from disk? During server startup the interface gets set to half duplex. How does one force it to be full duplex both from autoyast startup and regular machine bootup? I would appreciate any help on this. Please let me know if anything I've said is unclear. Regards, Akira

1 0

Network Installation Problems
by Paul Anthony Rae (QC/EMC) 09 May '05

09 May '05

Hi all, I am encountering a serious difficulty installing an HP DL-385 ProLiant using PXE boot and NFS source. I am trying to do an automatic, hands off installation of SuSE 9.0 Enterprise Server, but the installation fails everytime just after the server recovers the control.xml file from the boot server. The problem seems to be that it's trying to download "driverupdate" from the source directory, but no such file exists. After it can't find that file the Installation stops with "Error in Installation". >From what I have gleaned, "driverupdate" is included in Service Packs. However I am simply trying to install 9.0 with no service packs so how do I get past this difficulty? Any help appreciated, Paul Rae System Inegrator, MMS Ericsson Canada

1 0

Fwd: [suse-autoinstall] auto updating install tree
by Ashe Canvar 06 May '05

06 May '05

I am still not clear about the process of getting the updates from SuSe. 1. The command line (online_update) does not have any parameters for passing my portal username and password. 2. I don't want to use the GUI because I want to script this. 3. man online_update does not exist. -h is very little help either. 4. If I use the gui via YaST2 then the patches get downloaded in /var/lib/Yast2/you/blah.. This happens for the i386 architecture by default. How do I also do this for the x86_64 architecture ? (SLES9). 5. There do not seem to be too many rpms doenloaded after step 4. But a lot of patch-xxx files. What do I do with these ? 6. What do I do with .patch.rpm packages ? I am so confused that I would rather go back to freebsd and its awesome cvsup system. Any help would be appreciated esp with the command lines to get the updates and info on what parts of the downloaded tree to move into the updates folder created by Anas's script. Thanks! On 4/27/05, Ashe Canvar <acanvar(a)gmail.com> wrote: > Perfect. I got the script after some digging. Will let you know if this works. > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > On 4/24/05, Anas Nashif <nashif(a)suse.de> wrote: > > Hi, > > > > If you dont know it by now, there is a command line utility for YOU > > > > /usr/bin/online_update > > > > What you can do is download all updates (download only) to the server, > > create an update source with the script I have posted some weeks ago and > > copy the rpms to this new source and recreate the package database > > everytime something changes. All those steps can be automated using a > > smart script run by cron. > > > > Then you can install new machines with the new packages and without the > > need to run YOU afterwards... > > > > > > Anas > > > > Ashe Canvar wrote: > > > 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 2

Re: [suse-autoinstall] Re: failure notice
by Michael Marion 05 May '05

05 May '05

On 4 May, Joubert Berger wrote: > I also created a yast directory with two files: > /yast/order: > /core9/cd1 /core9/cd1 > > /yast/instorder: > /core9/cd1 You only need the first cd... I think you're making the installer think there are more trees of suse stuff under cd2, cd3, etc.. but if it knows core9/cd1 it's smart enough to look for cd2, cd3, etc on it's own. i.e. I have (for sles9): cornholio sles9 {623}$ ls SUSE-CORE-Version-9/ CD1 CD2 CD3 CD4 CD5 cornholio sles9 {626}$ ls SUSE-Updates/ content media.1 no updates cornholio sles9 {627}$ ls SUSE-SLES-Version-9/ CD1 cornholio sles9 {624}$ 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 {625}$ cat yast/instorder /SUSE-CORE-Version-9/CD1 /SUSE-Updates /SUSE-SLES-Version-9/CD1 I think, for each path you specify in order/instorder it'll look for a media.1 dir, content file, etc.. and it doesn't see those in your cd2, cd3, etc directories. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [The Quickie Mart was robbed, during the robbery Homer dove into the chips] Apu: "You can emerge now from my chips, the opportunity to prove yourself a hero is long gone." -- The Simpsons

1 0

Re: failure notice
by Joubert Berger 05 May '05

05 May '05

I am setting up an autoinstall environment so that I can autoinstall SuSe9.2. I copied all the ISO images to a directory and then created 5 directories and mounted the ISO images on those 5 directories. I have created symlinks in the root directory to boot, control.xml, content, and media.1 on cd1. I also created a yast directory with two files: /yast/order: /core9/cd1 /core9/cd1 /core9/cd2 /core9/cd2 /core9/cd3 /core9/cd3 /core9/cd4 /core9/cd4 /core9/cd5 /core9/cd5 /yast/instorder: /core9/cd1 /core9/cd2 /core9/cd3 /core9/cd4 /core9/cd5 So, I have something like this: /core9/cd1 /core9/cd2 /core9/cd3 /core9/cd4 /core9/cd5 /boot -> core9/cd1/boot /content -> core9/cd1/content /control.xml -> core9/cd1/control.xml /media.1 -> core9/cd1/media.1 /yast During the installation I eventually will get the error message: "Cannot read media description for /core9/cd2. Package from this media cannot be installed". It repeats this for cd3, cd4, and cd5. Any idea how I could get fix this error message? TIA, --joubert

1 0

Re: [suse-autoinstall] FAQs, autoyast, and auto updates
by Michael Marion 04 May '05

04 May '05

On 4 May, Robert Cummins wrote: > Please note that I need solutions for SuSE Pro-9.{0,1,2,3} and > SLES 9.0. For each release, download the updated rpms and create your own update paths in the install tree, and autoyast will install the updated versions automatically. Look in the archives of this list for many threads on this, i.e. subjs: [suse-autoinstall] Custom install source for yast in SLES9 [suse-autoinstall] How can I regularly update the install repository? etc. -- 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

FAQs, autoyast, and auto updates
by Robert Cummins 04 May '05

04 May '05

Hello, I hope someone on this list can either point me to a FAQ or answer my question. First let me explain what I'm doing in the hopes that my question will make complete sense. I install a base system, with autoyast, on a new machine I apply the updates I apply/build custom source rpms including kernel based modules I apply custom configurations I can do three of the four steps from autoyast but I'm having problems applying the updates. Does anyone out there have any experience with this? I can't use the YOU Automatic Mode Setup because I want this to happen right after the installation of the base system. I also need to be able to point to my own distribution as these machines are on a private wan that is not routed to the internet. Please note that I need solutions for SuSE Pro-9.{0,1,2,3} and SLES 9.0. TIA. R.

1 0

clone this server function in SLES9 SP1
by Harald Milz 04 May '05

04 May '05

Hi, I am trying to use the "Clone this server" function in SLES9 SP1 with a -147 kernel. Whenever I try to save the created XML file, I get the error "An error occured while saving the file" and no XML file is created. Is that a known problem, and how do I get around it? TIA! The Install Server function in SP1 is great, I set up an install server with SLES9 SP1 and SLES8 SP3 and 4 within half a day, a breeze. -- Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works.

2 1

Create DVD from Network Installation
by Robertson, Hill 03 May '05

03 May '05

I have a working network installation for SLES9 with SP1. I basically boot the PC with the SP1 CD and a floppy with an info file containing the info for the NFS autoinst.xml file and repository directory for the automatic installation. Everything works flawlessly. The network installation repository was build from the SLES9 CDs and SP1 CDs. Now, I need to do the same thing on a DVD. Is there any simple way to take the network repository and put it on a DVD with some minor changes where it will work installing from the DVD? Are there any info file parameters I need to specify or other tricks required? Everything I try gives me "Could not find the SUSE LINUX Enterprise Server 9 Installation Source - Activating manual setup program.". Then, I have to manually tell it to install from hard drive (not CD or DVD as you would expect) where I specify hda (the CD/DVD drive) and the directory for the repository and the install works. There must be one or two simple little things I am missing. Any ideas??? Thanks for any help....... - Hill

1 0

Lilo
by suse_list＠infineon.net 02 May '05

02 May '05

Hi, In our shop we are required to use Lilo as a boot loader, since some of the machines (IBM's) don't return the correct HD param (geometry) values to Grub. So my question is, does anyone know the what parameters/values/configs i need to add to the autoyast file to automatically select the first partition (drive like in grub) to auto-boot. Also how do i setup a timeout type value, so that it only shows the menu list for x number of seconds and then boots to the default partition as designated above. Please let me know Thanks Sascha

1 0

DVD Install
by Robertson, Hill 02 May '05

02 May '05

I need help please! I just need to create a SLES9 DVD from the CDs that I can autoinstall with a autoinst.xml control file. I need to include SP1 also. I would think this should be a simple thing to do but I can't seem to get it done. Is there a procedure (or scipt or something) that can show me specifically how to do this? See my post on Friday for more info. Any help would be GREATLY appreciated. Thanks, Hill

1 0