101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

623
active users

@b0rk @dlatchx I've been saying for years that there ought to be an environment variable to disable stdio buffering. Then instead of a weird trick you would
NO_STDOUT_BUFFERING=1 cmd | grep whatever

(or alias cmd='NO_STDOUT_BUFFERING=1 cmd' or something like that.)

Apparently NetBSD even has this feature. Not Linux though.

blog.plover.com//Unix/stdio-bu
blog.plover.com/Unix/stdio-buf

The Universe of Disco : Proposal for turning off standard I/O bufferingProposal for turning off standard I/O bufferingFrom the highly eclectic blog of Mark Dominus

@nabijaczleweli @b0rk @dlatchx It has been invented several times, in several ways, as I discussed in the second article.

The implementation of stdbuf is somewhat ridiculous though. It forces the process to dynamically load a completely different standard I/O library. Whereas if my environment variable solution had been baked in, no ridiculousness would be required.

наб

@mjd @b0rk @dlatchx this is false as well, and in fact no extant stdbuf(1) implementation does this

@mjd @b0rk @dlatchx every stdbuf-like implementation, ever (i have just validated this), consists of a libstdbuf (except for NetBSD which has this built into libc), which has a constructor that parses the environment variables and calls setvbuf(). any other implementation would be utter lunacy

all /bin/stdbuf does is LD_PRELOAD=libstdbuf.so; _STDBUF_I=argv[optind]; exec(argv + 1)

(here's a sample implementation (although a bad one for a demo, because this is really size-optimised; 0BSD): git.sr.ht/~nabijaczleweli/vore; and of /bin/stdbuf: git.sr.ht/~nabijaczleweli/vore. all of them are, functionally, identical)

@mjd well the markdown linkification broke but otherwise this is reasonable