From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] alternative kernels
Date: Sun, 26 Oct 2014 22:42:41 +0200 [thread overview]
Message-ID: <544D5CC1.3010708@gmail.com> (raw)
In-Reply-To: <CAJ1xhMUSiaN8mP=AKjLpCqxOEdidUTxt1ToXaOz4y0qLTdgsiQ@mail.gmail.com>
On 26/10/2014 22:21, Alexander Kapshuk wrote:
> On Sun, Oct 26, 2014 at 10:16 PM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>> On Sun, Oct 26, 2014 at 1:56 PM, Alec Ten Harmsel
>> <alec@alectenharmsel.com> wrote:
>>>
>>> On 10/26/2014 03:47 PM, Volker Armin Hemmann wrote:
>>>> Am 26.10.2014 um 20:09 schrieb Alexander Kapshuk:
>>>>> I've been using gentoo-sources for a while now.
>>>>>
>>>>> I remember reading on this list about some users using alternative
>>>>> kernels on their gentoo systems. My understanding is that amongst some
>>>>> of the other alternatives, besides the genkernel, which I'm not
>>>>> interested in using, are vanilla-sources available in the portage
>>>>> tree, and the sources available on kernel.org.
>>>>> I'd appreciate being given some pointers on how the folk here maintain
>>>>> their alternative kernels.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> .
>>>>>
>>>> I let portage update the vanilla-sources and once in a while a build and
>>>> install a new kernel. At the moment I am on 3.12.23. Maybe I install
>>>> 3.12.30 tonight. If I find a good reason to do so.
>>>>
>>> What happens when you run `emerge --depclean`?
>>>
>>> I always un-keyword the exact version of vanilla-sources that I'm
>>> running since I update and depclean on a weekly basis. I'm not a huge
>>> fan of having a bunch of kernels under /usr/src/linux-* but only having
>>> a couple of them compiled, but to each his own I guess.
>>
>> I have sys-kernel/vanilla-sources in package.keywords, unversioned. So
>> depclean cleans away the older versions, and I keep the latest one.
>>
>> I'm on 3.17.1 right now, but the moment 3.17.2 comes out I will switch
>> to it in all my machines: with kerninst is all of it mostly
>> automatized.
>>
>> And with systemd, rebooting to a new kernel takes just a few seconds ;)
>>
>> Regards.
>> --
>> Canek Peláez Valdés
>> Profesor de asignatura, Facultad de Ciencias
>> Universidad Nacional Autónoma de México
>>
>
> Do you know if vanilla-sources plays well with openrc, as that is what I use?
> Thanks.
Yes it does. There's no logical reason to think it doesn't.
You do have to set some kernel options, but that is true for just about
everything in the kernel - you won't have support for hardware X unless
you enable hardware X in the kernel config :-)
One of the additions with gentoo-sources is the very first menu item,
all it does is enable a bunch of stuff that supported init systems
(openrc and systemd) use - it's purely a convenience measure and doesn't
change the kernel itself per se. systemd for example will need cgroups
enabled, openrc needs udev-mount. It's all in the ebuild, and portage
throws an error is something required is not set in .config.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-10-26 20:42 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 19:09 [gentoo-user] alternative kernels Alexander Kapshuk
2014-10-26 19:23 ` Canek Peláez Valdés
2014-10-26 19:40 ` Alexander Kapshuk
2014-10-26 20:20 ` Rich Freeman
2014-10-26 20:45 ` Canek Peláez Valdés
2014-10-26 20:33 ` Giuseppe Pappalardo
2014-10-26 19:41 ` Canek Peláez Valdés
2014-10-26 19:43 ` Canek Peláez Valdés
2014-10-26 20:56 ` Giuseppe Pappalardo
2014-10-26 19:47 ` Volker Armin Hemmann
2014-10-26 19:52 ` Alexander Kapshuk
2014-10-26 19:56 ` Alec Ten Harmsel
2014-10-26 20:16 ` Canek Peláez Valdés
2014-10-26 20:21 ` Alexander Kapshuk
2014-10-26 20:42 ` Alan McKinnon [this message]
2014-10-26 20:48 ` Alexander Kapshuk
2014-10-26 20:46 ` Canek Peláez Valdés
2014-10-26 20:49 ` Alexander Kapshuk
2014-10-26 21:01 ` Volker Armin Hemmann
2014-10-26 21:16 ` Canek Peláez Valdés
2014-10-26 23:18 ` Volker Armin Hemmann
2014-10-26 23:41 ` Canek Peláez Valdés
2014-10-27 1:12 ` wabenbau
2014-10-27 1:35 ` Alec Ten Harmsel
2014-10-27 1:54 ` wabenbau
2014-10-29 19:08 ` Matti Nykyri
2014-10-26 21:34 ` Rich Freeman
2014-10-26 21:10 ` Alec Ten Harmsel
2014-10-26 21:23 ` Canek Peláez Valdés
2014-10-26 21:48 ` Alan McKinnon
2014-10-26 23:25 ` Volker Armin Hemmann
2014-10-30 7:56 ` J. Roeleveld
2014-10-30 10:31 ` Rich Freeman
2014-10-31 6:30 ` J. Roeleveld
2014-10-31 6:37 ` Canek Peláez Valdés
2014-10-31 7:11 ` J. Roeleveld
2014-10-31 8:22 ` Canek Peláez Valdés
2014-10-31 9:42 ` Gregory Woodbury
2014-10-31 11:05 ` Tanstaafl
2014-10-31 14:09 ` J. Roeleveld
2014-10-31 16:16 ` Peter Humphrey
2014-10-31 17:24 ` Volker Armin Hemmann
2014-10-31 17:53 ` Rich Freeman
2014-10-31 20:26 ` Neil Bothwick
2014-11-01 11:19 ` Peter Humphrey
2014-11-01 15:38 ` Neil Bothwick
2014-11-01 17:19 ` Peter Humphrey
2014-11-01 22:28 ` Neil Bothwick
2014-11-02 13:14 ` Volker Armin Hemmann
2014-11-02 15:28 ` Neil Bothwick
2014-11-03 2:09 ` Tom H
2014-11-03 8:36 ` Neil Bothwick
2014-11-02 23:05 ` Tom H
2014-11-03 0:46 ` Peter Humphrey
2014-11-03 2:26 ` Tom H
2014-10-31 22:09 ` Tom H
2014-10-31 22:30 ` Rich Freeman
2014-11-01 1:03 ` Alec Ten Harmsel
2014-11-01 9:47 ` Rich Freeman
2014-11-01 15:50 ` Alec Ten Harmsel
2014-11-03 1:54 ` Tom H
2014-11-03 1:40 ` Tom H
2014-11-03 0:22 ` Tom H
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=544D5CC1.3010708@gmail.com \
--to=alan.mckinnon@gmail.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