Hello, Thank you for your help, together with your hints, and the SuSE Advanced Deployment guide, I *almost* have a working installation routine! So far, I have created the following file structure in my TFTP server's directory: ============================================================ stg-backup:/install # ls -l /tftpboot/ total 8601 drwxr-xr-x 3 root root 208 Feb 2 16:26 . drwxr-xr-x 25 root root 808 Feb 2 16:19 .. -r--r--r-- 1 root root 7076988 Sep 14 12:05 initrd -r--r--r-- 1 root root 1606360 Sep 14 12:05 linux -r--r--r-- 1 root root 90292 Sep 14 12:05 memtest -r--r--r-- 1 root root 456 Sep 14 12:05 message -rw-r--r-- 1 root root 11822 Sep 9 16:39 pxelinux.0 drwxr-xr-x 2 root root 72 Feb 2 16:41 pxelinux.cfg stg-backup:/install # ls -l /tftpboot/pxelinux.cfg/ total 4 drwxr-xr-x 2 root root 72 Feb 2 16:41 . drwxr-xr-x 3 root root 208 Feb 2 16:26 .. -r--r--r-- 1 root root 813 Feb 2 16:41 default stg-backup:/install # ============================================================ The above files were copied from "DVD:/boot/loader/" and "/usr/share/syslinux/pxelinux.0" with "default" being copied from "DVD:/boot/loader/isolinux.cfg". I then edited "/tftpboot/pxelinux.cfg/drfault" so it contains the following: ============================================================ default harddisk # hard disk label harddisk kernel linux append SLX=0x202 showopts # install label linux kernel linux append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml # noacpi label noacpi kernel linux append initrd=initrd splash=silent showopts acpi=off # failsafe label failsafe kernel linux append initrd=initrd splash=silent showopts apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml # rescue label rescue kernel linux append initrd=initrd splash=silent rescue=1 showopts # memory test label memtest kernel memtest implicit 1 display message prompt 1 timeout 200 notice 6 ============================================================ The only changes I made to the original file were the following additions on the append lines for "linux" and "failsafe": insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml They are actually Dell SC1425 servers, but I believe they have an Intel network card (I could be wrong) which is definitely gigabit. Also, that xml file on that NFS server definitely exists because I can mount it from other machines. However, I have two problems: 1. When the system first boots into the screen giving me the option to boot from "harddisk", "linux", "noacpi", "failsafe" etc... I get a warning that says: Unknown keyboard in config file. Missing parameter in config file. Nevertheless, I still have the option of chosing an option, so I type "linux" and hit return. It then boots up, and after a minute or two, a read box appears on screen stating: Could not find the Suse Linux Installation Source. Activating manual setup program. Does this mean I have chosen the incorrect network drivers? If so, how can I possibly start the manual setup program if it can't access the source? Or is the manual setup program part of what's been copied into the tftp sevrer? Thanks again for your help, it's most appreciated :-) Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Gunreben, Peter (Peter) [mailto:pgunreben@lucent.com] Sent: 02 February 2006 15:03 To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Help with installing multiple machines over network
Richard,
Richard Hobbs wrote:
[...]
I have multiple machines, all of which are identical, onto which I would like to install SuSE 10.
I have already installed one machine and got it setup the way I would like it, in terms of package selections, partitioning etc... And I would now like to replicate that across the remaining machines if possible.
I have read the first section of the SuSE 10 manual, entitled "Advanced Deployment Scenarios", but this only seems to document how to boot the system into the manual installation routine remotely. Ideally, I need to boot from the network and begin a fully automated install which duplicates every single aspect of the first system, except with a different hostname and IP (which I don't mind entering manually during the install if necessary).
Can this be done? I'm sure it can, but I can't find any guides or tutorials on how to do it, so if anyone can help, that would be very much appreciated
Yes, it can be done. Basically, you need two things: 1) The mechanism to boot from the network 2) The mechanism for the automatic installation
ad 1) Regarding the boot from network, I'd recommend pxegrub: http://www.gnu.org/software/grub/manual/grub.html#Network Alternatively, you could also build a boot-CD, which contains bootloader, kernel and initrd and starts the network installation. However, this might not be your preferred way of installing the computers.
ad 2) I'd recommend to use autoyast. The autoyast is the SuSE mechanism for automatic installation. Using "yast2 autoyast" you can generate an XML-File, which contains the entire configuration for the installation. To install using autoyast, you just need to boot the kernel load the Installation initrd (DVD:/boot/loader/initrd) and add the kernel-parameter install=nfs://<IP-Adressse>/<Pfad>/<XML-File> in your boot-loader configuration. Mailing-List: mailto:suse-autoinstall@suse.com Archive with search function: http://marc.theaimsgroup.com/?l=suse-autoinstall Documentation: http://www.suse.com/~ug/autoyast_doc
Regards, Peter.
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com