All of lore.kernel.org
 help / color / mirror / Atom feed
From: joy <gracecott@sancharnet.in>
To: James Miller <jamtat@mailsnare.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: 2.6.0 kernel compile overview
Date: Mon, 05 Jan 2004 22:51:23 +0530	[thread overview]
Message-ID: <3FF99D13.1050403@sancharnet.in> (raw)
In-Reply-To: Pine.LNX.4.58.0401050850220.3345@localhost

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
>
>  
>
There isn't much of a difference actually, the only major difference (to 
us end users ;)
is that the compilation looks cleaner.
also, now there are fewer steps to follow (thank god)
1. make mrproper
2. make menuconfig
    here you can load the config file created and add the rest of the 
necessary options.
3. make
    this takes care of even generating the bzImage (hooray!)
4. make modules
5. make modules_install (which I had forgotten and asked on this list today)
so all you have to do is copy the image to your /boot, run lilo (after 
editing lilo.conf, obviously) and you are done!


-
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

  parent reply	other threads:[~2004-01-05 17:21 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
2004-01-05 17:21 ` joy [this message]
2004-01-05 18:16   ` Theo. Sean Schulze
2004-01-05 21:36 ` James Turnbull
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=3FF99D13.1050403@sancharnet.in \
    --to=gracecott@sancharnet.in \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.