public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] One more note on Install Instructions
Date: 16 Mar 2002 20:29:52 +0200	[thread overview]
Message-ID: <1016303393.11041.2.camel@nosferatu.lan> (raw)
In-Reply-To: <5.1.0.14.2.20020416135248.00b2e6d8@mindspring.com>

On Tue, 2002-04-16 at 20:01, Michael Lang wrote:
> It seems that by default, Kernel 2.4.18 is being built and yet everyone 
> seems to be advising to downgrade to 2.4.17.  I personally think that as 
> you go to release 1.0, we should have instructions for building the latest 
> *stable* release of the kernel rather than grabbing the latest experimental 
> kernel (or whatever y'all call 2.4.18)...athough I am not so sure about:
> 
> ebuild /usr/portage/sys-kernel/linux-source/linux-sources-2.4.17.rc5.ebuild 
> merge

# emerge =sys-kernel/linux-sources-2.4.17-r5

would be the better/shorter form.

> 
> ...as a cmd to document in install instructs.  Maybe a better option is to 
> roll up the first four commands from Code Listing 24 (First code listing of 
> "Installing the Kernel and Sys logger") into a script that queries the 
> directories under sys-kernel and prompts user to pick which version to ebuild.
> 
> Any thoughts?
> 
> Michael
> 
> "All things should be as simple as possible, but no simpler" -- Albert Einstein
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa




  reply	other threads:[~2002-03-16 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 18:01 [gentoo-dev] One more note on Install Instructions Michael Lang
2002-03-16 18:29 ` Martin Schlemmer [this message]
2002-03-16 20:31 ` Daniel Robbins

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=1016303393.11041.2.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.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