To view parent comment, click here.
To read all comments associated with this story, please click here.
I don't know who gave you the idea that I was a kernel hacker. The only people who can maintain Reiser and Reiser4 is the Resier team. Random Joe Clueless cannot delve into the source code and automatically start maintaining it.
Who told you that once Reiser4 enters the kernel's stable branch it will be maintained by hackers other than the Reiser4 team? No dude, it doesn't work that way.
I'll take that as a "no".
So if Reiser4 is incorporated into mainline, and people start using it, the Linux Kernel developers are basically at the mercy of Namesys, because they have users that are dependent upon code that only Namesys can maintain? Wonderful. I think you are getting close to understanding the problem.
All that glitters is not gold, and often comes with a price. Namesys wants it to come with a price so that they can leverage it later. No thanks!







Member since:
2005-08-11
> If what you postulate happens, what will be Reiser4's differentiating factor as compared to other filesystems?
This is where our viewpoints diverge. You are looking at Namesys's business requirements. I am looking at the long-term consequences for the community.
Are you volunteering to take over Reiser4 as maintainer after Namesys loses interest in it? If so, and if you could guarantee a suitable timeframe, that would no doubt help get it into mainline.
Are you interested?