logo

utils-std

Collection of commonly available Unix tools
commit: 402c4268b5ff431a8faa57a219751682c004c8ae
parent 54b0cd7abcba5c5a4502a7c44f84cd0e32dd94e4
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Tue, 26 Mar 2024 17:35:46 +0100

README: Add note about utmp/wtmp

Diffstat:

MREADME.md1+
1 file changed, 1 insertion(+), 0 deletions(-)

diff --git a/README.md b/README.md @@ -9,6 +9,7 @@ Tested on Linux(musl), FreeBSD, NetBSD, OpenBSD: <https://builds.sr.ht/~lanodan/ ## Design differences - All programs prefix their messages with their name. This way you don't end up with context-less messages in scripts. - When the output is structured data, a terminal gets human-oriented output, others like piped programs get machine-oriented output (line separation, CSV, JSON, …). Prior art: most `ls(1)` implementations, i3/sway, FreeBSD utils via `libxo`, … +- As the `utmp` and `wtmp` files are considered broken by design, utilities dependant on them like `who` and `lastlog` won't be implemented. Proper authentication logs shouldn't be writable into by multiple programs, some of them third-party (like SSH and Display Managers typically are). ## Goals - (long-run) Effectively serve as one of the blocks to replace BusyBox, GNU coreutils, …