Which is why I am going to email @bagder and complain to him, for some random reason.
Sometimes known as IcePic.
| OpenBSD | jj |
| C64/Amiga | IcePic |
| OpenBSD | jj |
| C64/Amiga | IcePic |
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.
@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?
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..
â