FreeBSD Kernel Internals Documentation

David Jackson djackson452 at
Mon Jan 9 20:37:32 UTC 2012

On Tue, Jan 3, 2012 at 9:46 AM, Alejandro Imass <ait at> wrote:

> On Tue, Jan 3, 2012 at 1:41 AM, Da Rock
> <freebsd-questions at> wrote:
> > On 01/03/12 12:06, Walter Alejandro Iglesias wrote:
> >>
> >> On Mon, Jan 02, 2012 at 12:33:20PM -0700, Chad Perrin wrote:
> >>>
> >>> Ubuntu, actually, has thrown out the baby with the bathwater.  In its
> >>> zeal to make things "just work" in a particular manner, it seems
> I would just like to add that is FreeBSD was so crappy open sour
> software, why does it run half the Internet?
> --
> Alejandro Imass
> _______________________________________________
> freebsd-questions at mailing list
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at"

I Never said that FreeBSD was not a good OS to use on a server, if you just
want to install it and use it, its a really great OS on a server.

My concerns, and this is entirely sincere and a result of my own attempts
to read the source, that rarely, if ever, have I ever seen C code that is
self documenting and where additional textual descriptions would not speed
up learning of the source code to be able to work on the source code of the
kernel. There is very little documentation of kernel internals and the
source code comments are, really quite honest, do not really do a good job
of explaining things.An example of somewhat better source code commenting
can be seen in Minix.

this makes it really hard, and it takes much longer than it should to
become acquinted with the kernel and it is just an unproductive and bad
coding style to not document source code, not necessarily in the file but
it can be in a wiki of some sort. Document your stuff is really important
and a well known good coding practice,

Ubuntu got some things right but has gone awry on one  thing the HORRIBLE
Unity UI which most everyone i talk to hates it. The good thing about
Ubuntu is with apt-get installing and maintaining up to date packages is
easy and things usually come in an working out of the box state. If you
dont like how Ubuntu is configured it is a real Unix system and one can get
into the configuration files and change anything that one needs to.

I used to use FreeBSD a lot but since Linux tends to support more hardware
and plays better with Virtualbox I have had to use that more.

I actually was considering starting my own project to develop some sort of
driver compatability layer that would allow Darwin and or Linux drivers to
be loaded on FreeBSD, and provide a stable binary ABI, in a kernel module.
This is one reason I have started to look at the FreeBSD source code and
noticed how difficult it really is to understand anything due to lack of

More information about the freebsd-questions mailing list