Which releases are production stable?
by
S.+Invicta
·
· Score: 5, Interesting
I must say that I am getting a little bit leary about using the 2.4.x series in production. The fast releases don't inspire confidence. On one hand people (perhaps rightfully so) say don't use a kernel that is newer than 6 mo. old or you are a beta tester. But of course those older kernels were once bleeding new as well...how to know which to use and which to avoid? That 6 mo. old one might be the right age and yet perfectly horrible. Perhaps what is needed is a kernel stability/security chart that shows how well different kernel versions have "aged". Anyone know of such a beast?
Alan's branch
by
BlowCat
·
· Score: 5, Interesting
SlashDot seems to pay more attention
to the Linus' branch, but if you really
want to be on the edge, you should
track the Alan's branch (i.e. the "ac"
series). The branches are synchronized
with each other from
time to time, but if you want to fix some
problem, check the code in the AC branch -
it may have the fix already.
That's especially true for the sound
drivers.
As for stability, the Linus' releases
don't seem to be formally tested anyway.
Maybe Linus is more conservative in
applying patches before the release,
but the recent events (2.4.11 and 2.4.12)
show that the kernel may not compile
in a common configuration and
be released notwithstanding.
I just wish that some day I will see a working Linux bttv driver. For some reason, I always drop WAY too many frames with every Linux video capture program I use. (MainActor has been best so far - it only drops a few frames, almost gets perfect video quality, almost keeps A&V in sync and almost saves in format that can be read to Virtualdub in Windows, or any other Win32 editing app).
I need to use Windows programs to do video captures, which technically isn't nice either because the driver really doesn't work perfectly there either - it either works perfectly or not at all, depending on the phase of the moon.
Better multimedia support is always nice. One day, I will be able to use Linux for everything. =)
Slashdot Mirror
I must say that I am getting a little bit leary about using the 2.4.x series in production. The fast releases don't inspire confidence. On one hand people (perhaps rightfully so) say don't use a kernel that is newer than 6 mo. old or you are a beta tester. But of course those older kernels were once bleeding new as well...how to know which to use and which to avoid? That 6 mo. old one might be the right age and yet perfectly horrible. Perhaps what is needed is a kernel stability/security chart that shows how well different kernel versions have "aged". Anyone know of such a beast?
As for stability, the Linus' releases don't seem to be formally tested anyway. Maybe Linus is more conservative in applying patches before the release, but the recent events (2.4.11 and 2.4.12) show that the kernel may not compile in a common configuration and be released notwithstanding.
Yeah, am trolling.
;)
But I still wonder why has FreeBSD had a stable
rw support for NTFS, and the linux kernel is still
lagging...
I mean, can't they copy^H^H^H^Hmodel it after
the BSD code like they have done in some many cases?
- Gerd Knorr: btaudio/bttv update
@whee. Sounds good.
I just wish that some day I will see a working Linux bttv driver. For some reason, I always drop WAY too many frames with every Linux video capture program I use. (MainActor has been best so far - it only drops a few frames, almost gets perfect video quality, almost keeps A&V in sync and almost saves in format that can be read to Virtualdub in Windows, or any other Win32 editing app).
I need to use Windows programs to do video captures, which technically isn't nice either because the driver really doesn't work perfectly there either - it either works perfectly or not at all, depending on the phase of the moon.
Better multimedia support is always nice. One day, I will be able to use Linux for everything. =)