From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: linux-headers-2.6.38
Date: Wed, 10 Aug 2011 20:36:10 +0700 [thread overview]
Message-ID: <CAA2qdGW2Z7C77s1JQ=JkGOXrixr=2NfzSv2q=zwT97dRYbKwyA@mail.gmail.com> (raw)
In-Reply-To: <86aabhh12r.fsf@jane.chrekh.se>
On Wed, Aug 10, 2011 at 20:02, <che@chrekh.se> wrote:
> Pandu Poluan <pandu@poluan.info> writes:
>
>> While I'm about to do an `emerge -e @world` ...
>>
>> Should I `emerge -av "=sys-kernel/linux-headers-2.6.38" ` ?
>>
>> Any benefits over the current "sys-kernel/linux-headers-2.6.36.1" ?
>
> There is at least a theoretical benifit if you set NPTL_KERN_VER=2.6.38
> in make.conf and recompile glibc. That way glibc could use things not
> present in older kernels.
>
> I haven't researched if there are any such things, perhaps someone else
> knows.
>
Hmmm... without a reference, I'd rather not do something too drastic...
> Also, beware. If you recompile glibc withe NPTL_KERN_VER set, you can't
> boot with older kernels anymore.
>
Can you explain what did you mean with "older kernels"? Kernels older
than a certain version, or a previously-compiled kernel on my system?
Anyways, this is a fresh install, so I don't think I'll have any trouble.
But will still appreciate a reference and/or explanation re:
NPTL_KERN_VER, though.
Rgds
--
FdS Pandu E Poluan
~ IT Optimizer ~
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
next prev parent reply other threads:[~2011-08-10 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 9:00 [gentoo-user] linux-headers-2.6.38 Pandu Poluan
2011-08-10 13:02 ` [gentoo-user] linux-headers-2.6.38 che
2011-08-10 13:36 ` Pandu Poluan [this message]
2011-08-10 13:58 ` che
2011-08-11 0:50 ` Nikos Chantziaras
2011-08-11 7:37 ` Pandu Poluan
2011-08-11 8:07 ` che
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='CAA2qdGW2Z7C77s1JQ=JkGOXrixr=2NfzSv2q=zwT97dRYbKwyA@mail.gmail.com' \
--to=pandu@poluan.info \
--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