On Fri, 9 Feb 2007, Grok Mogger wrote:
Thanks for the advice. I have to admit, sounds a little scary for someone
who has never compiled a kernel before. =\ But I may actually try it.
There's a first time for everything! And you'll have a better
understanding of the kernel that way too.
What about security updates though (and just bug fixes for that matter) if
I've compiled my own kernel? Basically what you're saying is that I won't
have a Debian kernel, I'll just have a kernel built from the sources off
kernel.org. Right? So I guess to stay up-to-date, I'd just need to try and
keep up with the latest stable release from kernel.org?
Security updates to the kernel are rare - usually they're to the rest of
the softare in the distro. But it's a reasonable idea to check kernel.org
for updates.
Also, I have to say this whole problem I've stumbled on to seems kind of
silly to me in a way. I love Debian's approach to stability and security,
but why not at least keep adding hardware support to the kernel as it becomes
available? Seems like it would make a lot of sense to at least just keep
adding drivers even if the rest of the kernel remains frozen at 2.6.18 or
whatever.
Really a kernel's a kernel - the debian packages have just been tweaked
more for convenience than substantively changed. To add some parts of a
kernel release without others would be really difficult, I would expect.
----------------------------------------------------------------------
Andrew J Perrin - andrew_perrin (at) unc.edu - http://perrin.socsci.unc.edu
Assistant Professor of Sociology; Book Review Editor, _Social Forces_
University of North Carolina - CB#3210, Chapel Hill, NC 27599-3210 USA
New Book: http://www.press.uchicago.edu/cgi-bin/hfs.cgi/00/178592.ctl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
