hi,
Thanks for your pointers. Please see my concerns
in-line.
--- Luciano Rocha <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 25, 2008 at 10:48:15AM +0000,
> kalyanatejaswi balabhadrapatruni wrote:
> > Hi,
> > I did "help" in sash shell and compared the output
> to
> > the commands i found in BB-1.9.0 as
> > 1. shell/ash.c built-in commands and
> > 2. NOFORK (or even NOEXEC ) applets
> >
> > And these are what i found missing in BB-1.9.0 as
> > built-in commands:
> >
> > aliasall,
>
> Not applicable.
>
> > setenv, quit, source
>
> These must be in ash, if not under different name:
> - setenv -> export var=val
> - quit -> exit
> - source -> source and .; could never be an external
> command, like "cd"
>
> > ar, chattr, cmp, ed, file, grep, gunzip,
> > lsattr, mknod, more, mount, mv, printenv, prompt,
> > sum, tar, umount, where
>
> These should all be available, but they don't need
> to be marked as
> built-in.
But if they are not implemented as builtin, we are
loosing primary advantage of built-in commands, i.e.,
no forking overhead. Isnt it?
If you can run ash, you can run the
> others, if compiled in
> busybox. You do have a configuration switch for
> trying compiled-in
> commands first.
Is CONFIG_FEATURE_SH_STANDALONE feature you are
suggesting? As i understand, this feature helps in
case my system is screwed up and busybox comes to the
rescue with its commands. But again, it doesnt ensure
"no forking" for non built-in commands. Isnt it?
>
> --
> lfr
> 0/0
>
Meet people who discuss and share your passions. Go to
http://in.promos.yahoo.com/groups
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
