Bug#270550: Using d-i as rescue disk.
On Thu, Sep 09, 2004 at 02:53:10PM +0200, Sven Luther wrote: > On Wed, Sep 08, 2004 at 04:43:43PM +0100, Colin Watson wrote: > > On Wed, Sep 08, 2004 at 01:00:26PM +0100, Alex Owen wrote: > > > In boot-floppies (bf) the bf kernel was installed in the target system. Is > > > that the case in d-i ? > > > > No, it's not. > > > > > If the d-i kernel ins not installed on the target system then I think that > > > the d-i boot floppy cannot have the "rescue" boot option that bf had as > > > there will be no matching kernel modules in the root filesystem. > > > > Most of the modules are available in the d-i environment, although you > > need to run the appropriate "Load installer components from ..." stage > > to get a lot of them. The standard procedure is to run the installer up > > to the point where it starts the partitioner (by which point it still > > hasn't written anything to the disks), then switch to tty2, mount your > > root filesystem on /target, and chroot. > > Maybe a installer option that would do just that would be a good idea. This > way we could redo the rescue functionality of the old boot-floppies. > > Not sure if it is easily doable technically though. It probably is, maybe a set of two .udebs which are placed just before partman in priority. The first one would check for the presence of a certain boot option (or cdebconf value set from the kernel command line) and drop into a shell, while the second would simply halt the machine or something such. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270550: Using d-i as rescue disk.
On Wed, Sep 08, 2004 at 04:43:43PM +0100, Colin Watson wrote: > On Wed, Sep 08, 2004 at 01:00:26PM +0100, Alex Owen wrote: > > In boot-floppies (bf) the bf kernel was installed in the target system. Is > > that the case in d-i ? > > No, it's not. > > > If the d-i kernel ins not installed on the target system then I think that > > the d-i boot floppy cannot have the "rescue" boot option that bf had as > > there will be no matching kernel modules in the root filesystem. > > Most of the modules are available in the d-i environment, although you > need to run the appropriate "Load installer components from ..." stage > to get a lot of them. The standard procedure is to run the installer up > to the point where it starts the partitioner (by which point it still > hasn't written anything to the disks), then switch to tty2, mount your > root filesystem on /target, and chroot. Maybe a installer option that would do just that would be a good idea. This way we could redo the rescue functionality of the old boot-floppies. Not sure if it is easily doable technically though. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270550: Using d-i as rescue disk.
On Wed, Sep 08, 2004 at 09:00:17PM +0200, siward wrote: > On Wednesday 08 September 2004 17:43, Colin Watson wrote: > > The standard procedure is to run the installer up > > to the point where it starts the partitioner (by which point it still > > hasn't written anything to the disks), then switch to tty2, mount your > > root filesystem on /target, and chroot. > > that is nice to hear, > but please note that i never got further than > installer showing these 2 lines about loading kernel and initrd. I don't know that bug, I'm afraid. It'll probably be a kernel problem, at a guess ... > Installer failing suggests that d-i is calling a bios routine there. > I expect that this also would need to be fixed, > i hope this is not hard, > maybe code is in woody's bootfloppies allready. d-i is a total and complete rewrite; code from boot-floppies is rarely at all applicable. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270550: Using d-i as rescue disk.
On Wednesday 08 September 2004 17:43, Colin Watson wrote: > The standard procedure is to run the installer up > to the point where it starts the partitioner (by which point it still > hasn't written anything to the disks), then switch to tty2, mount your > root filesystem on /target, and chroot. that is nice to hear, but please note that i never got further than installer showing these 2 lines about loading kernel and initrd. I never got to see any installer screen. I did not try to get a shell then, i expect that would not have been possible. Installer failing suggests that d-i is calling a bios routine there. I expect that this also would need to be fixed, i hope this is not hard, maybe code is in woody's bootfloppies allready. have fun, Siward
Bug#270550: Using d-i as rescue disk.
On Wed, Sep 08, 2004 at 01:00:26PM +0100, Alex Owen wrote: > In boot-floppies (bf) the bf kernel was installed in the target system. Is > that the case in d-i ? No, it's not. > If the d-i kernel ins not installed on the target system then I think that > the d-i boot floppy cannot have the "rescue" boot option that bf had as > there will be no matching kernel modules in the root filesystem. Most of the modules are available in the d-i environment, although you need to run the appropriate "Load installer components from ..." stage to get a lot of them. The standard procedure is to run the installer up to the point where it starts the partitioner (by which point it still hasn't written anything to the disks), then switch to tty2, mount your root filesystem on /target, and chroot. Automating this would, I think, be essentially a preseeding exercise, perhaps with the aid of an additional udeb. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#270550: Using d-i as rescue disk.
Am 2004-09-08 13:00:26, schrieb Alex Owen: > In boot-floppies (bf) the bf kernel was installed in the target system. Is > that the case in d-i ? Right > I seem to remember d-i asking me which kernel to install so I suspect this > means that the d-i kernel is not installed on the target system. Sometimes right... :-/ > If the d-i kernel ins not installed on the target system then I think that > the d-i boot floppy cannot have the "rescue" boot option that bf had as > there will be no matching kernel modules in the root filesystem. This is right... > The d-i can still be used as a rescue system by booting into expert mode > and then dropping to a shell to mount and fix your damaged system. Perhaps > a rescue mode could be added to d-i which loads up the ramdisk prompts > for language and keyboard info then drops to a root shell. This would be a > different kind of rescue mode to the old bf rescue mode. Why not use '/usr/sbin/mkrescue' ? > If I have got this wrong and we just need to add a rescue stanza to > syslinux.cfg (and simmilar for other arches) then do let me know and I'll > try to prepare a patch some time next week. > > Alex Owen Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Bug#270550: Using d-i as rescue disk.
On Wed, Sep 08, 2004 at 01:00:26PM +0100, Alex Owen wrote: > In boot-floppies (bf) the bf kernel was installed in the target system. Is > that the case in d-i ? > > I seem to remember d-i asking me which kernel to install so I suspect this > means that the d-i kernel is not installed on the target system. > > If the d-i kernel ins not installed on the target system then I think that > the d-i boot floppy cannot have the "rescue" boot option that bf had as > there will be no matching kernel modules in the root filesystem. > > The d-i can still be used as a rescue system by booting into expert mode > and then dropping to a shell to mount and fix your damaged system. Perhaps > a rescue mode could be added to d-i which loads up the ramdisk prompts > for language and keyboard info then drops to a root shell. This would be a > different kind of rescue mode to the old bf rescue mode. Another nice feature would be a easy way to rerun just the boot loader installation, for dual-boot cases, where some other os decided to wipe the boot loader. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270550: Using d-i as rescue disk.
In boot-floppies (bf) the bf kernel was installed in the target system. Is that the case in d-i ? I seem to remember d-i asking me which kernel to install so I suspect this means that the d-i kernel is not installed on the target system. If the d-i kernel ins not installed on the target system then I think that the d-i boot floppy cannot have the "rescue" boot option that bf had as there will be no matching kernel modules in the root filesystem. The d-i can still be used as a rescue system by booting into expert mode and then dropping to a shell to mount and fix your damaged system. Perhaps a rescue mode could be added to d-i which loads up the ramdisk prompts for language and keyboard info then drops to a root shell. This would be a different kind of rescue mode to the old bf rescue mode. If I have got this wrong and we just need to add a rescue stanza to syslinux.cfg (and simmilar for other arches) then do let me know and I'll try to prepare a patch some time next week. Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
