Post a Comment
The last link doesn't points correctly to http://kernelnewbies.org/LinuxChanges
Already done...
http://test.kernel.org/perf/index.html
Linus' announcement on the LKML made me laugh really hard. Geeky humor, gotta love it.
Something I noticed skimming through the changelog (available here: http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.19): bcm43xx now supports 64bit and systems with >1GB of RAM. Sweet!
Edited 2006-11-30 08:38
So Reiser4 does not make it in because it still needs further development... but Ext4 does because, they say, it is, "for developers"?
Smacks like a case of NIH syndrome to me. All these objections to the inclusion of Reiser4, yet when they create their own it goes straight in even though it is not yet stable.
You should have read the article instead.
http://kernelnewbies.org/LinuxChanges
"Like OCFS2 and like any other filesystem that wants to be merged in the linux kernel, GFS2 developers asked for submission long time ago. They were asked to fix things (even considering that GFS2 had already been developed at Sistina and it was already a stable final product), they submitted it again, they were asked to fix more things, and so on, for a long period of time. Their developers have fixed every thing they were asked to fix. Because of their hard work, GFS2 is now ready to be merged, nobody opposes to it, and everyone is happy. (Amazing, isn't it? In fact, 3 new filesystems are being merged in 2.6.19 and nobody is flaming nobody, quite the contrary)"
I don't think it is NIH syndrome. I believe that there were technical reasons, that required some give on what "became" a two sided issue.
I'm sure Reisers persuasive abilities let him down, simply because he had to ask people to compromise. Now thats a little tricky anyway, but you can't bully people into maintaining your code.
What I am surprised by, it that since Reiser is erm...occupied. That nobody from is company has stepped up to push the Filesystem for kernel inclusion for there own reasons.



