August 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

cannot use keyboard other than language
by Michal Kubecek 06 Oct '03

06 Oct '03

I have a problem with automatic installation of SuSE Linux 8.1 and 8.2. I need to select czech language but english (US) keyboard map. Generated XML file contains <keyboard> <keymap>english-us</keymap> </keyboard> <language>cs_CZ</language> but the system is installed with czech keyboard map anyway. Is there a way to use czech language but english-US keyboard map? Michal Kubecek

4 6

Keeping auto installs YOU-current
by Peets 31 Aug '03

31 Aug '03

I wonder if there is a way to set up an automatic YOU-style update of the packages to work with AutoYast. The idea is to keep the packages on the install server as current as possible, thus shortening the cycle of (1) install system with certain combination (2) patching it via auto YOU from the central mirror to get it up to date I would much rather update the non-critical stuff like desktop install sources directly (I'd be more careful with server builds ;-). Having run Auto YOU for over a year on a couple of test systems I have found the patch release process and quality good enough to trust. = P =

1 0

Re: [suse-autoinstall] Placing autoinst.xml onto the nfs-server?
by damien.selles＠eu.effem.com 29 Aug '03

29 Aug '03

Hi Kurt, I suggest you do two things: 1- in your info file change : AutoYaST:ftp://autoinst.xml to AutoYaST:ftp://XX.XX.XX.XX/autoinst.xml where XX.XX.XX.XX stands for the ftp server ip address. 2- You can either check dierctly by adding AutoYaST=ftp://XX.XX.XX.XX/autoinst.xml in your current command line . if your command line is; for example kernel (nd)/linux install=nfs://192.168.0.59/home/suse82/ ip=192.168.0.230 netmask=255.255.255.0 change it to : kernel (nd)/linux autoyast=ftp://XX.XX.XX.XX/autoinst.xml install=nfs://192.168.0.59/home/suse82/ ip=192.168.0.230 netmask=255.255.255.0 where XX.XX.XX.XX stands for the ftp server ip address. It works on my system. Best regards, Damien. --------------------------------------------------------------- Damien Selles Kurt Kronschnabl <k.kronschnabl(a)ica-intercom-akademie.de> ica-intercom-akademie.de 29/08/2003 14:06 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Placing autoinst.xml onto the nfs-server? Hi all, normally autoinst.xml resides on the floppy. In the autoyast docu I found the description of the info file. There is an entry which seems to describe the location of autoinst.xml file. I tried to put a line in "info" (which resides in the root on the floppy): AutoYaST:ftp://autoinst.xml A ftp deamon (vsftpd) is running on the server which allows an anonymous login. autoinst.xml will be presented in the ftp ano-root directory. I assume that the same IP-Adress will be used as for the nfs-Server because there is no field in the info file which allows me to provide a separate ftp IP-Adresss. When yast2 tried to locate the autoinst.xml file I get an interactive dialog which offers me to choose several. I can type in what I want (nfs, tftp) autoinst.xml will not be found. nfs is running ok, otherwise yast2 will not go so far. Who can help me please? Regards, Kurt -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Placing autoinst.xml onto the nfs-server?
by Kurt Kronschnabl 29 Aug '03

29 Aug '03

Hi all, normally autoinst.xml resides on the floppy. In the autoyast docu I found the description of the info file. There is an entry which seems to describe the location of autoinst.xml file. I tried to put a line in "info" (which resides in the root on the floppy): AutoYaST:ftp://autoinst.xml A ftp deamon (vsftpd) is running on the server which allows an anonymous login. autoinst.xml will be presented in the ftp ano-root directory. I assume that the same IP-Adress will be used as for the nfs-Server because there is no field in the info file which allows me to provide a separate ftp IP-Adresss. When yast2 tried to locate the autoinst.xml file I get an interactive dialog which offers me to choose several. I can type in what I want (nfs, tftp) autoinst.xml will not be found. nfs is running ok, otherwise yast2 will not go so far. Who can help me please? Regards, Kurt

1 0

Update SuSE 7.2 to 8.2 via YaST?
by Torsten Schlabach 28 Aug '03

28 Aug '03

Dear list, sorry if this question has been answered before, but I could not find any real answer on the achives. I have a SuSE 7.2 system and would like to upgrade to 8.2. Can I do this "online" just using YaST or YaST2? I do not have physical access to the system which is why I cannot boot from the 8.2 CD and upgrade "offline". Extra question: If this is not possible: What would be the difference between updating or manually updating the kernel and updating all packages via YaST? Torsten

2 1

update kernel customised boot cd
by Berge, Harry ten 28 Aug '03

28 Aug '03

Hi, I've created a customised bootable cd that starts an autoyast installation procedure. Is it possible to update the kernel (image) that is used when booting from the installation cd? > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test Engineer HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

RE: [suse-autoinstall] textmode was: Re: partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Theytaz Antoine 27 Aug '03

27 Aug '03

cheers ! -----Message d'origine----- De : Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de] Envoyé : mercredi 27 août 2003 16:23 À : suse-autoinstall(a)suse.com Objet : Re: [suse-autoinstall] textmode was: Re: partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE I got it!!! It's only nessecary to put a info fileon the grub floppy with the single line "textmode:1", then it works: yast2 runs in ncursesmode!! Thank you for all the input! Regards, Kurt -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

autoinstall from CD (SuSE 8.2) grub problem (wrong/missing gfxmenu line)
by Holger Rauch 27 Aug '03

27 Aug '03

Hi! I'm using the current autoyast2 (2.7.19) on a SuSE 8.2 Professional system. The problem I got is that the gfxmenu line for grub offered by autoyast2 is syntactically wrong. It looks like gfxmenu (hd0,5)hd0,5)/boot/message ^^^^^^ here's the error The partition (hd0,5) itself is correct, but I can't think of any reason why the redundant stuff, leading to a syntactically incorrect line, is in here. Sure, I can click on "Booting" and manually edit the line so that it's correct and gets included in the grub config of the installed system, but that's kind of awkward. If I don't edit the line and instead leave it as it is, it won't be included in the menu.lst file and I will thus have a textual boot menu instead of the desired GUI one. My question thus is: Why does this happen and how can I prevent it from happening again during future autoyast2 install sessions? Thanks in advance for any info/suggestions! Below you'll find my autoinst.xml file which, apart from the issue just mentioned, works flawlessly: ----------------------------------------------------------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "autoyast-dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <domain>local</domain> <hostname>servunit</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto></bootproto> <device>eth0</device> <ipaddr>192.168.0.1</ipaddr> <netmask>255.255.255.0</netmask> <startmode>onboot</startmode> </interface> </interfaces>  </networking>  <scripts> <post-scripts config:type="list"> <script> <filename>txspost.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh # run txs support script cd /opt/txs-support/install ./install.sh # insserv aladdin insserv /etc/init.d/aladdin # mark device with MBR as bootable sfdisk -A1 $(grep " / " /etc/fstab | awk '{print $1}' | sed 's/[0-9]//') # reboot system #reboot ]]> </source> </script> </post-scripts> </scripts> <security> <console_shutdown>ignore</console_shutdown> <displaymanager_remote_access>yes</displaymanager_remote_access> <gid_min>500</gid_min> <kdm_shutdown>root</kdm_shutdown> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>easy</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <uid_min>500</uid_min> </security> <users config:type="list"> <user> <username>root</username> <user_password>6efyaD43bst2Q</user_password> <encrypted config:type="yes">true</encrypted> </user> </users> <x11> <color_depth config:type="integer">16</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> <height config:type="integer">1024</height> <max_hsync config:type="integer">80</max_hsync> <max_vsync config:type="integer">75</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">50</min_vsync> <width config:type="integer">1280</width> </display> <monitor_device>1280X1024@75HZ</monitor_device> <monitor_vendor> VESA</monitor_vendor> </monitor> <resolution>1280x1024</resolution> <start_x11 config:type="boolean">true</start_x11> </x11> </configure> <install> <bootloader> <activate config:type="boolean">true</activate> <location>mbr</location> </bootloader> <general> <clock> <hwclock>UTC</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">true</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>probe</id> </mouse> </general> <partitioning config:type="list"> <drive> <device></device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="swap"></filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <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">10</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="">10</timeout> </warnings> </report> <software> <base>TXS</base> <packages config:type="list"> <package>aladdin</package> <package>txs-support</package> </packages> </software> </install> </profile> ----------------------------------------------------------------------- Greetings, Holger

1 0

RE: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Theytaz Antoine 27 Aug '03

27 Aug '03

I think the correct line is : Textmode: 1 You have to put this line in the 'info' file on the floppy, whenever you use it... Antoine -----Message d'origine----- De : Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de] Envoyé : mercredi, 27. août 2003 14:53 À : suse-autoinstall(a)suse.com Objet : Re: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE Berge, Harry ten schrieb: > > >>-----Original Message----- >>From: Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de] >>Sent: Wednesday, August 27, 2003 2:31 PM >>To: suse-autoinstall(a)suse.com >>Subject: Re: [suse-autoinstall] partition problems with >>AutoYast / boot >>pr oblems with Intel onboard pro/100 VE >> >> >> >>chapter 4.10, page 29 :-) > >>Succes! > >Perfect! The script is part of autoinst.xml All clear! > Perhaps you know another miracle: Where should I put the "textmode=1" command for yast2 to avoid long X11 startup times? The manual (yes, I read this section! :=)) explains to put it on the yast2 command line. But I have no access to the command line. Regards, Kurt > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

Re: [suse-autoinstall] textmode was: Re: partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Kurt Kronschnabl 27 Aug '03

27 Aug '03

I got it!!! It's only nessecary to put a info fileon the grub floppy with the single line "textmode:1", then it works: yast2 runs in ncursesmode!! Thank you for all the input! Regards, Kurt

1 0

Re: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Kurt Kronschnabl 27 Aug '03

27 Aug '03

Berge, Harry ten schrieb: > > >>-----Original Message----- >>From: Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de] >>Sent: Wednesday, August 27, 2003 2:31 PM >>To: suse-autoinstall(a)suse.com >>Subject: Re: [suse-autoinstall] partition problems with >>AutoYast / boot >>pr oblems with Intel onboard pro/100 VE >> >> >> >>chapter 4.10, page 29 :-) > >>Succes! > >Perfect! The script is part of autoinst.xml All clear! > Perhaps you know another miracle: Where should I put the "textmode=1" command for yast2 to avoid long X11 startup times? The manual (yes, I read this section! :=)) explains to put it on the yast2 command line. But I have no access to the command line. Regards, Kurt > >

2 2

Re: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Kurt Kronschnabl 27 Aug '03

27 Aug '03

> > >>Yes you have. Using the command line of isolinux (the boot image of the SuSE >>dvd/cd.). All parameters that are not used by isolinux/linuxrc are given to >>yast. > >So I don't know if you are using a customised dvd or cd, but ifso you can >put 'textmode=1' into the isolinux.cfg file that is located in /boot/loader >on the dvd/cd. >Regards Harry For the cd-boot Methode it's good to know. Perhaps I'll switch later from Floppy to CD Booting. But now I load the kernel via floppy tftp grub and the rest will be loaded via nfs. The nfs "share" is a directory in which I have copied in all the 5 Suse 8.2 CDs. >As far I understood linuxrc will be used only when a CD based install Methode is used. Or can it "activated" using the floppy methode as well? > Regards, Kurt

1 0

I'm new on this list
by Michael Binder 27 Aug '03

27 Aug '03

Hi, I'm new on this list. I'm blind - so I think autoyast is the best way for me to install linux. I'm looking for a simple example xml-stream for a SuSE 8.2 to install it on a i386 Hardware. A friend (he is also blind) gave me an example but it doesn't run with SuSE 8.2 but it runs with SuSE 8.1. please send me a xml stream that runs on your system. thanks. Michael

2 2

Re: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Kurt Kronschnabl 27 Aug '03

27 Aug '03

Berge, Harry ten schrieb: >>-----Original Message----- >>From: Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de] >>Sent: Wednesday, August 27, 2003 1:19 PM >>To: suse-autoinstall(a)suse.com >>Subject: [suse-autoinstall] partition problems with AutoYast / boot pr >>oblems with Intel onboard pro/100 VE >> >> >> >>Do you have the documentation from AutoYast? It is clearly described with >>some examples. I don't have 'real-life' examples, but they are in the >>manual. > Yes, I have it, but not yet discovered this section. I'll have a closer look right now, thanks a lot! > >Hope this will get you started! Sure, it will! Regards, Kurt > >

1 0

partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Kurt Kronschnabl 27 Aug '03

27 Aug '03

>Message-ID: <8C6ADF4772B7D511A3E40008C7BB878A014E55DB(a)chopin.hitt.nl> >From: "Berge, Harry ten" <berge(a)hitt.nl> >Date: Wed, 27 Aug 2003 07:47:32 +0200 >Subject: RE: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE >Maybe I have an answer to your first question: > > >AFAIK the autoinstaller will create new partitions at the END of the disk. > You mention that you have already 2 partitions at the end of the disk.... > A possible solution is to do the partitioning yourself in a script and leave >the disk untouched by the autoinstaller. > >Regards Harry Hi Harry, I am Kurt, a Team member together with Ralf. You are right, our existing partitons are at the END! I thought at the end they are sure enough for creating new ones through autoyast. :=) Could you please give me a hint where I can place and call the mentioned selfmade script inside the autoyast process? Regards, Kurt

1 0

problem loading initrd....
by damien.selles＠eu.effem.com 27 Aug '03

27 Aug '03

Hi all, I m trying to perform yast autoinstallation via nfs .. but booting on a SINGLE floppy... (mandatory requierments) What should I add to the bootdisk so that it would be able to get it initial ramdisk via nfs? Is there a way to get initrd from the network? If not, has anybody ever succeed in stripping initrd down to 350 ko and add it to the bootdisk? Has anybody ever experienced performing autoinstallation with only one floppy and the network? moreover, despite different readings i had, i m not sure to be clear on the interactions between the initrd ramdisk and the root ramdisk could anybody give me some explanations? Thanks in advance, --------------------------------------------------------------- Damien Selles

2 1

Re: [suse-autoinstall] boot partition beyond 1024 cylinders
by Thomas Mack 27 Aug '03

27 Aug '03

>Hi, >Do you have install/mode/confirm set to true by any chance! This check >is only in confirmation mode, it should not happen if it is set to false. > Well, I have set install/general/mode/confirm to false - is there a difference to install/mode/confirm? Thomas Mack TU Braunschweig, Abt. Informationssysteme

2 1

boot partition beyond 1024 cylinders
by Thomas Mack 27 Aug '03

27 Aug '03

Hi! When trying to keep an existing Windows partition on hda1, we encounter a message to be manually clicked away that the boot partition is beyond cylinder 1024 ("so it cannot boot", but that is not a problem). So we cannot really autoinstall these machines so far: is there any solution to it available? <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> <use>2,3,4,5,6,7</use> </drive> </partitioning> Thomas Mack TU Braunschweig, Abt. Informationssysteme

2 1

autoyast supported for ppc64?
by Joachim Jordan 27 Aug '03

27 Aug '03

Hello, i'm trying to set up a autoyast installation for pBlades and i get some problems. First question: Is yaboot supported in autoyast? It is supported in the normal Yast2 of the ppc64 distribution... Second question: How to i enforce that a partitions is a primary partition? In the documentation it says it should be possible by using partition_id, but i did not found any hint which value to use. 130? 5?, 131 seems to be logical drive... I also get a problem with partitioning if there are some partitions from a previous run... Best regards, Joachim Jordan Linux IT Architect, EMEA Linux Center of Competence IBM Laboratories, Dept.3300, Schoenaicherstr.220, D 71032 Boeblingen, Germany Sametime/e-mail: jordanj(a)de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232

2 1

partition problems with AutoYast / boot problems with Intel onboard pro/100 VE
by Ralf.Pichler＠t-online.de 27 Aug '03

27 Aug '03

Hello Ansa, I am new on the AutoYast mailinglist and today i want to contact you with following problem: goal is to autoinstall SUSE 8.2 in a 3GB primary ext2 partition for "/" and 300 MB for an additonal 300MB swap (as primary) keeping the already existing logical 300 MB swap and 2500MB ext2 at the end of the harddisk. I use a grub bootfloppy with the image from your website. It loads the kernel via tftp and makes the rest via nfs. Yast2 starts and reads the autoinst.xml. Result: No space left on Harddisk. I made the section "region_entry config" by hand based on a start autoinst from yast2. To create the two additional partitions with parted is no problem, but yast2 has problems to do this. What could be the reason? My second problem is when booting with a compiled grub bootloader from floppy on a second PC. Here I build grub from the spec file with the option "--enable-eepro100" for supporting an Intel 82801 BD PRO/100 VE onboard network card. When booting with this floppy, the module EEPRO100 can't be loaded. Did I enable the correct network device in the spec file or which is the right one? With regards and thanks for your affords, Ralf Pichler -- ________________________________ Ralf Pichler Gräfelfinger Straße 151 81375 München phone: +49-89-74 02 93 45 mobil: +49-170-90 80 44 3 email: ralf.pichler(a)t-online.de

2 1

RE: [suse-autoinstall] partition problems with AutoYast / boot pr oblems with Intel onboard pro/100 VE
by Berge, Harry ten 27 Aug '03

27 Aug '03

Maybe I have an answer to your first question: AFAIK the autoinstaller will create new partitions at the END of the disk. You mention that you have already 2 partitions at the end of the disk.... A possible solution is to do the partitioning yourself in a script and leave the disk untouched by the autoinstaller. Regards Harry > -----Original Message----- > From: Ralf.Pichler(a)t-online.de [SMTP:Ralf.Pichler@t-online.de] > Sent: Tuesday, August 26, 2003 10:38 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] partition problems with AutoYast / boot > problems with Intel onboard pro/100 VE > > Hello Ansa, > > I am new on the AutoYast mailinglist and today i want to contact you > with following problem: > > goal is to autoinstall SUSE 8.2 in a 3GB primary ext2 partition for "/" > and 300 MB for an additonal 300MB swap (as primary) keeping the already > existing logical 300 MB swap and 2500MB ext2 at the end of the harddisk. > > I use a grub bootfloppy with the image from your website. It loads the > kernel via tftp and makes the rest via nfs. Yast2 starts and reads the > autoinst.xml. > > Result: No space left on Harddisk. > > I made the section "region_entry config" by hand based on a start > autoinst from yast2. > > To create the two additional partitions with parted is no problem, but > yast2 has problems to do this. > > What could be the reason? > > My second problem is when booting with a compiled grub bootloader from > floppy on a second PC. Here I build grub from the spec file with the > option "--enable-eepro100" for supporting an Intel 82801 BD PRO/100 VE > onboard network card. When booting with this floppy, the module EEPRO100 > can't be loaded. > Did I enable the correct network device in the spec file or which is the > right one? > > > With regards and thanks for your affords, > > Ralf Pichler > -- > ________________________________ > Ralf Pichler > Gräfelfinger Straße 151 > 81375 München > > phone: +49-89-74 02 93 45 > mobil: +49-170-90 80 44 3 > email: ralf.pichler(a)t-online.de > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Additional package not in ISO-image, updated also
by silverio.santos＠equant.com 25 Aug '03

25 Aug '03

That was it! Thanks Silvério Santos Richard Bos <radoeka(a)xs4all.nl> 19.08.2003 13:08 To: suse-autoinstall(a)suse.com Please respond to richard.bos cc: bcc: Subject: Re: [suse-autoinstall] Additional package not in ISO-image, updated also Op dinsdag 19 augustus 2003 10:27, schreef silverio.santos(a)equant.com: > Hi, > > I found a strange behaviour of AutoInstall regarding addition and update of > RPMs, which have not been in the original distribution. > > Completing what I wrote below, packages are not prepared for > CD-image-creation, when: > - I copy a freshly downloaded and updated package, deleting the original > one (happened to autoyast2-installation) > - I add any new RPM to the respective architecture folder (e.g. i386) > Of course the create_package_descr is run after every change. > > Does anybody know how AutoInst compiles the list of files to prepare for > CD-creation and if any, where the (temporary) file is located? I would like > to learn more how AutoInst works, to understamd why it is unable to behave > the expected way. > > Silvério Santos What happens if you remove and re-add the Software source (in yast). Normally yast uses some kind of caching... -- Richard Bos Without a home the journey is endless -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Manual remote installation
by Christian Tröster 23 Aug '03

23 Aug '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I want to install a new SuSE to a server with remote access only. There are already 3 partitions (hda1 to 3) which I want to be untouched and a fourth partition hda4 to which the installation shoud go. The existing partitions hold the 'old' setup on hda1 and hda3 and a swap partition on hda2. For the setup I have remote access to to server through ssh only and a possibility to force a reboot via a web interface. My plan was to copy the /boot-Directory of the first SuSE cd to the new partition. Setup a new lilo entry for <mount point>/boot/loader/linux with several kernel parameters so I can gain ssh access and start a manual installation as if I was in front of the server. Unfortunatelly it didn't work :) I tried to setup everything as described in http://sdb.suse.de/en/sdb/html/remote_install.htm locally with two other computers to see how far I would come. But in spite of the supplied kernel parameters linuxrc still required someone pressing enter at the 'server'. I didn't figure out why, but i didn't work. The lilo entry was as follows. Perhaps it helps or someone could find an error. > image=/mnt/hda4/boot/loader/linux > label=suse_cdrom > ramdisk=65536 > initrd=/mnt/hda4/boot/loader/initrd > root=/dev/hda4 > append="showopts manual=1 usessh=1 sshpassword=password acpi=off > ip=192.168.0.42 netmask=255.255.255.0 insmod=8139too" Is it possible to perform a manual setup this way and if not could autoyast help? It would be nice if someone could give me a few hints. TIA. Bye, Christian - -- | mailto:c.troester@gmx.de | http://www.fen-net.de/~na2929 | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/R+8uCXo2j/oAbHQRAqznAJ9IlmuWmHEg9mIDCMxEWrD83NyQewCfeB6j Kp8ROMeoafAcA369g/GN8Yo= =mkjw -----END PGP SIGNATURE-----

1 0

Problems while partitioning
by Michael Binder 22 Aug '03

22 Aug '03

Hi, Im new on this list and not very well informed about autoyast. My problem is that a xml-stream that runs with SuSE 8.1 without any problems doesn't run with SuSE 8.2. it aborts at partitioning! any idea? thanks, Michael

1 0

Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

Greetings, I had a couple of questions I'm wrestling with right now. 1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation? 2. When I use AutoYaST with a control file, as the system gets to the point that it will read the control file, it goes through and looks at hardware, and loads what modules it needs to. So, I was wondering if it was possible to PREVENT a specific module from loading? I have found that when I have a Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a QLogic driver, and a Megaraid driver, which is a problem, since they are the same card. My workaround at the moment is to run a manual setup, answering yes/no to whichever modules to load. This defeats the purpose of having a hands-off autoinstallation routine. Any thoughts? Thank you! -p Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam(a)fhcrc.org

3 2

RE: [suse-autoinstall] Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

Sorry. This is SuSE 8.2 ftp version. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, August 21, 2003 8:52 AM To: Hirayama, Pat Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Two Questions What version are you installing, SLES or 8.2? Anas Hirayama, Pat wrote: > That doesn't appear to help, as the setup program seems to want to load the > other module regardless. So, it just locks the system up a little faster. > > -p > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Wednesday, August 20, 2003 7:02 PM > To: Hirayama, Pat > Cc: suse-autoinstall(a)lists.suse.com > Subject: Re: [suse-autoinstall] Two Questions > > Hirayama, Pat wrote: > <<snip>> > >>2. When I use AutoYaST with a control file, as the system gets to the > > point > >>that it will read the control file, it goes through and looks at hardware, >>and loads what modules it needs to. So, I was wondering if it was > > possible > >>to PREVENT a specific module from loading? I have found that when I have > > a > >>Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a >>QLogic driver, and a Megaraid driver, which is a problem, since they are > > the > >>same card. My workaround at the moment is to run a manual setup, > > answering > >>yes/no to whichever modules to load. This defeats the purpose of having a >>hands-off autoinstallation routine. Any thoughts? >> > > > What about loading the right module before yast2 even starts with > insmod=<module name> as a kernel parameter, would this help? > > Anas > > >>Thank you! >> >> -p >> >> >>Pat Hirayama >>IT / Server Operations >>Fred Hutchinson Cancer Research Center >>phirayam(a)fhcrc.org >> >> > > > >

1 0

RE: [suse-autoinstall] Two Questions
by Hirayama, Pat 21 Aug '03

21 Aug '03

That doesn't appear to help, as the setup program seems to want to load the other module regardless. So, it just locks the system up a little faster. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, August 20, 2003 7:02 PM To: Hirayama, Pat Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Two Questions Hirayama, Pat wrote: <<snip>> > > 2. When I use AutoYaST with a control file, as the system gets to the point > that it will read the control file, it goes through and looks at hardware, > and loads what modules it needs to. So, I was wondering if it was possible > to PREVENT a specific module from loading? I have found that when I have a > Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a > QLogic driver, and a Megaraid driver, which is a problem, since they are the > same card. My workaround at the moment is to run a manual setup, answering > yes/no to whichever modules to load. This defeats the purpose of having a > hands-off autoinstallation routine. Any thoughts? > What about loading the right module before yast2 even starts with insmod=<module name> as a kernel parameter, would this help? Anas > Thank you! > > -p > > > Pat Hirayama > IT / Server Operations > Fred Hutchinson Cancer Research Center > phirayam(a)fhcrc.org > >

2 1

Bootlogo
by Robison, Jonathon (M.) 21 Aug '03

21 Aug '03

The bootlogo file in /boot/loader - anyone know what graphic format that is? I'd like to replace it with a company logo. I know the gfxboot needs gfx-devel package, and I've succeeded in altering that, but I am having trouble with bootlogo. -jmr

1 0

Where are my partitions ?
by Alexander Luedtke 21 Aug '03

21 Aug '03

Hi folks, I'm trying to use autoyast, nearly everything works, at the moment I've only one problem: I want three partitions /dev/hda1 - swap 256 MB /dev/hda2 / reiserfs 25 GB /dev/hda3 /export - rest of drive what I get is that the swap partition is using the hole hda drive (eg. 76 GB !) here is my config: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>+256M</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+25GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/export</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Can anybody help me ? greetings Alex -- Alexander Lüdtke Systemadministrator Adresse: TUM - Garching Boltzmannstr. 3 85747 Garching b. München Lehrstuhl: Frau Prof. Feldmann Zimmer: 01.08.036 Tel: ++49 (89) 289 - 18039

2 1

RE: [suse-autoinstall] Switching from floppies to disk
by Robison, Jonathon (M.) 20 Aug '03

20 Aug '03

What about the info file? I want to enforce the load structure, thus I have to have different CD's with different info files pointing to different xml files. i.e. one info file points to "laptop_developer.xml". Another points to "laptop_user.xml" etc. etc. Those xml files also have a lot of embedded scripts and config files to set up our krb5 authentication as well as the pam_mount login mounting system. I can't let user's do a "normal, choose what you want" install. For developers, I hand them the CD with the info file for developers. Users get the CD with the info file pointing to the regular user.xml. At least that's what I planned on doing. What I am hoping for is someone to tell me "edit these files ... put everything in from all 5 floppies into one subdirectory somewhere . . . now run mkisofs with these switches . . . burn the iso to CD." Or am I misunderstanding how this all works? (It wouldn't be the first time) --Jonathon -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wed 8/20/2003 12:11 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] Switching from floppies to disk Robison, Jonathon (M.) wrote: > I have created an install server, and the necessary floppies (1 boot, > 4 module). The info file is working on the module1 floppy, and > installing from the http server, as desired. > > Can someone guide me on what I would need to do to combine all of > these floppies into one image? I have some of those "Business Card" > CD's, capable of holding 50M. If you have this, then there is no need to create floppies at all, just create a bootable CD using the kernel and initrd available on the first CD in "boot/loader". Anas

3 2

Switching from floppies to disk
by Robison, Jonathon (M.) 20 Aug '03

20 Aug '03

I have created an install server, and the necessary floppies (1 boot, 4 module). The info file is working on the module1 floppy, and installing from the http server, as desired. Can someone guide me on what I would need to do to combine all of these floppies into one image? I have some of those "Business Card" CD's, capable of holding 50M. Each floppy has a module.config that tells it "for more network cards, see floppy 2" etc, so I know those files would need edited somehow, I'm just not sure how. I also don't know what other files might need edited. The end result I want is to hand out these small CD's that people can boot from and their system will perform the same network install as if I handed them the 5 floppies. --Jon Robison

2 1

managing classes under SLES8...
by damien.selles＠eu.effem.com 20 Aug '03

20 Aug '03

Hi, reading the archive of last june, I found this article : http://lists.suse.com/archive/suse-autoinstall/2003-Jun/0025.html talking about classes under SUSE 8.2... does it also work under SLES8 . I m trying to do that : ... <install> <classes config:type="list"> <class> <class_name>location</class_name> <configuration>home.xml</configuration> </class> </classes> ... .. </install> but it does not seem to work.... Am I wrong or does autoyast version of SLES8 refuse the merging of the fly of the config file? Regards. Damien Selles

1 0

Problems with ip addresses using dhcpd and tftpd
by Markus Klimke 20 Aug '03

20 Aug '03

Hi there, I'm running a dhcpd to give an installing client an IP and to say it where the tftp is. Every client has a fixed address. My problem is, that, every time the client starts up, he gets an IP. Surely he should do this, but if it reboots after an installation... he installs again. That's not fine ;-) Do anyone know how to tell the dhcpd to only use an IP once? Next problem is, that I want to read out the overgiven IP address by the dhcpd. But if I do an `ifconfig' on client side, eth0 has no IP. Also I want to reuse the hostname statically, but there is none. Any hints? Thanks in advance, Markus

1 0

output of autoyast
by george_king 20 Aug '03

20 Aug '03

Does autoyast print its output to /dev/console? I tested autoyast in two cases: Firstly, I gave the kernel parameters "console=tty1,console=ttyS0". As the kernel document, kernel would assign /dev/ttyS0 as /dev/console. The autoyast printed the output on ttyS0. Secondly, I gave the kernel parameters "console=ttyS0,console=tty1". In this cases, /dev/console should be /dev/tty1. But the autoyast still printed the output on ttyS0. Who can tell me why?

1 0

Additional package not in ISO-image, updated also
by silverio.santos＠equant.com 19 Aug '03

19 Aug '03

Hi, I found a strange behaviour of AutoInstall regarding addition and update of RPMs, which have not been in the original distribution. Completing what I wrote below, packages are not prepared for CD-image-creation, when: - I copy a freshly downloaded and updated package, deleting the original one (happened to autoyast2-installation) - I add any new RPM to the respective architecture folder (e.g. i386) Of course the create_package_descr is run after every change. Does anybody know how AutoInst compiles the list of files to prepare for CD-creation and if any, where the (temporary) file is located? I would like to learn more how AutoInst works, to understamd why it is unable to behave the expected way. Silvério Santos ----- Forwarded by Silverio SANTOS/Germany/Equant on 19.08.2003 10:16 ----- To: suse-autoinstall(a)suse.com Silverio SANTOS cc: 28.07.2003 11:46 bcc: Subject: Additional package not in ISO-image Hi, I added an additional package into a newly created i386-folder and have run the create_package_descr as described. The package identifies itself as i386-arch. The problem is that the file is not added to the ISO-image, from which I would like to install the target-system. I found that an earlier version of the package that I created (compiled and packaged) on this system is found in every packages-file that has been created by create_package_descr. That means that there is the same package with 2 different version numbers in the packages files. Is this the cause for the malfunction? How can I get the additional package integrated into the ISO-file? Thanks Silvério Santos

2 1

kernel update [AGAIN]
by Berge, Harry ten 19 Aug '03

19 Aug '03

Hi, I've a customised bootable SuSE cd (8.2). Is it possible to update the kernel that is used by the initial installation process? > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test Engineer HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

"Abandon all changes" dialog locks YaST
by Timo C. Nentwig 16 Aug '03

16 Aug '03

Hi! Everytime I want to quit (or use..) YaST it opens the "Abandon all changes" dialog - without any reason at all. No matter whether I acknoledge or refuse (ok, cancel), the window opens again. So, to put it simply YaST is no more usable. What can I do about that?

1 0

NFS install w/ static IP
by Debbie Velarde 14 Aug '03

14 Aug '03

Hi Everyone, I'm trying to setup an NFS autoinstall using a static IP where my autoinst.xml and info files are on the NFS server instead of the floppy. My NFS install is successful when autoinst.xml and info are on a floppy. What would I need to do to in order to be able to have those files on my NFS server instead of a floppy and not use dhcp? Thanks, Debbie

2 1

Software selection is ignored by autoinst.
by peter.palsherm＠t-online.de 14 Aug '03

14 Aug '03

Hello, I try to install SLES8 on a bunch of servers with SuSE AutoYaST. Everything works fine but the software selection in my autoinst.xml file is ignored by autoyast. I want a "Minimal" installation with some additional packages. But the autoinstaller allways ignores my settings, and takes the "Default System for United Linux" settings. So I have to switch manualy to the the "minimum" installation on every server. :-( Here is my autoinst.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <bootloader> <location>mbr</location> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>de_DE</language> <mouse> <id>20_imps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">1567</region_entry> </region> <size>12879986689</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/import</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">1567</region_entry> <region_entry config:type="integer">131</region_entry> </region> <size>1069219841</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">3</partition_nr> <region config:type="list"> <region_entry config:type="integer">1698</region_entry> <region_entry config:type="integer">262</region_entry> </region> <size>2146664449</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> <packages config:type="list"> <package>samba</package> <package>samba-client</package> <package>nfs-utils</package> <package>nfs-server</package> <package>iputils</package> <package>bind9-utils</package> <package>ypserv</package> <package>ypbind</package> <package>yp-tools</package> <package>xntp</package> <package>lukemftp</package> <package>cups</package> <package>cups-drivers</package> <package>cups-drivers-stp</package> <package>cups-lips</package> <package>yast2-nis-server</package> </packages> </software> </install> </profile> My info file: install: nfs://10.181.206.63:/export/daten/dis/sles_8_0 netdevice: eth server: 10.181.206.63 serverdir: /export/daten/dis/sles_8_0 ip: 10.181.49.73 netmask: 255.255.255.0 gateway: 10.181.49.1 nameserver: 10.181.210.52 autoyast: floppy I'am installing the servers over the network via nfs. I have also followed the instructions in "Chapter 6.1. Creating NFS directory for UL/SLES from distribution CD's" from the AutoYast2 manual. I thing I have the same problem as Thomas. see: http://lists.suse.com/archive/suse-autoinstall/2003-Apr/0037.html y2log files are available on request What did I do wrong???? Please help!!!!! Regards --> Peter Palsherm

2 2

kernel update
by Berge, Harry ten 14 Aug '03

14 Aug '03

Hi, I've a customised bootable SuSE cd (8.2). Is it possible to update the kernel that is used by the initial installation process? > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test Engineer HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

Lib GL and php
by Tarjei Huse 14 Aug '03

14 Aug '03

Hi, after doing a nice and fine autoinstall, I get the following error when starting apache: Cannot load /usr/lib/apache/libphp4.so into server: libGL.so.1: cannot open shared object file: No such file or directory I've done some searching for ligGL.so.1. It is installed, and in PHP it points here: ldd /usr/lib/apache/libphp4.so |grep GL libGL.so.1 => /usr/lib/libGL.so.1 (0x412a1000) libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x4149a000) However, these files have not been created on the new server AND, when I run rpm -qf on my dev. machine I get the answer that these files do not belong to any package. Has anyone else had this problem? If so how did you solve it? If not, what is the correct package for /usr/lib/libGL.so.1? Tarjei

1 0

Keeping Partitions and y2update
by Frank Pascher 14 Aug '03

14 Aug '03

Hi, At the moment I'm running in circles. I'm trying to integrate y2update on our install-server. Installation is done via nfs with option: autoyast=nfs://xxx.xxx.xxx.xxx/install/repository/pc232_inst and install=nfs://xxx.xxx.xxx.xxx/install/suse8.2 The y2update is located here: /install/suse8.2/linux/suse/i586-8.2/y2update/y2update Result: y2update does not seem to be used. Any ideas ??? Thanks in advance. cheers frank pascher +----------------------------------------------------------+ | Max-Planck-Institut für Radioastronomie | | Abt.1 (wissenschaftliche DV) | | | | Frank Pascher | +----------------------------------------------------------+ | Auf dem Huegel 69 Tel.: +49 (228) 525 359 | | 53121 Bonn Fax.: +49 (228) 535 229 | +----------------------------------------------------------+ | Email: mailto:fpascher@mpifr-bonn.mpg.de | | WWW: http://www.mpifr-bonn.mpg.de | | PGP Fingerprint: 13D1 8C86 57B3 2850 F158 4879 E5F3 7E20 | +----------------------------------------------------------+

3 5

serious problem: installation crash
by Berge, Harry ten 14 Aug '03

14 Aug '03

Hi, I've got a serious problem: the installation procedure crashes when YaST2 is coming up. I'm using a patched bootable SuSE (8.2) CD, and it worked perfectly until now. After some debugging I found out that the problem is somehow hardware related: if I run 'hwinfo' manually before YaST2 is starting it's autoinstallation procedure everything goes ok. If not, than YaST2 crashes. Strange thing is that when i run 'hwinfo' there is a lot of screen garbage generated when it shows my NIC settings (Intel). I've tested it on 2 new machines (we're using HP XW4000 workstations) so it's not a faulty machine... I'm guessing the machines are equipped with a new chipset or something... Anyone a suggestion what to do? I can patch my CD that 'hwinfo' will be run before the auto installation process does this, but I find it a ugly hack :-( > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test Engineer HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

Network install, floppy only
by Robison, Jonathon (M.) 13 Aug '03

13 Aug '03

I realize that this seems old hat for many of you, but we are having difficulty creating this. We would like to have a floppy somehwhat like RedHat's "bootnet.img" which can be used to boot a system and the system will begin an installation from an http server. No CDROM required. I've looked at the /boot/bootdisk file, and I see no config file that will let me edit to point it at the server. Obviously I am missing something (probably simple), but I'd appreciate it if someone could "give me a clue". Jon R.

2 1

Defaulting to DE keyboard and runlevel 3, also DHCPTimeout bug? (SuSE 8.2)
by Robert Giles 11 Aug '03

11 Aug '03

Hi folks - I'm having a problem with the autoinstaller ignoring configuration choices I've made with the "yast2 autoyast" configuration editor: - Keyboard defaults to German, during the install and even after I get X up and running, have to edit the XF86Config file by hand to fix this. (I've set the keyboard to en_US in autoyast of course). - Regardless of what I pick in the autoyast runlevel editor, the freshly-installed system always starts in console mode (init 3). - I've picked "local time" in autoyast, but the installer always defaults to Zulu on the hardware clock. Not a big deal, but why is YaST2 ignoring directives from my autoinstall XML file? - Setting a value for DHCPTimeout in /info on my network install CD causes the system to immediately abort after trying eth0 (the whole purpose is to reduce the timeout so we can get to eth1, eth2, eth3, etc., a little more quickly, right?) Thanks in advance for any help out there! ----------------------------------------------------------- Robert Giles Group System Administrator SPD/ARL:UT (512) 835-3077 � Fax (512) 490-4244

1 0

SuSe 8.1 partition table problem
by Maxim Cherniavsky 11 Aug '03

11 Aug '03

Hi list. I have a problem during installation of SuSE 8.1 Pro on a machine with already installed version of SuSE 7.1 with kernel 2.2.18. I want to make a clean installation but with keeping one partition untouched. So I begin with the installation, but when process reaches partition setup step, YaST reports that there are no partition tables avalible on my disk. I've tried to tell Yast to reload partition table but this made no sense. This seems very strange to me :( If I boot from my old system fdisk reports: fdisk -l /dev/sda Disk /dev/sda: 255 heads, 63 sectors, 4462 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 66 530113+ 82 Linux swap /dev/sda2 67 719 5245222+ 83 Linux /dev/sda3 720 2025 10490445 83 Linux /dev/sda4 2026 4462 19575202+ 83 Linux But if I boot from SuSE 8.1 rescue system fdisk reports that there are no partition table. What may cause this sort of troubles? Maybe the problem is in the new driver for AMD Raid (my disks are under its control) included in SuSE 8.1 ? -- Best regards, Maxim Cherniavsky MTU-Intel, Internet Department mailto:maxim@mtu.ru

1 0

Script for updating a repository
by Tarjei Huse 10 Aug '03

10 Aug '03

Hi, I got two new questions :-) 1) Does anyone have a script for updateing a repository with the latest rpms from SuSE? I preferably want something that may work with apt-get. 2) Does anyone have set up systems for automatic updating an autoinstall from a central repository? If so, how is this set up, is there any best pratices etc? Thanks, Tarjei

1 0

Custom repository not working
by Tarjei Huse 08 Aug '03

08 Aug '03

Hi, I've created a custom repository out of downloading the 8.2 directory from ftp.gwdg.de. I did not however download all of the src directory. Now, after running /usr/lib/YaST2/bin/create_package_descr -d /mp3/8.2/suse while standing in /mp3/8.2/suse, I change the default YAST2 installation source to the directory /mp3/8.2/suse After doing this, I run autoyast2 ant try to select different packages. The problem is that I cannot find many packages I know are in the repository. For example, I try to find logrotate, but the package is not in the list. However, the package is in the suse/i586 directory where it should be. Has anyone experienced this before? Does anyone know what is wrong? (Yup I've bought the pro version, but I want to use the ftp version so I may use apt-get afterwords....) Tarjei

1 0

init process failed over pxe with own initrd
by Markus Klimke 08 Aug '03

08 Aug '03

Hello again, a little update: I have copied the original linuxrc file from the SuSE initrd into my own ramdisc... and it works. So, in which format has a linuxrc to be? It seems to be a statically linked binary, but I want to use a shell script, because it will fit all my needs. Can anybody help?? Markus

2 2

autoyast over nfs works, over http fails.....
by Joachim Jordan 08 Aug '03

08 Aug '03

Hello, it looks as if put the CDs in different directories and use the yast/order and yast/instorder files to tell them where to find them, the install via http and ftp fails. When i change it to nfs, everything works fine. And i checked in the apache log files, it only fails for the files suse/desc/packages that exist only for a one-source install. My grub config is this: default pxeboot label pxeboot kernel /xSLES8/linux append initrd=/xSLES8/initrd insmod=tg3 acpi=oldboot autoyast=http://192.168.70.254/Configurations/ \ "in the real config its in one line" install=nfs://192.168.70.254/store/BootRepository/xSeries/SLES8/ UseSSH=1 SSHPassword=none textmode=1 label disk localboot 0 if i exchange the nfs path against http, and it works for w3m, the install fails with error in the software selection. Best regards, Joachim Jordan Linux IT Architect, EMEA Linux Center of Competence IBM Laboratories, Dept.3300, Schoenaicherstr.220, D 71032 Boeblingen, Germany Sametime/e-mail: jordanj(a)de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232

1 0

init process failed over pxe with own initrd
by Markus Klimke 08 Aug '03

08 Aug '03

Hi there, I've created my own ramdisc. The kernel loads the basic root-filesystem into the ram without any problems. The conf file on my tftp server looks like this: ---snip--- default linux label linux kernel linux append init=/linuxrc rw initrd=initrd root=/dev/ram ---snap--- I've also tried it with some other options like 'load_ramdisk=1' and other stuff, but nothing really solves it, that, during the boot sequence, he stucks with the following kernel panic: ---snip--- Freeing initrd memory: 278k freed VFS: Mounted root (ext2 filesystem) Freeing unused kernel memory : 160k kernel panic: No init found. Try passing init= option to kernel ---snap--- With the original SuSE initrd it works fine, and after I decompressed it I found a linuxrc binary. My linuxrc is a sh-script. But I think this don't mind here, because it doesn't find an init at all. My ramdisc holds this: ---snip--- /bin linuxrc ---snap--- Some workarounds failed also: 1.) Copying a bare skeleton consisting of 'init' and '/etc/init.d/{rc,rc1.d}' leads to that it won't process the init program (a little success, but I only tried it to figure out whether the problem relates to my initrd). 2.) Writing a C file which starts a shell script. The binary C file is called 'init' and was found in /sbin of my ramdisc. Am I blind of something nasty I forgot? Or depends the failure on some other facts not mentioned above? Please help, my brain feels like filled up with scrap since three days of troubleshooting... Best regards and many thanks for every advice Markus

1 0

Bug in switching from static to DHCP IP address (SuSE 8.2)
by Hayo Schmidt 07 Aug '03

07 Aug '03

I had set up my network with a static IP address for my home network. I wanted to change this to use the laptop at work. It was not possible to do this with YaST. YaST always created an entry in /etc/hosts containing the old static IP address. So it was not possible to access the system by name. /etc/sysconfig/network/ifcfg-eth0 looked like this: BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='CLZK.uKObkw8DXlC' WIRELESS='no' BROADCAST='192.168.162.127' IPADDR='192.168.162.123' NETMASK='255.255.255.128' NETWORK='192.168.162.0' I changed it as follows and deleted the entry form /etc/hosts: BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='CLZK.uKObkw8DXlC' WIRELESS='no' BROADCAST='' IPADDR='' NETMASK='' NETWORK='' It was not possible to delete these entries with YaST. After running YaST (-> SuSEconfig) it works now. But it ist not satisfying, as i am going to have thes problems everytime i change the network - almost daily. Hayo Schmidt

1 0

partition full?
by Mag. Furtschegger Franz 06 Aug '03

06 Aug '03

Hi all, I'm trying to install suse 8.2 with autoyast2; installfiles over nfs. Now I have a big problem and no solution: I want to have on the target system two primary partitions: /dev/hda1 mounted as / (size 5GB) /dev/hda2 mounted as swap (size 512MB) during auto-installation - after partition hda1 is ready formated I get an error, that it isn't possible to mount /dev/hda1 into /mnt/. If I analyse the generated partitions with partitionimage I see, that after formatting hda1 every space on hda1 is used (no space left on hda1!!!) But: Everything works best (no error), if I use ext2 instead of reiser What am I doing wrong? I have installed autoyast2-installation-2.7.19-0 and autoyast2-2.7.19-0 Hope anybody can help me. Franz --- my entries in my xml-file are: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>5GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>512MB</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

2 1

AW: [suse-autoinstall] Autoyast2 - Disable graphical installation
by matthias.redlich＠freudenberg.de 01 Aug '03

01 Aug '03

> The parameter is textmode=1 > See also the autoinst manual, 6.2. Advanced Linuxrc Options: > http://w3.suse.de/~nashif/autoinstall/8.1/html/x1306.html#AEN1333 Thanks a lot! That's exactly the parameter we searched for. Best regards - Matthias Redlich

1 0

Autoyast2 - Disable graphical installation
by matthias.redlich＠freudenberg.de 01 Aug '03

01 Aug '03

Hello, we are currently testing the automation of Linux installations. (SLES 8) So far, everything works pretty good, but there is still one detail we would like to improve: Before the installation begins a X server is started to provide a graphical installation. Since we do not think it is necessary to have a graphical installation (with xserver) for an automatic installation we are searching for a solution to avoid this. How can I tell the system not to start xserver whilst installation but install in textmode? (the same effect as pressing F2 (text mode) in the boot menue when booting from a SuSE CD) A parameter for the bootloader would be most convenient. We have already tried to use "vga=normal", but this parameter does not work. Thanks in advance, - Matthias Redlich

2 1