From: Spider <spider@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 16:51:21 +0200 [thread overview]
Message-ID: <1114181481.3552.13.camel@Darkmere> (raw)
In-Reply-To: <1114179312.32174.5.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Fri, 2005-04-22 at 10:15 -0400, Ned Ludd wrote:
> On Fri, 2005-04-22 at 16:03 +0200, Spider wrote:
> > On Fri, 2005-04-22 at 09:38 -0400, Mike Frysinger wrote:
> >> [STUFF]..
>
>
> > Oh, and unless you have another editor as binary built into your shell,
> > don't remove ed. A "trusted" editor is good. Sash is seldom used for
> > "My system is haxxored" however its often used for "I fucked up glibc"
> > and an editor is a handy thing, even if its as obscure as "ed"
>
> busybox.static would provide a minimal vi editor.
>
> A default compile should produce the following applets (give or take a
> few based on what the new ebuild will provide)
>
<snip>
Yep, and the vi editor would be a very good choice as an builtin.
Especially since its far easier to use than Ed is.
( yes, this is an area I feel rather strongly about, its not a single
time that I've been in static shells doing system recovery after either
hardware,software or administrator failure. Having a good recovery
system on-disk is wonderful )
//Spider
--
begin .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end
[-- 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 14:50 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
2005-04-22 14:03 ` Spider
2005-04-22 14:15 ` Ned Ludd
2005-04-22 14:51 ` Spider [this message]
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=1114181481.3552.13.camel@Darkmere \
--to=spider@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