Re: vi almost unusable in recovery console
- From: "Brian McKee" <brian.mckee@xxxxxxxxx>
- Date: Thu, 31 Jul 2008 16:56:07 -0400
On Thu, Jul 31, 2008 at 3:35 PM, NoOp <glgxg@xxxxxxxxxxxxx> wrote:
On 07/31/2008 10:36 AM, Brian McKee wrote:
I'm off to file a bug - wish I knew what the right package to complainI just loaded up "rescue a broken system" and see what you mean. FYI:
about was.
I'm kinda shocked nobody's noticed this before. Maybe I'm missing
something obvious - or maybe everybody just uses the live cd for this
stuff normally.
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/154396
https://bugs.launchpad.net/ubuntu/+source/rescue/+bug/35400
https://bugs.launchpad.net/ubuntu/+source/rescue/+bug/228249
Your Launchpad foo is better than mine - I only spotted some of those.
My bug is https://bugs.launchpad.net/bugs/253758
If you have a working network connection on the machine:
# apt-get install bogl-bterm
That installs bterm and thereafter you will be able to use vi or nano in
"rescue a broken system". This is a pretty serious bug IMO as you
shouldn't have to have a network connection the "rescue a broken system".
Aha ! Thank you - that does help me out. I hadn't realized the
problem was that bterm wasn't even installed.
Maybe that's why the other bugs that mention disabling framebuffer worked.
I'll update the bug.
Brian
--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
- References:
- vi almost unusable in recovery console
- From: Brian McKee
- Re: vi almost unusable in recovery console
- From: NoOp
- Re: vi almost unusable in recovery console
- From: Brian McKee
- Re: vi almost unusable in recovery console
- From: NoOp
- vi almost unusable in recovery console
- Prev by Date: Re: Win98 -- all kidding aside
- Next by Date: RE: Win98 -- all kidding aside
- Previous by thread: Re: vi almost unusable in recovery console
- Next by thread: Re: problem removing package (Fixed)
- Index(es):
Relevant Pages
|