January 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] example for sles8 + sp3 install server setup?
by Joachim Jordan 02 Feb '04

02 Feb '04

Hi everyone, it works for me to it that way. I added the SP3 just as another source to the installation tree. Here is my script i'm using to setup the distribution: ------------------------------------------------------- #!/bin/sh # Script to setup SLES netinstall source if [ $# -lt 1 ] then echo "Please provide the path of the new driver as parameter!" exit 1 fi cd $1 # check if in correct directory! if [ ! -f suse/CD1/content ] then echo "Error: Looks like wrong directory!" exit 1 fi # remove previous configurations if [ -d yast ] then rm -r yast fi if [ -d boot ] then rm -r boot fi if [ -d media.1 ] then rm -r media.1 fi if [ -f content ] then rm content fi if [ -f driverupdate ] then rm driverupdate fi # Now we have to move some data around to make this # a multiple source directory # # first we copy the order directory described above. mkdir yast cp suse/CD1/content yast/ cp suse/CD1/content . # Then the boot directory with the installation image cp -a suse/CD1/boot . # The content file and the media directory cp -a suse/CD1/media.1 . if [ -f media.1/info.txt ] then rm media.1/info.txt fi # Now we copy the description files from SLES to the order directory as # described earlier. mkdir -p yast/suse/suse/setup/descr cp -a suse/CD1/suse/setup/descr yast/suse/suse/setup cp suse/CD1/content yast/suse/ cp -a suse/CD1/media.1 yast/suse/ cp -a suse/CD2/media.2 yast/suse/ cp -a suse/CD3/media.3 yast/suse/ # Same applies for supplementary mkdir -p yast/sup/suse/setup/descr cp -a supplementary/CD1/suse/setup/descr yast/sup/suse/setup cp supplementary/CD1/content yast/sup/ cp -a supplementary/CD1/media.1 yast/sup/ cp -a supplementary/CD2/media.2 yast/sup/ # Do the same for Service Pack 3 mkdir -p yast/sp3/suse/setup/descr cp -LRp sp3/CD1/suse/setup/descr yast/sp3/suse/setup cp sp3/CD1/content yast/sp3/ cp -a sp3/CD1/media.1 yast/sp3/ cp -a sp3/CD2/media.2 yast/sp3/ # overwrite the old file in the boot directory with new ones cp -a sp3/CD1/boot . # copy driverupdate file cp sp3/CD1/driverupdate . # Do the same for Addons mkdir -p yast/ad/addons/setup/descr cp -a Addons/addons/setup/descr yast/ad/addons/setup cp Addons/content yast/ad/ cp -a Addons/media.1 yast/ad/ # We are almost done.. # Now we'll adapt the order files. # Fields of the order files are TAB delimited cat << EOF > yast/order /yast/ad Addons /yast/sp3 sp3/CD1 /yast/suse suse/CD1 /yast/sup supplementary/CD1 EOF cat << EOF > yast/instorder /yast/sup /yast/suse /yast/sp3 /yast/ad EOF # final stuff #cp ../Code/root/root.neu boot/root chown -R wwwrun:nogroup . # End ------------------------------------------------------------------- I even added another source for my own packages. For that i reused the content and media.1 files from the SLES distribution and changed them. I'm using HTTP as installation protocol and this is for an Power PC based installation for JS20 blades. But it is more or less the same for Intel. Just one thing about the SP3, to get all the Yast fixes included in the installation process( for example necessary for HTTP support, HTTP is broken in the SLES8 and fixed with the code in the SP3), you have to copy the driverupdate file to the root of your new multi source distribution(or if you use NFS, you can also copy the subdirectory containing all from the CD to the root). For me, the driverupdate file does not work. If i use it, yast dies in the middle of the installation with an segfault. If i copy all files from the driverupdate file into the root file manually, it works. 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 Hal Wine <hal(a)reactivity.c To: suse-autoinstall(a)suse.com om> cc: Subject: [suse-autoinstall] example for sles8 + sp3 install server setup? 13.01.2004 18:32 Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3? I followed Anas' example laytout for my original installation server setup. I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source. If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct? Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs. Thanks, --Hal -- 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] BUG: SP3 CD: boot options only 180 chars
by Ness, Todd 30 Jan '04

30 Jan '04

Try using an info file. http://www.suse.de/~nashif/autoinstall/faq.html -----Original Message----- From: Hans Kamm [mailto:hans753@hotmail.com] Sent: Friday, January 30, 2004 11:42 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] BUG: SP3 CD: boot options only 180 chars Hi, I had the idea to start installation via nfs, but there is a big Problem! boot options max length ist 180 chars (-instllation word = 168 chars) Ever tried to set such a boot option: boot options: netdevice=eth0 ip=192.168.1.210 netmask=255.255.255.0 gateway=192.168.1.1 insmod=pcnet32 autoyast=nfs://192.168.1.135/data-dir/linux/sles8/profiles/ install=nfs://192.168.1.135/data-dir/linux/sles8/ The Instllation will not start, it doesn' t find the NFS installserver (the install-server is set to: 192.168.1 the rest is missing) This is probably not the right mailing list? I' m still waiting for SP4 Hans _________________________________________________________________ Schützen Sie Ihren Posteingang vor unerwünschten E-Mails. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt Hotmail-Junk-Filter aktivieren! -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

BUG: SP3 CD: boot options only 180 chars
by Hans Kamm 30 Jan '04

30 Jan '04

Hi, I had the idea to start installation via nfs, but there is a big Problem! boot options max length ist 180 chars (-instllation word = 168 chars) Ever tried to set such a boot option: boot options: netdevice=eth0 ip=192.168.1.210 netmask=255.255.255.0 gateway=192.168.1.1 insmod=pcnet32 autoyast=nfs://192.168.1.135/data-dir/linux/sles8/profiles/ install=nfs://192.168.1.135/data-dir/linux/sles8/ The Instllation will not start, it doesn' t find the NFS installserver (the install-server is set to: 192.168.1 the rest is missing) This is probably not the right mailing list? I' m still waiting for SP4 Hans _________________________________________________________________ Schützen Sie Ihren Posteingang vor unerwünschten E-Mails. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt Hotmail-Junk-Filter aktivieren!

1 0

SuSE 9 and clone function
by Harald.Milz＠computacenter.com 30 Jan '04

30 Jan '04

Hi, I was looking for the "clone this system" function in autoyast2 on SuSE 9. I've used it a couple of times on SLES8 but I can't seem to find it on SuSE 9. Is it just me or is it actually missing? 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.

2 1

searchable mailing list archive available [was Re: Problems customizing an install CD]
by Robert Pollak 30 Jan '04

30 Jan '04

I found a searchable archive of this list at <http://marc.theaimsgroup.com/?l=suse-autoinstall>. The list FAQ also mentions Google: Prepend your search by "autoinstall site:lists.suse.com" (without quotes). The searchable archive at <http://www.netsys.com/#l#/index.html>, which is mentioned in the FAQ, is temporarily unavailable since 2003-10-07.

2 1

Some bugs in AY2/SuSE 9.0
by Frank Steiner 30 Jan '04

30 Jan '04

Hi Anas, I'm using autoyast2 with SuSE 9.0. Here are some bugs that I found: - According to the dtds I cannot use classes anywhere. And indeed, wherever I tried to include classes, the xml validation failed, even when validating a profile generated with yast2. - When you specify lilo as boot loader but lilo is not in the software selection, no warning is issued, but the installation will hang after installing the packages with "creating initrd..." when configuring the bootloader. - The boot-loader device is ignored. On a host with /dev/hda and /dev/sda (via gdth module), I specified a partition table for /dev/sda and also <bootloader> <loader_device>/dev/sda</loader_device> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> Although the loader_device line made it into the final xml file (checked during and after install), the installation ends up with boot=/dev/hda in /etc/lilo.conf which prevented the system from booting. You can get the log file from the installation here: http://wwwtest.bio.informatik.uni-muenchen.de/tmp/y2log-1 Some errors in the online documentation for 9.0: - Section 4.2 Reporting: - order should be errors/messages/warnings to match dtd - order within these should be log/show/timeout At least my sgml validator tells me. I don't know if there is some relaxed xml which allows arbitrary ordering of elements on the same level. - 4.1: mouse specifies wrong id and an element device. Due to dtd, should only be id. - 4.3: - kernel_parameters is not defined as part of bootloader element in dtd - order should be: device, type, location - initrd_modules uses module_entry instead of initrd_module, module_args is not opened - 4.5.2: When adding your own packet selection, one needs to add the name in the suse/setup/descr/selections file, not just copy the selection there. At least that was necessary for me, otherwise autoyast would complain that it could not read from my selection... Hope this helps :-) Best regards, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Phone: +49 89 2180-4049, Fax: -4054 LMU, Amalienstr. 17 http://www.informatik.uni-kiel.de/~fst/ 80333 Muenchen, Germany * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

Problem with selection file
by steven.cardinal＠adheris.com 30 Jan '04

30 Jan '04

I have tried creating this selection file in order to include the Samba3 rpms in my autoinstall: =Ver: 3.0 =Sel: Samba3 9.0 =Siz: 35448056 70000000 =Sum: Samba3 =Req: Minimal =Cat: addon =Vis: true =Ord: 01 +Ins: samba3 samba3-client samba3-winbind samba3-doc libsmbclient libsmbclient-devel -Ins: The docs don't say how to include it, but I tried using the 'Import' option and chose the .sel file - but it gave me an error "Error loading package list from /SUSE9/suse/setup/descr/Samba3.sel" I am also unable to load any of the .sel files included on the CDs, so I can't determine if my format is wrong. I placed the needed rpms in /SUSE9/suse/i586 The docs really didn't say what the 'Siz:' statement is for (some of the included .sel files do not use it). I assume it is to ensure that there is adequate space to copy the RPMs (the first field, I added the size of each of my files together) and perhaps enough space to install the software? (assume we can just put a ballpark guess) Any ideas?

2 2

Re: [suse-autoinstall] Server without VGA graphics card - how to convince BIOS to continue booting
by Carl Peto 30 Jan '04

30 Jan '04

We cannot have a PCI graphics card because the box has only one PCI slot (and one AGP slot but we don't want to spend money just to get an AGP card for this server that will never be used) and that is needed for the RAID card. Interestingly enough your point about kernel panics - I've had quite a few and invariably the VGA doesn't work either, especially if the console has X running - completely hopeless in that case. In my experience, when the kernel kills scheduling (as it often seems to do if there's a misbehaving driver), only the SysRq mechanism does anything. I'd hoped that a serial console was the way out of that, so I could at least get proper oops messages to feed to ksymoops. Anyway we plan to run either Win 2003 Server or a very, very stable install of SuSE 8.2 on this box so kernel instability should not occur. The openbios project sounds interesting - my business partner and I were hoping that there might be something like that around, I'll look into that. Thanks for your help Simon and Frank. Carl Peto Linux Administrator Bookman Associates ----- Original Message ----- From: "Simon Thornton" <simon.thornton(a)swift.com> To: "'Carl Peto'" <carl(a)bookmanassociates.com> Sent: Friday, January 30, 2004 9:24 AM Subject: RE: [suse-autoinstall] Server without VGA graphics card - how to convince BIOS to continue booting > Hi Carlo, > > On some systems it is possible to disable the graphics card in the bios, > but for many you will get an error if it is removed. There is no harm in > leaving a card in, you don't have to connect anything to it. What I do > is get an old PCI card (5-$10) with limited capabilities and put that > in, I can then re-use the graphics card elsewhere. > > Overall, having the card maybe a life saver if there is a problem with > the system, you can then connect a monitor to see what the problem was. > A classic would be if there was a kernel panic/BSoD event; you r serial > console would be inoperative. Unlike Solaris machines, where the console > is always active, the PC requires a working OS to drive the serial port. > > One other thought, the linux bios project (also the openbios project) > have a replacement for the conventional BIOS. One feature of this is > serial console access at boot up. I've never tried this but it maybe > worth a look. > > Rgds, > > Simon > > ----- Original Message ----- From: "Frank Steiner" <fst(a)bio.informatik.uni-muenchen.de> To: "Carl Peto" <carl(a)bookmanassociates.com> Sent: Friday, January 30, 2004 9:08 AM Subject: Re: [suse-autoinstall] Server without VGA graphics card - how to convince BIOS to continue booting > As far as I know, you cannot boot a PC-base computer without a graphics > card. It considers a graphics card as essential as e.g. memory. > > cu, > Frank > -- > Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de > Lehrstuhl f. Bioinformatik Phone: +49 89 2180-4049, Fax: -4054 > LMU, Amalienstr. 17 http://www.informatik.uni-kiel.de/~fst/ > 80333 Muenchen, Germany > * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * >

1 0

Server without VGA graphics card - how to convince BIOS to continue booting
by Carl Peto 29 Jan '04

29 Jan '04

We have a server that, for convoluted reasons, we are interested in running without any graphics cards. It is accessed purely over the network and needs no console input. Nevertheless I have read the Serial-Console documentation and am able to configure a Linux server to output all LILO and kernel messages to a dumb terminal on the serial port plus even allow root logins on that dumb terminal for administration purposes. Our Linux server will work fine like this, without a screen and it means we can tuck it in the corner and forget about it, which is nice! :) However the problem is that we want to remove the graphics card. When we do so the server seems to no longer boot. I can only assume that the BIOS is complaining (on a non-existant display?!?) and won't boot without at least a VGA graphics card. Does anyone have any experience of this annoying problem and could they give us some help? Regards, Carl Peto

1 0

Problems customizing an install CD
by steven.cardinal＠adheris.com 29 Jan '04

29 Jan '04

I'm new to both SuSE and Autoyast. I've read through the autoinstall docs on the Suse site and find that I don't seem to know enough about autoyast in the first place to figure out what they are telling me. Here's what I've done and the problems I am having: I created a directory /SUSE9 and copied (cp -a /mnt/* /SUSE9/) all 5 CDs into this directory. I setup Yast to use this as a repository (I already used Yast update to patch this machine, so my yast utilities should be the latest available). I found that, using the GUI to select my source directory, if it appends a trailing / to the path (/SUSE9/) - it is not seen as a valid source. Finally figured that out and got autoyast to see the directory as well. I created a config for a server I am building. I used the Minimal+X11 selection plus added dhcp and bind. I setup some user accounts, etc. Everything seemed fine (the disks on this compaq dl360 show as /dev/ida/c0d0 so I had to hand-edit my config file afterwards). I then chose to build an ISO based on this config. It said it found all the necessary files and created an iso file, which I burned to media. First problem I had was that the compaq seems to have acpi issues, so I had to boot the cd with "linux acpi=off". Is there a way to configure autoyast to add those parameters by default? This CD will be used to rebuild the system should it die for some reason (hard drive crash or something) - it would be easier to hand off to my support people if they had very few ways of generating problems ;-) Second, I had an error installing grub (in the config file I told it to use the MBR and to replace what is there) The error was 'File not found'. I chose to reconfigure and retry and it worked ok - not sure if this is a problem with this particular machine or in my config. Any ideas? Next, it rebooted and went to install packages, but it suddenly couldn't find most of my packages and started prompting me for CD2. Shouldn't the 'Create ISO' setup the necessary paths in the iso image so that it works? Is there something I have to configure elsewhere? Once I get past this I'll hack away at adding extra packages (samba3, etc). I haven't had any luck getting autoyast to recognize my custom .sel file (it can't open any of my CD-provided .sel files either, so I don't understand how it works) Also, autoupdate pulls down patch.rpm files. Is there a way to apply these to my source directory so that my final build cd is patched already? Thanks Steve Oh, is there any plan to make the mailing list archives searchable?

1 0

AutoYaST FAQ
by Anas Nashif 27 Jan '04

27 Jan '04

Hi, for your information, I have just started an FAQ section on http://www.suse.de/~nashif/autoinstall/. Currently with some questions and answers that have been posted here recently, but I will try to keep it up to date and any interesting issues on the mailinglist will be added. If you have any suggestion, please dont hesitate. Thanks, Anas

1 0

JDS - SLES8 issues
by Todd Ness 27 Jan '04

27 Jan '04

I have added a custom selection package used create_package_descr to update my suse/setup/descr files.When I go to manual selections I can see the package and the items inside it. But, when I add it to the autoinst.xml file I get an error that the selection can not be made. Also, the following 3 packages now get errors since runnign create_package_descr. gdm2.3.2.101 says it requires /sbin/nologin k_deflt2.4.19-345 says it requires /sbin/mk_initrd and /usr/sbin/wget is missing. yet when I check the rpms responsible for those files they are selected for install. Any clues on where to start to fix either issue? Todd Ness

1 0

Single Disk Network Install - Not Network Boot
by discip＠pjm.com 27 Jan '04

27 Jan '04

Hey, I am trying to do an NFS install and would really like to get everything I need to get this to work onto a single diskette (or CD if it's absolutely necessary). I'd like to just pop in a floppy, turn on the machine and have it boot, restart, and be ready to go. As it stands now, I have all the config setup (info file and autoinst.xml), but I need to swap 3 floppies first for modules and stuff. Can I get these all on a single disk? I can do this with Redhat's kickstart. Any help would be greatly appreciated as I will eventually need to hand this process off to some less informed individuals who I don't want to have to mess with lots of disks,etc. Thanks a lot, Paul

3 3

Package Repository problem
by no chance 27 Jan '04

27 Jan '04

Running SUSE 9 PRO I can't seem to find where to set the Package Repository path. 1.Starting autoyast with "yast2 autoyast" at the command line while logged in as root. 2.Have created clone.xml using Tools -> Create Reference Profile. 3.Trying to create ISO image using Tools -> Create ISO Image. 4.Get - Error Package database not found. 5.Next I go to File -> Preferences -> Repositories. The text in the left pane says "The package repository is where you have copied the SuSE CDs." But, there is no where to enter the path to the copies of the CDs. What am I missing? Thanks, Hudson --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it!

2 1

Installation with Suse 9.0 on Sata Drive
by Joe Compton 26 Jan '04

26 Jan '04

Hi folks, Anyway to install to hde (sata)? Install locks when it recognizes hde during kernel load. Thanks, Joe Compton

1 0

RE: [suse-autoinstall] Single Disk Network Install - Not Network Boot
by discip＠pjm.com 26 Jan '04

26 Jan '04

As per the Subject line, I am trying to do this without having to netboot. I cannot disclose the reasons for this in this forum. Thanks, Paul -----Original Message----- From: Harald.Milz(a)computacenter.com [mailto:Harald.Milz@computacenter.com] Sent: Monday, January 26, 2004 10:48 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Single Disk Network Install - Not Network Boot How about using a etherboot or netboot floppy? 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. suse-autoinstall-return-1561-harald.milz=computacenter.com(a)suse.com on 26.01.2004 15:00:46 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Single Disk Network Install - Not Network Boot -------------------------------------------------------------------------- Hey, I am trying to do an NFS install and would really like to get everything I need to get this to work onto a single diskette (or CD if it's absolutely necessary). I'd like to just pop in a floppy, turn on the machine and have it boot, restart, and be ready to go. As it stands now, I have all the config setup (info file and autoinst.xml), but I need to swap 3 floppies first for modules and stuff. Can I get these all on a single disk? I can do this with Redhat's kickstart. Any help would be greatly appreciated as I will eventually need to hand this process off to some less informed individuals who I don't want to have to mess with lots of disks,etc. Thanks a lot, Paul -- 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] Single Disk Network Install - Not Network Boot
by Harald.Milz＠computacenter.com 26 Jan '04

26 Jan '04

How about using a etherboot or netboot floppy? 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. suse-autoinstall-return-1561-harald.milz=computacenter.com(a)suse.com on 26.01.2004 15:00:46 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Single Disk Network Install - Not Network Boot -------------------------------------------------------------------------- Hey, I am trying to do an NFS install and would really like to get everything I need to get this to work onto a single diskette (or CD if it's absolutely necessary). I'd like to just pop in a floppy, turn on the machine and have it boot, restart, and be ready to go. As it stands now, I have all the config setup (info file and autoinst.xml), but I need to swap 3 floppies first for modules and stuff. Can I get these all on a single disk? I can do this with Redhat's kickstart. Any help would be greatly appreciated as I will eventually need to hand this process off to some less informed individuals who I don't want to have to mess with lots of disks,etc. Thanks a lot, Paul

1 0

Re: [suse-autoinstall] Can I write my Scripts in an own File
by Thomas Pangborn 23 Jan '04

23 Jan '04

Fabian, You will need to either create a customized package containing your new scripts or you will need to create a base postscript that hooks into the autoinst.xml and calls your collection of scripts you wish to run. There are many choices, Thomas S. Pangborn Linux Software Engineer "Lenz, Fabian" <Fabian.Lenz(a)telekom.de> 01/23/2004 01:53 AM To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Can I write my Scripts in an own File Hello! I don´t want to write my scripts in the autoinst.xml, I want to write the scripts in own files. But I don´t know if there is a way to do it. The scripts should be in an own directory on the CD. Fabian -- 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] How to apply SP3 to server copy of SLSS 8.0
by Thomas Pangborn 23 Jan '04

23 Jan '04

Tom, You will need to pull the contents from the SP3 CD and place them in a directory under your server dir. You will need to update the yast directory in your server dir to reflect this new addition. You will also have to update the order/instorder files under the yast directory as well. This will not get ALL of the packages installed from SP3, but it will grab most of them. In order to do this you will need to install a system by hand, apply SP3, clone the system look at the packages and compare against those in your original autoinst.xml file. These new additions or changes will be what you need to have a FULL SP3 update done with AutoYaST. I hope this helps, Thomas S. Pangborn Linux Software Engineer "Tom Davidson" <suse(a)nashwan.org> 01/22/2004 10:19 AM To: <suse-autoinstall(a)suse.com> cc: Subject: [suse-autoinstall] How to apply SP3 to server copy of SLSS 8.0 Hi, I've got CDs for SuSE Linux Standard Server 8.0, and SP3 CDs for the same. I have an autoyast server configured with the contents of the CDs on an NFS export, but I want to update the RPMs etc. to SP3. How do I do this? Is it just a case of copying the SP3 CDs contents over my server dir? Or does the SP3 CD completely replace in its entirety the original CDs? Tom PS. incidently, has anyone else been unable to get grub to correctly probe the disks on a HP Compaq DL360 G2? It just doesn't find any disks, and grub is completely fscked up so it won't boot. RedHat ES 3.0 works fine... -- 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] How to apply SP3 to server copy of SLSS 8. 0
by Jan.Albrecht＠bertelsmann.de 23 Jan '04

23 Jan '04

Hi Tom, > -----Original Message----- > From: Tom Davidson [mailto:suse@nashwan.org] > Sent: Thursday, January 22, 2004 4:20 PM > > > PS. incidently, has anyone else been unable to get grub to > correctly probe the disks on a HP Compaq DL360 G2? It just > doesn't find any disks, and grub is completely fscked up so > it won't boot. RedHat ES 3.0 works fine... We got the problem, that our DL380G3 wouldn't boot with just one cpu installed. After parsing "pci=noacpi" as an additional command to the boot loader it worked. SuSE says this is an IRQ Problem of the hardware design from HP. By the way: With a a second cpu the problem does not appear. Kind regards Jan

2 1

Can I write my Scripts in an own File
by Lenz, Fabian 23 Jan '04

23 Jan '04

Hello! I don´t want to write my scripts in the autoinst.xml, I want to write the scripts in own files. But I don´t know if there is a way to do it. The scripts should be in an own directory on the CD. Fabian

1 0

How to apply SP3 to server copy of SLSS 8.0
by Tom Davidson 22 Jan '04

22 Jan '04

Hi, I've got CDs for SuSE Linux Standard Server 8.0, and SP3 CDs for the same. I have an autoyast server configured with the contents of the CDs on an NFS export, but I want to update the RPMs etc. to SP3. How do I do this? Is it just a case of copying the SP3 CDs contents over my server dir? Or does the SP3 CD completely replace in its entirety the original CDs? Tom PS. incidently, has anyone else been unable to get grub to correctly probe the disks on a HP Compaq DL360 G2? It just doesn't find any disks, and grub is completely fscked up so it won't boot. RedHat ES 3.0 works fine...

1 0

Using autoyast to install with no documentation
by Togan Muftuoglu 22 Jan '04

22 Jan '04

Hi, Is there a way to create a custom ISO which will install without the documentation of the packages. Rebuilding the whole distro packages without the documentation is time and disk consuming. -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum

1 0

manipulating RPMS in package Selection Files
by Francois, Jean (J.L.) 21 Jan '04

21 Jan '04

I have created a set of custom selection files. In the "+Ins" section is my master list of packages. Appended in the "-Ins" are packages I no longer want to install. When I install via autoyast, the packages listed after "-Ins" still get installed and do not get removed. Is there a better/smarter/right way to accomplish this? PURPOSE: I have users that do not want certain packages installed. By creating lists of those packages and appending them to the known default list, I expect autoyast to either not install them or to remove them. Thanks. -- Jean L. Francois

2 1

RE: [suse-autoinstall] Auto-Update
by discip＠pjm.com 21 Jan '04

21 Jan '04

Do you have any suggestions for a system of this type? Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, January 20, 2004 10:13 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Auto-Update Hi, Where did you see this? No, autoyast is intended for installation only. Anas discip(a)pjm.com wrote: > While I am familiar with the autoinstall procedures, I thought I had > come across something about AutoYast being able to push out new > packages to managed hosts. Does anyone have any information about this? > > Thanks, > Paul > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

5 4

RE: [suse-autoinstall] Other OS installations
by Ness, Todd 21 Jan '04

21 Jan '04

So, does that mean that I need to get SuSE8.1 installed or Enterprise8 to get the proper autoyast interface? Or can I install some packages on my 9.0 server? Todd -----Original Message----- From: Raphael Goulais [mailto:raphael.goulais@eds.com] Sent: Wednesday, January 21, 2004 8:04 AM To: Ness, Todd Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Other OS installations Le mer 21/01/2004 à 15:36, Ness, Todd a écrit : > By manage I mean running autoyast2 to create and maintain the XML > files, and getting a hands off build of a workstation. AutoYast in JDS is a lower version than the AutoYast provided with SuSE 9.0. The changes in the file format can be an issue in this case. You can have some informations about the differences here : http://www.suse.de/~nashif/autoinstall/ Raphael

2 1

RE: [suse-autoinstall] Other OS installations
by Ness, Todd 21 Jan '04

21 Jan '04

Anas, By manage I mean running autoyast2 to create and maintain the XML files, and getting a hands off build of a workstation. The importing I was speaking of is in the autoyast2 tool doing package selection(Software->Package Selection) Trying to get the base selection from the JDS images I have copied on my hard drive, I was trying to get the GUI to see the JDS packages instead of SuSE9 packages. Thanks for looking at this. Todd -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, January 20, 2004 8:12 PM To: Ness, Todd Cc: 'suse-autoinstall(a)suse.com' Subject: Re: [suse-autoinstall] Other OS installations Ness, Todd wrote: > Hi, > I have a lot of experience using jumpstart and Solaris, just starting > at looking at SuSE autoyast2 for installing Sun-JDS (SuSE8.1 variant). > Is it possible to have a SuSE 9.0 server to manage the JDS installs? I > have read the majority of the HowTo's and documentation, I just am not > finding an answer. It depends how you define "manage". In general an installation server can be anything, even a windows machine can server as an installation server. > And when I try to import a package list from JDS software I get "Error > loading package list from /..." > Importing where? I dont understand what are you trying to do here. > Todd Ness > EDS - Platform Infrastructure Engineering Phone:+1-303-255-4530 > mobile : 303-263-2589 > pager mail: nessts(a)vtext.com >

2 1

Re: [suse-autoinstall] BitTorrent
by humvee 21 Jan '04

21 Jan '04

On Wed, 2004-01-21 at 04:08, aan agustiono wrote: > i've questions about this program. this program like imesh or kazza ? > i read in thats website this program not like kazza or imesh, but the > functions is the same, n more power full from imesh or kazza, so how > much port to open if we run this program. > I can only say that from a Windozze perspective I found the BT software easier to use....didn't add loads of spyware (as memory seems to remind me that Kazza certainly did). I don't know about imesh because i have never used it! I am afraid I cannot answer your question with regard porting as this is out of my knowledge area. Other than to say I think it just runs via the normal internet port. But hopefully someone else can help with that one!! humvee a n00b and proud of it > > > > Yes it is a peer to peer download process. I have used it on Windozzze > > but not on linux. > > > > There is a small file that you need to download which sits in the > > background of your machine and works automatically when you connect to > > one of the many sites that subsribe to Bittorrent. > > > On Fri, 2004-01-16 at 03:46, aan agustiono wrote: > > > anyone know about bittorrent, pls help, information, instalations, and > > > how to use about bittorent. > > > > > > Thanks > > > > > > Aan --

1 0

RE: [suse-autoinstall] Auto-Update
by Ness, Todd 21 Jan '04

21 Jan '04

There seems to be a fairly nice commercial tool Open Country that I have been investigating for pushing rpm packages and managing hosts remotely. Todd -----Original Message----- From: discip(a)pjm.com [mailto:discip@pjm.com] Sent: Wednesday, January 21, 2004 6:42 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Auto-Update Do you have any suggestions for a system of this type? Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, January 20, 2004 10:13 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Auto-Update Hi, Where did you see this? No, autoyast is intended for installation only. Anas discip(a)pjm.com wrote: > While I am familiar with the autoinstall procedures, I thought I had > come across something about AutoYast being able to push out new > packages to managed hosts. Does anyone have any information about this? > > Thanks, > Paul > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Other OS installations
by Ness, Todd 21 Jan '04

21 Jan '04

Hi, I have a lot of experience using jumpstart and Solaris, just starting at looking at SuSE autoyast2 for installing Sun-JDS (SuSE8.1 variant). Is it possible to have a SuSE 9.0 server to manage the JDS installs? I have read the majority of the HowTo's and documentation, I just am not finding an answer. And when I try to import a package list from JDS software I get "Error loading package list from /..." Todd Ness EDS - Platform Infrastructure Engineering Phone:+1-303-255-4530 mobile : 303-263-2589 pager mail: nessts(a)vtext.com

3 2

/dev/fd0 unknown fs type when trying to install from floppy
by Gunreben, Peter (Peter) 21 Jan '04

21 Jan '04

Hi, I'm currently trying to use autoyast (SuSE 9.0) for the first time. After creating the autoinst.xml, I've created a boot floppy and the modules1 floppy disk via yast2. Hence, I've copied the autoinst.xml into the root directory of the Modules1 floppy. When booting from floppy, I've selected the Installation and used "autoyast=floppy" in the boot parameters. Everything works fine until the installation procedure tries to find the configuration file. In console 3 it reports ... Hardware probing finished. floppy: /dev/fd0 /dev/fd0: unknown fs type got info from cmdline Automatic setup is not possible. ... As said before, this floppy is the Modules1 disk and was created using yast2. However, I can mount this floppy on another computer without any problems and I can read the content. Any ideas? Peter.

2 1

Auto-Update
by discip＠pjm.com 21 Jan '04

21 Jan '04

While I am familiar with the autoinstall procedures, I thought I had come across something about AutoYast being able to push out new packages to managed hosts. Does anyone have any information about this? Thanks, Paul

2 1

Post-install script question
by Mouncef_Belcaid＠blm.gov 21 Jan '04

21 Jan '04

Hi everyone, I was wondering if anyone has a sample post install script that will load a NIC module (bcm5700) and configure it to start on boot using DHCP. The DHCP server will be providing the hostname, domain name and resolv.conf info. Any help will be appreciated. Thanks, mb

2 1

is there a length limit on the line of parameters passed to isolinux.bin ?
by francois.blaes＠eu.effem.com 20 Jan '04

20 Jan '04

Hi all To perform AutoYAST installs, we use a custom boot CD based on the boot CD that ships with SLES8 SP2a The isolinux.cfg file has been tweaked to contain our standard install parameters (config and rpms repository, for instance) At the boot prompt, we append additional per-server parameters like the hostip, which makes the line even longer The install process works fine on some servers but fails on some others, noticeably on ones located on differnet subnets. Switching to the log displayed on tty3, we eventually found out that it fails when the line of parameters exceeds a certain length. The last characters are dropped, so the gateway IP is truncated and linuxrc fails of course to reach the repository Is this a known issue with isolinux ? What is the authorized length ? Is there a workaround ? Thanks in advance for your help. Francois BLAES ? Global Unix Team ? Mars ISI DDI *170 1639 ? Tel +33 (0) 3 88 05 16 39 ? Fax +33 (0) 3 88 05 16 79

3 3

Possible to install Suse Linux 8.1 with Suse Linux 9.0 autoyast?
by Kristian Köhntopp 20 Jan '04

20 Jan '04

Is it possible to PXE install Suse Linux 8.1 with a Suse Linux 9.0 autoyast installation? I have a vmware Suse Linux 9.0 ingeniously called "server" that has a copy the Suse Linux 8.1 CDs. I PXE boot a second vmware called "client", which shall be installed as a Suse Linux 8.1 system (with tons of addons). Possible? The Suse Linux 8.1 autoyast seems to be very much a work in progress and I'd rather use the 9.0 autoyast to do the install. Kristian

1 0

problem configuring network interface
by Duane Mari I. Deang 20 Jan '04

20 Jan '04

hi, i'm new to autoyast and did my first network autoinstall of suse8.2pro last week. everything went well except that no network interface was configured even if it was defined in the config file as follows: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>local</domain> <hostname>linux</hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth-pcmcia</device> <dhclient_set_down_link>yes</dhclient_set_down_link> <startmode>hotplug</startmode> <wireless>no</wireless> </interface> </interfaces> <modules config:type="list"/> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"/> </routing> </networking> after installation, i had to configure the pcmcia device by hand using normal yast. then everything was ok. i would appreciate any ideas as to why the network configuration was not done during the autoinstall. thanks, Duane Deang

1 0

typo in rules.dtd in SuSE 9.0
by Frank Steiner 20 Jan '04

20 Jan '04

Hi Anas, the rules.dtd on SuSE 9.0 (DVD version) specifies "hostadress" with one "d", while the docu and the yast2 module specify and expect hostaddress with two "d". cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

1 0

"Device not found"/ configuring/operating modem
by Chris Guillet 20 Jan '04

20 Jan '04

> I am having difficulty getting a Winmodem to be detected and operable, > running version 9.0. Here's the situation: 1. Using Sony VAIO, Intel Pentium II (former stock Windows 95 machine) 2. Removed Windows and all files prior to installing 9.0 3. No problems during auto-installation--used all suggested settings 4. 9.0 could not configure the Lucent winmodem 5. Downloaded the ltmodem rpm file through the ftp server (of SuSE) and installed with YaST2--no problems 6. Configured the modem with YaST--again, no problems 7. The auto-configure set the modem at: /dev/ttyLT0 8. I set up Internet settings after configuring modem 9. When I try to connect via KInternet, nothing happens; the log message says something like "No such device: /dev/ttyLT0. 10. I did verify using the bash shell that the file "ttyLT0" > is in fact located in /dev. Any suggestions? As you might tell, I am a relative novice. The SuSE support people got me this far but the winmodem isn't covered in support, so I must solve myself. Thanks in advance.

1 0

Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 19 Jan '04

19 Jan '04

I stopped getting that error after copying the DVD to the 8.2 directory using the same command mentioned below. I apologize for wasting everyone's valuable time. Thanks mb ----- Forwarded by Mouncef Belcaid/NIRM/BLM/DOI on 01/19/2004 04:19 PM ----- Mouncef_Belcaid@b lm.gov To: suse-autoinstall(a)suse.com cc: 01/19/2004 08:50 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro AM Thank you for the suggestion. I copied all CDs to one directory using the following command for all CDs: mount /media/cdrom; cp -va /media/cdrom /repository/suse/8.2; eject Mouncef Anas Nashif <nashif(a)suse.de> To: suse-autoinstall(a)suse.com cc: 01/16/2004 07:02 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro PM Patrick Greenwell wrote: > http://portal.suse.de/sdb/en/2003/03/rschmid_slesnfs.html > may help. > not reallly, this is more for sles configurations.. Mouncef, how did you copy the CDs, are all in the same directory or do you have seperate dirs for every CD? You have to copy them all into one directory if you wish to run the create_package_descr command, otherwise you dont need to run it, unless you change the packages. Anas > > On Jan 16, 2004 4:29 PM, Mouncef_Belcaid(a)blm.gov wrote: > > >> >> >> >> >>Hi everyone, >> >>I have been trying to install SuSE 8.2 using autoyast2 for the past couple >>of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. >>I set up a repository from the 5 CDs provides with the SuSE distribution >>under /repository/suse/8.2, ran the following command: >>/usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and >>shared it using nfs. This server is the pxe/tftp server as well as the nfs >>and dhcp server. >> >>I start the test machine, it goes through the configuration, formatting and >>installation process. Once it reboots the first time, it tries to install >>more packages and that is when it asks me to insert "CD 2". My question is, >>why doesn't it retrieve the rest of the packages from the nfs mount? This >>issue didn't happen with the SuSE 9.0 automated installation. >> >>Any help will be appreciated. >> >>Thanks in advance, >>Mouncef >> >> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> > > > > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

logrotate
by Lyle Giese 19 Jan '04

19 Jan '04

I have installed my first SuSE(pro v8.2) machine and have a minor problem. It looks like logrotate is broken. Or did I miss something simple? I see all the required stuff in /etc and /etc/cron.* and /etc/crontab.d, but no log rotations... The binary is in /usr/sbin and cron is working.... Thanks, Lyle

1 0

<hwclock>localtime</hwclock> bug?
by Holger Hellmuth 19 Jan '04

19 Jan '04

Hi, after installing with the hardware clock set to localtime (because there might be a windows on a few machines, too) with <hwclock>localtime</hwclock> the machine still uses UTC, in /etc/sysconfig/clock there is still only the line HWCLOCK="-u" instead of HWCLOCK="--localtime" This is not the fault of YAST, with a manual install it works, only autoyast seems not to take the value. Here the relevant excerpts from y2log: 2003-12-22 17:56:30 <1> linux(1130) [YCP] modules/AutoInstall.ycp(Continue):147 Found and read saved autoinst data : <...> "general":$["clock":$["hwclock":"localtime", "timezo ne":"Europe/Berlin"], "keyboard":$["keymap":"german"], <...> and later: 2003-12-22 17:56:42 <1> linux(1130) [Interpreter] clients/installation.ycp:150 Loading YCP module Timezone 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241 .sysconfig.clock.TIMEZONE: <Europe/Berlin> 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241.sysconfig.clock.DEFAULT_TIMEZONE: <Europe/Berlin> 2003-12-22 17:56:42 <1> linux(1130) [YCP] modules/Misc.ycp(Misc::SysconfigRead):241 .sysconfig.clock.HWCLOCK: <-u> 2003-12-22 17:56:43 <1> linux(1130) [YCP] modules/Timezone.ycp(Timezone::Set):177 Set timezone:Europe/Berlin sel:0 name:Europa / Deutschland Holger.

1 0

Howto define IP ranges in rules?/script question
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, I've installed dozens of computers with autoyast1 and SuSE 7.3 in the last years. Now I need to switch to SuSE 9.0 and try to learn the new autoyast2 interface. However, even after reading the complete html docu for 9.0 and browsing the mailing list archives, I still don't unterstand two things: 1) Is there any way to define IP ranges in rules? In autoyast1 I used to have lines like CLASS 141.84.1.210-240 k_smp in the main info file and info.k_smp would then contain a definition for using the k_smp kernel. In the rules.xml, I only see the hostaddress attribute which must match exactly. I tried a range there, but it did not work. How can I apply a rule to a set/range of ips without specifying each ip? 2) Do I really have to write all the scripts inside a profile? Is itnot possible to just call an external script file? Thanks a lot for any help (especially for the first question, the second is not really that important..) cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

2 2

Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 19 Jan '04

19 Jan '04

Thank you for the suggestion. I copied all CDs to one directory using the following command for all CDs: mount /media/cdrom; cp -va /media/cdrom /repository/suse/8.2; eject Mouncef Anas Nashif <nashif(a)suse.de> To: suse-autoinstall(a)suse.com cc: 01/16/2004 07:02 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro PM Patrick Greenwell wrote: > http://portal.suse.de/sdb/en/2003/03/rschmid_slesnfs.html > may help. > not reallly, this is more for sles configurations.. Mouncef, how did you copy the CDs, are all in the same directory or do you have seperate dirs for every CD? You have to copy them all into one directory if you wish to run the create_package_descr command, otherwise you dont need to run it, unless you change the packages. Anas > > On Jan 16, 2004 4:29 PM, Mouncef_Belcaid(a)blm.gov wrote: > > >> >> >> >> >>Hi everyone, >> >>I have been trying to install SuSE 8.2 using autoyast2 for the past couple >>of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. >>I set up a repository from the 5 CDs provides with the SuSE distribution >>under /repository/suse/8.2, ran the following command: >>/usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and >>shared it using nfs. This server is the pxe/tftp server as well as the nfs >>and dhcp server. >> >>I start the test machine, it goes through the configuration, formatting and >>installation process. Once it reboots the first time, it tries to install >>more packages and that is when it asks me to insert "CD 2". My question is, >>why doesn't it retrieve the rest of the packages from the nfs mount? This >>issue didn't happen with the SuSE 9.0 automated installation. >> >>Any help will be appreciated. >> >>Thanks in advance, >>Mouncef >> >> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> > > > > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

"searching /etc/fstab" functionality from ay1 lost?
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, studying section 4.4 of the ay2-docu from SuSE 9.0, it seems that one great functionality from autoyast1 is los in autoyast2: In ay1 you could specify this: AUTO_FDISK_DISK /dev/hda FSTAB_SEARCH /dev/hda1 /dev/hda2 /dev/hda3 FSTAB_FORMAT / /boot Behaviour would be: On a unpartitioned disk /dev/hda, partition it according to the specification in some file (was in the descr directory). If the disk is already partitioned, search for /etc/fstab in partition 1, 2 and 3. If no fstab was found, partition the whole drive according to the specification. If fstab was found, just format the partitions that were mounted as /boot and / according to this fstab. Thus, for a partitioned drive, you could just let autoyast format some partitions, without any knowledge about number, id, size etc. of this partition, while a fresh hard disk would be partitionied automatically. In autoyast2, it seems that I have to know the partition numbers of /boot and /. This would make things very complicated for a large set of different hosts, because you would need a different partitions instruction for a lot of hosts. Also I don't see how I can perform a "if partitions exist, only format some, if partitions do not exist, create them" scenario in general, even if I would specify the partition numbers etc. Would a combination of "<use>free</use>" and "<create>no</create>" create any partitions on an empty hard disk..? I will try some things like that... Are there any known solutions to these problems? cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

1 0

Re: [suse-autoinstall] Need Help Creating a Network Boot Floppy
by Harald.Milz＠computacenter.com 19 Jan '04

19 Jan '04

There is no need to compile anything with Etherboot as long as you go to www.rom-o-matic.net. If you want/need to boot via PXE on a machine which doesn't support PXE, get the RBFG.exe file from a w2000 or w2003 server or from argontechnology. It does not support that many ethernet NICs, though, and it doesn't work too well within VMware. 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. suse-autoinstall-return-1508-harald.milz=computacenter.com(a)suse.com on 16.01.2004 16:16:14 To: <suse-autoinstall(a)suse.com>, <marshall28(a)juno.com> cc: Subject: Re: [suse-autoinstall] Need Help Creating a Network Boot Floppy -------------------------------------------------------------------------- Note: http://www.tldp.org/HOWTO/NFS-Root.html may be your best source of information. "True" network boot: I did this years ago using Slackware, before SuSE was big. I used a package called "Boot-ROM" written by Gero Kuhlmann. It is really a package for writing Boot ROMs for putting into network cards if you have an EEPROM burner but you can use it just loaded onto a floppy too. It scans for an IP address then attempts to load a kernel over tftp using compiled in parameters. Also see http://www.etherboot.org/ as recommended on the PXE Linux homepage (http://syslinux.zytor.com/pxe.php). You'll need to do some compiling either way but etherboot looks like the most maintained. At the time I was doing it (6 years ago) etherboot was a bit basic as I remember. Possibly a simpler/better option: If you are sure that you won't ever want to distribute new kernels to your thin client PCs (i.e. they are not up the side of a mountain with no postal service! :) then you could just put a kernel directly onto a floppy disk for them. This is covered in the above HOWTO. Checking my SuSE 8.2 kernel I see it's got the relevant IP options discovery and NFS root code compiled in. To use this you'll need to pass the correct parameters to the kernel at boot time - see nfsroot.txt in /usr/src/linux (you have to have the kernel_source.rpm package installed). To go this route you'll also need to install LILO or GRUB on the floppy. If none of this works (one problem is that there may not be enough room on the floppy disk) you'll probably need to compile a kernel, which isn't all that hard really - there are many HOWTOs on how to do this. If you get nowhere finding stuff, I do have a disk image of a precompiled boot-rom for floppy disk if you want it, ask me and I'll email it directly to you but it will only work with NE2000 compatible NIC though which is probably little use. Regards, Carl Peto Linux Support Bookman Associates ----- Original Message ----- From: <marshall28(a)juno.com> To: <suse-autoinstall(a)suse.com> Sent: Thursday, January 15, 2004 6:29 PM Subject: [suse-autoinstall] Need Help Creating a Network Boot Floppy > I've got my tftp/dhcp server up and running but need help preparing a boot floppy which will start the install for me. I want to be able to just boot off the floppy, contact the tftp/dhcp servers and start the install. The attached document is very similiar to my configuration, except a few ip address differences. If someone knows how to create a network boot floppy using this configuration, please respond. > > thanks > marshall > ---------------------------------------------------------------------------- ---- > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Rules example
by Frank Steiner 19 Jan '04

19 Jan '04

Hi, can someone provide some examples for rules using a) custom scripts b) the range match type? I haven't found any further explanations about those in the documentation. Thanks a lot! Best regards, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/ * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

SLES vs UnitedLinux from NFS install
by Hal Wine 18 Jan '04

18 Jan '04

I'm a relative newbie to SuSE/yast, so first question is: what's the best way to search the list archive? Second question is on setting up an installation server. I used script in http://www.suse.de/~nashif/autoinstall/8.1/html/index.html and get an apparently good manual install. However, lsb-release thinks it's a UnitedLinux system, instead of a SLES8 system. When I install from the CD's, for lsb_release -a I get # lsb_release -a LSB Version: 1.2 Distributor ID: SuSE Description: SuSE SLES-8 (i386) Release: 8.1 Codename: n/a From the NFS install, I get: # lsb_release -a LSB Version: 1.2 Distributor ID: UnitedLinux Description: UnitedLinux 1.0 (i586) Release: 1.0 Codename: n/a This happens to be significant to us.... Any pointers to correcting this would be much appreciated.... --Hal

2 1

Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 17 Jan '04

17 Jan '04

Hi everyone, I have been trying to install SuSE 8.2 using autoyast2 for the past couple of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. I set up a repository from the 5 CDs provides with the SuSE distribution under /repository/suse/8.2, ran the following command: /usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and shared it using nfs. This server is the pxe/tftp server as well as the nfs and dhcp server. I start the test machine, it goes through the configuration, formatting and installation process. Once it reboots the first time, it tries to install more packages and that is when it asks me to insert "CD 2". My question is, why doesn't it retrieve the rest of the packages from the nfs mount? This issue didn't happen with the SuSE 9.0 automated installation. Any help will be appreciated. Thanks in advance, Mouncef

3 2

Re: [suse-autoinstall] Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 16 Jan '04

16 Jan '04

Hi Anas, Yes, I am using the original files that come with the SuSE 9.0 Pro. I tried SuSE 8.2 Pro and it worked. Thanks, Mouncef Anas Nashif <nashif(a)suse.de> To: Mouncef_Belcaid(a)blm.gov cc: suse-autoinstall(a)suse.com 01/15/2004 06:54 Subject: Re: [suse-autoinstall] Autoinstall+pxe+raid1 PM Hi, Are you using the original installation files, ie. kernel, initrd? This is probably due to version mismatch, the raid modules should be loaded automatically... Anas Mouncef_Belcaid(a)blm.gov wrote: > > > > Hi everyone! > > I have two 40GB drives that I want to mirror (hda and hdc). I am trying to > install SuSE 9.0 Pro using autoyast. I tried using software raid (raid1) > with no success. At the formatting stage of the auto installation I get the > following error: > "Error > Could not load module raid1" > > I would like to put /boot and / in /dev/md0 and /dev/md1. I also created > two swap partitions, one in each drive. Here is my raid config in the XML > control file: > ======================================================= > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <partitions config:type="list"> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md0</raid_name> > <raid_type>raid</raid_type> > <size>100mb</size> > </partition> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md1</raid_name> > <raid_type>raid</raid_type> > <size>36gb</size> > </partition> > <partition> > <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>1gb</size> > </partition> > </partitions> > <use>all</use> > </drive> > <drive> > <device>/dev/hdc</device> > <partitions config:type="list"> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md0</raid_name> > <raid_type>raid</raid_type> > <size>100mb</size> > </partition> > <partition> > <partition> > <format config:type="boolean">false</format> > <partition_id config:type="integer">253</partition_id> > <partition_type>primary</partition_type> > <raid_name>/dev/md1</raid_name> > <raid_type>raid</raid_type> > <size>36gb</size> > </partition> > <partition> > <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>1gb</size> > </partition> > </partitions> > <use>all</use> > </drive> > <drive> > <device>/dev/md</device> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">xfs</filesystem> > <format config:type="boolean">true</format> > <mount>/boot</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">0</partition_nr> > <raid_options> > <chunk_size>4</chunk_size> > <parity_algorithm>left-asymmetric</parity_algorithm> > <raid_type>raid1</raid_type> > </raid_options> > </partition> > <partition> > <filesystem config:type="symbol">xfs</filesystem> > <format config:type="boolean">true</format> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">1</partition_nr> > <raid_options> > <chunk_size>4</chunk_size> > <parity_algorithm>left-asymmetric</parity_algorithm> > <raid_type>raid1</raid_type> > </raid_options> > </partition> > </partitions> > <use>all</use> > </drive> > </partitioning> > ========================================================= > > Any help will be greatly appreciated. > > Thanks, > mb > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Need Help Creating a Network Boot Floppy
by marshall28＠juno.com 16 Jan '04

16 Jan '04

I've got my tftp/dhcp server up and running but need help preparing a boot floppy which will start the install for me. I want to be able to just boot off the floppy, contact the tftp/dhcp servers and start the install. The attached document is very similiar to my configuration, except a few ip address differences. If someone knows how to create a network boot floppy using this configuration, please respond. thanks marshall

2 1

Re: No Kernel SLES8 SP3 autoinstallation
by Anas Nashif 16 Jan '04

16 Jan '04

Martin Möser wrote: > Hello Anas, > > I still have the problem when autoinstalling with autoyast with > custom-CD, that no kernel is installed at all. > This appears since we updated our installation server with SP3 and put > the SP3 packages into the repository. > > I told You before that we built our own script for setting up an > iso-skeleton where the necessary packages are copied to and the iso > image is generated from. This doesn't work anymore since the update was > processed. > > Now I tried to build an iso-image with the > autoyast-configuration-interface, but that has no better effect, the > kernel is still missing. What can be the reason for this? The > kernel-packages (k_deflt etc.) are on the CD. I already sent You an > excerpt of the y2log before, maybe it helps You. > The kernel to be installed is determined during installation, so if you 100% not sure about the system you are installing on, you should include all kernel packages on the CD. Besides, the kernel package should not be listed in the packages list, this might cause some conflicts as it is determined automatically. SLES8 and SP3 installation using only one, custom built CD is not easy to accomplish, you have to select the right packages from each source or you have to include the different sources (3 in this case) on the CD and use the order/instorder files for processing the CD. The autoyast2 interfaec does not support creating CD for SLES8 installation or in general terms, a CD from multiple sources. We need more information about what you are doing here, otherwise there is no way to know whats happening. Anas P.S.: Please dont email me directly, others on the list might be interested in the solution of such issues. > Best regards, > > > Martin >

3 2

Warning message in create_package_descr 8.1
by Fermín Galán Márquez 16 Jan '04

16 Jan '04

Hello, When creating a package description for a SuSE 8.1 repository using the create_package_descr script for that version (in autoyast-2.6.42), I'm getting a lot of warning messages with the following text: "only V3 signatures can be verified, skipping V4 signature" Somebody knows what if the cause of that message, how to fix it and if this situation can lead to a incorrect package database description? Thanks in advance! ------ Fermín

2 2

Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 16 Jan '04

16 Jan '04

Hi everyone! I have two 40GB drives that I want to mirror (hda and hdc). I am trying to install SuSE 9.0 Pro using autoyast. I tried using software raid (raid1) with no success. At the formatting stage of the auto installation I get the following error: "Error Could not load module raid1" I would like to put /boot and / in /dev/md0 and /dev/md1. I also created two swap partitions, one in each drive. Here is my raid config in the XML control file: ======================================================= <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>100mb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>36gb</size> </partition> <partition> <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>1gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdc</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>100mb</size> </partition> <partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>36gb</size> </partition> <partition> <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>1gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> </partitioning> ========================================================= Any help will be greatly appreciated. Thanks, mb

3 2

AW: [suse-autoinstall] Autoinstall+pxe+raid1
by Mouncef_Belcaid＠blm.gov 14 Jan '04

14 Jan '04

Thanks Stefan. I did what you suggested without success. I still get the same error. Do you have any other suggestions? Thanks in advance. mb ----- Forwarded by Mouncef Belcaid/NIRM/BLM/DOI on 01/14/2004 09:34 AM ----- Voss Stefan <stefan.voss@itel To: "'Mouncef_Belcaid(a)blm.gov '" <Mouncef_Belcaid(a)blm.gov>, lium.com> "'suse-autoinstall(a)suse.com '" <suse-autoinstall(a)suse.com> cc: 01/14/2004 02:44 Subject: AW: [suse-autoinstall] Autoinstall+pxe+raid1 AM Hi, you probably have to put the raid1 module into the initrd: <install> <bootloader> <initrd_modules config:type="list"> ... <initrd_module> <module>raid1</module> <module_args/> </initrd_module> ... </initrd_modules> </bootloader> </install> Regards, Stefan Voss

1 0

invalid ram disk image error since 9.0
by Felix Guettler 14 Jan '04

14 Jan '04

Hi *, i use 3com PXE Util to load different images for installation. Thats what i do: 1) Format boot disk and "syslinux /dev/fd0" 2) Copy "bootlogo isolinux.bin linux message initrd isolinux.cfg memtest" from "/boot/loader" to diskimage using 3com PXE Util 3) Rename "isolinux.cfg" to "syslinux.cfg" 4) Generate PXE Menue and link the diskimage 5) Place diskimage and PXE Menuefile on tftp server 6) Link PXE Menuefile in dhcpd.conf This workes fine - i have done such images for SuSE 8.x, Redhat 8.x and 9.x for Debian 3.x and Fedora 1.0 - with SuSE 9.0 the Kernel panics when try to access the ramdisk, caused by the previous error: "Couldn't find valid ram disk image starting at 0". Files in image (and LDLINUX.SYS of course): 117523 Oct 20 14:53 bootlogo 5459309 Oct 20 14:53 initrd 14840 Oct 20 14:53 isolinux.bin 802 Oct 20 14:53 syslinux.cfg 1191629 Oct 20 14:53 linux 80324 Oct 20 14:53 memtest 490 Oct 20 14:53 message the initrd is original and unmodified version. load_ramdisk=1 wont change anything and got nothing to deal with the problem anyway (not 120% sure of this). I already replaced isolinux.bin with the latest version from kernel.org. I can reproduce the error on different systems. BTW, is there somebody out there using 3com PXE Util (except for RIS) ? Thanks, Felix.

1 0

Empty lines at start and end of Config-files
by Theo Gross 14 Jan '04

14 Jan '04

Hello, we are trying to use the autoinstall feature of SuSE Linux 9.0. When adding complete config files to the autoinst.xml using the editor provided by yast2 autoinstall, we discovered a Problem. (In German: Yast2: Modul: "Automatische Installation" -->"Sonstiges"-> "Komplette Konfigurationsdateien") To each file 3 or 4 empty lines are added before the first line and after the last line. These empty lines are not present in the XML-file. for example: ---begin of file--- Line1 Line2 Line3 ---end of file --- is writen on the installed System as follows: ---begin of file--- Line1 Line2 Line3 ---end of file --- This is not a Problem for most config-files, but some are diffrent. So my question ist, what to do against that? At the moment we have a workaraound for that by using a post-install-script. Theo Gross --- Theo Gross Sysadmin WsPool Informatik/ServiceGruppe University of Ulm theo.gross(a)informatik.uni-ulm.de James-Franck-Ring Work: 0731/50-24205 89081 Ulm Fax: 0731/50-24202 Germany

1 0

create_package_descr questions
by Fermín Galán 14 Jan '04

14 Jan '04

Hello, I have a pair of questions about the package database creation process (performed by create_package_descr script): 1. Can be used the same script for all SuSE versions (SuSE 8.1, SuSE 8.2 and SuSE 9.0) or each version have its own script file (in the autoyas2 package that comes with the version)? 2. Is create_package_descr a stand-alone program? (It seems that it uses the file /usr/share/autoinstall/EXTRA_PROV) Thanks in advance! ------- Fermín

4 4

example for sles8 + sp3 install server setup?
by Hal Wine 13 Jan '04

13 Jan '04

Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3? I followed Anas' example laytout for my original installation server setup. I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source. If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct? Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs. Thanks, --Hal

1 0

Integrate a 3rd party module into an autoyast configuration
by Schlabach, Torsten 13 Jan '04

13 Jan '04

Dear list, we have some machines that require a vendor supplied kernel module for their RAID controller. How could we integrate such a module into an autoyast installation? P.S.: Bear with me if this has been asked before, but I was not able to find any _searchable_ archive of this list. ----------------------------------------- Torsten Schlabach +49 228 936 34735 torsten.schlabach(a)t-mobile.de T-Mobile Deutschland GmbH -----------------------------------------

3 2

Developer team info required - yaST
by Anoop Kumar 13 Jan '04

13 Jan '04

Hi : Can somebody give a lead to find out which team works on yaST. I have to clarify some doubts on yaST. Thanks Anoop

1 0

Issues with PXE boot for installation
by Simon Thornton 13 Jan '04

13 Jan '04

Hi, I've a test network setup to use PXE to boot/install SuSE 8.2. The machines are setup with multiple OS's which use DHCP for address allocation, everything boots normally. I followed the instructions given in the pxelinux.doc file for configuring dhcpd.conf and the autoyast setup docs. After which I was able to boot/install the machines, without problems. However, if I then boot back into windows or another OS on one of the machines, the DHCP settings are incorrect (missing default route, domain name). Removing the PXE entries from dhcpd.conf resolves this. Does anyone have any ideas what might be the problem? Ideally I would like to be able to use the network boot option for install/emergency and run the OS's as normal without having to switch configs. Thanks for your help. Simon

1 0

command line arguements for NFS auto install
by Hal Wine 12 Jan '04

12 Jan '04

Folks, Somehow, I'm not getting something about the command line arguements for an automatic install using a profile on an NFS server. I have the server set up, and I boot from the first SLES 8 cd. When I do a manual install install, everything works correctly, and all the "cds" are found on the NFS server. I then used "yast2 autoyast" to clone the resulting system config, then edited that to reflect the NFS settings. I copied the result to the NFS server. When I try to use this profile, again when booting from the first SLES 8 cd, it can't find the 2nd cd (United Linux cd1) and prompts for it (same dialog box as cd-switch). ctrl-alt-f2 shows the correct spot on the NFS server mounted. As I read the docs, it seemed the only thing I needed to specify was the autoyast profile locations (which it finds). I've also tried adding the install=, server=, & serverdir= options with no luck. I saw a message related to DHCP setup that referenced an "install=nfs" arguement, and have tried that. Any suggestions? (I feel like it must be something obvious that I just am missing.) Thanks! --Hal

1 2

Re: [suse-autoinstall] YaST Online Update
by Harald.Milz＠computacenter.com 12 Jan '04

12 Jan '04

Folks, this mailing list is about SuSE autoinstallation. This is not a generic SuSE help mailing list. :-)) 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. suse-autoinstall-return-1483-harald.milz=computacenter.com(a)suse.com on 09.01.2004 19:06:30 To: <suse-autoinstall(a)suse.com> cc: Subject: [suse-autoinstall] YaST Online Update -------------------------------------------------------------------------- Hello everyone, I am using SuSE SLES 8.0 on my Intel Xeon i386. I am trying to do an ONLINE UPDATE for the latest patches released last week. Here is my YaST Information: Update Mode: Manual Mode Install Source: sdb.suse.de/download I enter my Registeration data (code and password) and on clicking next I get following Error Message - wonder why: Initialization failed. Try again. if failure continues choose another SuSE FTP/HTTP Server. Can anyone please help me out or give any hints/tricks? HARI OM I live in a very small house... but my windows open to a big world...

1 0

YaST Update
by HARI OM 09 Jan '04

09 Jan '04

Hello everyone, I am using SuSE SLES 8.0 on my Intel Xeon i386. I am trying to do an ONLINE UPDATE for the latest patches released last week. Here is my YaST Information: Update Mode: Manual Mode Install Source: sdb.suse.de/download I enter my Registeration data (code and password) and on clicking next I get following Error Message - wonder why: Initialization failed. Try again. if failure continues choose another SuSE FTP/HTTP Server. Can anyone please help me out or give any hints/tricks? HARI OM I live in a very small house... but my windows open to a big world...

1 0

YaST Online Update
by HARI OM 09 Jan '04

09 Jan '04

Hello everyone, I am using SuSE SLES 8.0 on my Intel Xeon i386. I am trying to do an ONLINE UPDATE for the latest patches released last week. Here is my YaST Information: Update Mode: Manual Mode Install Source: sdb.suse.de/download I enter my Registeration data (code and password) and on clicking next I get following Error Message - wonder why: Initialization failed. Try again. if failure continues choose another SuSE FTP/HTTP Server. Can anyone please help me out or give any hints/tricks? HARI OM I live in a very small house... but my windows open to a big world...

1 0

SV: SV: [suse-autoinstall] Setting display properties...
by Peter Bergström 09 Jan '04

09 Jan '04

Thanks, I will try this! br, Peter -----Ursprungligt meddelande----- Från: Robison, Jonathon (M.) [mailto:jrobiso2@ford.com] Skickat: den 9 januari 2004 15:57 Till: Peter Bergström Ämne: Re: SV: [suse-autoinstall] Setting display properties... If you get the gray screen and the cross, then something positive is happening. Make sure that xfs is installed, then install ICE-WM and ice-wm-default (it's named something like that). Then use yast (still in charater mode) to turn on autologin (so we don't have to worry about the pesky kdm or gdm login screens) and set your windowmanager to ice-wm. Ice is extremely basic, but it also uses less proprietary stuff. If this works, then it tells us that it's your KDE or Gnome window manager that is fscked, and perhaps a re-install is in order? Beyond that, I cannot be too much help. The last time I hand wrote an XF86Config file, it was for XFree 3.3, and 4.X is very different. Keep asking the list, I am sure someone will be able to help. --Jonathon On Fri, 2004-01-09 at 09:40, Peter BergstrÃ¶m wrote: > Hi Jon! > > Thanks for your help! I have been able to reduce the problem (I > think). I > ran sax2 and also installed the nvidia driver provided by Nvidia Corp. > I > don't get the out of range error any more but when I start XFree86 I > only > get a grey screen (startup screen for X I think) and the mouse pointer > cross, after that, nothing... The problem seems to be XFree86's > ability to > detect my ViewSonic VG700 LCD Display (atleast that is what I think) > and I > can't find that model in the list of monitors under vendor ViewSonic > in > sax2... > > On the other hand, if I run Knoppix which also uses XFree86 Ãt all > works > great?!? I even tried he XF86Config file that Knoppix produces as > config for > X with SuSe but I get the same problem as mentioned above. > > If I use a default VESA or LCD screen in sax2, set the resolution to > something not too high, set the update frequencies according to > ViewSonic > specs. and run the test (click test after finalize) I get the > following > error: > > X server test failed > (EE) NVIDIA (0): Failed to allocate external video decoder object. > > I don't understand what that means... > > When sax2 is started I get a message saying VSC3e08 is an unknown > monitor > and I need to setup the monitor manually. > > What should I do? Just try any possible monitor? Re-install SuSe? > Install > Mandrake? How come it works fine with Knoppix???? > > regards, > > Peter > > > -----Ursprungligt meddelande----- > FrÃ¥n: Robison, Jonathon (M.) [mailto:jrobiso2@ford.com] > Skickat: den 6 januari 2004 21:48 > Till: Peter BergstrÃ¶m; suse-autoinstall(a)suse.com > Ã"mne: RE: [suse-autoinstall] Setting display properties... > > > Peter, > > When you reboot, at the grub boot prompt, add a "3" (just hit 3, then > enter). This will boot you into non-graphical mode. If you use LILO, > instead > of grub, then type "linux 3" (Suse defaults to grub). > > Then, as root, run sax2 to re-configure your graphics settings. > > Lastly, just an FYI, your graphics control file is > /etc/X11/XF86Config. > Within this file, you can find the monitor settings. Just below the > "DefaultDepth" line is the resolution settings for each depth. Find > the one > for your DefaultDepth (probably 16) and remove the resolutions above > 1024x768. That's the manual method, but unless you are handy with the > VI > editor and know what you are doing, stick with sax2. > > --Jon Robison > > > -----Original Message----- > From: Peter BergstrÃ¶m [mailto:peter.bergstrom@sverige.nu] > Sent: Tue 1/6/2004 2:32 PM > To: suse-autoinstall(a)suse.com > Cc: > Subject: [suse-autoinstall] Setting display properties... > Hi! > > Im very new to Linux and suse and just installed my first suse 9.0 > system on > a Dual P2 350 MHz machine with a Nvidia Riva/TNT graphics card. During > the > install phase I noticed that the resolution was configured to 1280x??? > but I > doubt my old card can handle this. When I was ready to boot up the > system > for the first time my ViewSonic VG700 LCD display gives me an error > message: > "Out of range ??MHZ Vsynch ??MHz Hsync". Nothing is shown apart from > that > (blank screen) > > If I start in failsafe mode I get to the prompt, but I don't know how > I can > set the display settings from here. I guess there is a graphical > interface > that should start up and the resolution is set too high here, how can > I fix > this? > > thanks in advance! > > / Peter > > > > -- > 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] Setting display properties...
by Robison, Jonathon (M.) 09 Jan '04

09 Jan '04

Peter, When you reboot, at the grub boot prompt, add a "3" (just hit 3, then enter). This will boot you into non-graphical mode. If you use LILO, instead of grub, then type "linux 3" (Suse defaults to grub). Then, as root, run sax2 to re-configure your graphics settings. Lastly, just an FYI, your graphics control file is /etc/X11/XF86Config. Within this file, you can find the monitor settings. Just below the "DefaultDepth" line is the resolution settings for each depth. Find the one for your DefaultDepth (probably 16) and remove the resolutions above 1024x768. That's the manual method, but unless you are handy with the VI editor and know what you are doing, stick with sax2. --Jon Robison -----Original Message----- From: Peter Bergström [mailto:peter.bergstrom@sverige.nu] Sent: Tue 1/6/2004 2:32 PM To: suse-autoinstall(a)suse.com Cc: Subject: [suse-autoinstall] Setting display properties... Hi! Im very new to Linux and suse and just installed my first suse 9.0 system on a Dual P2 350 MHz machine with a Nvidia Riva/TNT graphics card. During the install phase I noticed that the resolution was configured to 1280x??? but I doubt my old card can handle this. When I was ready to boot up the system for the first time my ViewSonic VG700 LCD display gives me an error message: "Out of range ??MHZ Vsynch ??MHz Hsync". Nothing is shown apart from that (blank screen) If I start in failsafe mode I get to the prompt, but I don't know how I can set the display settings from here. I guess there is a graphical interface that should start up and the resolution is set too high here, how can I fix this? thanks in advance! / Peter -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] Network autoinstall of SLES8 SP3 - what to do to include y2updates
by Harald.Milz＠computacenter.com 09 Jan '04

09 Jan '04

And while we're at it - does somebody have a working script that generates a SP3 install repository from loopback mounted ISO images (that can be provided to install clients via TFTP not NFS)? I would rather not copy the whole CD contents to the install file system when I've got the CD iso images already there... Why the heck is there no SLES8 DVD? 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. suse-autoinstall-return-1478-harald.milz=computacenter.com(a)suse.com on 09.01.2004 10:58:08 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Network autoinstall of SLES8 SP3 - what to do to include y2updates -------------------------------------------------------------------------- Hi! I have a working SLES8 network installation source. Before SP3 i found here on the list the docu how to update the "root" file with the y2 updates. It seems that it works now differently for the SP3. What do i have to do to get the y2 updates included in the install? BTW, i'm installing in on ppc64 (JS20). 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Network autoinstall of SLES8 SP3 - what to do to include y2updates
by Joachim Jordan 09 Jan '04

09 Jan '04

Hi! I have a working SLES8 network installation source. Before SP3 i found here on the list the docu how to update the "root" file with the y2 updates. It seems that it works now differently for the SP3. What do i have to do to get the y2 updates included in the install? BTW, i'm installing in on ppc64 (JS20). 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

Recognition of a harddrive (Raid 0, 4 HDs) on a HP LH3 Netserver with HP NetRaid on a Symbios controller
by J.Staretzek＠hsd-online.de 08 Jan '04

08 Jan '04

Hallo, I try to setup a SuSE 9.0 on an old HP LH3 Netserver. The LH3 has a SCSI Raid 0 with 4 HDs on a Symbios controller with sys53c895 chip under HP NetRaid. When autoinstalling routines passed, Yast states that there is no harddrive available, why? During installing Yast recognize the sym53c8xx chip and decide for the ncr53c8xx module. I unloaded the ncr53c8xx module and loaded the sys53c8xx and tried also the sym53c8xx-old module by hand, but there was no other result! Checking the log so I can see nothing seems wrong - the chip will be recognized and no fail message is given when initialized. In next step Yast shows me that has recognized the Symbios controller with the sym53c895 chip and the HP NetRaid system, very correctly, but will still see no harddrive! I know that the HP Netserver LH3 was certified for SuSE 6.2. Hoping for help get the old horse running under Linux! Mit freundlichen Grüssen Joachim Staretzek

1 0

Suse and Nagios
by Browett, Darren 07 Jan '04

07 Jan '04

I am planning on using the nagios that comes with SLES 8.0, and have noticed that is an older version (1.04) then what is currently available (I think 1.1). How do I go about upgrading the Suse version ? Or should I simply create an entire new installation (/usr/local/nagios ) using the packages from Nagios. ? Not sure if this is the correct list for this question, if it isn't can somebody direct me to the correct one. Thanks Darren ------------------------------------------------------------------------ -------------------------------------------------- Darren Browett P.Eng This message was transmitted Data Administrator using 100% recycled electrons Information and Communication Technology City of Coquitlam P:(604)927 - 3614 E:dbrowett@coquitlam.ca ------------------------------------------------------------------------ ---------------------------------------------------

1 0

Can't load configs into autoyast
by Paul Byrne 07 Jan '04

07 Jan '04

Hi, I'm having a problem with autoyast in Suse 9.0 pro. Once I've built a configuration and saved it I can't load it back into autoyast. The load operation seems to access the file but nothing appears in the tool. Is anyone else seeing this ? Rgds Paul

1 0

how to copy installations?
by Ricardo Kleemann 06 Jan '04

06 Jan '04

Hi, I have one server where I've installed SUSE 9.0 and a number of other things. How can I duplicate this installation to another server? Is there a way to boot from CD and then copy the installation over the network? Thanks Ricardo

4 3

a few questions
by Tom Davidson 05 Jan '04

05 Jan '04

Hi, I've got a few questions about configuring autoyast2 and the answers don't appear to be in the manuals on http://www.suse.de/~nashif/autoinstall: 1) Is it possible to configure the bootloader resource to not do anything to the bootloader? I have multiple entries of all sorts in my grub config and don't want SuSE to touch anything. In fact, I'm reinstalling SuSE a number of times and already have the required entries for it in the config. 2) How can I make the installation fully automatic? I don't want to be asked to confirm the settings and then confirm that I *really* want to do this... 3) Does autoinstalling generate a profile anywhere for the system that it just installed, like RedHat does with anaconda-ks.cfg? It would be nice to be able to install a system manually as desired and then use a generated profile to effectively clone it. I know that the YaST2 GUI can read the current machine into a profile, but it doesn't do a perfect job, and only lists shed loads of packages, rather than the install type (default,Minimal etc.). Apologies if these questions have already been asked on the list, but with it not being searchable (and the netsys.com engine being down) I couldn't find out easily. Cheers, Tom -- Tom Davidson Unix SysAdmin

1 0

k_smp4G missing from created SUSE9.0 ISO image
by Magnus Hagebris 05 Jan '04

05 Jan '04

My created ISO image does only contain the k_deflt, k_athlon and k_smp kernels. Where is the k_smp4G kernel? Is this a bug in the autoinstall iso creation? I created a patched source tree;the description files look good and properly includes the k_smp4G kernel. It just doesn't get added to the ISO. During install YaST complains about not finding the k_smp4G kernel on the cd... Install works perfectly fine on systems not using the k_smp4G kernel. Any work-around for this? Or tips... Thanks, Magnus

2 2

No Kernel installed
by Martin Möser 05 Jan '04

05 Jan '04

Hi List, since we build our custom-CD's (SLES8) with SP3, there will be no kernel installed by autoyast. As a result, all modules are missing, and /boot is almost empty, no boot-image or initrd in there. So the network interfaces don't work and the reboot fails because of the missing vmlinuz. We use a machine with two processors and therefore we need an smp-kernel installed which worked fine BEFORE we put the SP3-Packages into the repository. The needed kernel was detected and installed automatically. Any ideas? Regards, Martin Möser -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

2 1

SuSE 9.0 PXE boot problem
by Harald.Milz＠computacenter.com 04 Jan '04

04 Jan '04

Hi, since my notebook's CD-ROM drive is dying slowly I tried to install SuSE Linux 9.0 Prof. from my existing PXE/DHCP/TFTP server which already has working configs for 8.0 and 8.2: label 8.0 kernel kernel-8.0 append initrd=initrd-8.0 acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-8.0" label 8.2 kernel kernel-8.2 append initrd=initrd-8.2 acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-8.2" As usual, copied boot/loader/linux and boot/loader/initrd to /tftpboot and added a config entry to pxelinux.cfg/default: label 9.0 kernel kernel-9.0 append initrd=initrd-9.0 ramdisk_size=65536 showopts ide=nodma acpi=off apm=off install="nfs://192.168.20.1/pub/suse/SuSE-9.0" which, apart from some additional options taken from the CD isolinux.cfg file, are identical to the ones above. The additional options don't change any of the descibed behaviour, which is: - notebook boots via pxelinux just fine, I get my text menu, enter 9.0 - kernel unpacks, and ... - the screen is an 80x25 chaos of ASCII characters with various attributes, like blink, etc. Machine stops. Nothing happens. It looks as if the kernel was unpacked into the EGA video memory region at segment b800. Any clue what happens? 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

2 1

SLES 8 SP3 Bugs?
by Hans Kamm 01 Jan '04

01 Jan '04

Hi, I think, there are some bugs with the SLES SP3 installer. e. g. some packages get always installed (SuSEFirewall, providers, jfsutils, rsh, rsync...) I' ve set <base></base> and no addons. I don't want to delete the packages after isntallation. I think without sax2 you can't do a automated installation with a minimal X-system. The ntp-server will get no entry in the /etc/ntp.conf. The entry under /etc/sysconfig/xntp exists. <ntp_servers config:type="list"> <ntp_server>ntp-server</ntp_server> </ntp_servers> How to eject CD-Rom before reboot? Hans _________________________________________________________________ Schützen Sie Ihren Posteingang vor unerwünschten E-Mails. http://www.msn.de/antispam/prevention/junkmailfilter Jetzt Hotmail-Junk-Filter aktivieren!

2 1