So your saying I should actually trust my distro to build a kernel right? I build my own kernels, I have since day one. But, heres a semi-key point, what happens to vendor patches? Do they ever get folded back into the main tree? mdk and rh I know do alot of patching. Its a waste of effort if the patches arnt looked at. And also, I was using that as a rant example. Ive never had a kernel break for me except for the parport and loopback problems. And then, I just built parport without ieee, and Im not using loopback rightnow anyhow, so its not a big loss.
On 24-Nov-2001, J Sloan wrote:
> Patrick McFarland wrote:
>
> > What If I get up one day, and I cant print? Or build isos?
>
> Who would switch kernels on you while you sleep?
>
> > The Kernel needs Quality Assurance.
>
> Yep, and that's what the vendors do for you.
>
> Stick with the tested, QA'd, vendor-supplied
> kernel unless you're a developer or a skilled,
> adventurous sys admin who reads lkml!
>
> kernel tarballs are NOT for mom -
>
> cu
>
> jjs
>
>
-- Patrick "Diablo-D3" McFarland || unknown@panax.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:19 EST