2.6.0-test, how to test it? [Was: Linux v2.6.0-test1]

[Antonio Vargas <wind@cocodriloo.com>]

On Sun, Jul 13, 2003 at 08:59:07PM -0700, Linus Torvalds wrote:
> 
> Ok,
>  the naming should be familiar - it's the same deal as with 2.4.0.
> 
> One difference is that while 2.4.0 took about 7 months from the pre1 to 
> the final release, I hope (and believe) that we have fewer issues facing 
> us in the current 2.6.0. But very obviously there are going to be a
> few test-releases before the real thing.
> 
> The point of the test versions is to make more people realize that they
> need testing and get some straggling developers realizing that it's too
> late to worry about the next big feature. I'm hoping that Linux vendors
> will start offering the test kernels as installation alternatives, and
> do things like make upgrade internal machines, so that when the real
> 2.6.0 does happen, we're all set.

In the meantime, what about a "running 2.6.0-test HOWTO"?

ie:

1. base distro you using right now for testing

2. which updates are needed for said distro (I assume modutils, any others?)

3. compiler to use

4. parts which should be abused without fears for data loss

5. parts which could eat disks, for those with separate desktop/test machines

6. whatever else you can think about


on a related note, from reading lkml I can see that in-tree ext3
is in good shape, what about reiser3 or reiser4?


>
> 		Linus
> 
> [ BIIIIIIG SNIP ]
>

Greets, Antonio.

-- 

In fact, this is all you need to know to be
a Caveman Database Programmer:

A relational database is a big spreadsheet
that several people can update simultaneously.