Trouble Compiling modules/kernel

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jan 08, 2009 at 12:48:54PM +0900, Kerry Hoath wrote:
> I must say i'm mystified as to why most people seem to want to "get rid 
> of" the distribution kernel; fearing that it is bloated and overloaded.

Well, here are my own reasons for it:

1. I'm currently running 2.6.27.8, while debian still seems to be
   providing 2.6.26. I'll grant that this isn't a big deal for me, but
   it relates to my second reason for still building my own kernel.

2. When I started building the 2.6.x.x series on this hardware,
   speakup still had to be built into the kernel in those days. This
   meant that I had to build my own kernel if I wanted something
   fairly recent (both linux, and speakup), and if I was going to do
   that, I might as well customize it to my hardware, and only include
   the support I know I need.

Once we move into the 2.7.x series, or the 3.x series, (whatever is
coming next), where previous experience dictates that you can't use
your current .config file fairly painlessly, I plan to go with the
distro-provided kernels than. To summarize, as long as I don't need to
extensively modify my .config file to build a newer kernel, and as
long as I can get a newer kernel than what the distro provides if I
want to do that, I see no reason not to do it, that's my personal choice.

> If everyone documented what they did as they did it and submitted it to 
> the site then we wouldn't have these problems to anywhere this degree.

The problem here is that the information is scattered through the list
archives, since there are a good number of us who post instructions on
how to do this or that, a lot of times, more than once. This info is
however not on the site, because Kirk has much better things to do
than maintain the web pages, and nobody from the community, it seems,
wants to take on the job, which I frankly can't altogether
fault. maintaining a web site is a big job to do for one person,
especially if it's done as a volunteer, and not as a paid
employee. When you throw 2 or more people into the mix, say assigning
person 1 to this section of the site, and person 2 to another section,
this is a big responsibility for each of those people also, and has
the potential to lead to a conflict, since person 1 may not like the
way person 2 wants to do things.

My own suggestion therefore would be to turn linux-speakup.org into a
wiki, where those who want to help can do so, without having to take
on the responsibility for the entire site, or a section, if they don't
want to. I personally would have no problem expanding the wiki here,
and there whenever I had the chance to do so, but I couldn't commit to
be responsible for an entire site, or even a certain section of it, if
I had to be the single person who made sure that it stays up to date
all the time. Of course, it would be best if those who wanted to
contribute got a login account, as opposed to a free-for-all, and
ideally, there should be a team who would monitor the contents once a
while for quality control, and accuracy. So Kirk, and others, how
about something like apt-get install phpwiki (since I believe Kirk is
running debian on linux-speakup.org), any thoughts?

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager at EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklloKoACgkQ7s9z/XlyUyCBuwCgutT4mgQX+SGj/+d/nouDRsHX
GdQAn1SRAYG3GiJMRMaLHH105hVzBXPj
=GdfM
-----END PGP SIGNATURE-----