It's #octOpenBSD month so I've written about why #OpenBSD offers a more reliable, stable, and productive view on computing.
It's #octOpenBSD month so I've written about why #OpenBSD offers a more reliable, stable, and productive view on computing.
#OpenBSD 7.6 is officially released!
New webzine issue releases as well
Let me unveil The OctOpenBSD special #OpenBSD webzine issue
https://webzine.puffy.cafe/issue-16-special-octopenbsd-2023.html
@prahou tailored this very special issue to celebrate our favorite operating system. 👏
A Spanish version by @quobit is already available. Some other translation should be expected very soon.
last of the spooky special [ice cream]
#unix_surrealism #technomage #fediart #mastoart #linux #bsd #9front #fossangel #octopenbsd
lightning review: CONSUL 231.2 #permacomputing
This is a well built machine, but the limited keyboard makes it difficult to write any good software. Writing very basic shell scripts is viable.
All in all, the machine is fine for writing samizdats, but #lisp programmers, beware: there are no parentheses.
PROS:
- no win/super key, love to see it
- nice default font
- (e-)ink output
CONS:
- max no. of columns is 72
- limited keyboard
- no parentheses
I love spkr(4) so much, but I don't know how music works. Still, I can't stop trying.
It's a weird obsession.
Here is my addition to OctOpenBSD
7.4 Memory Leak Testing, I see this as a great addition to OpenBSD.
Compile with -g (I also use -O0)
Execute:
export MALLOC_OPTIONS="D"
$ ktrace -tu ./a.out [args]
$ kdump -u malloc
A report will be printed with the command to use to see where the leak is (addr2line).
To me this is much easier than using valgrind :)