I think I know quite some things about OS internals, but not that much as a guy how writes device drivers daily. Would happily read such book to get in par with the author.
> This book has negative value. It is actively destructive to FreeBSD, even if in the short term it boosts the author's public profile.
I won't be that radical, the book still has value. There are many useful code samples with descriptions and explanations of concepts I did not know before. But to get to them one has to dig through a forrest of useless tokens. Someone has to pass it through an LLM and publish distilled edition. :-)
Indeed! I read through a couple of paragraphs. Each begins with a bloated introduction where each sentence repeats same idea many times in different words. Lot's of bullets repeating same statement. That's exactly how LLM scam looks like. The whole book is full of water. It can be reduced in size by a factor of 5.
No. SELinux is based on the Linux Security Module framework, which places explicit hooks at key points within the kernel.
They also operate under pretty fundamentally different philosophies. Seccomp is based on a program dropping its own permissions. SELinux is based on a system integrator writing an ahead of time policy restricting what a program can do.
When I was watching that Lunduke's video a couple of days ago initially I was thinking he's just making a joke of that Vendefoul Wolf distro on 200MB box. I recalled using FreeBSD as access server with lots of modems (PPP/SLIP), Apache, Samba and QuakeWorld server running on a box with just 32MB of RAM. That was also my daily working machine with XF86 and Enlightenment desktop manager, circa 2000. So, 200MB is a whole lot of memory!
That's interesting, thanks. I feel a need for simple multitasking/networking OS for synthesizable RV32I core (not RTOS like, but more like Unix or CP/M). Would be nice to try Plan9 on it once port is out.
