> Sorry for that Otto,
> If its not documented somewhere then unfortunately old things tends to
> stick. And also, the project takes a conservative view on BIOS (8G
> barrier), so I thought OpenBSD has this limitation.
Well, the real answer is: The code is the documentation. In this case
sys/arch/i386/stand/boot/conf.c contains the boot block version
string, so a cvs log on that file does a partial job of showing the
history. But even if I gave you 10 files to read the cvs log for, it
would not give you the whole story. Even I don't know that whole
story.
We do between 20 and 200 commits a day to the project. At that rate
the assumption that old things are going to remain the same is just...
incredibly unrealistic.
> Undeadly is a good place to learn what limitations have been removed.
No, undeadly is not a good place to learn that.
> I was just reading your undeadly post from 2008 about what changed in
> FFS2. I hope you guys can manage to do a update on what's changed in
> the last year every year.
Your hopes are misplaced.
The people making most of the changes do it because they enjoy making
changes. You wish that those same people would also be the types who
enjoy like trumpetting their work, publishing, explaining it.
Besides making minimal updates to the manual pages, that is pretty
unlikely.
> Just like in the papers section of the
> website, there's a recent update, that becomes very helpful for new
> people like me who are coming in.
The papers section shows that our group has developers who like to
travel. They write papers or give talks at conferences.
If it wasn't for their love of travel, they probably would not write
those papers.
You want us to do a better job of communicating what we change. I
think we are doing a great job
Every day the tree changes in many ways -- check out
[email protected]
