midfavila/sbase
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity
f9a1e11661
sbase/README

120 lines
5.6 KiB
Plaintext
Raw Normal View History

Add initial README
2014-02-12 09:34:09 -05:00
sbase - suckless unix tools
===========================
sbase is a collection of unix tools that are inherently portable
across UNIX and UNIX-like systems.
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
The following tools are implemented (* == finished):
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 18:01:56 -05:00
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
UTILITY POSIX 2008 COMPLIANT MISSING OPTIONS
------- -------------------- ---------------
* basename yes none
Mark cal(1) as finished in README
2015-01-16 16:19:52 -05:00
* cal yes none
Add mandoc-manpage for cat(1) and mark it as finished in the README.
2015-01-16 04:40:59 -05:00
* cat yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
chgrp no -h, -H, -L, -P
Add mandoc-manpage for chmod(1) and mark it as finished in README. One small rationale on the way the manpage is set up: Looking at the coreutils manpage, it does not invite to be a quick reference guide, whereas I wrote this manpage to be short and concise in regard to the information the advanced user needs. No one needs to explain what an octal number is. That's not part of the scope of this manpage. Also, nobody wants to read a block of text just to find out how to build an octal mode string.
2015-01-17 16:33:19 -05:00
* chmod yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
chown no -h, -H, -L, -P
chroot non-posix none
Add mandoc-manpage for cksum(1) and clean up code and mark it as done in README.
2015-01-17 17:38:38 -05:00
* cksum yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
* cmp yes none
* cols non-posix none
Add mandoc-manpage for comm(1) and clean up code and mark it as finished in README.
2015-01-17 18:07:29 -05:00
* comm yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
cp no -H, -i, -L
* cron non-posix none
cut yes none
date yes none
dirname yes none
du no -H, -L, -x
echo yes none
env yes none
expand yes none
expr yes none
Add manpages for false(1) and true(1) and mark them as finished in the README.
2015-01-15 19:05:20 -05:00
* false yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
fold yes none
* grep yes none
head yes none
hostname non-posix none
* kill yes none
link yes none
ln yes none
* logger yes none
logname yes none
ls no -C, -H, -L, -R, -c, -q, -u
md5sum non-posix none
mkdir yes none
mkfifo yes none
mktemp non-posix none
mv no -i
nice yes none
nl no -d, -f, -h, -l, -n, -p, -v, -w
nohup yes none
paste yes none
printenv non-posix none
printf stolen stolen
* pwd yes none
readlink non-posix none
renice yes none
rm no -i
rmdir no -p
sleep yes none
setsid non-posix none
sort no -m, -o, -d, -f, -i
split yes none
sponge non-posix none
strings no -a, -n, -t
sync non-posix none
tail no -c, -f
tar non-posix none
tee no -i
test yes none
touch no -a, -m, -r
Add mandoc-manpage for tr(1) and mark it as finished in the README.
2015-01-15 18:53:50 -05:00
* tr yes none
Add manpages for false(1) and true(1) and mark them as finished in the README.
2015-01-15 19:05:20 -05:00
* true yes none
Amend list of tools with asterisks to mark tools considered finished. Finished doesn't mean work has stopped on these, but that these programs are in a satisfying state according to the current suckless coding practices, this includes having a 1) mandoc manpage 2) clean code In most cases, 1) was the failing criterion. So in the interest of finishing more tools and if you want to, well-written mandoc man- pages are very much appreciated.
2015-01-15 16:17:55 -05:00
tty yes none
uudecode no -o
uuencode no -m
uname yes none
unexpand yes none
uniq no -f, -s
unlink yes none
seq non-posix none
sha1sum non-posix none
sha256sum non-posix none
sha512sum non-posix none
wc yes none
xargs no -I, -L, -p, -s, -t, -x
yes yes 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 18:01:56 -05:00
Minor fix for README
2014-02-12 13:39:13 -05:00
The complement of sbase is ubase[1] which is Linux-specific and
Add initial README
2014-02-12 09:34:09 -05: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
--------
Update note on building sbase on OpenBSD
2014-11-21 05:36:42 -05:00
You need GNU make to build sbase on OpenBSD.
Require GNU make to build sbase We seem to have problems building individual tools across various make implementations. If anyone can step up and fix this we will remove the dependency on GNU make.
2014-11-17 08:50:19 -05:00
Add initial README
2014-02-12 09:34:09 -05:00
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
individual tools to sbase-box.
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