What to do when Ubuntu boots into Busybox CLI?
dotancohen at gmail.com
Tue Mar 11 19:02:52 UTC 2008
On 11/03/2008, Liam Proven <lproven at gmail.com> wrote:
> On 11/03/2008, Dotan Cohen <dotancohen at gmail.com> wrote:
> > On 11/03/2008, Liam Proven <lproven at gmail.com> wrote:
> > > On 09/03/2008, Dotan Cohen <dotancohen at gmail.com> wrote:
> > > > What should one do when booting Ubuntu gets the Busybox CLI screen?
> > >
> > > Are you sure it's Busybox and not a vanilla Bash shell?
> > It clearly says Busybox. I've never heard of busybox before this incident.
> It's a very small all-in-one shell replacement that also includes a
> large number of what are normally external commands. It's often used
> in embedded Linux and distros intended to boot from a single floppy
> and things like that: very resource-constrained installations, in
> other words. I had no idea the Ubuntu install used it, though!
Yes, I discovered that's what is it by googling it. It has all the
commands in a single program, saving overhead. In some commands, the
overhead can apparently be over 80% of the program.
> > I did mean irqpoll. Freud would have something wise to say about that
> > slip, I'm sure.
> :¬) Just checking. I'm sure that "ircpoll" wouldn't help very much.
irqpoll didn't help much, either :)
> Just out of interest, I've found that on at least one recalcitrant
> system, "acpi=force" worked better than "acpi=off" or "noacpi".
> Compelling the kernel to enable it on an elderly BIOS, rather than
> forcing it to be disabled, got Ubuntu 7.04 to at least boot.
I will try that, thanks.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
More information about the ubuntu-users