From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Kernel upgrading and linux symlink
Date: Sat, 31 Oct 2009 13:09:37 -0500 [thread overview]
Message-ID: <877hubcu5a.fsf@newsguy.com> (raw)
In-Reply-To: hchtvu$1et$1@ger.gmane.org
Nikos Chantziaras <realnc@arcor.de> writes:
> The link is created only if you have the "symlink" USE flag enabled.
>
> Also, "Gentoo requires that the [...] symbolic link points to the
> sources of the kernel you are running" is not entirely correct. It is
> required only when you want to build something against that
> kernel.
> . . . . Obviously, you need to create the symlink if you want to build
> the newly installed kernel, even though the system is still running an
> older one.
Why is that obvious? That's what seemed confusing to me.
Nothing about creating it with USE=symlin, eselect, or by hand is a
problem. Or hard to follow, and I've always just done it by hand.
next prev parent reply other threads:[~2009-10-31 18:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 16:52 [gentoo-user] Kernel upgrading and linux symlink Harry Putnam
2009-10-31 18:00 ` [gentoo-user] " Nikos Chantziaras
2009-10-31 18:09 ` Harry Putnam [this message]
2009-10-31 18:41 ` Nikos Chantziaras
2009-10-31 19:18 ` Alan McKinnon
2009-10-31 20:03 ` Nikos Chantziaras
2009-10-31 21:07 ` Alan McKinnon
2009-10-31 21:27 ` Nikos Chantziaras
2009-10-31 21:43 ` Mark Knecht
2009-10-31 22:17 ` Alan McKinnon
2009-10-31 20:06 ` Harry Putnam
2009-10-31 21:03 ` Alan McKinnon
2009-11-01 7:00 ` Dirk Heinrichs
2009-10-31 20:50 ` Neil Bothwick
2009-10-31 18:24 ` [gentoo-user] " Denis
2009-10-31 21:26 ` Dale
2009-10-31 22:20 ` Alan McKinnon
2009-10-31 22:52 ` Dale
2009-10-31 22:58 ` Alan McKinnon
2009-10-31 23:25 ` Neil Bothwick
2009-10-31 23:29 ` Mark Knecht
2009-10-31 23:40 ` [gentoo-user] " walt
2009-10-31 23:43 ` Mark Knecht
2009-10-31 23:41 ` [gentoo-user] " Alan McKinnon
2009-10-31 23:50 ` Mark Knecht
2009-10-31 23:43 ` Mike Edenfield
2009-11-01 6:55 ` Dirk Heinrichs
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=877hubcu5a.fsf@newsguy.com \
--to=reader@newsguy.com \
--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