From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kerninst (was Optional /usr merge in Gentoo)
Date: Wed, 2 Oct 2013 11:02:52 -0500 [thread overview]
Message-ID: <CADPrc82Vhtuq=K0O_djpO-OJo=eg8irig=YJ3ncyv3nUpMD2OA@mail.gmail.com> (raw)
In-Reply-To: <524C0820.9030501@xunil.at>
On Wed, Oct 2, 2013 at 6:48 AM, Stefan G. Weichinger <lists@xunil.at> wrote:
> Am 01.09.2013 19:30, schrieb Canek Peláez Valdés:
>> I am following vanilla-sources in all my machines, which is what
>> people like Greg Kroah-Hartman actually recommends [1][2]. Since they
>> are now never stabilized [3], this means that I need to update them
>> pretty regularly to keep them safe.
>>
>> This implies that I have to change the /usr/src/linux symbolic link,
>> configure the kernel using make oldconfig, compile it, install it,
>> install its modules, reemerge any package that provides kernel modules
>> (if any), regenerate its initramfs, regenerate the GRUB2 config file
>> OR adding a new entry in GRUB.
>>
>> None of this steps are particularly difficult, but any mistake in one
>> of them can result in an unbootable system. So I wrote a little script
>> that takes care of each of this steps automagically:
>>
>> https://github.com/canek-pelaez/kerninst
>>
>> So now everytime I need to use a new kernel version, I only do:
>>
>> # eselect kernel set <new-kernel>
>> # kerninst
>>
>> Everything is done by the script.
>
>
> Canek, how to handle changing configs?
>
> AFAI understand I do:
>
> eselect kernel set x
> cd /usr/src/linux
> make menuconfig
> (SAVE .config)
> cp .config /etc/kerninst/kernel-config
> kerninst
>
> ... right?
>
> I am currently struggling with a kernel not showing /dev/kvm ... and
> toggling kvm_amd on/module ... etc
Yeah, that's the way to do it. However, kerninst is not for testing
different configurations of kernels. I suppose you could use it that
way, but I wrote exactly for the opposite case: when you finally have
your configuration nailed down, and just want to automatize the
installation of the kernel.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-10-02 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 17:30 [gentoo-user] kerninst (was Optional /usr merge in Gentoo) Canek Peláez Valdés
2013-09-01 18:01 ` Stefan G. Weichinger
2013-09-01 18:16 ` Canek Peláez Valdés
2013-09-01 18:29 ` Stefan G. Weichinger
2013-09-03 15:01 ` Douglas J Hunley
2013-09-03 16:19 ` Canek Peláez Valdés
2013-09-03 16:34 ` Douglas J Hunley
2013-09-03 18:38 ` Stefan G. Weichinger
2013-09-03 18:40 ` Canek Peláez Valdés
2013-10-02 11:48 ` Stefan G. Weichinger
2013-10-02 16:02 ` Canek Peláez Valdés [this message]
2013-10-09 15:14 ` Stefan G. Weichinger
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='CADPrc82Vhtuq=K0O_djpO-OJo=eg8irig=YJ3ncyv3nUpMD2OA@mail.gmail.com' \
--to=caneko@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