fbt/sbase
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
90751ab4ba
sbase/README

123 lines
5.7 KiB
Plaintext
Raw Normal View History

Add initial README
2014-02-12 14:34:09 +00:00
sbase - suckless unix tools
===========================
sbase is a collection of unix tools that are inherently portable
across UNIX and UNIX-like systems.
Add column to mark UTF-8 support One major milestone is to have the sbase-tools supporting UTF-8. Tools like cut(1) with the -n flag don't make sense otherwise. And while the gnu coreutils cut(1) blatantly ignores such an important aspect, we will not tolerate this madness and mark it as a TODO in the main README. Since most tools inherently support UTF-8 anyway, this just concerns tools which mangle with text or search in it in special ways.
2015-01-18 18:36:13 +00:00
The following tools are implemented ('*' == finished, '#' == UTF-8 support,
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
'=' == implicit UTF-8 support, '|' == audited):
Add an easier to edit "table" of tools in README We need to go through the tools and update this table to reflect current state.
2014-11-20 23:01:56 +00:00
Audit basename(1) 1) be stricter which number of arguments is accepted (1 or 2) 2) basename already returns a pointer to "." is argv[0] is "" 3) No need to check for *p != '/', because basename() only returns a string beginning with '/' which has length 1, so if strlen(p) == 1, the only way for suffix to be "evaluated" is for off to be > 0, being equal to suffix being "", but "" != "/". 4) don't calculate strlen twice for each string. Store it in a ssize_t and check if it's > 0.
2015-02-28 13:48:44 +00:00
UTILITY POSIX 2008 COMPLIANT MISSING OPTIONS
------- -------------------- ---------------
=*| basename yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* cal yes none
Audit cat(1) 1) Fix usage ... spacing 2) use *argv instead of argv[0] in the idiomatic for-loop 3) Stop the naïve usage of "/dev/fd/0" and use plain stdin instead (This also makes error-messages more consistent). 4) Add newline before return 5) Remove comma in manpage
2015-03-01 23:36:51 +00:00
=*| cat yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* chgrp yes none
Audit chmod(1) 1) Update manpage, refactor the HLP-section and other wordings. 2) BUGFIX: If chmod() fails, don't recurse. 3) Rewrite the arg-loop, fixing several issues: BUGFIX: Handle multi-flags (e.g. -RH) BUGFIX: Properly handle the termination flag --, error on e.g. --x BUGFIX: Error out on an empty flag -. 4) Refactor logic after the arg-loop, which is now simpler thanks to argv-incremention.
2015-03-05 18:08:28 +00:00
=*| chmod yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* chown yes none
Audit chroot(1) 1) Fix usage() 2) Rename *p to *cmd 3) _exit trick with 126 + (savederrno == ENOENT) 4) return-style-fix
2015-03-02 16:41:58 +00:00
=*| chroot non-posix none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* cksum yes none
=* cmp yes none
#* cols non-posix none
Add col command col is used to display troff documents in ttys, removing the reverse line feeds generated by .2C in ms. This implementation keeps the limit of 256 lines of 800 characteres of the original implementation.
2015-03-03 09:52:34 +00:00
col yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* comm yes none
Audit cp(1) 1) Refactor the manpage, which has been a bloody mess, documenting fantasy-flags (-d for example) and add a STANDARDS section 2) fix usage() 3) sort ARG-block 4) Check return-value of stat() separately, so a lack of permissions doesn't tell the user "the directory doesn't exist", which could be a bit confusing. 5) Add empty line before return.
2015-03-02 18:15:19 +00:00
=*| cp yes none (-i)
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* cron non-posix none
#* cut yes none
Audit date(1) 1) Update usage as already done in the manpage 2) group and sort local variable declarations 3) Be pedantic about the number of options. Don't just ignore it if argc > 1.
2015-03-02 14:12:19 +00:00
=*| date yes none
Audit dirname(1) Be stricter about the number of arguments passed to it.
2015-02-28 18:50:12 +00:00
=*| dirname yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* du yes none
Audit echo(1) Just a small change in the manpage.
2015-02-28 19:16:10 +00:00
=*| echo yes none
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself!
2015-03-02 13:50:43 +00:00
=*| env yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
#* expand yes none
#* expr yes none
Mark false(1) and true(1) as audited Nothing to be done there.
2015-02-28 14:12:19 +00:00
=*| false yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
= find yes none
#* fold yes none
=* grep yes none
Audit head(1) 1) Use (s)size_t in head(). 2) BUGFIX: only check buf[len - 1] when len > 0, else there would be an overflow when getline returns 0 (which can happen) and a very potential segmentation fault. 3) fix error-messages. 4) update usage(). 5) argv-argc-style. 6) clear up the main loop with if (newline). 7) add newline before return.
2015-03-04 23:58:12 +00:00
=*| head yes none
Audit hostname(1) 1) Be strict about argc 2) Fix a small error in the manpage
2015-02-28 20:22:55 +00:00
=*| hostname non-posix none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* kill yes none
Audit link(1)
2015-02-28 18:42:26 +00:00
=*| link yes none
Audit ln(1) 1) Clarify behaviour when the f-flag is given and a target is in its own way. 2) Fix usage()-style. 3) Group local variable declarations. 4) reorder args 5) argc style, other boolean style changes 6) improve error messages 7) set argv[argc - 1] to NULL to allow argv-centric loop later 8) BUGFIX: POSIX specifies that when with the f-flag there's a situation where a file stands in its own way for linking it should be ignored. 9) Add weprintf() where possible, so we don't pussy out when there's a small issue. This is sbase ffs!
2015-03-05 20:14:43 +00:00
=*| ln yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* logger yes none
=* logname yes none
= ls no (-C), -S, -f, -m, -s, -x
Update *sum(1)-manpages and mark them as finished and audited Now that -c behaves correctly, the tools are pretty much done. Only the manpages were not clear enough what happens when you specify the c-flag. This is fixed now.
2015-03-01 21:59:20 +00:00
=*| md5sum non-posix none
Audit mkdir(1) 1) No need for strchr() in mkdirp or a while-loop. Rewrite it in a sane and readable way. 2) fix usage according to the manpage. 3) order includes, don't align local variables. 4) argc-style-fix. 5) BUGFIX: Don't try to chmod() *argv when mkdir() / mkdirp() failed. 6) Add newline before return in two places.
2015-03-05 17:03:08 +00:00
=*| mkdir yes none
Audit mkfifo(1) 1) Fix usage() 2) Group local variables 3) Idiomatic argv-loop 4) BUGFIX: When the m-flag is specified, POSIX clearly says: "Set the file permission bits of the newly-created FIFO to the specified mode value." This means, that if mkfifo() fails for some reason, it should not try to chmod() the given path (which has been fixed with the "else if") A simple testcase is: $ touch testfile; mkfifo -m 000 testfile; GNU mkfifo(1): ls -l testfile -rw-r--r-- 1 testfile sbase mkfifo(1): ls -l testfile ---------- 1 testfile 5) Add blank line before return
2015-03-02 16:25:29 +00:00
=*| mkfifo yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* mktemp non-posix none
Audit mv(1) 1) Make argument-naming consistent with other tools (cp(1), ...) 2) style fixes 3) usage() fix 4) BUGFIX: Probably from the old non-arg.h days, the directory- check was only done when argc > 3, but with arg.h, this ignores the case when 3 arguments were given. This is actually a pretty serious issue and I'm glad it's fixed. 5) Moreover, be more verbose when stat() fails and make it clearer what the hell is going on at this checkpoint.
2015-03-04 22:22:43 +00:00
=*| mv yes none (-i)
Audit nice(1) 1) val is sufficient as "int" (read the standard) 2) BUGFIX: If getpriority fails, it returns -1 and sets errno. Previously, it would correctly catch the errno but not take care of the fact that by then val has been decremented by 1. Only change val if the getpriority-call has been successful. 3) Add LIMIT()-macro from st to increase readability. 4) setpriority returns < 0 on failure 5) Remove bikeshedding-comment. Read the standard if you wonder. 6) return-value trick from env(1)
2015-03-02 15:53:13 +00:00
=*| nice yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
= nl no -d, -f, -h, -l, -p
Audit nohup(1) 1) no need to include sys/stat.h 2) remove the enum which just added a layer too thick on this simple program 3) argc-style, other style 4) weprintf instead of enprintf, then save the error-message of execvp before and return the proper status. 5) write consistent "not reached" comment.
2015-03-04 21:39:12 +00:00
=*| nohup yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
#* paste yes none
Audit printenv(1) 1) argc style 2) safeguard argv-loop as already seen in echo(1) with argc-decrement.
2015-02-28 20:47:17 +00:00
=*| printenv non-posix none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
#* printf yes none
Audit pwd(1) Nothing special 1) Update manpage to current style. 2) Reorder functions 3) Logical trickery in getpwd()
2015-03-03 16:24:14 +00:00
=*| pwd yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
= readlink non-posix none
=* renice yes none
Audit rm(1) 1) One small argc-style-matter 2) manpage cleanup 3) NOTE: The utility-functions will be evaluated separately.
2015-02-28 20:30:20 +00:00
=*| rm yes none (-i)
Audit rmdir(1) 1) style fix (don't arrange local variables) 2) BUGFIX: Previously, if ret was turned 1 for some folder, it would disable the p-flag for every following folders, which is not desired. Instead, the "else if" makes sure that the p-flag-section is only entered when the initial rmdir succeeds. 3) BUGFIX: Previously, the program would cancel with eprintf if it failed to remove one folder in the parent-pathname. This is not desired, as we have other folders pending. Instead, print a warning for the current failing parent-folder, set ret to 1 and break off the loop at this point. This allows to finish the other pending folders without issues.
2015-03-02 14:39:39 +00:00
=*| rmdir yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
# sed
seq non-posix none
Audit setsid(1) Nothing special, just a small style-fix.
2015-03-01 23:20:35 +00:00
=*| setsid non-posix none
Update *sum(1)-manpages and mark them as finished and audited Now that -c behaves correctly, the tools are pretty much done. Only the manpages were not clear enough what happens when you specify the c-flag. This is fixed now.
2015-03-01 21:59:20 +00:00
=*| sha1sum non-posix none
=*| sha256sum non-posix none
=*| sha512sum non-posix none
Audit sleep(1) 1) Be strict about argc 2) Use "unsigned" instead of "unsigned int"
2015-02-28 19:10:25 +00:00
=*| sleep yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
sort no -m, -o, -d, -f, -i
=* split yes none
Audit sponge(1) Just a little usage()-fix. Mark it as audited in README.
2015-03-01 22:42:16 +00:00
=*| sponge non-posix none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
#* strings yes none
=* sync non-posix none
=* tail yes none
=* tar non-posix none
Audit tee(1) 1) "duplicate" implies that you can only specify two outputs, "multiply" is a better word describing the functionality. 2) fix other wording in the manpage 3) fix usage() 4) reorder local variables 5) fix sizeof() style 6) we need argv later, don't increment argv and rather iterate over argc. 7) Improve error messages, print the filename which the write failed to instead of printing the buffer itself (how much sense does that make, printing 1024 Bytes of garbage?). Also, give the name of the function which failed.
2015-03-04 22:05:11 +00:00
=*| tee yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* test yes none
Mark time(1) as finished and audited in README
2015-03-04 23:29:03 +00:00
=*| time yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* touch yes none
#* tr yes none
Mark false(1) and true(1) as audited Nothing to be done there.
2015-02-28 14:12:19 +00:00
=*| true yes none
Audit tty(1) 1) Be strict about number of arguments passed 2) Use a simpler logic while returning
2015-02-28 18:59:34 +00:00
=*| tty yes none
Mark uname(1) as audited in README No changes needed.
2015-03-04 23:33:28 +00:00
=*| uname yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
#* unexpand yes none
=* uniq yes none
Audit unlink(1) One small thing, use argv0 in usage. Also, add a blank line in link.c which I forgot earlier.
2015-02-28 19:05:22 +00:00
=*| unlink yes none
Add audit-section to README Okay, so why another section? The finished-section applies to general feature-completeness and manual status. It somehow is not an indicator for general code- clarity, so the audited-column reflects a thorough audit of the underlying code and optimization. Take a look at the upcoming basename(1)-patch for an example on how this goes.
2015-02-28 13:42:26 +00:00
=* uudecode yes none
=* uuencode yes none
#* wc yes none
= xargs no -I, -L, -p, -s, -t, -x
Mark yes(1) as audited in README
2015-02-28 20:12:27 +00:00
=*| yes non-posix none
Add an easier to edit "table" of tools in README We need to go through the tools and update this table to reflect current state.
2014-11-20 23:01:56 +00:00
Minor fix for README
2014-02-12 18:39:13 +00:00
The complement of sbase is ubase[1] which is Linux-specific and
Add initial README
2014-02-12 14:34:09 +00:00
provides all the non-portable tools. Together they are intended to
form a base system similar to busybox but much smaller and suckless.
Building
--------
To build sbase, simply type make. You may have to fiddle with
config.mk depending on your system.
You can also build sbase-box, which generates a single binary
containing all the required tools. You can then symlink the
README: document sbase-box-install rule
2015-02-28 14:40:16 +00:00
individual tools to sbase-box or run: make sbase-box-install
Add initial README
2014-02-12 14:34:09 +00:00
Ideally you will want to statically link sbase. If you are on Linux
we recommend using musl-libc[2].
Portability
-----------
sbase has been compiled on a variety of different operating systems,
including Linux, *BSD, OSX, Haiku, Solaris, SCO OpenServer and others.
Various combinations of operating systems and architectures have also
been built.
You can build sbase with gcc, clang, tcc, nwcc and pcc.
[1] http://git.suckless.org/ubase/
[2] http://www.musl-libc.org/
Reference in New Issue Copy Permalink