public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug McNaught <doug@wireboard.com>
To: "Rob" <rwideman@austin.rr.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: configuring the kernel
Date: 08 Aug 2001 13:56:28 -0400	[thread overview]
Message-ID: <m3n15aigfn.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <LHEGJICMMCCGOHKDFALMOEMHCAAA.rwideman@austin.rr.com>
In-Reply-To: "Rob"'s message of "Wed, 8 Aug 2001 12:11:44 -0500"

"Rob" <rwideman@austin.rr.com> writes:

> 1-does "make menuconfig" require X to be installed? I dont have X, i just
> have RH 7.1 with kernel dev and kernel sources installed (atleast those were
> the ONLY things i had selected during install).

No, all you need is the 'ncurses-devel' package.  

> 2-if i untared/unpacked the kernel to the folder /root/newkern (here is
> where i did the "gzip -cd linux 2.4.7...... |tar xvf -" command) is it ok to
> delete the newkern folder and unpack nd then do the "make menuconfig"?

Yes, but this will reset your configuration to the defaults.  If you
want to preserve the choices you made and then modify them in
menuconfig, save off the '.config' file before nuking, then move it
into the newly unpacked directory.

That said, you shouldn't have to remove the source tree.  Simply do:

$ make menuconfig
$ make dep && make clean && make bzImage

-Doug
-- 
Free Dmitry Sklyarov! 
http://www.freesklyarov.org/ 

We will return to our regularly scheduled signature shortly.

  reply	other threads:[~2001-08-08 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 17:11 configuring the kernel Rob
2001-08-08 17:56 ` Doug McNaught [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-08 18:34 Per Jessen

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=m3n15aigfn.fsf@belphigor.mcnaught.org \
    --to=doug@wireboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwideman@austin.rr.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