135 Followers
109 Following
622 Posts
Mostly harmless swedish bsd hacker. Also speaks 6502, m68k and some mips64. Hoster of slackathons and some *.eu.openbsd.org infra.
Sometimes known as IcePic.
OpenBSDjj
C64/AmigaIcePic
Seems like the holes in my garden is caused by badgers.
Which is why I am going to email @bagder and complain to him, for some random reason.
The unseen hero of OpenBSD :: Forensic wheels

The unseen hero of OpenBSD: otto’s malloc What this is about This is me learning about OpenBSD’s malloc. I try not to do a surface-level overview. I want to understand the internals better, the data structures, the design decisions, and why those decisions make heap exploitation so much harder. What malloc actually does Every C program that needs memory at runtime calls malloc. malloc is a library function. It’s not a syscall – it’s a layer between your code and the kernel.

Forensic wheels
oh fuck I need that-
@b0rk In the times when many gnu tools moved to info pages, there were many inconsistencies and missing details where "--help" output, man pages and info docs were out of sync, and often distributions would in turn miss out on things like sed(1) not going into regexps per se, but pointing to another package like perlre to explain the format of basic and extended regexps (and difference between posix regexps and the one gnu sed supports). So while the latter is a fault(?) of the distribution packaging if the SEE ALSO links are not there, it still leaves you as the user without the needed docs in man format. While on BSDs the base tools can and do refer to other installed base tools but unless you deliberately strip out things, the links would work out, and you would be able to read about re_format(7) from the base tools that do support regexps.
But just to take one example from the "ip" command that replaced "ifconfig", on Ubuntu 24.04, the synopsis lists a certain amount of commands and options. Still, the options below contain -echo which is not in the synopsis, even though the synopsis does contain "long" options already. So at some point, someone added -echo to have the kernel tell you what got applied, it got its line in the lower part of the manpage, but synopsis doesn't mention it. Also, "ip --help" doesn't list it either.

@b0rk
```In general it seems like there’s a technical and cultural divide in how documentation works on BSD and on Linux that I still haven’t really understood, but I have been feeling curious about what’s going on in the BSD world.```

From the BSD side, it feels almost too simple to mention in that when you add a new flag to program X, you must also correct/add to the manpage. Of course this would not explain is there are visible differences in examples, but at least it would explain why BSD manpages are regarded highly in general, even if they are sometimes arcane or imperfect, almost all details are there somewhere. All flags are in, not just some of them.

How about an #OpenBSD story on oooooooooold hardware this morning?

http://miod.online.fr/software/openbsd/stories/arcofi.html

Audio on hp300

Migration to #openbsd for my personal website completed!

That was quite a painless process. At last an OS that is well designed and well documented. It just makes sense. And it’s really just what I need for hosting a small website.

And thanks to @OpenBSDAms it was easy to get a VPS running this beautiful OS 😇

#OpenBSD/luna88k has been switched to gcc4! â€‹

And with that the last GCC3_ARCH is gone!

Not with a bang but a whimper.. â€‹

https://marc.info/?l=openbsd-cvs&m=176124507027163&w=2

https://marc.info/?l=openbsd-cvs&m=176124650328448&w=2

'CVS: cvs.openbsd.org: src' - MARC

New attempt to get pt2-clone running on big-endian IRIX ⏳ đŸŽ¶
@joacim Vi och vÄra 1090 partners respekterar helt klart lite av din integritet. Eller nÄt.