ruthenic
/
drakecoreutils
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
A horrifyingly bad set of coreutils.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
124 Commits
1 Branch
0 Tags
198 KiB
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '15dd71baec'
${ noResults }
Go to file
Drake 15dd71baec
Fix up readme 		2 years ago
.github/workflows workflows: add github graphql analysis. 3 years ago
doc TODO.md: remove old file. 3 years ago
lib `dbox`/Makefile/funcs.h: fix remaining compiler warnings. 2 years ago
src `dbox`/Makefile/funcs.h: fix remaining compiler warnings. 2 years ago
.gitignore gitignore: remove *all* .vscode files. 3 years ago
LICENSE move copyright attribution back to me 3 years ago
Makefile Makefile: avoid race condition if building in parallel. 2 years ago
README.md Fix up readme 2 years ago

README.md

drakecoreutils

the best coreutils since minix

building

  1. reconsider your life decisions
  2. use glibc and x86 otherwise my code is shredded into pieces
  3. run make to produce the dbox executable (CC,CC_FLAGS,LD_FLAGS are the env variables i use for compiler settings)
  4. similar to busybox, you can either manually invoke dbox with the name of the executable (i.e. bin/dbox ls -cCa), or link the dbox executable to whatever you want to use (i.e. ln bin/dbox bin/ls; bin/ls -cCa)
  5. congrats, you have built the best set of coreutils since minix

todo

  • fix memory issues in everything (but ls specifically)
  • proper formatting in ls
  • allow a way to manually use multi-binary mode? (currently you can (in theory) just rename the dbox executable to whatever program you want, albiet with the slight overhead of dbox)
  • better name for the executable than dbox