From: "Richard B. Tilley " "(Brad)" <rtilley@vt.edu>
To: SK <linuxkern@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: How to extract CONFIG file for a kernel
Date: 10 Dec 2002 13:54:22 -0500 [thread overview]
Message-ID: <1039546462.11575.9.camel@oubop4.bursar.vt.edu> (raw)
In-Reply-To: <20021210184805.19739.qmail@web14601.mail.yahoo.com>
If you have RH's /usr/src directory installed, you can cd to
/usr/src/linux-2.4/configs and pick from several pre-built config files.
they work nicely. I use them to build kernel.org kernels. It's *much*
easier to make a few config changes to their config file than starting
from scratch. They tend to be highly modular though... some people don't
like this.
Good luck!
On Tue, 2002-12-10 at 13:48, SK wrote:
>
> Is there any way to extrace the CONFIG file
> used to compile a kernel. I have 2.4.18-14 kernel
> from RedHat and I want to know the config options
> used for compiling that kernel.
>
> Any ideas..?
> Thanks
> Santhosh
>
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
--
Richard B. Tilley (Brad), System Administrator & Web Developer
Virginia Tech, Office of the University Bursar
Phone: 540.231.6277
Fax: 540.231.3238
Page: 557.0891
Web: http://www.bursar.vt.edu
next prev parent reply other threads:[~2002-12-10 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:48 SK
2002-12-10 18:54 ` Richard B. Tilley (Brad) [this message]
2002-12-10 19:13 ` Arjan van de Ven
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=1039546462.11575.9.camel@oubop4.bursar.vt.edu \
--to=rtilley@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxkern@yahoo.com \
/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
all inboxes | Powered by JetHome®