From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] README update from the stone age
Date: Tue, 20 Sep 2005 16:53:51 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0509201644040.19786@shark.he.net> (raw)
In-Reply-To: <20050920184544.14557.15273.stgit@zion.home.lan>
On Tue, 20 Sep 2005, Paolo 'Blaisorblade' Giarrusso wrote:
> We have no options which the user can set in the Makefile. Only the
> EXTRAVERSION, which is also useful in place of the "backup modules"
> suggestion.
>
> Hey! Can anybody tell me when we last had configuration options in the top
> Makefile? Please?
>
> Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
> ---
>
> README | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/README b/README
> --- a/README
> +++ b/README
> @@ -149,6 +149,9 @@ CONFIGURING the kernel:
> "make gconfig" X windows (Gtk) based configuration tool.
> "make oldconfig" Default all questions based on the contents of
> your existing ./.config file.
> + "make silentoldconfig"
> + Like above, but avoids cluttering the screen
> + with question already answered.
questions
>
> NOTES on "make config":
> - having unnecessary drivers will make the kernel bigger, and can
> @@ -169,9 +172,6 @@ CONFIGURING the kernel:
> should probably answer 'n' to the questions for
> "development", "experimental", or "debugging" features.
>
> - - Check the top Makefile for further site-dependent configuration
> - (default SVGA mode etc).
> -
> COMPILING the kernel:
>
> - Make sure you have gcc 2.95.3 available.
> @@ -199,6 +199,9 @@ COMPILING the kernel:
> are installing a new kernel with the same version number as your
> working kernel, make a backup of your modules directory before you
> do a "make modules_install".
> + In alternative, before compiling, edit your Makefile and change the
Alternatively,
> + "EXTRAVERSION" line - its content is appended to the regular kernel
> + version.
Or consider using CONFIG_LOCALVERSION, which can be set by
using the "make *config" tools in the "General Setup" menu.
>
> - In order to boot your new kernel, you'll need to copy the kernel
> image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
--
~Randy
next prev parent reply other threads:[~2005-09-20 23:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 18:45 [PATCH 1/7] Add dm-snapshot tutorial in Documentation Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:45 ` [PATCH 2/7] i386: little pgtable.h consolidation vs 2/3level Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:45 ` [PATCH 3/7] fix locking comment in unmap_region() Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:45 ` [PATCH 4/7] README update from the stone age Paolo 'Blaisorblade' Giarrusso
2005-09-20 23:53 ` Randy.Dunlap [this message]
2005-09-20 18:45 ` [PATCH 5/7] Clearify comment in swapfile.c Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:45 ` [PATCH 6/7] update stale comment for removal of page->list Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:46 ` [PATCH 7/7] Add a note about partially hardcoded VM_* flags Paolo 'Blaisorblade' Giarrusso
2005-09-20 22:13 ` [PATCH 1/7] Add dm-snapshot tutorial in Documentation Nix
2005-09-21 15:04 ` Blaisorblade
2005-09-21 16:11 ` Nix
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.0509201644040.19786@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®