editors in rescue mode (thanks)

[Brian McKee]

On Mon, Aug 4, 2008 at 3:38 PM, NoOp <glgxg at sbcglobal.net> wrote:
> On 08/04/2008 12:20 AM, Robert Holtzman wrote:
>> On Sun, 3 Aug 2008, NoOp wrote:
>>> It wouldn't have worked properly anyway; see Brian's earlier thread on
>>> this: "vi almost unusable in recovery console"
>>
>> I had skipped over that thread before but went back and picked it up.
>>
>>>
>>> If you have a working network connection on the machine:
>>>
>>> # apt-get install bogl-bterm
>>
>> To ask a stupid question: in recovery mode?
>
> To add to my previous: I just brought up the Alternate CD and arrowed
> down to "Rescue a broken system". I then selected F6 and selected
> "Expert Mode" and allowed it to boot. That brings up a menu:
> o choose language
> o configure keyboard
> o detect and mount cd-rom
> o load installer components from cd
> o change debconf priority
> o check the cd-rom(s) integrity
> o save debug logs
> o execute a shell
> o abort the installation
>
> [I've never tried the "Expert Mode" before]
>
> I selected "Execute a shell" and the menu then brings up:
> <quote>
> After this message, you will be running "ash", a Bourne-shell clone.
>
> The root file is a RAM disk. The hard disk file systems are mounted on
> "/target". The editor available to you is nano. It's very small and easy
> to figure out. To get an idea of what Unix utilities are available to
> you, use the "help" command.
> </quote>
>
> From there I cd'd to /usr/share/terminfo/b/ and sure enough, bterm is
> there _and_ nano is working normally. I've no idea why it doesn't work
> in non-expert mode (yet).

Huh,  I never tried that either.  I'll have to twiddle more.
Thanks for noticing.

Brian