POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
Busybox POSIX conformance table
|
|
|
|
|
|
|
|
See POSIX documentation (1003.1-2008) here:
|
|
|
|
http://www.opengroup.org/onlinepubs/9699919799/
|
|
|
|
And the complete list of all utilities that POSIX covers:
|
2009-06-12 19:02:51 +05:30
|
|
|
http://www.opengroup.org/onlinepubs/9699919799/idx/utilities.html
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
2009-07-19 04:39:42 +05:30
|
|
|
This listing is a work in progress, and currently only covers
|
2009-09-06 06:28:59 +05:30
|
|
|
tool options (not operands, environment variables, return codes, etc..).
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
For each option it is set if it (a) exists and (b) compliant to POSIX 2008.
|
|
|
|
Some options exist but there is no value in the 'compliant' column: that
|
2009-07-19 04:39:42 +05:30
|
|
|
means no one has yet bothered to make sure that the option does what it is
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
required to do.
|
|
|
|
|
|
|
|
-----------------------------------------------
|
|
|
|
|
|
|
|
POSIX Tools supported only as shell built-ins (ash shell):
|
2009-07-19 04:39:42 +05:30
|
|
|
alias, bg, cd, fg, getopts, hash, jobs, read, type, umask, ulimit,
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
unalias, wait, write
|
|
|
|
|
|
|
|
POSIX Tools not supported:
|
2009-07-19 04:39:42 +05:30
|
|
|
asa, at, batch, bc, c99, command, compress, csplit, ex, fc, file,
|
|
|
|
gencat, getconf, iconv, join, link, locale, localedef, lp, m4,
|
2017-03-23 22:05:20 +05:30
|
|
|
mailx, newgrp, nl, pathchk, pax, pr, qalter, qdel, qhold, qmove,
|
2009-07-19 04:39:42 +05:30
|
|
|
qmsg, qrerun, qrls, qselect, qsig, qstat, qsub, tabs, talk, tput,
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
tsort, unlink, uucp, uustat, uux
|
|
|
|
|
|
|
|
POSIX Tools not supported (DEVELOPMENT):
|
2009-07-19 04:39:42 +05:30
|
|
|
admin, cflow, ctags, cxref, delta, fort77, get, lex, make, nm, prs, rmdel,
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
sact, sccs, strip, unget, val, what, yacc
|
|
|
|
|
|
|
|
|
|
|
|
POSIX Tools supported:
|
|
|
|
|
2009-07-19 04:39:42 +05:30
|
|
|
Note: echo, printf, kill, pwd documented here as stand-alone applets,
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
not as ash built-ins.
|
|
|
|
|
|
|
|
|
2009-06-12 19:02:51 +05:30
|
|
|
ar POSIX options ********************* Failed to recognize zip & tar (did not compare to regular ar)
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-C | no | no |
|
|
|
|
-T | no | no |
|
|
|
|
-a | no | no |
|
|
|
|
-b | no | no |
|
|
|
|
-c | no | no |
|
|
|
|
-d | no | no |
|
|
|
|
-i | no | no |
|
|
|
|
-m | no | no |
|
|
|
|
-p | yes | |
|
|
|
|
-q | no | no |
|
|
|
|
-r | no | no |
|
|
|
|
-s | no | no |
|
|
|
|
-t | yes | |
|
|
|
|
-u | no | no |
|
|
|
|
-v | yes | |
|
|
|
|
-x | yes | |
|
|
|
|
ar Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-o
|
|
|
|
|
|
|
|
awk POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-F ERE | yes | |
|
|
|
|
-f progfile | yes | |
|
|
|
|
-v assignment | yes | |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
awk Busybox specific options: None
|
|
|
|
|
|
|
|
basename POSIX options: None
|
|
|
|
basename Busybox specific options: None
|
|
|
|
|
|
|
|
cal POSIX options: None
|
2009-07-19 04:39:42 +05:30
|
|
|
cal Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-y, -j
|
|
|
|
|
|
|
|
cat POSIX options
|
|
|
|
option | exists | compliant | remarks
|
|
|
|
-u | yes | no | option is ignored
|
|
|
|
cat Busybox specific options: None
|
|
|
|
|
|
|
|
chgrp POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | yes | |
|
|
|
|
-L | yes | |
|
|
|
|
-P | yes | |
|
|
|
|
-R | yes | |
|
|
|
|
-h | yes | |
|
|
|
|
chgrp Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-f, -c, -v
|
|
|
|
|
|
|
|
chmod POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-R | yes | yes |
|
|
|
|
chmod Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-f, -v, -c
|
|
|
|
|
2009-06-12 19:02:51 +05:30
|
|
|
chown POSIX options *********************************************
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
option | exists | compliant | remarks
|
2009-06-12 19:02:51 +05:30
|
|
|
-H | yes | | It seems like all flags are supported (according to printout), but
|
|
|
|
-L | yes | | it fails to work on my machine
|
2009-07-19 04:39:42 +05:30
|
|
|
-P | yes | |
|
|
|
|
-R | yes | |
|
|
|
|
-h | yes | |
|
|
|
|
chown Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-f, -c, -v
|
|
|
|
|
|
|
|
cksum POSIX options: None
|
|
|
|
cksum Busybox specific options: None
|
|
|
|
|
|
|
|
cmp POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-l | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
cmp Busybox specific options:
|
|
|
|
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
comm POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-1 | yes | yes |
|
|
|
|
-2 | yes | yes |
|
|
|
|
-3 | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
comm Busybox specific options: None
|
|
|
|
|
|
|
|
cp POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | yes | yes |
|
|
|
|
-L | yes | yes |
|
|
|
|
-P | yes | yes |
|
|
|
|
-R | yes | yes |
|
|
|
|
-f | yes | yes |
|
|
|
|
-i | yes | yes |
|
|
|
|
-p | yes | yes |
|
|
|
|
cp Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-d, -a, -s, -c, -r, -l
|
|
|
|
|
|
|
|
crontab POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-e | yes | |
|
|
|
|
-l | yes | |
|
|
|
|
-r | yes | |
|
|
|
|
crontab Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-u, -c
|
|
|
|
|
|
|
|
cut POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-b list | yes | yes |
|
|
|
|
-c list | yes | yes |
|
|
|
|
-d delim | yes | yes |
|
|
|
|
-f list | yes | yes |
|
|
|
|
-n | yes | yes |
|
|
|
|
-s | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
cut Busybox specific options: None
|
|
|
|
|
|
|
|
date POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-u | yes | yes |
|
|
|
|
date Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-I[SPEC], -d TIME, -r FILE, -R, -D FMT
|
|
|
|
|
2009-06-12 19:02:51 +05:30
|
|
|
dd POSIX options:
|
|
|
|
option | exists | compliant | remarks
|
|
|
|
if | yes | |
|
|
|
|
of | yes | |
|
|
|
|
ibs | yes | |
|
|
|
|
obs | yes | |
|
|
|
|
bs | yes | |
|
|
|
|
cbs | no | no |
|
|
|
|
skip | yes | |
|
|
|
|
seek | yes | |
|
|
|
|
count | yes | |
|
2009-07-19 04:39:42 +05:30
|
|
|
conv=ascii | no | no |
|
2009-06-12 19:02:51 +05:30
|
|
|
conv=ebcdic | no | no |
|
|
|
|
conv=ibm | no | no |
|
|
|
|
conv=block | no | no |
|
|
|
|
conv=unblock | no | no |
|
|
|
|
conv=lcase | no | no |
|
|
|
|
conv=ucase | no | no |
|
|
|
|
conv=swap | no | no |
|
|
|
|
conv=noerror | yes | |
|
|
|
|
conv=notrunc | yes | |
|
|
|
|
conv=sync | yes | |
|
2016-02-01 06:47:28 +05:30
|
|
|
iflag=skip_bytes| yes | |
|
2009-07-19 04:39:42 +05:30
|
|
|
dd Busybox specific options:
|
2009-06-12 19:02:51 +05:30
|
|
|
conv=fsync
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
df POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-P | yes | yes |
|
|
|
|
-k | yes | yes |
|
|
|
|
-t | no | no |
|
|
|
|
df Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-a, -m, -B SIZE, -i, -h
|
2009-06-12 19:02:51 +05:30
|
|
|
Remark:
|
2009-06-15 12:46:27 +05:30
|
|
|
- It seems that GNU df does not round percents up in its output (thus its results are a bit different)
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
diff POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-C n | no | no |
|
|
|
|
-U n | yes | |
|
|
|
|
-b | yes | |
|
|
|
|
-c | no | no |
|
|
|
|
-e | no | no |
|
|
|
|
-f | no | no |
|
|
|
|
-r | yes | |
|
|
|
|
-u | no | no |
|
|
|
|
diff Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-d, -a, -s, -t, -L, -N, -i, -T, -w, -q, -S
|
|
|
|
|
|
|
|
dirname POSIX options: None
|
|
|
|
dirname Busybox specific options: None
|
|
|
|
|
|
|
|
du POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | yes | |
|
|
|
|
-L | yes | |
|
|
|
|
-a | yes | |
|
|
|
|
-k | yes | |
|
|
|
|
-s | yes | |
|
|
|
|
-x | yes | |
|
|
|
|
du Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-c, -m, -h, -d N, -l
|
|
|
|
|
2009-06-12 19:02:51 +05:30
|
|
|
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
echo POSIX options: None
|
2009-06-12 19:02:51 +05:30
|
|
|
option | exists | compliant | remarks
|
|
|
|
-n | yes | yes | The result of -n is "implementation-defined"
|
2009-07-19 04:39:42 +05:30
|
|
|
echo Busybox specific options:
|
2009-06-12 19:02:51 +05:30
|
|
|
-e, -E
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
ed POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-p string | no | no |
|
|
|
|
-s | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
ed Busybox specific options: None
|
|
|
|
|
|
|
|
env POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-i | no | no |
|
|
|
|
env Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-u, -, -i
|
|
|
|
|
|
|
|
expand POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-t tablist | yes | yes |
|
|
|
|
expand Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
--tabs=N, -i, --initial
|
|
|
|
|
2009-06-12 19:02:51 +05:30
|
|
|
expr POSIX operations:
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
| | yes | yes |
|
|
|
|
& | yes | yes |
|
|
|
|
= | yes | yes |
|
|
|
|
> | yes | yes |
|
|
|
|
>= | yes | yes |
|
|
|
|
<= | yes | yes |
|
|
|
|
< | yes | yes |
|
|
|
|
!= | yes | yes |
|
|
|
|
+ | yes | yes |
|
|
|
|
- | yes | yes |
|
|
|
|
* | yes | yes |
|
|
|
|
/ | yes | yes |
|
|
|
|
% | yes | yes |
|
|
|
|
: | yes | yes |
|
|
|
|
(expr) | yes | yes |
|
|
|
|
integer | yes | yes |
|
|
|
|
string | yes | yes |
|
|
|
|
expr Busybox specific operations:
|
2009-06-12 19:02:51 +05:30
|
|
|
match, substr, index, length, quote
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
|
|
|
|
false POSIX options: None
|
|
|
|
false Busybox specific options: None
|
|
|
|
|
|
|
|
find POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | no | no |
|
|
|
|
-L | no | no |
|
|
|
|
find Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-group NAME, -mtime DAYS, -print, -maxdepth N, -exec CMD ARG ;, -newer FILE, -context, -iname PATTERN, -follow, -depth, -xdev, -inum N, -type X, -print0, -mindepth N, -mmin MINS, -regex PATTERN, -prune, -path PATTERN, -user NAME, -delete, -perm NNN, -name PATTERN, -size N[bck]
|
|
|
|
|
|
|
|
fold POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-b | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
-w width | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
fold Busybox specific options: None
|
|
|
|
|
|
|
|
fuser POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | no | no |
|
|
|
|
-f | no | no |
|
|
|
|
-u | no | no |
|
|
|
|
fuser Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-m, -k, -4, -SIGNAL, -6, -s
|
|
|
|
|
|
|
|
grep POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-E | yes | |
|
|
|
|
-F | yes | |
|
|
|
|
-c | yes | |
|
|
|
|
-e pattern_list | yes | |
|
|
|
|
-f pattern_file | yes | |
|
|
|
|
-i | yes | |
|
|
|
|
-l | yes | |
|
|
|
|
-n | yes | |
|
|
|
|
-q | yes | |
|
|
|
|
-s | yes | |
|
|
|
|
-v | yes | |
|
|
|
|
-x | no | no |
|
|
|
|
grep Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-A, -C, -B, -L, -H, -o, -h, -w, -r, -z, -m MAX
|
|
|
|
|
|
|
|
head POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-n number | yes | yes |
|
|
|
|
head Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-v, -c NUM, -q
|
|
|
|
|
|
|
|
id POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-G | yes | yes |
|
|
|
|
-g | yes | yes |
|
|
|
|
-n | yes | yes |
|
|
|
|
-r | yes | yes |
|
|
|
|
-u | yes | yes |
|
|
|
|
id Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-Z
|
|
|
|
|
|
|
|
ipcrm POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-M shmkey | no | no |
|
|
|
|
-Q msgkey | no | no |
|
|
|
|
-S semkey | no | no |
|
|
|
|
-m shmid | no | no |
|
|
|
|
-q msgid | no | no |
|
|
|
|
-s semid | no | no |
|
|
|
|
ipcrm Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-mM, -qQ, -sS
|
|
|
|
|
|
|
|
ipcs POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | yes | |
|
|
|
|
-b | no | no |
|
|
|
|
-c | yes | |
|
|
|
|
-m | yes | |
|
|
|
|
-o | no | no |
|
|
|
|
-p | yes | |
|
|
|
|
-q | yes | |
|
|
|
|
-s | yes | |
|
|
|
|
-t | yes | |
|
|
|
|
ipcs Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-l, -i, -u
|
|
|
|
|
|
|
|
kill POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-l | yes | yes |
|
|
|
|
-s signal_name | yes | yes |
|
|
|
|
-signal_name | yes | yes |
|
|
|
|
-signal_number | yes | yes |
|
|
|
|
kill Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-q, -o
|
|
|
|
|
|
|
|
ln POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-L | no | no |
|
|
|
|
-P | no | no |
|
|
|
|
-f | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
ln Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-S suf, -n, -b
|
|
|
|
|
|
|
|
logger POSIX options: None
|
2009-07-19 04:39:42 +05:30
|
|
|
logger Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-p PRIO, -t TAG, -s
|
|
|
|
|
|
|
|
logname POSIX options: None
|
|
|
|
logname Busybox specific options: None
|
|
|
|
|
|
|
|
ls POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-1 | yes | yes |
|
|
|
|
-A | yes | yes |
|
|
|
|
-C | yes | yes |
|
2009-06-12 19:02:51 +05:30
|
|
|
-F | yes | yes | And more: '=' for sockets (not defined by POSIX)
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | no | no |
|
2009-06-12 19:02:51 +05:30
|
|
|
-L | yes | yes | But coloring may be wrong (at least POSIX does not require correct colors :) )
|
2009-07-19 04:39:42 +05:30
|
|
|
-R | yes | yes |
|
|
|
|
-S | yes | yes |
|
|
|
|
-a | yes | yes |
|
2009-06-12 19:02:51 +05:30
|
|
|
-c | yes | no | Sorts output with '-l' (should only show ctime with '-l', and sort only with '-t')
|
|
|
|
-d | yes | no | When invoked together with '-L' should read symbolic links, and doesn't
|
2009-07-19 04:39:42 +05:30
|
|
|
-f | no | no |
|
|
|
|
-g | no | no |
|
|
|
|
-i | yes | yes |
|
2009-06-12 19:02:51 +05:30
|
|
|
-k | yes | no | Does something completely unrelated! (Lists security context instead of specifying block size)
|
2009-07-19 04:39:42 +05:30
|
|
|
-l | yes | yes |
|
|
|
|
-m | no | no |
|
2009-06-12 19:02:51 +05:30
|
|
|
-n | yes | no | Works correctly only together with '-l' (but POSIX requires '-l' to be implicitly assumed)
|
2009-07-19 04:39:42 +05:30
|
|
|
-o | no | no |
|
|
|
|
-p | yes | yes |
|
|
|
|
-q | no | no |
|
|
|
|
-r | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
-t | yes | yes |
|
|
|
|
-u | yes | yes |
|
|
|
|
-x | yes | yes |
|
|
|
|
ls Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
--color, -T NUM, -K, -X, -Z, -e, -h, -v, -w NUM
|
|
|
|
|
|
|
|
man POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-k | no | no |
|
|
|
|
man Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-a Display all pages
|
|
|
|
|
|
|
|
|
|
|
|
mesg POSIX options: None
|
|
|
|
mesg Busybox specific options: None
|
|
|
|
|
|
|
|
mkdir POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-m mode | yes | yes |
|
|
|
|
-p | yes | yes |
|
|
|
|
mkdir Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-Z
|
|
|
|
|
|
|
|
mkfifo POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-m mode | yes | yes |
|
|
|
|
mkfifo Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-Z
|
|
|
|
|
|
|
|
more POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | no | no |
|
|
|
|
-e | no | no |
|
|
|
|
-i | no | no |
|
|
|
|
-n number | no | no |
|
|
|
|
-p command | no | no |
|
|
|
|
-s | no | no |
|
|
|
|
-t tagstring | no | no |
|
|
|
|
-u | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
more Busybox specific options: None
|
|
|
|
|
|
|
|
mv POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-f | yes | yes |
|
|
|
|
-i | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
mv Busybox specific options: None
|
|
|
|
|
|
|
|
nice POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-n increment | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
nice Busybox specific options: None
|
|
|
|
|
|
|
|
nohup POSIX options: None
|
|
|
|
nohup Busybox specific options: None
|
|
|
|
|
|
|
|
od POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-A address_base | no | no |
|
|
|
|
-N count | no | no |
|
|
|
|
-b | no | no |
|
|
|
|
-c | no | no |
|
|
|
|
-d | no | no |
|
|
|
|
-j skip | no | no |
|
|
|
|
-o | no | no |
|
|
|
|
-s | no | no |
|
|
|
|
-t type_string | no | no |
|
|
|
|
-v | no | no |
|
|
|
|
-x | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
od Busybox specific options: None
|
|
|
|
|
2017-03-23 22:05:20 +05:30
|
|
|
paste POSIX options
|
|
|
|
option | exists | compliant | remarks
|
|
|
|
-d list | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
paste Busybox specific options: None
|
|
|
|
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
patch POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-D define | no | no |
|
|
|
|
-N | no | no |
|
|
|
|
-R | yes | yes |
|
|
|
|
-b | no | no |
|
|
|
|
-c | no | no |
|
|
|
|
-d dir | no | no |
|
|
|
|
-e | no | no |
|
|
|
|
-i patchfile | yes | yes |
|
|
|
|
-l | no | no |
|
|
|
|
-n | no | no |
|
|
|
|
-o outfile | no | no |
|
|
|
|
-p num | yes | yes |
|
|
|
|
-r rejectfile | no | no |
|
|
|
|
-u | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
patch Busybox specific options: None
|
|
|
|
|
|
|
|
printf POSIX options: None
|
|
|
|
printf Busybox specific options: None
|
|
|
|
|
|
|
|
ps POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-A | no | no |
|
|
|
|
-G grouplist | no | no |
|
|
|
|
-U userlist | no | no |
|
|
|
|
-a | no | no |
|
|
|
|
-d | no | no |
|
|
|
|
-e | no | no |
|
|
|
|
-f | no | no |
|
|
|
|
-g grouplist | no | no |
|
|
|
|
-l | no | no |
|
|
|
|
-n namelist | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-o format | yes | no | not supported: ruser, group, rgroup, pcpu
|
2009-07-19 04:39:42 +05:30
|
|
|
-p proclist | no | no |
|
|
|
|
-t termlist | no | no |
|
|
|
|
-u userlist | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
ps Busybox specific options: None
|
|
|
|
|
|
|
|
pwd POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-L | no | no |
|
|
|
|
-P | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
pwd Busybox specific options: None
|
|
|
|
|
|
|
|
renice POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-g | yes | yes |
|
2009-06-12 19:02:51 +05:30
|
|
|
-n increment | yes | yes | Note POSIX allows only to run with this option (busybox also allows to run without '-n' and set niceness directly)
|
2009-07-19 04:39:42 +05:30
|
|
|
-p | yes | yes |
|
|
|
|
-u | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
renice Busybox specific options: None
|
|
|
|
|
|
|
|
rm POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-R | yes | yes |
|
|
|
|
-f | yes | yes |
|
|
|
|
-i | yes | yes |
|
|
|
|
-r | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
rm Busybox specific options: None
|
|
|
|
|
|
|
|
rmdir POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-p | yes | yes |
|
|
|
|
rmdir Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
--parents
|
|
|
|
|
|
|
|
sed POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-e script | yes | |
|
|
|
|
-f script_file | yes | |
|
|
|
|
-n | yes | |
|
|
|
|
sed Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-i, -r
|
|
|
|
|
|
|
|
sh POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | no | no |
|
|
|
|
-i | no | no |
|
|
|
|
-s | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
sh Busybox specific options: None
|
|
|
|
|
|
|
|
sleep POSIX options: None
|
|
|
|
sleep Busybox specific options: None
|
|
|
|
|
|
|
|
sort POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-C | no | no |
|
|
|
|
-b | yes | yes |
|
|
|
|
-c | yes | yes |
|
|
|
|
-d | yes | yes |
|
|
|
|
-f | yes | yes |
|
2009-06-12 19:02:51 +05:30
|
|
|
-i | yes | yes | But is not like GNU sort, which isn't! (try to sort 'a\nA\nB\nb' with and without -f)
|
2009-07-19 04:39:42 +05:30
|
|
|
-k keydef | yes | |
|
|
|
|
-m | no | no |
|
|
|
|
-n | yes | yes |
|
|
|
|
-o output | yes | yes |
|
|
|
|
-r | yes | yes |
|
|
|
|
-t char | yes | |
|
|
|
|
-u | yes | yes |
|
|
|
|
sort Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-mST, -g, -M, -s, -z
|
|
|
|
|
|
|
|
split POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a suffix_length | yes | yes |
|
|
|
|
-b n | yes | yes |
|
|
|
|
-b nk | yes | yes |
|
|
|
|
-b nm | yes | yes |
|
|
|
|
-l line_count | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
split Busybox specific options: None
|
|
|
|
|
|
|
|
strings POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | yes | yes |
|
|
|
|
-n number | yes | yes |
|
|
|
|
-t format | no | no |
|
|
|
|
strings Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-o, -f
|
|
|
|
|
|
|
|
stty POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | yes | yes |
|
|
|
|
-g | yes | yes |
|
|
|
|
stty Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-F DEVICE
|
|
|
|
|
|
|
|
tail POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c number | yes | yes |
|
|
|
|
-f | yes | yes |
|
|
|
|
-n number | yes | yes |
|
|
|
|
tail Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-v, -q, -s SEC
|
|
|
|
|
|
|
|
tee POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | yes | yes |
|
|
|
|
-i | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
tee Busybox specific options: None
|
|
|
|
|
|
|
|
test POSIX options: None
|
|
|
|
test Busybox specific options: None
|
|
|
|
|
|
|
|
time POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-p | no | no |
|
|
|
|
time Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-v
|
|
|
|
|
|
|
|
touch POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | no | no |
|
|
|
|
-c | yes | yes |
|
|
|
|
-d date_time | no | no |
|
|
|
|
-m | no | no |
|
|
|
|
-r ref_file | no | no |
|
|
|
|
-t time | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
touch Busybox specific options: None
|
|
|
|
|
|
|
|
tr POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-C | no | no |
|
|
|
|
-c | yes | yes |
|
|
|
|
-d | yes | yes |
|
|
|
|
-s | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
tr Busybox specific options: None
|
|
|
|
|
|
|
|
true POSIX options: None
|
|
|
|
true Busybox specific options: None
|
|
|
|
|
|
|
|
tty POSIX options: None
|
2009-07-19 04:39:42 +05:30
|
|
|
tty Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-s
|
|
|
|
|
|
|
|
uname POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-a | yes | yes |
|
|
|
|
-m | yes | yes |
|
|
|
|
-n | yes | yes |
|
|
|
|
-r | yes | yes |
|
|
|
|
-s | yes | yes |
|
|
|
|
-v | yes | yes |
|
|
|
|
uname Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-p
|
|
|
|
|
|
|
|
uncompress POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | yes | yes |
|
|
|
|
-f | yes | yes |
|
|
|
|
-v | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
uncompress Busybox specific options: None
|
|
|
|
|
|
|
|
unexpand POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-06-12 19:02:51 +05:30
|
|
|
-a | yes | no | POSIX requires converting two or more spaces to tabs, busybox converts one or more spaces
|
2009-07-19 04:39:42 +05:30
|
|
|
-t tablist | yes | yes |
|
|
|
|
unexpand Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
--tabs=N, -f, --first-only, --all
|
|
|
|
|
|
|
|
uniq POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | yes | yes |
|
|
|
|
-d | yes | yes |
|
|
|
|
-f fields | yes | yes |
|
|
|
|
-s chars | yes | yes |
|
|
|
|
-u | yes | yes |
|
|
|
|
uniq Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-w N
|
|
|
|
|
|
|
|
uudecode POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-o outfile | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
uudecode Busybox specific options: None
|
|
|
|
|
|
|
|
uuencode POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-m | yes | yes |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
uuencode Busybox specific options: None
|
|
|
|
|
|
|
|
vi POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-R | yes | |
|
|
|
|
-c command | yes | |
|
|
|
|
-r | no | no |
|
|
|
|
-t tagstring | no | no |
|
|
|
|
-w size | no | no |
|
|
|
|
vi Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-H
|
|
|
|
|
|
|
|
wc POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-c | yes | yes |
|
|
|
|
-l | yes | yes |
|
|
|
|
-m | no | no |
|
|
|
|
-w | yes | yes |
|
|
|
|
wc Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-L
|
|
|
|
|
|
|
|
who POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-H | no | no |
|
|
|
|
-T | no | no |
|
2009-06-12 19:02:51 +05:30
|
|
|
-a | yes | no | just shows all
|
2009-07-19 04:39:42 +05:30
|
|
|
-b | no | no |
|
|
|
|
-d | no | no |
|
|
|
|
-l | no | no |
|
|
|
|
-m | no | no |
|
|
|
|
-p | no | no |
|
|
|
|
-q | no | no |
|
|
|
|
-r | no | no |
|
|
|
|
-s | no | no |
|
|
|
|
-t | no | no |
|
|
|
|
-u | no | no |
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
who Busybox specific options: None
|
|
|
|
|
|
|
|
xargs POSIX options
|
|
|
|
option | exists | compliant | remarks
|
2009-07-19 04:39:42 +05:30
|
|
|
-E eofstr | no | no |
|
|
|
|
-I replstr | no | no |
|
|
|
|
-L number | no | no |
|
|
|
|
-n number | yes | yes |
|
|
|
|
-p | yes | yes |
|
|
|
|
-s size | yes | yes |
|
|
|
|
-t | yes | yes |
|
|
|
|
-x | yes | yes |
|
|
|
|
xargs Busybox specific options:
|
POSIX conformance documentation for busybox
Attached a start for POSIX conformance documentation for busybox (see
TODO file and discussion last week).
A table of all options as defined by POSIX and as implemented by
busybox (see for a FreeBSD example
http://people.freebsd.org/~schweikh/posix-utilities.html).
Only the tools that are stand-alone applets are documented (not ash
built-ins as 'read'), as there are multiple shells.
When there are two versions (echo) the stand-alone version was
checked. I think this may be the wrong way to go, as most users will
probably use the built-in version - but which shell?
The table was auto-generated by running, for each POSIX utility,
latest git allyesconfig* "busybox <tool> --help" and parsing the
output, and comparing that to tool options extracted from its man page
at http://www.opengroup.org/onlinepubs/9699919799/.
This means that it the usage string is not correct, the table is also
wrong. I noticed that for 'kill', for example, the usage string does
not mention the -s, -q, -o options.
For each option is set whether it exists in busybox and if it is, is
it compliant to the standard. Of course, checking compliance can only
be done manually - a process which will probably take some time (see
'cat' for example).
I didn't post the auto-generation script (python, ugly) because the
table will now change manually; I can post it if there is anyone
interested.
As for the tools not implemented by busybox at all, I think most of
them are indeed fairly esotetic. Some I was suprised to see missing
are link, file, newgrp, unlink.
* Well, almost allyesconfig - but nothing very POSIX-y was disabled.
Signed-off-by: David Krakov <krakov@gmail.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2009-05-27 05:12:34 +05:30
|
|
|
-e[STR], -0, -r
|
|
|
|
|
|
|
|
zcat POSIX options: None
|
|
|
|
zcat Busybox specific options: None
|