Changeset bc417a4 in freewrt

Timestamp:

Jul 27, 2006, 2:10:07 PM (19 years ago)

Author:

Thorsten Glaser <tg@…>

Branches:

freewrt_1_0, freewrt_2_0

Children:

9a87912

Parents:

6be9a4d9

Message:

flesh out shell stuff into extra file

git-svn-id: ​svn://www.freewrt.org/trunk/freewrt@438 afb5a338-a214-0410-bd46-81f09a774fd1

Location:

package

Files:

• Config.in (modified) (2 diffs)
• Config.shell (added)

package/Config.in

@@ -1 @@
-#
+# $FreeWRT$
 
 menu "Package Selection"
@@ -16 +16 @@
 source "package/nvram/Config.in"
 source "package/webif/Config.in"
-comment "/bin/sh"
-choice
-        prompt "Choose your default shell"
-        default BUSYBOX_CONFIG_FEATURE_SH_IS_ASH
-        help
-          Choose a shell which is to be used for /bin/sh.
-          The ash shell is the most bash-compatible shell
-          and full-featured one in busybox; mksh is a bit
-          more heavy-weight but feature-complete.
-
-config BUSYBOX_CONFIG_FEATURE_SH_IS_ASH
-        select BUSYBOX_CONFIG_ASH
-        bool "ash (busybox)"
-        help
-          Tha 'ash' shell adds about 60k in the default configuration and is
-          the most complete and most pedantically correct shell included with
-          busybox.  This shell is actually a derivative of the Debian 'dash'
-          shell (by Herbert Xu), which was created by porting the 'ash' shell
-          (written by Kenneth Almquist) from NetBSD.
-
-config FWRT_PACKAGE_MKSH_AS_BINSH
-        select FWRT_PACKAGE_MKSH
-        select BUSYBOX_CONFIG_FEATURE_SH_IS_NONE
-        bool "mksh"
-        help
-          mksh is the MirBSD enhanced version of the Public Domain Korn
-          shell (pdksh), a bourne-compatible shell which is largely similar
-          to the original AT&T Korn shell. It includes bug fixes and
-          feature improvements in order to produce a modern, robust shell
-          good for interactive and especially script use. Some sh/ksh/pdksh
-          compatibility kludges have been removed.
-
-config BUSYBOX_CONFIG_FEATURE_SH_IS_HUSH
-        select BUSYBOX_CONFIG_HUSH
-        bool "hush (busybox)"
-        help
-          hush is a very small shell (just 18k) and it has fairly complete
-          Bourne shell grammar.  It even handles all the normal flow control
-          options such as if/then/elif/else/fi, for/in/do/done, while loops,
-          etc.
-
-          It does not handle case/esac, select, function, here documents ( <<
-          word ), arithmetic expansion, aliases, brace expansion, tilde
-          expansion, &> and >& redirection of stdout+stderr, etc.
-
-config BUSYBOX_CONFIG_FEATURE_SH_IS_LASH
-        select BUSYBOX_CONFIG_LASH
-        bool "lash (busybox)"
-        help
-          lash is the very smallest shell (adds just 10k) and it is quite
-          usable as a command prompt, but it is not suitable for any but the
-          most trivial scripting (such as an initrd that calls insmod a few
-          times) since it does not understand any Bourne shell grammar.  It
-          does handle pipes, redirects, and job control though.  Adding in
-          command editing makes it a very nice lightweight command prompt.
-
-config BUSYBOX_CONFIG_FEATURE_SH_IS_MSH
-        select BUSYBOX_CONFIG_MSH
-        bool "msh (busybox)"
-        help
-          The minix shell (adds just 30k) is quite complete and handles things
-          like for/do/done, case/esac and all the things you expect a Bourne
-          shell to do.  It is not always pedantically correct about Bourne
-          shell grammar (try running the shell testscript "tests/sh.testcases"
-          on it and compare vs bash) but for most things it works quite well.
-          It also uses only vfork, so it can be used on uClinux systems.
-
-endchoice
+source "package/Config.shell"
 endmenu