Integration and testing are important too.
One want to bang on the development series before it becomes "stable."
2.2.0 is no good if it doesn't run on your hardware.
One might also want to get early access to device support in development
kernels that is not present in the stable ones, but in that case it's a
matter of tracking both the current Linux kernel and some third-party
patches or a module.
>So why are kernel modules so different? And why are "system programs"
>different (I don't mind occasionally breaking programs like "ifconfig" and
>"modprobe" etc, for example)?
Another reason for tracking the kernel. Better to learn that 'ipfwadm -V'
has no replacement in 2.2 early, and try to get a replacement put in before
2.2's release, than to complain about it afterwards.
-- Zygo Blaxell, Linux Engineer, Corel Corporation, zygob@corel.ca (work), zblaxell@furryterror.org (play). It's my opinion, I tell you! Mine! All MINE! Size of 'diff -Nurw [...] winehq corel' as of Wed Mar 10 12:14:00 EST 1999 Lines/files: In 2058 / 29, Out 5773 / 59, Both 7821 / 85- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/