All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Tom Rini <trini@konsulko.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Removing busybox
Date: Wed, 27 Feb 2019 23:40:37 +0200	[thread overview]
Message-ID: <20190227214037.GA11051@localhost> (raw)
In-Reply-To: <20190227200902.GG12046@bill-the-cat>

On Wed, Feb 27, 2019 at 03:09:02PM -0500, Tom Rini wrote:
> On Wed, Feb 27, 2019 at 09:06:38PM +0100, Jean-Christian de Rivaz wrote:
>...
> > So as expected systemd is there and busybox is not. But there is a lot of
> > useful commands missing on the resulting QEMU image:
> > 
> > root@qemux86:~# ps
> > ~sh: ps: command not found
> > root@qemux86:~# w
> > ~sh: w: command not found
> > root@qemux86:~# find
> > ~sh: find: command not found
> > root@qemux86:~# grep
> > ~sh: grep: command not found
> > root@qemux86:~# ip addr
> > ~sh: ip: command not found
> > 
> > I expected that all the limited busybox commands would be replaced by
> > the full
> > featured commands. How to fix that ?
> 
> Correct, you're missing a lot of stuff.  Somewhere on my (and other
> folks too) TODO list is a packagegroup that includes procps and psmisc
> and grep and tar and various network packages and less and more and...

"all the limited busybox commands would be replaced" would be a huge 
list from dc through gawk, minicom and wget to vim.

And would vim-tiny qualify as "the full featured command" of busybox vi,
or should this include vim with full features?

The nice thing about busybox is that it is so small,
in many cases one full featured command alone
is bigger than busybox.

It is not obvious to me what usecases people have in mind for
getting rid of busybox, and whether everyone is aware that
something like "all busybox commands replaced" is *very*
expensive regarding filesystem size.

> Tom

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  parent reply	other threads:[~2019-02-27 21:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 12:16 Removing busybox Jean-Christian de Rivaz
2019-02-27 17:06 ` Tom Rini
2019-02-27 17:25   ` Mark Hatle
2019-02-27 17:42     ` Burton, Ross
2019-02-27 17:58       ` Tom Rini
2019-02-27 18:35         ` Burton, Ross
2019-02-27 18:45           ` Tom Rini
2019-02-27 18:47             ` Burton, Ross
2019-02-27 18:54               ` Tom Rini
2019-02-27 18:48             ` Scott Rifenbark
2019-02-28 18:43       ` Tom Rini
2019-02-27 20:06   ` Jean-Christian de Rivaz
2019-02-27 20:09     ` Tom Rini
2019-02-27 21:31       ` Paul Eggleton
2019-02-27 21:35         ` Tom Rini
2019-02-27 21:40       ` Adrian Bunk [this message]
2019-02-27 21:46         ` Tom Rini
2019-02-27 21:49         ` Burton, Ross
2019-02-27 22:24         ` Jean-Christian de Rivaz
2019-02-27 22:58           ` Philip Balister
2019-02-27 23:02           ` Burton, Ross
2019-02-27 23:54             ` Tom Rini
2019-02-27 23:59               ` Burton, Ross
2019-02-28  0:10                 ` Jean-Christian de Rivaz
2019-02-28  0:11                   ` Burton, Ross
2019-02-28  5:19                 ` Adrian Bunk
2019-02-28 12:05                   ` Burton, Ross
2019-02-28 14:27                     ` Richard Purdie
2019-02-28 14:37                       ` Tom Rini
2019-02-28 14:55                         ` Richard Purdie
2019-02-28 15:30                   ` Jean-Christian de Rivaz
2019-03-02 18:38                   ` Randy MacLeod

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190227214037.GA11051@localhost \
    --to=bunk@stusta.de \
    --cc=trini@konsulko.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.