Re: d-i using kexec
I demand that Justin Pryzby may or may not have written...
> Has anybody ever considered the possibility of a 0-reboot installation?
> It seems that this should be possible with (or without?) kexec.
> I think the reason the installer presently reboots is to load the *real*
> kernel (which will be used during normal runtime) rather than the installer
> kernel.
> Rebooting also allows the boot process as a whole to get tested ("Did the
> MBR get written correctly?").
> Are there other reasons?
WRT Acorn and compatible hardware...
In the absence of r/w support for ADFS (is it absent in the install kernel
for ARM? I've not checked), it'd be needed to allow the installed kernel to
be copied into the boot partition and to give the admin a chance to edit the
loader script. In the presence of said r/w support, you'll _definitely_ want
/dev/hda1 to be mounted as /boot if you want to do this from Linux.
In the MBR, there's no loader program to worry about ;-)
--
| Darren Salt | linux (or ds) at | nr. Ashington,
| woody, sarge, | youmustbejoking | Northumberland
| RISC OS | demon co uk | Toon Army
| http://www.youmustbejoking.demon.co.uk/progs.linux.html>
Do not speak about Time until you have spoken to him.
Re: d-i using kexec
Justin Pryzby wrote: > Has anybody ever considered the possibility of a 0-reboot > installation? > > It seems that this should be possible with (or without?) kexec. > > I think the reason the installer presently reboots is to load the > *real* kernel (which will be used during normal runtime) rather than > the installer kernel. That and so if it *doesn't* boot, you don't find yourself 3 hours (or 3 days) into installing Debian only to have to start over because of some problem with the boot loader. Note that in some installation methods in expert mode, there is a menu item down near the bottom that lets you run the second stage if installation without rebooting, although this is not well tested. -- see shy jo signature.asc Description: Digital signature
d-i using kexec
Has anybody ever considered the possibility of a 0-reboot
installation?
It seems that this should be possible with (or without?) kexec.
I think the reason the installer presently reboots is to load the
*real* kernel (which will be used during normal runtime) rather than
the installer kernel.
Rebooting also allows the boot process as a whole to get tested ("Did
the MBR get written correctly?").
Are there other reasons?
Justin
signature.asc
Description: Digital signature
