From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: Re: 2.6.0 kernel compile overview
Date: Mon, 5 Jan 2004 09:43:39 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401050926380.3345@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0401050850220.3345@localhost>
In case anyone should get any ideas about going to the "source" for the
sort of information I hope to find: I've just been to
www.kernel.org/pub/linux/kernel/v2.6 and there is, indeed, a README-2.6
file there. If one would expect to find the sort of information I need,
one would think that, of all places, it should be here. Unfortunately, it
is a zero byte file. It doesn't contain any text. All focus on
development here, it seems clear, with explication only following as an
afterthought.
James
PS Nothing on the system under /usr/src/linux or
/usr/src/linux/Documentation seems very relevant, either.
On Mon, 5 Jan 2004, James Miller wrote:
> A precocious 16 year old "Linux guru" friend (I taught him the basics
> about a year ago, now he knows about 3x more than I do) recently set up a
> new laptop for me with Gentoo and the 2.6.x kernel. Despite the obvious
> genius displayed in this endeavor, he forgot (as adolescents are prone to
> do) to implement some fairly basic features in the kernel: namely the
> system speaker and wireless networking. This leaves me the task of
> getting those things operational myself, which means recompiling the
> kernel. I've not done much kernel compiling - once or twice, if memory
> serves - and all documentation I have refers to 2.4.x kernels and earlier.
> I just did a quick 'net search and couldn't find anything specific on
> 2.6.x kernel compiling. At the same time, I have understood from the
> friend that 2.6.x kernel compiling differs somewhat. So, can anyone
> direct me to any sources on 2.6.x kernel compiling? I have an overall
> grasp of the earlier kernel compiling process, so I'm mainly interested in
> how compiling the newer kernel differs. I generated a .config file for
> the current kernel using instructions provided by the friend in question,
> and of course have the kernel source on the system. So, pointers to any
> overviewish documentation specific to 2.6.x kernel compiling would be
> appreciated, as would general remarks on how compiling differs with the
> 2.6.x kernel from compiling earlier kernels.
>
> Thanks, James
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-05 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 15:13 2.6.0 kernel compile overview James Miller
2004-01-05 15:43 ` James Miller [this message]
2004-01-05 17:21 ` joy
2004-01-05 18:16 ` Theo. Sean Schulze
2004-01-05 21:36 ` James Turnbull
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 19:39 EXT-Reimer, Jim D
2004-01-05 20:09 ` James Miller
2004-01-05 21:45 chakkerz
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=Pine.LNX.4.58.0401050926380.3345@localhost \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/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