June 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

rpm without any effect
by Cyprien Simons 28 Jun '04

28 Jun '04

Hi everybody! I'm trying to install the db41 (version 4.1.25-72) package for KDevelop 3.0.4. When I do it with Konqueror, it open the software manager from Yast, but then I get the window of the software manager as if I opened it manually in Yast. I mean, there is nothing selected to be installed. And when I try to do it with the command line, nothing happen (rpm -v -i <package>). It just show me the version, and then prompt again... Do anybody have an idea? By the way, it is not the first package which is doing this... regards Cyprien

1 0

Antwort: [suse-autoinstall] sles8 on AMD 64? [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 28 Jun '04

28 Jun '04

For us autoyast works in the same way for SLES 8 for AMD64 as for SLES 8 32bit. Instead of using yast2 and the graphical interface we are distributing our installation medium by editing the autoinst.xml file by hand. Regards Hartmut Dunker Stephen Mah <steve.mah@oracle An: suse-autoinstall(a)suse.com .com> Kopie: Thema: [suse-autoinstall] sles8 on AMD 64? [FinanzIT: Viruscheck] 25.06.2004 18:30 Does Autoyast work on Suse 8 64bit? I have a colleage that said it didn't work too well. here is his email: Unfortunately Autoyast appears has not yet been ported for SuSE 8 64. When you run /sbin/yast2 autoyast or /sbin/yast2 austyast2 the product fails to start. I tried downloading the autoyast2 and alice updates and have had no luck with them. Due to time constraints, my time would be better spent building the systems by hand than trying to create a automatic build process. -- cheers steve -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Documentation: Using CD-ROM and floppy
by J. David Eisenberg 25 Jun '04

25 Jun '04

The autoyast documentation (PDF file), chapter 7, section 2.2, says: "You can use the original SuSE CD-ROMs in combination with other media, i.e. with a floppy to hold the control file or in combination with network where the control file can be located." Unfortunately, it doesn't give any details of how to do this. After much fumbling around, I figured out that this refers to an "info" file on the floppy, as detailed in Appendix B. (Also, I spent a while trying to find the "linuxrc" program before realizing that it is part of the install process.) A few extra sentences in the documentation would be useful to perplexed, clueless newbies such as me. -- J. David Eisenberg http://catcode.com/

1 0

RE: [suse-autoinstall] Could not write the LILO Boot Sector
by Ness, Todd 25 Jun '04

25 Jun '04

If you can boot off the CD and have a DHCP server running then I would suggest: Put your auto.xml file on the nfs server Then boot from CD, in the command line at the bottom of the boot screen type: install=nfs://IP/pathtosource autofs=nfs://IP/pathto/xml.file If you don't have DHCP I think you would just have to add the ip, netmask, and gateway command options on the command line. And for your info all the important parts of JDS for autoinstall and installable rpms think SuSE 8.1 Out of curiosity how many seats are you trying to deploy? Are you just doing an evaluation of JDS? Todd Sun JDS Model Office -----Original Message----- From: Monirul Alam [mailto:razu92@hotmail.com] Sent: Friday, June 25, 2004 2:23 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Could not write the LILO Boot Sector Hi, Actually I am trying to implement Nfs Auto installation with Sun Java Desktop which is combination of Suse 8.1 and 8.2. The following steps I have done: copy all the three CDs to my NFS Server at /jds/install and setting the NFS server thru exportfs command and it is working properly( cam mount the /jds/install from other machine in the network) create boot floppies( 3 - boot, modules1, modules3) and autoinst.xml and copy autoinst.xml file in all the floppies and laso create info file as iw was not finding installation media. Info file is like: install: nfs://10.55.135.115/jds/install netdevice:eth0 server:10.55.135.115 serverdir:/jds/install ip: 10.55.135.251 netmask: 255.255.255.0 gateway: 10.55.135.1 nameserver: 10.55.32.132 autoyast: default Boot from floppy and provide all the flopies when promted, it went to auto installation mode but giving error when try to install boot manager " Could not write the LILO boot sector" But JDs only have grub not LILO my bootloader entry ing autoinst.xml file is <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters></kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <loader_type>grub</loader_type> <location>mbr</location> </bootloader> Please note I create auto.xml using yast2 autoinstaller tool and I use cd and install it manually it works fine. Any help will be highly appreciated. Monir _________________________________________________________________ SEEK: Now with over 50,000 dream jobs! Click here: http://ninemsn.seek.com.au?hotmail -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Could not write the LILO Boot Sector
by Monirul Alam 25 Jun '04

25 Jun '04

Hi, Actually I am trying to implement Nfs Auto installation with Sun Java Desktop which is combination of Suse 8.1 and 8.2. The following steps I have done: copy all the three CDs to my NFS Server at /jds/install and setting the NFS server thru exportfs command and it is working properly( cam mount the /jds/install from other machine in the network) create boot floppies( 3 - boot, modules1, modules3) and autoinst.xml and copy autoinst.xml file in all the floppies and laso create info file as iw was not finding installation media. Info file is like: install: nfs://10.55.135.115/jds/install netdevice:eth0 server:10.55.135.115 serverdir:/jds/install ip: 10.55.135.251 netmask: 255.255.255.0 gateway: 10.55.135.1 nameserver: 10.55.32.132 autoyast: default Boot from floppy and provide all the flopies when promted, it went to auto installation mode but giving error when try to install boot manager " Could not write the LILO boot sector" But JDs only have grub not LILO my bootloader entry ing autoinst.xml file is <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters></kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <loader_type>grub</loader_type> <location>mbr</location> </bootloader> Please note I create auto.xml using yast2 autoinstaller tool and I use cd and install it manually it works fine. Any help will be highly appreciated. Monir _________________________________________________________________ SEEK: Now with over 50,000 dream jobs! Click here: http://ninemsn.seek.com.au?hotmail

1 0

"ERROR: No proposal" message with default install params
by David Corlette 24 Jun '04

24 Jun '04

Hello there, Since I couldn't get LVM working, I decided to give a very very minimal partitioning setup a test. I copied the sample code verbatim from http://www.suse.de/~nashif/autoinstall/9.0/html/createprofile.partitio ning.html, e.g. Example 4-4, I just copied and pasted it into my control file. When I get to the confirmation step of the autoinstall, under "Partitioning" it says "ERROR: No proposal". BTW, I've verified that the device names match, e.g. my system uses /dev/hda. So, shouldn't the example on the website actually work? Thanks for any help... Here's the relevant section of my control file: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> </drive> </partitioning> Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu

2 3

Managing autoyast installed systems
by Peter Niessen 22 Jun '04

22 Jun '04

Dear autoinstall-list, faced with the threat of a new cluster here, I familiarised myself with autoyast. All runs find and the machine installs without intervention. But how can one update/add packages on the clients? Should I setup passwordless ssh access and the run for CLIENT in box1 box2 ... boxn ; do ssh $CLIENT "rpm -I the_user_wants_this_yesterday.rpm" done Or should I update my autoyast generated configuration and reboot and re-install everytime something changes? Sounds pretty uncool. Cheers, Peter. Peter Nie[df]en (Peter Niessen for special character challenged displays) Bartol Research Institute University of Delaware Newark, DE 19716-4793 U.S. of America Tel (+1)302/831-8700 Fax (+1)302/831-1843 e-mail niessen(a)ifh.de www http://www.ifh.de/~niessen /"\ ASCII ribbon campaign \ / --------------------- X against HTML mail / \ and postings pgp public key at http://www.ifh.de/www_users/amanda/niessen/www/pgp_pubkey.asc

4 4

disapearing devices
by Dan Carpenter 21 Jun '04

21 Jun '04

I'm installing SuSE 9.1 on an Opteron. The first time I installed this it report errors while formating partitions. "Error: Unable to set up swap on /dev/hda3" etc. It turned out that the /dev/hda1, hda2, hda3 and hda5 were not present on the system. I recreated them using `mknod /dev/hda3 b 3 3` etc and formatted them. The system seems to be fine. I've tested the memory with memtest86. I tried to install the system again but I wasn't able to reproduce the problem. My understanding from poking around during the install is that the device are created at boot and then some are deleted and recreated during the install. Perhaps there is a bug with this code... Has anyone seen something like this? thanks, dan carpenter

2 3

RE: [suse-autoinstall] Managing autoyast installed systems
by Ness, Todd 21 Jun '04

21 Jun '04

You can use the SuSE supplied YOU (YaST Online Update) or fou4s (fast online update for suse). -----Original Message----- From: Peter Niessen [mailto:niessen@ifh.de] Sent: Sunday, June 20, 2004 11:23 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Managing autoyast installed systems Dear autoinstall-list, faced with the threat of a new cluster here, I familiarised myself with autoyast. All runs find and the machine installs without intervention. But how can one update/add packages on the clients? Should I setup passwordless ssh access and the run for CLIENT in box1 box2 ... boxn ; do ssh $CLIENT "rpm -I the_user_wants_this_yesterday.rpm" done Or should I update my autoyast generated configuration and reboot and re-install everytime something changes? Sounds pretty uncool. Cheers, Peter. Peter Nie[df]en (Peter Niessen for special character challenged displays) Bartol Research Institute University of Delaware Newark, DE 19716-4793 U.S. of America Tel (+1)302/831-8700 Fax (+1)302/831-1843 e-mail niessen(a)ifh.de www http://www.ifh.de/~niessen /"\ ASCII ribbon campaign \ / --------------------- X against HTML mail / \ and postings pgp public key at http://www.ifh.de/www_users/amanda/niessen/www/pgp_pubkey.asc -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SuSE 9.1 automatic Konfiguration of grub
by Joachim.Tork＠gad.de 19 Jun '04

19 Jun '04

Hello, I face the problem that I have to install computers with different hard disk hardware, i.e. harddisk with /dev/hda, /dev/sda /dev/rd/c0d0 with one installation CD. In the partitioning type this is no problem leaving the device configuration empty in the autoinst.xml file. But how do I handle the boot loader grub in that way ? Can anybody help? Regards Joachim

2 1