From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
Date: Tue, 16 Apr 2024 12:15:57 +0100 [thread overview]
Message-ID: <7653903.EvYhyI6sBW@rogueboard> (raw)
In-Reply-To: <704c7656-9700-297c-7f2d-4c67d4eda6c8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
On Tuesday, 16 April 2024 11:55:20 BST Dale wrote:
> If you update often, it shouldn't take long answer the questions. If
> you do like me and don't update often, it may take longer but no more
> time than it would if you updated often and added all the time
> together. As far as I know, if one manually updates their kernel, make
> oldconfig is the safest and recommended method. You are prompted for
> new drivers/options and can see if they apply to you or not. If you
> don't want to update that way, I think there is a kernel that does it's
> own thing. I think it is sort of like boot media uses. If the time
> needed to answer all the questions isn't there, that may be a option to
> look into. It's called genkernel. I've never used it but read it works.
The sys-kernel/genkernel package will automatically build & install your
kernel and initramfs in /boot, but it will NOT prepare a kernel configuration
tuned to your hardware and desired options. It uses a generic default
configuration safe for most circumstances. The user can tweak the default
configuration to suit their needs and genkernel will use that.
For quick(er) and automated kernel update and installation there are the
gentoo *distribution kernels*:
https://wiki.gentoo.org/wiki/Project:Distribution_Kernel
> In short, make oldconfig is the recommended way as far as I know. In my
> opinion, it is the safest way to know what you are going to get. Links
> for more info.
>
> https://wiki.gentoo.org/wiki/Kernel/Upgrade
>
> https://wiki.gentoo.org/wiki/Kernel/Configuration
>
> Someone else may have a different opinion, even a better one. This is
> how I always do it and kernel failure is rare. Hope it helps.
>
> Dale
>
> :-) :-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-16 11:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:46 [gentoo-user] Slightly corrupted file systems when resuming from hibernation Dr Rainer Woitok
2024-04-14 18:41 ` [gentoo-user] " Dr Rainer Woitok
2024-04-15 11:48 ` Michael
2024-04-16 9:04 ` Dr Rainer Woitok
2024-04-16 10:15 ` Michael
2024-04-16 13:29 ` Dr Rainer Woitok
2024-04-16 13:53 ` Arve Barsnes
2024-04-16 14:53 ` Grant Edwards
2024-04-16 15:07 ` Dale
2024-04-16 15:01 ` Dale
2024-04-16 15:14 ` Grant Edwards
2024-04-16 16:43 ` Dr Rainer Woitok
2024-04-16 19:26 ` Grant Edwards
2024-04-17 9:10 ` Michael
2024-04-17 13:52 ` Grant Edwards
2024-04-17 20:05 ` Dale
2024-04-17 20:32 ` Grant Edwards
2024-04-17 22:18 ` Dale
2024-04-17 15:50 ` Dr Rainer Woitok
2024-04-17 17:52 ` Wols Lists
2024-04-17 10:37 ` Dr Rainer Woitok
2024-04-17 10:56 ` Michael
2024-04-17 14:11 ` Grant Edwards
2024-04-17 16:11 ` Dr Rainer Woitok
2024-04-17 17:53 ` Grant Edwards
2024-04-16 10:55 ` Dale
2024-04-16 11:15 ` Michael [this message]
2024-04-16 12:48 ` Dale
2024-04-16 14:32 ` Jack
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=7653903.EvYhyI6sBW@rogueboard \
--to=confabulate@kintzios.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