public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bastian Balthazar Bux <BastianBalthazarBux@pnpitalia.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which kernel ??? 2.4 or 2.6
Date: Mon, 06 Dec 2004 22:46:05 +0100	[thread overview]
Message-ID: <41B4D31D.1060009@pnpitalia.it> (raw)
In-Reply-To: <e00942e404120609304c58411f@mail.gmail.com>

Collins Richey wrote:

>On Mon, 06 Dec 2004 18:09:20 +0100, pat <pat@xvalheru.org> wrote:
>  
>
>>Hi All,
>>
>>I have question. Which kernel is better 2.4 or 2.6 ??? I want to install
>>Gentoo 2004.3 and I'm new to Gentoo.
>>    
>>
>
>There isn't a simple answer to that question. 2.6 has new features and
>may break a very few components. 2.4 works just fine.
>
>If you want to start with 2.6, there is a separate bootstrap26.sh
>procedure for doing that from a stage1 install. There could be some
>problems. Check forums or this list archives for more information.
>  
>
from 2004.3

bootstrap26.sh is no more there 

>OTOH, as a new user, you may want to stick with the standard 2.4
>instructions and reserve building a 2.6 kernel for a later date after
>you have a running system and after you have become more familiar with
>gentoo. Gentoo has not yet switched over to 2.6 for the standad
>install.
>
>I'm not trying to discourage you, and I did indeed install a 2.6
>kernel at my initial install, but you need to be prepared to recover
>from potential unusual problems if you take that approach.
>
>  
>
>>And is it necessary to have nptl install for 2.6 kernel ??? I think yea,
>>but I want to be shure.
>>
>>    
>>
>
>Unless you are running highly thread-intensive applications (java,
>maybe), you probably won't notice much difference with or without
>nptl. You can run 2.6 with or without nptl, but it is necessary to be
>running a 2.6 kernel to enable nptl. If you are intending to do that
>from the initial install, you need to select the smp kernel when
>booting from the LiveCD, since the default kernel on the LiveCD is
>still 2.4.
>  
>
also this is changed. Booting kerne is gentoo-dev-sources (2.6.9 seems 
to remember)

>After you are up and running, do this:
>
>1. emerge a 2.6 kernel source, build a kernel, and boot from that kernel.
>2. emerge -C linux24-headers
>3. emerge linux26-headers
>4. set USE="nptl" or USE="nptlonly"
>  
>
set both ??? I remember problems compiling mysql applying only USE="nptl"

>5. emerge glibc
>6. you may need to emerge a few additional packages if anything stops working.
>
>Good luck and welcome to gentoo. If you don't understand any of this,
>try searching the forum entries, then ask more questions.
>
>  
>
welcome from me too

--
gentoo-user@gentoo.org mailing list


  reply	other threads:[~2004-12-06 21:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 17:09 [gentoo-user] which kernel ??? 2.4 or 2.6 pat
2004-12-06 17:22 ` Jerry McBride
2004-12-06 17:25 ` Mike Williams
2004-12-06 17:55   ` Jerry McBride
2004-12-06 20:52     ` Niklas Herder
2004-12-06 20:51   ` Uwe Thiem
2004-12-06 17:30 ` Collins Richey
2004-12-06 21:46   ` Bastian Balthazar Bux [this message]
2004-12-06 17:39 ` [gentoo-user] " James

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=41B4D31D.1060009@pnpitalia.it \
    --to=bastianbalthazarbux@pnpitalia.it \
    --cc=gentoo-user@lists.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