Bah. The only fucking thing that you have to do to be UNIX (tm) is to run a broken test-suite and get a certificate.
It just means you have implemented a number of functions the way you were supposed to. It doesn't mean your operating system is relevant or important to the market or to the computing field in general.
Linux *is* one of the most important operating systems being developed today because:
1. It adopts early technologies even in draft-phase 2. It's helping to extend POSIX 3. Its fast development model is bringing solutions for problems that bleeding-edge hardware introduces
But if you're a CVS/SVN user, I'd start by trying to understand the conceptual difference between centralized and distributed development models. Linus has a detailed explanation here: http://marc.info/?l=git&m=113072612805233&w=2
Re:Does it use a "hacked" kernel?
on
Fedora 7 Released
·
· Score: 2, Insightful
Yes, Fedora and any sane distribution will have its own version of the Linux kernel.
No one think they're better then upstream developers, the point is that *this* *is* the recommend way to work, for several reasons:
1. Some patches that are important to customers, may not be in mainline yet due to the long process submit-review-fix-submit process (eg, xen) or even because no one cared of submitting it
2. The kernel is changing very fast these days, while distros usually has a longer release process. Then you end up by freezing an 'old' kernel that works for your distro
3. If you freeze a kernel, you'll have to backport things making the original kernel looks quite different
Also, forks in the Linux kernel is not seem as a bad thing. On the contrary, forking is the recommended way to work: you fork the Linus' tree, work on it locally and then submit your changes. That's the way GIT works.
And you CAN use/proc/config.gz from a modified kernel. The kernel build system will just discard any invalid symbol on a 'make oldconfig'.
I think every low-level linux programmer should (although some of my teammates doesn't know).
IIRC, Ulrich Drepper was one of the programmers who worked on the 'linux GNU' integration back in the first years of Linux.
He was (is?) the responsible for the NPTL library, and besides the GNU C library, he is also responsible to implement POSIX semantics for processes control in the Linux kernel.
Slashdot Mirror
Bah. The only fucking thing that you have to do to be UNIX (tm) is to run a broken test-suite and get a certificate.
It just means you have implemented a number of functions the way you were supposed to. It doesn't mean your operating system is relevant or important to the market or to the computing field in general.
Linux *is* one of the most important operating systems being developed today because:
1. It adopts early technologies even in draft-phase
2. It's helping to extend POSIX
3. Its fast development model is bringing solutions for problems that bleeding-edge hardware introduces
So, that 'it's not UNIX' doesn't mean anything.
You can try one of the GIT crash courses at: http://git.or.cz/course/index.html
But if you're a CVS/SVN user, I'd start by trying to understand the conceptual difference between centralized and distributed development models. Linus has a detailed explanation here: http://marc.info/?l=git&m=113072612805233&w=2
Yes, Fedora and any sane distribution will have its own version of the Linux kernel.
/proc/config.gz from a modified kernel. The kernel build system will just discard any invalid symbol on a 'make oldconfig'.
No one think they're better then upstream developers, the point is that *this* *is* the recommend way to work, for several reasons:
1. Some patches that are important to customers, may not be in mainline yet due to the long process submit-review-fix-submit process (eg, xen) or even because no one cared of submitting it
2. The kernel is changing very fast these days, while distros usually has a longer release process. Then you end up by freezing an 'old' kernel that works for your distro
3. If you freeze a kernel, you'll have to backport things making the original kernel looks quite different
Also, forks in the Linux kernel is not seem as a bad thing. On the contrary, forking is the recommended way to work: you fork the Linus' tree, work on it locally and then submit your changes. That's the way GIT works.
And you CAN use
I think every low-level linux programmer should (although some of my teammates doesn't know).
IIRC, Ulrich Drepper was one of the programmers who worked on the 'linux GNU' integration back in the first years of Linux.
He was (is?) the responsible for the NPTL library, and besides the GNU C library, he is also responsible to implement POSIX semantics for processes control in the Linux kernel.
So, yes, his opnion is very important.
Agreed, they should create something like 'erc.slashdot.org'. Rationale: easy to ignore.