March 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] Question/suggestion Linux Installation over Network
by damien.selles＠eu.effem.com 05 Mar '04

05 Mar '04

Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

UNSUSCRIBE ME PLEASE!
by Isabel Falcon 05 Mar '04

05 Mar '04

Ing. Isabel Falcón Consultor de Ventas Afina Sistemas ifalcon(a)afina.com.ve <mailto:ifalcon@afina.com.ve> Av Libertador Multicentro Empresarial del Este Torre Libertador Nucleo B Piso 3 Of B31 Chacao 1060 - Caracas - Venezuela tel: 58-212-2661163 // 7755 // 8980 fax: 58-212-2636502 mobile: 58-412-3729747 web: www.afina.com.ve <http://www.afina.com.ve> -----Original Message----- From: damien.selles(a)eu.effem.com [mailto:damien.selles@eu.effem.com] Sent: Viernes, 05 de Marzo de 2004 09:41 a.m. To: Bjorn Tore Sund Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- 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

Autoyast on pSeries machines.
by Paul Edgar 03 Mar '04

03 Mar '04

We have written a series of scripts for SuSE SLES 8that will setup the machine for autoyast installation and reboot the machine for installation. All works well on Intel and opteron platforms, but when we try to make a PPC machine install we run into a few issues. 1. It looks like the machine installs the OS, until the first reboot. At that time the machine refuses to boot up. If we put the installation CD in the cdrom drive, boot with that, we can select 'Boot installed system". 2. After selecting this, the machine boots up and finishes up the installation just like normal. Here is what I see when the machine does it's first reboot during install. /dev/sda invalid device Then I go into rescue CD mode from the installation CD and look at /etc/yaboot.conf which does not exist. So I chroot the mounted and look at lilo.conf which has the following in it. This does not look correct from what I have seen when the system is installed macnually. default=linux timeout=100 boot= activate image = /boot/vmlinux label = linux root = /dev/sda3 initrd = /boot/initrd append = "" If I try to run lilo at this point, it errors out on boot= which should be /dev/sda1. Activate is an extra parameter I have not seen before. Image pointed to /boot/vmlinux.initrd initrd = was not there append = "" was not there Any suggestions, questions, or pointers would be helpful. -- Paul Edgar Verification Engineer Linux Technology Center / IBM External 512.838.1493 / TieLine 678-1493 javaoops(a)us.ibm.com No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced.

4 7

How to avoid booting confirmation?
by Robert Pollak 03 Mar '04

03 Mar '04

Hello! I use the appended control file autoinst.xml on a floppy during installation from the original SLES8 CDs. At the end of the "Finishing Basic Installation" screen, i am asked > The LILO boot sector has been written to disk. You can restore > the old boot sector in the installed system with "lilo -u /dev/sda" > > Now booting your system... > [OK-Button] , and the installer waits for interactive confirmation. How can i change the control file such that this confirmation is not needed? Or can't it be suppressed by any of the <mode> entries? -Robert ****************autoinst.xml**************** <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XXXXXX</user_password> (<- pw removed) <username>root</username> </user> </users> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Vienna</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <mode> <installation config:type="boolean">true</installation> <upgrade config:type="boolean">false</upgrade> <confirm config:type="boolean">false</confirm> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> </software> </install> </profile>

2 2