public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Slackware: kernel confusion
Date: Mon, 25 Jun 2007 23:21:03 -0500	[thread overview]
Message-ID: <005301c7b7a9$6871c130$ab00a8c0@tenstac> (raw)
In-Reply-To: <BAY141-DAV130C4DD5D7430D9DDA57B78F0B0@phx.gbl>

Yea, listen to patrick, "unless you have a particular reason" to install
headers then it's better to not do so. The glibc is the crux of all of 
this toolchain, and the same reason why that old viavoice became 
a nightmare to support. The distro folks like patrick play with gcc,
glibc, and binutils combination until they find a stable combination
to build the entire system out of. The kernel headers, as he states 
in his warning, it's dangerous to use headers newer than the glibc
version on your system. You can still build the 2.6.x kernel. There
are some situations where stuff will not build, which is why he has
the headers on the site, but don't change headers as a default 
starting point, only as a last resort. And yes, you don't need the 
modules, in fact you don't need anything from there. Patrick uses
ONLY unmodified kernels anyways, so if you want the latest 
that still works with speakup, grab the last of the 2.21.x from 
kernel.org. Or be like us old folks who prefer the stable 
"trailing edge". I have not found a need for 2.6.x yet, so using
Patrick's similar logic, I will do so when I have a reason to. 
I used to chase the leading edge kernels but found that it was 
generally a waste of time in the large scheme of things.

  -- Doug


  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` ace
 ` Doug Sutherland
   ` Zachary Kline
     ` Doug Sutherland [this message]
       ` Steve Holmes
         ` Ralph W. Reid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005301c7b7a9$6871c130$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).