Language Selection

English French German Italian Portuguese Spanish

Just What is the "Linux Developers Community"?

Filed under
Linux

I must report that the woodshed session resulted in just a mere good old fashioned ‘talking-to”. As our readers know, we involve ourselves heavily in the linux developers community. We have offered and have given proven producers money for their efforts. Such fruits should be available for all to pick from in November of this year…and yes, resulting from the work of the Linux Developers Community. Now, I have been taken to task for using that term. Linux Developers community.

Yes, helios is aware that there is no monolithic structrure or sprawling complex with manned security that has huge granite signs stating: International Linux Development Headquarters. We also realize that there is no Brotherhood of Linux Union, organized Linux Fraternity or bowling league…at least not officially sanctioned by linux. See, that’s the point. Tell me of something that IS officially sanctioned by Linux.

So the question begs to be asked: Just who is a linux developer? Let’s look at the obvious choices we have. Ok Linus. Nothing like starting at the shallow end of the pool I say. Not many stumbles on this end. Now, some would argue that it gets mirky from here…and maybe it does. From there, we have legion of kernel developers and hackers, toiling away in obscurity. (I am informed that this is mutually benificial to hacker and society alike). As you butt-slide down the steep rocky slope that is Linux, you will begin to see more and more people involved in the development process. Some in clusters, some paired up…some working alone…but all working on one grand thing.

Linux.

and what are they doing?

Developing.

Developing what? Let’s take a look.

Full Article.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more