June 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Driver Disk
by Martin Möser 20 Jul '04

20 Jul '04

Hi all, does anyone know how to make a Driver Disk accessible for autoyast CD-installation? Is there a possibility to put it on the CD in order to not have an extra floppy? Thanks, Martin

2 3

Working autoyast file ?
by Wayne Pascoe 02 Jul '04

02 Jul '04

Hi all, Can anyone provide me with a working autoyast file to start from, as well as any additional information about loading drivers, etc. ? I've done a setup of a SLES9 RC1 machine and then generated a reference profile from that machine - this doesn't work however... The boot process happens and the installation starts. I then get a screen that looks roughly as follows: Left Pane: Please wait while the system is prepared for autoinstallation Right Window: [x] Probe Hardware => Retrieve read control file - ... - ... The bar at the bottom of this screen stops at 28% and it goes nowhere. This is the very same machine that I used to create the reference profile, so I'm confused as to why it's not working :( Regards, -- Wayne Pascoe

1 2

Autoinstall from HDisk
by Werner Hack 01 Jul '04

01 Jul '04

Hi, I try to install a PC from local HDisk using a selfmade BootCD. These are my parameters for autoyast : autoyast=device://hda9/install/autoyast/profiles/pc.xml serverdir=/install/autoyast/SuSE/ partition=hda9 I copied the SuSE DVD Distribution to 'serverdir'. Booting from CD is working fine, the autoyast-file is read. But then I get an error message : > Could not set base selection: default > Error while configuring software selections Any idea why this happens ? Thanks in advance. Regards, Werner Hack --

2 2

FastTrack Driver ft.o for autoinstallation (SLES8) on Blade Server
by Martin Möser 30 Jun '04

30 Jun '04

Hello, we use autoyast with Custom-CD for installing control-servers. Now, we have to use a diskless BladeServer as control-server. Thus, we need the module ft.o (FastTrack Driver) in order to let the Blade determine the Harddisk (sda) to be used. Is there any possibility to tell autoyast to load this driver before detecting the harddisk? The only opportunity we see is giving kernel parameters at boot-loader-time, but where do we have to place the driver then? Is it possible to make it accessible from CD or do we have to provide a floppydisk? We'd like to have it fully automatic! Thanks, Martin

1 0

exit code 127
by Thorsten Alge 30 Jun '04

30 Jun '04

Hi, i´ve set up an AutoYaST Installation Server. I want to install my clients via PXE-BOOT. When the client is booting, everything works fine but when yast ist starting, i got en error. In the log it says: starting /mounts/instsys/sbin/inst_setup yast install program exit code is 127 sync... ok i can´t find out what the hell means "exit code 127", becouse it seems that everything is well configured and works fine. thanks... thorsten

1 0

PXE/TFTP 9.1 Autoinstall on AMD64
by Charles Smith 28 Jun '04

28 Jun '04

Hello, I currently have SuSE 9.1 Pro PXE/TFTP booting/autoinstalling working great with our 32-bit machines. My problem is that I can't seem to get this to also work with our x86_64 machines. I don't know if there is a graceful way to separate 32 and 64-bit stuff in the /tftpboot directory, so what I initially tried to do was make an isolinux.cfg menu option which specified an alternate (64-bit) linux and initrd, but when it loads the 64-bit kernel and initrd, the machine immediately reboots. I tried to boot it off the 32-bit kernel/initrd just to do the install, but as soon as it loads the data into ramdisk, it goes to a blue yast screen with the message "An error occurred during installation!" (very helpful) Switching to other consoles at this point reveals only a little more info, such as the messages: lockd:failed to open /var/lib/nfs/state: err=2 request_module: runaway loop modprobe binfmt-464x (5 of these) Lastly, I backed up the /tftpboot directory and blew it away, making a brand new one with only stuff from the 64-bit distribution in there, and it behaved exactly like it did when I tried specifying the alternate linux and initrd (rebooted). Now this situation suggests that setting up 64bit network booting the same way as with the 32-bit stuff doesn't work with my 64-bit systems, and that there is something special I need to be doing for them. Is there some documentation specific to 64-bit network booting / autoinstalling? Does it in fact differ from the 32-bit procedure (aside from having an x86_64 kernel/initrd/distro/control-files)? I know Anas is still working on the 9.1 docs, but has anyone successfully PXE/DHCP/TFTP/autoinstalled an AMD64 machine? Perhaps it is just a compatibility problem with my hardware? The 64bit systems I'm installing are AMD Opteron 146's on Asus SK8N motherboards (nForce chipset). I've tried floppy booting, but it doesn't talk to the NIC correctly (not sure my problem would be avoided anyway). Otherwise I may go ask the suse-amd64 list as well. Thanks in advance, -Charles Smith

1 0

how to get aborted autoinstall log
by Carl Pecinovsky 28 Jun '04

28 Jun '04

This is probably a newbie question, but the scenario is that I'm trying to install a ppc LPAR partition on iSeries with SLES9 (rc2). I pass the install kernel parms for autoyast, install, and networking. The install proceeds to read the autoyast control file, do some more setup which flies by, and then pops the text installer out to the root "Main menu". No error condition was given -- it just popped out and the same thing happens if I repeat the process by choosing option 4 to start system installation. How do I look at the install log at this point? I don't know how to exit the main menu and get to the ramdisk, etc. Thanks. Carl Pecinovsky Dept X8X: eServer Middleware Enablement, 015-3/H106 "It is never safe to look into the future with eyes of fear." --E.H Harriman

3 5

sles8 on AMD 64?
by Stephen Mah 28 Jun '04

28 Jun '04

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

2 1

max size with LVM volumes?
by David Corlette 28 Jun '04

28 Jun '04

Hello there, I'm trying to set up a disk as follows: /dev/hda1: / 2GB /dev/hda2: swap auto size /dev/hda3: lvm "system" max (rest of disk) /dev/sys/var_lv: /var 200MB /dev/sys/home_lv: /home max (rest of LVM space) I would think this would be a pretty common arrangement (e.g. to have LVM fill a disk, and then a volume within that fill the LVM space), but for some reason the "/home" partition always ends up being of "unknown" size. Is there any way to get this to work, or am I hosed? Thanks! Here's the relevant section of my control file: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/</mount> <size>2GB</size> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> </partition> <partition> <mount>swap</mount> <size>auto</size> <format config:type="boolean">false</format> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> </partition> <partition> <lvm_group>system</lvm_group> <size>max</size> <partition_type>primary</partition_type> </partition> </partitions> </drive> <drive> <use>all</use> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>var_lv</lv_name> <mount>/var</mount> <size>200mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>home_lv</lv_name> <mount>/home</mount> <size>max</size> </partition> </partitions> <pesize>4M</pesize> </drive> </partitioning> Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu

2 1

Confused about clone / reference profile on SLES9 RC1
by Wayne Pascoe 28 Jun '04

28 Jun '04

Hi all, I'm trying to create an autoyast configuration with SLES9 RC1. I've done some searching and found that the clone function is now refered to as creating a reference profile. I've done this, but I'm a bit concerned by the outcome. I selected Partitioning, Boot Loader and Software under basic resources, but none of this appears to have taken. The machine I am doing this on has a minimal install. Yet when I check Package selection after creating my reference profile it is set to default, not minimal. Under partitioning, all I see is Drives Total of 1 drive * No specific device configured I'm also not seeing any configuration information under Network devices either. Ideally, I'm just trying to get to the point where I can do an auto-deploy, then I'll fiddle with the control file to do things like LVM, etc. Can anyone advise me on the best way to do this please? I'm currently trialing SLES against Red Hat Enterprise Linux AS 3, and the one thing that RHAS has going for it is that when you install a machine, a kickstart file is created in the /root directory as part of the install. So to create a profile for each machine, all you have to do is install one machine manually, and it's all there for you. Are there any plans for this in SLES ? Regards, -- Wayne Pascoe

2 1

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

autoinstall fails with SuSE 9.1
by David Corlette 19 Jun '04

19 Jun '04

Hello all, I'm having trouble getting autoinstall to work with SuSE 9.1. I'm not sure if I'm doing something wrong or if something's broken. Here are the basics: - I've downloaded a complete copy of the 9.1 distribution, put it on an NFS server (10.0.0.57) and exported it as /home/suse. - I've created a customized control file using YaST2-autoinstall (with manual customization) and placed it in /home/suse on the NFS server. - I've cut a CD using "boot.iso" from the distribution, with no customization; I'm just planning to manually enter the correct autoyast command-line. - I boot off the CD, interrupt the timer, and then put "autoyast=nfs://10.0.0.57/home/suse/arpmin.xml" in the command-line options line. - The system starts to attempt the autoinstall, then fails saying it can't contact the install server. Log attached below, please note comments following: Log from installer: ---trim--- Looking for network server.. Ok, that didn't work; see if we can activate another network device... insmod /modules/mii.ko insmod /modules/e100.ko Ok, that seems to have worked. :-) Looking for a network server again... Trying to activate eth0 Setting up localhost...done Sending DHCP request to eth0... no/incomplete answer. Ok, that didn't work;see if we can activate another network device... No further network carcds found giving up. hostname: 10.0.0.200 netmaks: 255.255.255.0 broadcast: 10.0.0.255 gateway: 10.0.0.1 server: 10.0.0.10 nameserver: 10.0.0.8 Looking for a network server... Trying to activate eth0 Setting up locathost...done **** dhcpcd: already running **** dhcpcd: if not then delete /var/run/dhcpd-eth0.pid file Sending DHCP request to eth0... no/incomplete answer. Ok that didn't work; see if we can activate another network device... No further network cards found; giving up.. Automatic setup not possible. ---end--- Does anyone else find it odd that the script appears to give up on DHCP just before the machine apparently gets a full set of parameters from DHCP? Perhaps the timeout is ridiculously low? In any case, if anyone has any idea how to fix this, I would really appreciate it. Thanks! Dave C --------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu

2 1

Re: Error while configuring software selections on SLES 8 SP3 ia64
by Anas Nashif 18 Jun '04

18 Jun '04

Bruno Cornec wrote: > Hello, > > After reading tons of documents and passing more than 2 days on that problem, > I think I need some help ;-) > The target is to deploy 50+ rx2600 HP ia64 servers, and I'd prefer not doing > that by hand ;-) > > Any hint, pointer would be greatly appreciated. > Bruno. > > Problem description: > =================== > > Autoyast doesn't validate our package selection stating > that the "default" selection is incorrect. This means something is wrong with your installation source setup. > > Details: > ======== > > When autoyast tries to analyse the autoyast.xml file that he gets > from the deployment servers, it aborts at the "configure software" > step issuing the following message: > > Error > Error while configuring software selections > Please try again ! > [OK] > > The autoyast.xml generated by the SUSE tool doesn't work from scratch. > > I've attached all the relevant files I found on both the server > and the client in order to help for the debug. If you'd like to > have other missing files, please ask ! > > My setup follows what is described here: > 1. http://www.suse.de/~nashif/autoinstall/faq.html > 2. http://www.suse.de/~nashif/autoinstall/sles8/html/x910.html > 3. http://www.suse.de/~nashif/autoinstall/multiplesource.html > > Especially I put the driverupdqte file in my root dir > I also used the sp3 kernel and initrd in my elilo configuration. > > The problem I see is around the order and instorder files: > > order: > > /sp3/CD1 /sp3/CD1 > /sles/CD1 /sles/CD1 > /ul/CD1 /ul/CD1 > > instorder: > > /ul/CD1 /ul/CD1 > /sles/CD1 /sles/CD1 > /sp3/CD1 /sp3/CD1 > once column is the right thing, I still have to update it in all docs, but this should not be the cause of the problem. Something is not right with the directories although your description below looks OK. > [Don't know why n the same doc it has once 2 columns and another time only one] > > and that part of autoyast.xml > > <software> > <addons config:type="list"/> > <base>default</base> > <packages config:type="list"> > [...] > </packages> > </software> > this is Ok. > > The documentation in 3. isn't for me sufficiently detailed and I > do not understand really what these 2 files do. > > I suspect that autoyast doesn't find the correct default.sel at > the right place, even if the log shows that it's loaded: > > [Note: we created files packages.en_US from packages.en in all directories as > it was missing, and changing language to en alone raised other issues] The logs show a bug that is known with SLES8 GA which was fixed with SP3. The driverupdate is featched correctly though. Can you verify that a directory named /y2update/modules does exist on the client during installation? Anas

2 1

autoinstall problem on ibm e325 and broadcom 5704
by nicolas.raspail＠bnpparibas.com 18 Jun '04

18 Jun '04

Hi, autoyast doesn't work on my ibm e325. I reach the autodection hardware, it loads tg3 or bcm5700 driver (depends on my test) but dhcp requests don't reach my dhcp server or if static IP are used, il can't activate the first time the networkd card so it tries a second time, it succeeds, but it tries to mount 0.0.0.0:/install/suse ! It seems it has forgotten the nfs server IP between the two activation. Morever, when I used the following setting DEFAULT linux64 LABEL linux64 KERNEL linux64 APPEND initrd=initrd64 insmod=tg3 hostip=10.252.82.231 netmask=255.255.255.0 gateway=10.252.82.1 nameserver=10.252.0.228 server=10.252.82.254 install=nfs://10.252.82.254/install/mirrors/suse/64/ autoyast=nfs://10.252.82.230/var/lib/autoinstall/repository/cg99-005.xml textmode=1 PROMPT 1 TIMEOUT 50 and switch to alt+F3 console, I see the following strange line server: 10.252.82.254 (no ip) <-- what does this no ip means ? linux64 and initrd34 are copied from the DVD and renamed to suit my needs. I do the same with the 32 bits version and it's works fine. Can anyone has auto installed the Suse 9.1 Pro (amd64) on an IBM e325 ? I've no problem install it on an IBM x335 (bi xeon) with a broadcom 5703, so I think the problem is on the network card. I'll receive soon a Sunfire v20z for some test, anyone have some information about suse 9.1 pro amd64 and this computer ? Best regards Nicolas This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

rules
by Werner Hack 18 Jun '04

18 Jun '04

Hi, I try to install a server machine with autoyast booting from a selfmade CD. A copy of the SuSE distribution is located on a local disk. There are several disks attached to this system. To determine the right harddisk where I intend to install the OS I want to use 'rules.xml'. These are my boot parameters for autoyast : > autoyast=device://sdb1/install/autoyast/profiles/ > serverdir=device://sdb1/install/autoyast/SuSE partition=sdb1 If no profile is specified, autoyast should go for the rules file. But when the system comes up autoyast stops : 'No profile for this machine could be found or retrieved' ... and autoyast shows the given profile location in its installation window for choosing an new one. This is my rules file located in .../profiles/rules : > <rules config:type="list"> > <rule> > <disksize> > <match>/dev/sda 100000</match> > <match_type>greater</match_type> > </disksize> > <result> > <profile>server.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > </rules> While booting all disks are detected (and modules are loaded) the right way. Any idea what went wrong ? Thanks in advance Regards Werner Hack BTW: What's the right syntax for the MAC attribute in rules.xml ? <mac> <match>123456ABCDEF</match> <match_type>exact</match_type> </mac> Is this correct ? Has the module for the network device to be loaded to detect the MAC address ?

2 1

How to keep a pre-install script partition scheme?
by Mike Rose 17 Jun '04

17 Jun '04

Hi, Our requirement for partitioning is not covered by autoyast (IMHO) so I've had to use a pre-install script that uses sfdisk to create what we want - create / as a primary partition, an extended partition with swap and the rest of the disk as another partition (later to be mounted as /scratch for obvious reasons), but not all of the HDDs we have can take a / partition of 10GB so sometimes we need not to create a 3rd partition and to reduce the size of /. I've added the script that does this to end of this email. Unfortunately this does not work. I am assuming I have messed up my partition XML - can you help? I am now going to try using the "Auto-detection of partitions to be kept" method while I wait for a reply. partitions before install (using exec /bin/bash -x so that I get an interactive prompt to be able to check that the pre-install script has worked): Disk /dev/hda: 9729 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 0+ 1305 1306- 10490413+ 83 Linux /dev/hda2 1306 9728 8423 67657747+ 5 Extended /dev/hda3 0 - 0 0 0 Empty /dev/hda4 0 - 0 0 0 Empty /dev/hda5 1306+ 1434 129- 1036161 82 Linux swap /dev/hda6 1435+ 9728 8294- 66621523+ 83 Linux partitions after install: Disk /dev/hda: 9729 cylinders, 255 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 0+ 1305 1306- 10490413+ 5 Extended /dev/hda2 1306 9728 8423 67657747+ 5 Extended /dev/hda3 0 - 0 0 0 Empty /dev/hda4 0 - 0 0 0 Empty /dev/hda5 1306+ 1434 129- 1036161 82 Linux swap /dev/hda6 1435+ 9728 8294- 66621523+ 83 Linux which is a bit of a mess so no wonder the installatin cannot succeed. >From reading: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Partitioning.… I thought I had understood the XML I needed to use to be: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr config:type="integer">5</partition_nr> </partition> </partitions> </drive> </partitioning> The XML pre_install script: <source><![CDATA[ #!/bin/sh wget http://XXXX/~install/suse9.1/pre_install_suse91.sh wget http://XXXX/~install/suse9.1/sfdisk chmod +x sfdisk chmod +x pre_install_suse91.sh ./pre_install_suse91.sh # exec /bin/bash -x ]]></source> pre_install_suse91.sh: #!/bin/sh -x # setup detault route to install server route add -net XXXXX netmask 255.255.255.0 dev eth0 # Now partition the disk SFDISK=./sfdisk mknod /tmp/hda b 3 0 CREATETEMP=false $SFDISK --no-reread -V /tmp/hda if $SFDISK --no-reread -V -q /tmp/hda; then DOPARTITION=false else DOPARTITION=true DISKSIZE=$((`$SFDISK --no-reread -s /tmp/hda` / 1024 )) # assume 1k blocks echo $DISKSIZE MEMSIZE=`cat /proc/meminfo | grep "MemTotal:" | cut -d":" -f2 | cut -d"k" -f1` echo $MEMSIZE if [ $(($MEMSIZE / 1024 )) -gt 128 ]; then SWAPSIZE=$(($MEMSIZE / 1024)) else SWAPSIZE=128 fi ROOTSIZE=$(($DISKSIZE - $SWAPSIZE)) # disk - swap if [ $ROOTSIZE -gt 10240 ]; then # 10GB in MB CREATETEMP=true ROOTSIZE=10240 TEMPSIZE=$(($DISKSIZE - $ROOTSIZE)) fi # if we always put swap in an extended partition, we can # guarantee: # # / is /dev/hda1 # swap is /dev/hda5 # /scratch is /dev/hda6 # and all is well and happy throughout the land ... echo $ROOTSIZE $SWAPSIZE $CREATETEMP fi if $DOPARTITION; then echo "past DOPARTITION" if $CREATETEMP; then # we're lurching into a different partitioning echo "createtemp" $SFDISK --no-reread -D -uM /tmp/hda <<EOF ,$ROOTSIZE ,,E , , ,$SWAPSIZE,S ,,L EOF else # we must have no /temp. echo "notemp" $SFDISK --no-reread -D -uM /tmp/hda <<EOF ,$ROOTSIZE ,,E , , ,,S EOF fi fi cheers, Mike Rose

2 2

RE: [suse-autoinstall] UK language and timezone settings ignored
by Wallace, Andrew 17 Jun '04

17 Jun '04

> Hi, > > I'm using autoyast-installation on SuSE 8.2 (I know it's old > but I don't > have a choice). > > I used the YaST GUI tool to create the inital configuration, and the > resulting xml file > looks OK. It works, it builds the boxes OK, runs my > post-install script OK > etc etc > > However, the time is set to 5 hours forward and the encoding > is ANSI-1968, > when it > should be ISO-8859-1. > <snip> Never mind, it's my fault. I'm using a custom package selection file and forgot to include glibc-locale, so there was no ISO-8859-1.so on the system. Oops.

1 0

UK language and timezone settings ignored
by Wallace, Andrew 17 Jun '04

17 Jun '04

Hi, I'm using autoyast-installation on SuSE 8.2 (I know it's old but I don't have a choice). I used the YaST GUI tool to create the inital configuration, and the resulting xml file looks OK. It works, it builds the boxes OK, runs my post-install script OK etc etc However, the time is set to 5 hours forward and the encoding is ANSI-1968, when it should be ISO-8859-1. It looks to me like the default US locale has been used instead. Here's the relevant bit of autoinst.xml <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/London</timezone> </clock> <keyboard> <keymap>english-uk</keymap> </keyboard> <language>en_GB</language> ... I can see nowhere else to specify which character encoding is used. A normal manual install sets it correctly to ISO-8859-1 Help! Have I missed something? Regards, Andrew Wallace Linux Administrator/Developer Siemens Business Services Coventry Tel: 02476 838433 Mob: 07766 560211

1 0

Réf. : Re: [suse-autoinstall] autoyast2, Suse 9.1 Pro and resolv.conf
by nicolas.raspail＠bnpparibas.com 17 Jun '04

17 Jun '04

Hi, thanks for the tip, I've a good resolv.conf. Now I must understand te meaning of these lines :) Best regards Nicolas PS : sorry for the quote, but I use Lotus notes at work ;( Extranet ulrich.bernhard(a)id.unizh.ch - 17/06/2004 09:06 Pour : suse-autoinstall cc : Objet : Re: [suse-autoinstall] autoyast2, Suse 9.1 Pro and resolv.conf Hi, I have had the same problem with more or less the networking definitions. At the end I have added the following sysconfig lines and now I have a /etc/resolv.conf file: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>MODIFY_RESOLV_CONF_DYNAMICALLY</sysconfig_key> <sysconfig_path>/etc/sysconfig/network/config</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> Best regards Ulrich nicolas.raspail(a)bnpparibas.com wrote: <snip> -- +-----------------------------------------------------------+ | Ulrich Bernhard | | Informatikdienste Tel: (+41-44) 635 67 73 | | Universitaet Zuerich Fax: (+41-44) 635 45 05 | | Winterthurerstr. 190 | | CH-8057 Zuerich Email: ulrich.bernhard(a)id.unizh.ch | | Switzerland | +-----------------------------------------------------------+ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

1 0

autoyast2, Suse 9.1 Pro and resolv.conf
by nicolas.raspail＠bnpparibas.com 17 Jun '04

17 Jun '04

Hi, I've just discovered Suse and autoyast2 (we are switching from Redhat and Systemimager for deployment) and I've have one problem. With yast2, I create a xml file for autoyast and everything works fine except for /etc/resolv.conf. The computer has the right IP address, the right gateway but no /etc/resolv.conf. I use static IP and here is an extract of my configuration file : <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>equities.net.intra</domain> <hostname>cg99-005</hostname> <nameservers config:type="list"> <nameserver>10.252.0.228</nameserver> <nameserver>10.252.0.248</nameserver> </nameservers> <searchlist config:type="list"> <search>equities.net.intra</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.252.82.255</broadcast> <device>eth0</device> <ipaddr>10.252.82.231</ipaddr> <netmask>255.255.255.0</netmask> <network>10.252.82.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>bcm5700</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.252.82.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> I've read some mails on this list and see it seems I can remove the <module_entry> (moreover, the tg3 driver is used instead on my IBM x335) but I've not tested that at te moment. Does anyone have an idea about the non-creation of the /etc/resolv.conf ? Where I can search logs for more information ? I'm using dhcp+pxe+nfs to boot the system and install it Thanks Nicolas This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

Re: [suse-autoinstall] Determining file layout
by D Umesh 17 Jun '04

17 Jun '04

There is a file called ls-lR.gz file in each CD which contains list of all files, I think while installing this file would get uncompressed, yast seaches in this file and prompts for correct CD. Regards Umesh >>> "Dustin Nielson" <DUNIELSON(a)novell.com> 06/14 8:17 PM >>> In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

2 1

RE: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same P roblem in 9.1
by discip＠pjm.com 15 Jun '04

15 Jun '04

Yup, that Did it! I added the "install" keyword to the info file, and now it is fine. The documentation, however, says that if I use the "autoyast" keyword that the "install" keyword is unnecessary. Oh well, I am just happy it works now. I think "overjoyed" is more the word. Thanks Anas! Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, June 09, 2004 8:16 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same P roblem in 9.1 Where do you set the installation source? You info file does not have it, do you have it on the command line? I would say yast cant find the installation source and trying DHCP to find it... Anas discip(a)pjm.com wrote: > This doesn't seem to help. I tried both netsetup=0 and > netsetup=-dhcp. Now pops up a window and tells me "your network has > already been configured. Do you want to keep this configuration?". > Then when I say yes, it tries to DHCP again. :-( > > Paul > > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Wednesday, June 09, 2004 12:03 PM > To: discip(a)pjm.com > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same Problem > in 9.1 > > > This is something new in 9.1/SLES9. Add netsetup=0 to skip DHCP. > > > 3. Advanced Network Setup > > > The netsetup keyword allows advanced network configurations and > enables > dialogs to setup the network where required. > > > netsetup=1 > > > the normal network setup questions > > > netsetup=xxx,yyy > > > just xxx and yyy > > > netsetup=+xxx,-yyy > > > default, additionally xxx, but not yyy > > > xxx could have the following values: dhcp, hostip, gateway, netmask, > nameserver. nameserverN asks for N nameservers (max. 4). > > > For example, the following can be entered on the command line: > > > netsetup=-dhcp,+nameserver3 > > > discip(a)pjm.com wrote: > >>No matter what I do to the info file, I still can't get linuxrc to not >>try to do dhcp on eth0. I look at console number 2 and I see that it >>has even configured eth0 with the right IP parameters, but it tries to >>do DHCP anyway. I am trying this with 9.1 now. Same behavior. What >>gives? >> >>Paul >> >>P.S. If you care, my info file looks like this: >> >>insmod: 3c59x >>netdevice: eth0 >>DHCP: 0 >>HostIP: 192.168.1.5 >>netmask: 255.255.255.0 >>gateway: 192.168.1.1 >>server: 192.168.1.18 >>autoyast: nfs://192.168.1.18/opt/Linux/SUSE-9/profiles/test.xml >> > >

1 0

Re: [suse-autoinstall] Fw: autoyast and loadorder of modules
by Helge Koehn 15 Jun '04

15 Jun '04

du hast recht, fuer sles8 funktionierts, indem man die treiberreihenfolge als append parameter fuer den bootkernel mitgibt (aber wahrscheinlich auch nur, weil sles8 erst alle pakete installiert, dann die postskripte ausfuehrt und danach der initial boot erfolgt, waehrend suse9 halt gleich nach der 1. cd rebooten will und die bis dahin zusammengebaute initrd die einstellungen einfach ignoriert!). wenn sles9 auf basis suse 9 aufgebaut ist, haben wir dann dort wahrscheinlich die mimik von suse9 nach der ersten cd?! waere einen versuch wert ;-) Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc Subject Re: [suse-autoinstall] Fw: autoyast and loadorder of modules Nur halt mit SLES8, da geht's ja. SuSE9 ist insofern kaputt. Mal sehen, was SLES9 macht - wenn sich's mal installieren läßt :-( Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz(a)computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. Helge Koehn <koehn(a)de.ibm.com> on 09.06.2004 12:03:42 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Fw: autoyast and loadorder of modules -------------------------------------------------------------------------- ... any ideas to that problem from march?! till now not one answer :-( helge. ----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM ----- Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall(a)suse.com PM cc Subject autoyast and loadorder of modules hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com COMPUTACENTER (UK) LTD The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Computacenter information is available from http://www.computacenter.com This footnote also confirms that this email message has been swept for the presence of computer viruses. ***************************************************************************************************************************

2 1

Antwort: [suse-autoinstall] Determining file layout [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 15 Jun '04

15 Jun '04

Hi Dustin, when you are creating a new multi CD install with create_package_description from the autoyast package, YaST stores the information of each package where it resides on. You can find this information in the packages file under /suse/setup/descr in each package description (=Loc:). Regards Hartmut "Dustin Nielson" <DUNIELSON@novell An: <suse-autoinstall(a)suse.com> .com> Kopie: Thema: [suse-autoinstall] Determining file layout [FinanzIT: Viruscheck] 14.06.2004 16:47 In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

1 0

Determining file layout
by Dustin Nielson 14 Jun '04

14 Jun '04

In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

1 0

Filesystem mount options on SuSE 9.1 LVM installs
by David Carter 14 Jun '04

14 Jun '04

Hello all, The <fstopt> option doesn't appear to work on LVM devices under SuSE 9.1. <install> . . . <partitioning config:type="list"> . . . <drive> <device>/dev/hermes</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <use>all</use> <partition> <filesystem config:type="symbol">ext3</filesystem> <fstopt>defaults,usrquota,nosuid</fstopt> <lv_name>homes</lv_name> <mount>/homes</mount> <size>250g</size> </partition> </partitions> </drive> The resulting fstab entry is: /dev/hermes/homes /homes ext3 defaults 1 2 Is this expected behaviour? Checking the list archives, I see someone asking a similar question about SLES 8 a few days back. -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH.

1 0

archives.gz
by Dustin Nielson 10 Jun '04

10 Jun '04

Curious as to how the ARCHIVES.gz file is generated on the first CD. If anyone knows I'd appreciate some information. Dustin

2 1

RE: [suse-autoinstall] Sample autoyast script
by Jesse Pretorius 10 Jun '04

10 Jun '04

Excellent, that works perfectly, thank you. -----Original Message----- From: Lee Mayes [mailto:autoinst@mayeses.com] Sent: 10 June 2004 01:58 PM To: Jesse Pretorius Subject: Re: [suse-autoinstall] Sample autoyast script Hi Jesse, Here's the relevant lines from my autoyast file: <install> <general> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">true</reboot> </mode> </general> </install> That will remove the need to accept anything (including the reboot before SuSE.config runs. Best Regards, Lee On Thu, 2004-06-10 at 06:54, Jesse Pretorius wrote: > Hi to all, > > Could anyone forward me a working autoinst.xml (autoyast script) file. > I need one from a fully automated installation. > > I'd like to use it for comparison to see where mine has a problem and > is thus requiring me to do two clicks to complete the install. > > Thanks, > > Jesse

1 0

Sample autoyast script
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi to all, Could anyone forward me a working autoinst.xml (autoyast script) file. I need one from a fully automated installation. I'd like to use it for comparison to see where mine has a problem and is thus requiring me to do two clicks to complete the install. Thanks, Jesse

1 0

Pxelinux process hangs
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi to all, I've now setup DHCPD, TFTPD and all the appropriate bits afaik to get the PXE-based boot and install to run. When I do a PXE-based boot, I receive an address, it downloads pxeconfig.cfg/default and runs to the point where the line indicates the start of the install program with ">>> SuSE Linux installation program" and the rest of the line is known to you. The problem I have is that it hangs there. What am I missing? Contents of pxeconfig.cfg/default: -- begin file -- default linux serial 0,9600n8 label linux kernel linux append console=ttyS0,9800 console=tty0 load_ramdisk=1 initrd=initrd insmod=pcnet32 autoyast=http://192.168.240.1/autoinst.xml install=nfs://192.168.240.1/srv/nfs -- end file -- Naturally 'initrd', 'linux', 'pxelinux.0' are all in /tftpboot/ Can anyone point me in the right direction? Thanks, Jesse

1 1

Creating a autoyast script for SLD
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi, I'm trying to create an autoyast script for SLD and have only been moderately successful. I used the autoyast module through the ncurses interface (no GUI on my server) to create a basic file with the partitioning info and a basic package selection. I the edited the file to change the package selection to use some of the SLD .sel files instead of the SLES8 .sel files. I'm finding that the script creation utility is basically designed to create a script file for SLES rather than for any SUSE distro and thus it's rather limiting and I have to edit the text files by hand to do the distro-specific settings. Is there a way to have the autoyast module pick up the details of the distro I want to customise a script for from a file path or something? There does appear to be a setting which allows you to indicate where your package sources are, which I've set. but it doesn't make a difference. Also, I'm finding that my script does the selections automatically now, but the installation still wants me to select 'Accept' to continue the installation. What's missing - I'm guessing it's something in the script file? I'm looking to do a completely hands-off installation. TIA, Jesse

1 0

Fw: autoyast and loadorder of modules
by Helge Koehn 10 Jun '04

10 Jun '04

... any ideas to that problem from march?! till now not one answer :-( helge. ----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM ----- Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall(a)suse.com PM cc Subject autoyast and loadorder of modules hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge.

3 4

how is the extra_prov file made
by Richard Bos 10 Jun '04

10 Jun '04

I wonder how the EXTRA_PROV files is being made, that is required by create_package_descr? Another thing I would like to know is why the information is actually needed by create_package_descr or is it YPM that needs this information? How does the information influence the behaviour of YPM? I understand that it could be needed as e.g: # rpm -q --whatprovides /bin/sh bash-2.05b-96 bug the other way around does not work: # rpm -q --provides bash (I would expect /bin/sh here) Is EXTRA_PROV made manually? Also in 9.1 the rpm kdebase3-SuSE provides an EXTRA_PROV too. This one and the one in suse/setup/description are rather different. Is this intended? Why not use the Provides tag in the rpm to store this information and use that?? It would be easy for suse rpm contributors to support this too => Would that make it easier to provide yast enabled rpm repositories? -- Richard Bos Without a home the journey is endless

4 4

RE: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same P roblem in 9.1
by discip＠pjm.com 10 Jun '04

10 Jun '04

This doesn't seem to help. I tried both netsetup=0 and netsetup=-dhcp. Now pops up a window and tells me "your network has already been configured. Do you want to keep this configuration?". Then when I say yes, it tries to DHCP again. :-( Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, June 09, 2004 12:03 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same Problem in 9.1 This is something new in 9.1/SLES9. Add netsetup=0 to skip DHCP. 3. Advanced Network Setup The netsetup keyword allows advanced network configurations and enables dialogs to setup the network where required. netsetup=1 the normal network setup questions netsetup=xxx,yyy just xxx and yyy netsetup=+xxx,-yyy default, additionally xxx, but not yyy xxx could have the following values: dhcp, hostip, gateway, netmask, nameserver. nameserverN asks for N nameservers (max. 4). For example, the following can be entered on the command line: netsetup=-dhcp,+nameserver3 discip(a)pjm.com wrote: > No matter what I do to the info file, I still can't get linuxrc to not > try to do dhcp on eth0. I look at console number 2 and I see that it > has even configured eth0 with the right IP parameters, but it tries to > do DHCP anyway. I am trying this with 9.1 now. Same behavior. What > gives? > > Paul > > P.S. If you care, my info file looks like this: > > insmod: 3c59x > netdevice: eth0 > DHCP: 0 > HostIP: 192.168.1.5 > netmask: 255.255.255.0 > gateway: 192.168.1.1 > server: 192.168.1.18 > autoyast: nfs://192.168.1.18/opt/Linux/SUSE-9/profiles/test.xml >

2 1

Patterned installs
by Jesse Pretorius 09 Jun '04

09 Jun '04

Hi to all, Thank you for the help with the previous request - I have come quite a way since then. I'd like to know if it's possible to use the existing patterned installations provided in the distribution. Eg SUSE LINUX Desktop has an 'Enterprise Template' and 'GNOME Desktop' pattern. I'd like to use these as the basis for my software selection and make some minor modifications. Any insight would be appreciated. Jesse

1 0

RE: How Do I Get Rid Of DHCP!!?! -- Same Problem in 9.1
by discip＠pjm.com 09 Jun '04

09 Jun '04

No matter what I do to the info file, I still can't get linuxrc to not try to do dhcp on eth0. I look at console number 2 and I see that it has even configured eth0 with the right IP parameters, but it tries to do DHCP anyway. I am trying this with 9.1 now. Same behavior. What gives? Paul P.S. If you care, my info file looks like this: insmod: 3c59x netdevice: eth0 DHCP: 0 HostIP: 192.168.1.5 netmask: 255.255.255.0 gateway: 192.168.1.1 server: 192.168.1.18 autoyast: nfs://192.168.1.18/opt/Linux/SUSE-9/profiles/test.xml

2 1

PXE-based autoinstallation setup
by Jesse Pretorius 09 Jun '04

09 Jun '04

> Hi to all, > > I'm busy trying to setup a PXE-based auto-installation of SUSE LINUX > Desktop. > > Part of the instructions indicate that I should have 'initrd', > 'pxelinux.0', and 'linux' in the /tftpboot/ directory, and that I should > be able to find 'initrd' and 'linux' in the /suse/images/boot directory of > any of the SLES CD's. > I didn't find them there - I did find them in /boot/loader though. Are > these the same files that I need? > > Also, I don't seem to find 'pxelinux.0' anywhere. can someone point me to > it, or if I need to build it can you please point me to a helpful > resource? > > Thanks, > > Jesse

3 2

AW: [suse-autoinstall] PXE-based autoinstallation setup
by Martin.Linten＠rzf.fin-nrw.de 09 Jun '04

09 Jun '04

Hi Jesse, The file pxelinux.0 is part of the syslinux package. (.rpm) The files linux and initrd can be found in /boot/loader. These are the correct files. I think the Docs http://www.suse.de/~nashif/autoinstall/ quite helpful. Greetings, Martin -----Ursprüngliche Nachricht----- Von: Jesse Pretorius [mailto:preycor@myrealbox.com] Gesendet am: Mittwoch, 9. Juni 2004 17:40 An: SUSE LINUX Auto-installation List Betreff: [suse-autoinstall] PXE-based autoinstallation setup > Hi to all, > > I'm busy trying to setup a PXE-based auto-installation of SUSE LINUX > Desktop. > > Part of the instructions indicate that I should have 'initrd', > 'pxelinux.0', and 'linux' in the /tftpboot/ directory, and that I should > be able to find 'initrd' and 'linux' in the /suse/images/boot directory of > any of the SLES CD's. > I didn't find them there - I did find them in /boot/loader though. Are > these the same files that I need? > > Also, I don't seem to find 'pxelinux.0' anywhere. can someone point me to > it, or if I need to build it can you please point me to a helpful > resource? > > Thanks, > > Jesse

1 0

How Do I Get Rid Of DHCP!!?!
by discip＠pjm.com 09 Jun '04

09 Jun '04

1 0

Re: [suse-autoinstall] nfs timeouts?! client or server specific?!
by Helge Koehn 09 Jun '04

09 Jun '04

this would be technical possible but it's not an answer to my question! (i don't wanted a workaround i wanted a solution!) imagine a situation where ftp or http protocol are not the allowed choice and you have to use nfs ... ;-) helge. Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc Subject Re: [suse-autoinstall] nfs timeouts?! client or server specific?! http? ftp? Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz(a)computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. Helge Koehn <koehn(a)de.ibm.com> on 09.06.2004 11:52:27 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] nfs timeouts?! client or server specific?! -------------------------------------------------------------------------- hi mailinglist, we have setup an autoyast environment which serves the installation data via nfs. we are facing the situation that some clients can't connect to the nfs-server (others do), the automatic installation process wents back to the manual installation menu. if we choose there network install and as source nfs the client find its way and can connect to the nfs install server, the installation starts and a "half automatic" installation goes on. how can we be sure that the client also connects to the nfs-server without going through the menu by hand?! are there any possible settings or parameters for the nfs-server or the client to change, may be timeout values or something like that?! thanks for answers. :-) helge. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com COMPUTACENTER (UK) LTD The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Computacenter information is available from http://www.computacenter.com This footnote also confirms that this email message has been swept for the presence of computer viruses. ***************************************************************************************************************************

1 0

Is there any way to refer the "info" file when install the SLES9?
by You, Yongkang 09 Jun '04

09 Jun '04

Hi all, I am now trying to automatically install the SLES9 by NFS with PXE booting or using SLES9 CD1 booting. There is an antoyast control file. It can be rightly used to auto-install the SLES9. But before auto-installation, it always jumped into manually installation. It said that it didn't found the installation source. Then I have to manually set the machine's IP address, IP mask, the network Gateway and NFS server etc. to locate the NFS installation source. I think there is an "info" file can help to locate them. Then the auto-installation process can skip the manual NFS server configuration. I also create a linuxrc configuration file "info" by the reference guide. But I don't know where I can put it, because our machines haven't any floppy. I have put it in the NFS with ramdisk or in the /rftproot. It seems to be useless. :-( Anybody can help me? I need know where to put the "info" file except in the floppy. And how can I refer it to Yast2 when installation. Thank you very much! Regards, You, Yongkang( Kangkang )

1 0

nfs timeouts?! client or server specific?!
by Helge Koehn 09 Jun '04

09 Jun '04

hi mailinglist, we have setup an autoyast environment which serves the installation data via nfs. we are facing the situation that some clients can't connect to the nfs-server (others do), the automatic installation process wents back to the manual installation menu. if we choose there network install and as source nfs the client find its way and can connect to the nfs install server, the installation starts and a "half automatic" installation goes on. how can we be sure that the client also connects to the nfs-server without going through the menu by hand?! are there any possible settings or parameters for the nfs-server or the client to change, may be timeout values or something like that?! thanks for answers. :-) helge.

1 0

fstopt option for lvm?
by Kohrs, Steven 08 Jun '04

08 Jun '04

Is there anyway to specify fstopt options when defining a LVM volume under a SLES8 autoinstall?

1 0

Re: [suse-autoinstall] Reboot in a post-script?
by Hubertus Haniel 05 Jun '04

05 Jun '04

Yes the permeissions will make a difference I belive. I have a chmod 700 right after the creation of the script in the postinstall script. Regards Hubba On Fri, 4 Jun 2004, Peter A. Schwenk wrote: > Date: Fri, 4 Jun 2004 22:00:42 -0400 > From: Peter A. Schwenk <schwenk(a)math.udel.edu> > To: Hubertus Haniel <hubba(a)unixcook.com> > Subject: Re: [suse-autoinstall] Reboot in a post-script? > > I've tried various permutations of Roy Butler's solution, and I have > yet to get it to work. I've tried putting the script in both > /etc/init.d/rc3.d and /etc/init.d/rc5.d, and in both cases the script > doesn't run (or doesn't cause a reboot). I even tried making a > pre-script write a reboot script into these directories, and it still > did not cause a reboot. The only thing I can think of is that the > script didn't have execute permissions, but I don't think that matters. > > On Jun 4, 2004, at 3:33 PM, Hubertus Haniel wrote: > > > > > > > > > I can confirm that Roy's solution works very well - I have used this > > for > > all my SLES8 deployments and I have done a lot of them. Rebooting at > > the > > end of a post scripts can cause grief if you have a lot of them and not > > just one. > > > > Best regards > > Hubba > > > > > > > > On Fri, 4 Jun 2004, Anas Nashif wrote: > > > >> Date: Fri, 04 Jun 2004 15:18:58 -0400 > >> From: Anas Nashif <nashif(a)suse.de> > >> To: suse-autoinstall(a)suse.com > >> Subject: Re: [suse-autoinstall] Reboot in a post-script? > >> > >> rebooting in postscripts should be OK if you run SuSEconfig before > >> rebooting. Usually SuSEconfig is the last thing run after the post > >> scripts are executed. > >> The solution belwoe might also be a good idea, did not test it though. > >> Alternative is to schedule a reboot using atd :-) > >> > >> Anas > >> > >> Roy Butler wrote: > >>> Peter, > >>> > >>> I'm not positive, but I think it may be a problem. What I believe > >>> would > >>> work in any case would be to create a post-script like so: > >>> > >>> ---------- > >>> > >>> #!/bin/sh > >>> > >>> cat /etc/init.d/rc3.d/S99reboot << EOF > >>> > >>> #!/bin/sh > >>> rm /etc/init.d/rc3.d/S99reboot > >>> reboot > >>> > >>> EOF > >>> > >>> ---------- > >>> > >>> > >>> Good luck, > >>> Roy > >>> > >>> > >>> Peter Schwenk wrote: > >>> > >>>> Hello: > >>>> > >>>> I am using autoyast w/ SuSE 9.0, and I was wondering if it is a bad > >>>> idea to reboot the system at the end of a post-script? Are there > >>>> steps after the post-script that would be skipped? I'm doing an > >>>> online_update in the post-script, and I would like to make sure that > >>>> the system comes up with the new kernel. Thanks in advance for your > >>>> help! > >>>> > >>>> -- > >>>> - Peter A. Schwenk | Mathematical Sciences > >>>> - schwenk(a)math.udel.edu | University of Delaware > >>>> - (302) 831-0437 | Newark, DE 19716-2553 USA > >>>> > >>>> > >>> > >>> > >> > >> > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > -- > - Peter Schwenk > - peterschwenk(a)comcast.net > - '79 SF >

1 0

Problems with SuSE SLES 9 -beta 6
by Joachim.Tork＠gad.de 05 Jun '04

05 Jun '04

Hi, I have got the problem that linuxrc in SuSE SLES 9 beta 6 always starts a network configuration with dhcp. I am only able to get beyond this point by pushing the ESC key. Then the second initrd is being loaded, yast starts and the automatic installation goes on ... I am using the following Kernel parameters ( with isolinux) append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd instusedhcp=0 textmode=1 Does anybody know Does anybody know how to avoid the dhcp thing ? The second thing I am wondering about is that in SLES 9 there is no such tool like create_package_descr to keep the package description files upto date ? Best regards Joachim

2 1

Mount From a Post-Install Script...
by Roy Butler 04 Jun '04

04 Jun '04

Autoinstall gurus, I'm trying to mount an NFS share from a post-install script and it's failing with the error "mount: only root can do that". I threw a call to id in the script and it reports "uid=0(root) gid=0(root)", so I'm a little baffled. The mount can be performed manually during the install or after completion with no problem. Here's the relevant part of my XML configuration file (server IP faked): -------------------- <![CDATA[#!/bin/sh mkdir /mnt/resources id mount 1.2.3.4:/autoinst/SuSE9.0 /mnt/resources for MYSCRIPT in /mnt/resources/scripts/generic/A*; do $MYSCRIPT done > /var/adm/autoinstall/logs/generic.log 2>&1 umount /mnt/resources]]> -------------------- Does anybody have an idea what the issue could be? I need it to happen after the RPM installs. I suppose I could throw this in a one-time rc script, but I'd like to understand the underlying issue... Thanks, Roy

4 11

Reboot in a post-script?
by Peter Schwenk 04 Jun '04

04 Jun '04

Hello: I am using autoyast w/ SuSE 9.0, and I was wondering if it is a bad idea to reboot the system at the end of a post-script? Are there steps after the post-script that would be skipped? I'm doing an online_update in the post-script, and I would like to make sure that the system comes up with the new kernel. Thanks in advance for your help! -- - Peter A. Schwenk | Mathematical Sciences - schwenk(a)math.udel.edu | University of Delaware - (302) 831-0437 | Newark, DE 19716-2553 USA

4 3

Aw: Re: [suse-autoinstall] textmode
by joerg.ranff＠arcor.de 04 Jun '04

04 Jun '04

Hi, > -> have you removed / commented these lines: > framebuffer 1 > gfxboot bootlogo thank you very much for your help. Kind regards, Joerg

1 0

textmode
by joerg.ranff＠arcor.de 04 Jun '04

04 Jun '04

we are currently in the process of preparing an autoyast based installation for hp proliant servers and we would like to control the installation by the ILO management console that accesses the bios console via a browser based interface. For this to work, the installation has to stay in textmode and not switch to framebuffer based display since that doesn't work with the ILO interface. When booting an installation CD this can be achieved with a parameter textmode=1 in isolinux.cfg, however when yast running in textmode starts the linux kernel, it switches to framebuffer display. It would be necessary to have some kind of configuration option that can be set to force textmode in the kernel boot process, but we didn't find such an option. When the installation process is started without the option textmode=1, setting textmode in the option screen by pressing F2 everything works, i.e. the kernel boots in textmode as well, but since the default option is booting in framebuffer mode, this is not useful. We would appreciate any pointers how this can be done. TIA

1 0

Re: [suse-autoinstall] Mount From a Post-Install Script...
by Roy Butler 03 Jun '04

03 Jun '04

Damien, I'm using SuSE 9.0 Intel. I might give this a try, but that fact that I can run it manually w/o the "-t nfs" makes me wonder... This might all end up going in a post-YaST2.firstboot start-up script. :) Roy damien.selles(a)eu.effem.com wrote: > Hi, > > Could you try "/bin/mount -t nfs" instead of "mount" ? > > you can also insert a "which mount" > .... I am not completely sure.. but I think it has something to do with > the path that are not all set. > > As far as I am concerned... the nfs mount works fine during the post > install when I use the /bin/mount -t nfs .... > > BTW... which version of SUSE are you using? > > Hope this can help. > > Regards, > Damien. > > Inactive hide details for Roy Butler <roy.butler(a)jpl.nasa.gov>Roy Butler > <roy.butler(a)jpl.nasa.gov> > > > > > > Roy Butler <roy.butler(a)jpl.nasa.gov> > jpl.nasa.gov > > 03/06/2004 03:37 > > > > Inactive hide details for To: suse-autoinstall > > > To: > > cc: > > > Subject: > [suse-autoinstall] Mount From a Post-Install Script... > > > Autoinstall gurus, > > I'm trying to mount an NFS share from a post-install script and it's > failing with the error "mount: only root can do that". I threw a call > to id in the script and it reports "uid=0(root) gid=0(root)", so I'm a > little baffled. The mount can be performed manually during the install > or after completion with no problem. Here's the relevant part of my XML > configuration file (server IP faked): > > -------------------- > > <![CDATA[#!/bin/sh > > mkdir /mnt/resources > > id > > mount 1.2.3.4:/autoinst/SuSE9.0 /mnt/resources > > for MYSCRIPT in /mnt/resources/scripts/generic/A*; do > $MYSCRIPT > done > /var/adm/autoinstall/logs/generic.log 2>&1 > > umount /mnt/resources]]> > > -------------------- > > Does anybody have an idea what the issue could be? I need it to happen > after the RPM installs. I suppose I could throw this in a one-time rc > script, but I'd like to understand the underlying issue... > > > Thanks, > Roy > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > -- Roy Butler - MIST Development Environment Jet Propulsion Laboratory email: roy.butler(a)jpl.nasa.gov phone: 818-354-8825

1 0

SLES8 + SP3 Autoinstall
by Frank Samuel 03 Jun '04

03 Jun '04

Hi, I've done an autoinstall for SLES8 through network succesfully and hope to make autoinstall for SLES8 + autoinstall work. I remember sometime ago there is an example on how to set up do an autoinstall for SLES8 + SP3. http://www.suse.de/~nashif/autoinstall/faq.html But it is no longer there now. Could someone sucessfully installed SLES8 + SP3 provide some instructions. Another thing when I copy stuff from SP3 CD1, I used "cp -av" but met a problem of "cp: will not create hard link ..../UnitedLinux/1.0/patches(rpm) to dir .../SuSE-SLES/8/pacthes(rpm)" So how should I do the copy? Thanks. Xuehua Chen __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/

2 1

YaST2: Problem defining a new Inst. source
by MANU 02 Jun '04

02 Jun '04

Hello: I'm trying to create an installation source from YaST2 (Control Center -> Software -> Change Instalation Source) I fill in the window: Protocol: FTP Server Name: ftp.suse.com/pub/suse (I've also tried with ftp.suse.com alone to no avail) Server Directory: i386/9.0/suse/src/ Authentication: Anonimous (I've also tried without it) I accept and after a while (adding installation source...) a meessage emerges: "Couldn't create an installation source from the URL 'ftp://ftp.suse.com/pub/ suse/i386/9.0/suse/src' Details: ERROR(InstSrc:E_no_instsrc_on_media) Try again?" I've checked that the server is in "/var/lib/YaST2/you/youservers". Where should I look into? Thanks in advance.

2 1

sles8sp2 ftp/smb installation
by Martin.Linten＠rzf.fin-nrw.de 01 Jun '04

01 Jun '04

Hi list, hi Anas! I set up an installation server with sles8sp2. Installing via nfs succeeds: Both - the root-cramfs-file and the installation source - are recieved and used by the client. But installing from the same source via smb://server/sles8sp2 or via ftp://server/sles8sp2 is different: The root-file works without problems, but I get the following error about the software selection: "Fehler bei der Konfiguration der Software-Auswahl. Bitte erneut versuchen." In the log-files I see that YaST2 tries to find my software selection ("default") but cannot find it. My pxelinux.cfg file looks like this: DEFAULT Installation_SUSE_SLES8sp2 LABEL Installation_SUSE_SLES8sp2 KERNEL linux.sles8sp2 APPEND initrd=initrd.sles8sp2 ramdisk_size=65536 autoyast=http://x.x.x.x/yast2/ install=ftp://x.x.x.x/sles8sp2 instmode=ftp username=anonymous password=egal I modified the tags <init> and <info_file> in the xml-file according to the pxe-config. Please give me any hints/suggestions! Thanks a lot, Martin

1 0

SuSE 9.1 autoinstall ISO
by Radu Voicu 01 Jun '04

01 Jun '04

Hi! I have this issue: I used to make auto-install customized CD's for every SuSE version since 8.2, but now I can't find the "build ISO image" menu / button on Autoyast2, in SuSE 9.1 :( Please help!

1 0