public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new genkernel problem
Date: Sat, 6 Jun 2020 23:11:03 +0100	[thread overview]
Message-ID: <20200606231103.4f7e7c48@digimed.co.uk> (raw)
In-Reply-To: <cf51c704-f0a5-0731-d3f7-790460f5a7c3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]

On Sat, 6 Jun 2020 11:34:28 -0500, Dale wrote:

> >> From what I've read, I like my way better.  I did have to change the
> >> names from bzimage* to kernel* but other than that, I can use the
> >> naming method I've used for years and keep the good kernels I want.  
> > make install names the kernels vmlinuz-$VERSION, and updates a
> > symlink to vmlinuz if one exists.  
> 
> But sometimes I have more than one of the same version.  I add a -1, -2,
> -3 etc to them as I go.  From my understanding, make install doesn't do
> that.  I do and with good reason. It seems make install won't accomplish
> what I do by hand.

There's a kernel option that does that automatically, LOCALVERSION I
think, but it's years since I've needed to touch it.

> >> My biggest problem, getting the dracut command options right.  If I
> >> didn't need dracut, I'd be in heaven.   

> > If you have a plain setup, dracut shouldn't need any options.

> I don't have a plain setup tho nor do I really want that setup.

You don't boot from an encrypted drive (yet) or use unusual hardware,
that's what I meant by a plain system. Dracut handles booting from a a
btrfs root on a LUKS encrypted block device here with no fancy
configuration. It really is impressive the way it figures so much out for
itself.

> I like
> having backup kernels and my own numbering system.  It has worked for me
> for decades, ever since I started using Gentoo and building my own
> kernels.  I don't see any point in changing what works unless I can
> streamline what I'm already getting with the results I expect.  If I
> could get rid of the init thingy, I would have zero issues with my
> method.  It's dracut that causes the issues. We all know how much I
> dislike init thingys tho.  ;-)  That said, dracut hasn't failed me in a
> while.  If it can't build correctly, it does spit out it failed.  It's
> been a while since the init thingy it creates has failed as well.  So,
> at least there is that. 

I use a shell script to compile and install the kernel, build the
initramfs and then update the bootloader. It means the process is always
executed consistently and I only have to remember one command :)


-- 
Neil Bothwick

WinErr 002: No Error - Yet

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-06-06 22:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 19:01 [gentoo-user] new genkernel problem Jack
2020-06-05 20:24 ` Andrew Udvare
2020-06-05 20:48   ` Jack
2020-06-05 22:46     ` Neil Bothwick
2020-06-05 20:57   ` Dale
2020-06-05 22:51     ` Neil Bothwick
2020-06-06 15:13       ` Dale
2020-06-06 16:13         ` Neil Bothwick
2020-06-06 16:34           ` Dale
2020-06-06 17:20             ` Jack
2020-06-06 22:11             ` Neil Bothwick [this message]
2020-06-06 22:34               ` Dale
2020-06-06 23:55                 ` Jack
2020-06-11 14:18               ` antlists
2020-06-11 17:04                 ` madscientistatlarge
2020-06-11 22:08                 ` madscientistatlarge
2020-06-12 17:19               ` antlists

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=20200606231103.4f7e7c48@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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