From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Replace 'sash' with 'busybox' as our static rescue shell
Date: Fri, 22 Apr 2005 09:51:29 -0400 [thread overview]
Message-ID: <1114177889.889.15.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200504220938.47437.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Fri, 2005-04-22 at 09:38 -0400, Mike Frysinger wrote:
> for those of you who do not know, busybox is a single binary which implements
> the functionality of most system utils ... it does not completely implement
> some features, just the most common ones, but then again sash does the same
> thing :)
>
> details:
> - busybox implements a *ton* more applets ... it can be configured to replace
> over 100 system funcs while sash provides about 35 ...
> - size wise, busybox would be larger, probably by about ~150k - ~200k
> - busybox commands are transparent while sash requires you to prefix internal
> commands with a '-' ... so running `cp` in busybox will use busybox's cp
> while sash needs to run '-cp', and you can still execute the real cp by
> doing /bin/cp in busybox
>
> feedback !?
Could this make it easier to use busybox for the actual root on a
LiveCD? If so, then I'm all for it.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-22 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 13:38 [gentoo-dev] Replace 'sash' with 'busybox' as our static rescue shell Mike Frysinger
2005-04-22 13:51 ` Chris Gianelloni [this message]
2005-04-22 14:03 ` Spider
2005-04-22 14:15 ` Ned Ludd
2005-04-22 14:51 ` Spider
2005-04-22 14:17 ` Mike Frysinger
2005-04-22 18:08 ` Stelian Ionescu
2005-04-22 19:26 ` Mike Frysinger
2005-04-23 4:44 ` [gentoo-dev] " Duncan
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=1114177889.889.15.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox