only one floppy. The images will be listed in your config file. I know and use Lilo so I will give you an example using Lilo (at the bottom). I am sure there are plenty of examples for grub users to follow. Google is your friend. If you don't want to mess with config files, just install the boot loader from SuSE. Yast will allow you to add as many of your other OS's using a point and click gui interface. I'm sure Redhat or Mandrake has the same ability. At least I assume they do, I just haven't use them in six or seven years. As to the rebooting during install. At some point in the install of every OS you must move from the operating system on the install media to the OS you have just installed on a hard drive. For many years Linux installs worked like SuSE still does. Install enough to get started, reboot early and finish the install and configuration. This was always seen as a practical way to handle installing Linux, because so much had to be configured by hand, and you were going to have to recompile the kernel for your device drivers. A lot has changed Contrast this to the Windows family of OS's. They install almost everything, and reboot very close to the end of installation. right at the end you reboot to your hard disk and there is just a teeny bit of configuration left. There is still a reboot. I know that you can also 'reboot on the fly'. switching from the OS on the install media to the installed OS. You can do it warm and hide it behind a splash screen or something. I don't know if RedHat or Mandrake do this, but theoretically it can be done. Seems like a waste of effort to me, but hey. But there is still a point where you stop using the OS on your install media and start using the os on your hard drive. So there must be some point where you reboot, early middle or end. Unless you use knoppix and always boot from CD and never install to hard drive. # example /etc/lilo.conf boot = /dev/hda # place lilo in MBR of first disk delay = 1000 # Wait 10 seconds, to give time to hit a key default = mandrake # the image labelled 'mandrake' will boot # if there is no intervention. other = /dev/hda1 # a windows partition label = windows # the label can be ny name table = /dev/hda # where this os will boot from image = /boot/zImage-2.4.22 # A Linux kernel, located in the /boot directory root = /dev/hda2 # The partition that will be mounted as root label = mandrake # The name you should type in to boot this kernel. image = /boot/zImage-2.6.10 # A Linux kernel, located in the /boot directory root = /dev/hda6 # The partition that will be mounted as root label = redhat # The name you should type in to boot this kernel. image = /boot/vmlinuz_suse # A Linux kernel, located in the /boot directory root = /dev/hda8 # The partition that will be mounted as root label = suse # The name you should type in to boot this kernel. I'm sure grub has many examples on the internet you can follow. On Fri, 21 May 2004 11:56:25 -0400 (EDT), michael12@mindspring.com wrote:

I'll try, but I have quite a few different boot images. Will I need one

disk per image? Also, neither Redhat nor Mandrake has ever required a reboot at this stage. It's just insane...

Michael

-----Original Message----- From: sean-lynch@sean-lynch.com Sent: May 21, 2004 10:39 AM To: suse-amd64@suse.com Subject: Re: [suse-amd64] Suse9.1 still fails to install

Oh! This is a problem. SuSE still does a reboot after installing the basic system. The reboot gets you off the dvd booted system and on to your newly installed system. Then there is more installation and setup after you do this re-boot.

If you did not install a bootloader, you will not be able to boot your newly installed SuSE to finish the install. Historically I believe almost all Linux ditributions used this reboot half way through install.

Here are two solutions to try A or B (please read both):

A) 1)Boot to Mandrake. Make a mandrake boot floppy. confirm you can boot to Mandrake with the boot floppy.

2)Install SuSE. Install the bootloader to your harddrive (yes, overwriting the Mandrake boot loader, but don't worry you have a Mandrake boot floppy from

1 above!). Completely install SuSE past the mid install re-boot, Sax X setup, post configuration. create a SuSE boot floppy now. Reboot again to make sure SuSE is perfectly installed. You might add Mandrake and any other OS's you have to the SuSE boot loader and quit here, or print out (or write down) the lines from Grub (or Lilo) config files for the SuSE boot.

3)Use your Mandrake boot floppy to boot to Mandrake. Edit your Mandrake Grub (or Lilo) config file to include SuSE. Update Grub (or Lilo) with these changes and re-install it to your hard drive. This overwrites your SuSE installed boot loader, but you get all your old Mandrake settings back, plus a new entry for SuSE.

B) On the other hand you may not have to start completely over...

You might be able to use the SuSE install DVD as a rescue disk to boot to an OS on the hard drive. Choose the partion you started your SuSE install to and boot to it. You might be able to pick up the installation where you left off, even without a boot loader installed. If this is the case, create a SuSE boot floppy as soon as you get a working system.

Good Luck,

Se�n

On Fri, 21 May 2004 08:48:23 -0500 (GMT-05:00), michael12@mindspring.com wrote:

...

I tried that. It reset before I was able to set up the root password,

...

XF86, etc... Basically, just after the RPM installs completed. When I tried booting from the DVD again, the DVD started as if it was a new install. Is there something else I'm supposed to do? I don't recall anything in the manual saying "Your system will reset before you can finish configuring it". I don't even have a root password, my XF86 hasn't been set up, etc... Neither Redhat nor Mandrake work that way - why does Suse work that way?

Thanks, Michael

-----Original Message----- From: Andi Kleen <ak@suse.de> Sent: May 21, 2004 3:44 AM To: Michael White <michael12@mindspring.com> Cc: suse-amd64@suse.com Subject: Re: [suse-amd64] Suse9.1 still fails to install

...

My plan was to add an entry in my Mandrake bootloader for Suse.

Well, this crashes too, but in a much worse way. I look down after all

floppy point printer, the

...

...

RPMs have been installed, and when I look up again I see Yast starting up.

...

...

Immediately after that, the system starts shutting down. No real indication as to why this is happening. I didn't see anything of any significance in

SUSE always reboots once during the installation. If you had looked you had seen a dialog box telling you that.

This is also documented in the handbook.

Just make it somehow boot again and then the installation will continue.

-Andi

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com