From: Rob Landley <rob@landley.net>
To: Isaac Dunham <idunham@lavabit.com>
Cc: toybox@lists.landley.net, musl@lists.openwall.com
Subject: Re: [Toybox] [musl] Re: toybox: Rough edges in pending
Date: Wed, 20 Mar 2013 01:22:05 -0500 [thread overview]
Message-ID: <1363760525.15703.43@driftwood> (raw)
In-Reply-To: <20130319123221.ddd8eb53.idunham@lavabit.com> (from idunham@lavabit.com on Tue Mar 19 14:32:21 2013)
On 03/19/2013 02:32:21 PM, Isaac Dunham wrote:
> A couple things that would have cleared this up for me--
> Either a note in toys/pending/README that said:
> "Code in this directory may or may not work." (somehow, "...await
> review
> and/or cleanup" doesn't seem to communicate this)
Good point. I'll add a note.
> or a "CONFIG_WORKING" that prevents enabling toys that are
> nonfunctional without
> realizing it (iirc, the kernel has a trick along these lines, so make
> allyesconfig
> doesn't turn _everything_ on).
The rule has been that "default n" means it's not ready.
(My current corner case here is "who", which works as advertised but
posix says it should support a bunch of options that it doesnt' yet,
and I don't want to make it default y and forget to add them. But when
I say "a bunch" I mean "-abdHlmpqrstTu" which I haven't had time to
just sit down and implement yet, and possibly we want to document a
variance and go "really, this is minicomputer stuff, modern systems
don't usually have lots of multiple simultaneous users without
containers anymore...")
> > > Also, when toybox is built with musl, and toybox sh executes ls,
> > > I get a hang; strace indicates that something funny is going on:
> >
> > I am honestly amazed it got _that_ far.
> >
> > > I anticipate this is a bug in musl, so I'll cross-post.
> >
> > If toysh _isn't_ corrupting the heap or something similar, I'd be
> > stunned. It's not a real command yet.
>
> Surprisingly enough, it makes it far enough to give the illusion it
> might be usable.
It's an illusion. It's using toybuf for parsing so the command line
can't be longer than 4k (kernel limit's 128k and I've seen patches
raise it), it has no environment variable support, can't parse quotes
(which turns out to be quite funky because "$(echo "hello world")" has
nested quote contexts), no flow control implemented yet (if, while,
shell functions...), no &&, ||, or pipeline support...
And so on, and so forth... One of my current half-finished pending
things I haven't even bothered to check in yet is test.c (which
implements [ and [[ the way "bc" shares code with $(())), and once I've
got that I can dink at toysh a bit and at least redo the parsing.
Anyway, not a musl thing. Feel free to poke me just on the toybox list
if you think i should take a weekend and make toysh suck less, but the
_scope_ of the shell promblem is...
http://landley.net/notes-2006.html#31-08-2006
http://landley.net/notes-2006.html#10-09-2006
http://landley.net/notes-2007.html#20-01-2007
http://landley.net/notes-2007.html#19-10-2007
Stuff.
Rob
prev parent reply other threads:[~2013-03-20 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 6:50 Isaac Dunham
2013-03-19 9:42 ` Szabolcs Nagy
2013-03-19 11:09 ` Szabolcs Nagy
[not found] ` <20130319110939.GJ19010-4P1ElwuDYu6sTnJN9+BGXg@public.gmane.org>
2013-03-19 17:33 ` [musl] " Rob Landley
2013-03-19 17:20 ` [Toybox] " Rob Landley
2013-03-19 19:32 ` [musl] " Isaac Dunham
2013-03-20 6:22 ` Rob Landley [this message]
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=1363760525.15703.43@driftwood \
--to=rob@landley.net \
--cc=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
--cc=toybox@lists.landley.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).