duckinator / boreutils Goto Github PK

View Code? Open in Web Editor NEW

8.0 3.0 2.0 178 KB

An implementation of common *nix utilities, especially those in POSIX.1-2017.

License: MIT License

Makefile 0.63% C 59.00% Python 39.27% Shell 1.10%

posix posix-compliant cli

boreutils's Introduction

boreutils's People

Contributors

Stargazers

Watchers

Forkers

thefresia

boreutils's Issues

Reduce number of magic arguments for `yes`

It's generally expected to accept no special flags, not even --help. Everything should just be treated as a normal argument.

Most implementations only print the first argument, so boreutils should do that too. (GNU is the only exception I'm aware of, and I don't give a fuck what they do for the most part.)

`date` can't set date with 8-digit argument

~/dev/os/awooos/boreutils master+ sudo ./bin/date 05220246
~/dev/os/awooos/boreutils master+ sudo ./bin/date 052202462020
./bin/date: Success
~/dev/os/awooos/boreutils master+

[mkdir] Implement `-m`

I've implemented mkdir [-p] DIR, but the -m MODE flag still hasn't been implemented.

mkdir [-p] -m MODE DIR is equivalent to mkdir [-p] DIR && chmod MODE DIR.

I'm unsure if -p + -m results in all created directories having that mode. That should be investigated.

https://pubs.opengroup.org/onlinepubs/9699919799/utilities/mkdir.html

Prioritized list of next 20 commands to implement

Investigate generating man pages from comments?

A decent approach — at least to start — may be to treat the topmost comment in src/foo.c as documentation for foo, then converting that to a .txt file and have a craptastic man implementation which is just a glorified cat that fetches files from a fixed path.

[kill] Implement `kill -l EXIT_STATUS`

I've implemented kill -l but not kill -l EXIT_STATUS

Frankly, I don't understand what https://pubs.opengroup.org/onlinepubs/9699919799/utilities/kill.html is trying to tell me:

-l
(The letter ell.) Write all values of signal_name supported by the implementation, if no operand is given.
If an exit_status operand is given and it is a value of the '?' shell special parameter (see Special Parameters and wait) corresponding to a process that was terminated by a signal, the signal_name corresponding to the signal that terminated the process shall be written. If an exit_status operand is given and it is the unsigned decimal integer value of a signal number, the signal_name (the symbolic constant name without the SIG prefix defined in the Base Definitions volume of POSIX.1-2017) corresponding to that signal shall be written.
Otherwise, the results are unspecified.

(Emphasis mine.)

[man] More robust `man` implementation

The current man implementation is pretty crude, and I'd love to replace it with something better.

Any improved version would ideally also support man -k name..., but this can possibly be done with the current one as well.

Setting date results in off-by-one error of +1 hour?

This might be an daylight savings thing? (setting EST, reading EDT)

[mkdir] Make `mkdir -p x` where ./x exists not raise error

mkdir -p is supposed to ignore all existing directories. As implemented, it'll throw an error if you do:

./bin/mkdir x && ./bin/mkdir -p x

[dir, mv] Add tests

At the moment, the following utilities have no tests:

dir
id
mv
which

This should be fixed.

[tail] Implement `tail -f`

I never actually implemented tail -f.

Support `$BLOCKSIZE` environment variable

On the pages for at least df, the standard suggests the use of a BLOCKSIZE environment variable:

The use of 512-byte units is historical practice and maintains compatibility with ls and other utilities in this volume of POSIX.1-2017. This does not mandate that the file system itself be based on 512-byte blocks. The -k option was added as a compromise measure. It was agreed by the standard developers that 512 bytes was the best default unit because of its complete historical consistency on System V (versus the mixed 512/1024-byte usage on BSD systems), and that a -k option to switch to 1024-byte units was a good compromise. Users who prefer the more logical 1024-byte quantity can easily alias df to df -k without breaking many historical scripts relying on the 512-byte units.

It was suggested that df and the various related utilities be modified to access a BLOCKSIZE environment variable to achieve consistency and user acceptance. Since this is not historical practice on any system, it is left as a possible area for system extensions and will be re-evaluated in a future version if it is widely implemented.

I think it's reasonable to only support values of 512 and 1024. To the best of my knowledge, the affected utilities also all have a -k option. Given that information and the way I've implemented Boreutils utililties so far, this seems like a reasonable approach:

// after normal argument parsing is done (to avoid issues if `-k` is passed but $BLOCKSIZE != 1024).
if (!dash_k) { dash_k = strcmp(getenv("BLOCKSIZE"), "1024") == 0; }

The utilities that should have support for this are any which provide information about files and/or has a -k option that switches to 1024 byte blocks. This list should be updated if more are found:

df
ls

There's also Infer:Pulse which looks really useful: https://fbinfer.com/docs/checker-pulse

Probably makes sense to add it to CI for boreutils.

[cal] Implement Julian calendar

At the moment only the hard-coded September 1752 (the month the Julian->Gregorian calendar transition happens in POSIX-compliant cal implementations) and later is implemented.

All dates before that are represented with the Julian calendar, but this needs to be implemented.

There is a j_build_month(char *buf, int y, int m) function that prints a TODO message, currently.

[chmod] Notes for implementing chmod

Was closing browser tabs and found some notes about implementing chmod:

duckinator / boreutils Goto Github PK

boreutils's Introduction

boreutils

Excluded utilities

Utilities, and current status

boreutils's People

Contributors

Stargazers

Watchers

Forkers

boreutils's Issues

Recommend Projects

Recommend Topics

Recommend Org