From: Jipok <Jipok@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "linux6.5: configured successfully" without initramfs
Date: Sat, 16 Sep 2023 19:09:44 +0200 [thread overview]
Message-ID: <20230916170944.pCZVce6h1ZoU8UZUjuP7mqXSpxQip-JoIVqBM2Ah81o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46006@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
New comment by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/46006#issuecomment-1722272981
Comment:
> Recovery is easy: reboot and select the last-booted kernel, then fix the problem from there.
For laptop or pc. Not so easy for server.
> You were bitten by a ZFS incompatibility with your kernel, but users are expected to understand fundamental aspects of the packages they use, like what kernels are supported with ZFS.
Well, I’ve had zfs for 4 or 5 years now. But the problem with the update only appeared now. Perhaps earlier I successfully updated with a delay.
> Changing grub doesn't work either since some users might boot a kernel without an initramfs.
Are you sure that there really are such users? If their number does not exceed 5, why not leave a flag/option for them to allow updating with a missing initramfs, and for all others by default throw an error with the appropriate description (including the necessary flag to update the grub anyway)
next prev parent reply other threads:[~2023-09-16 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 17:18 [ISSUE] " Jipok
2023-09-10 18:47 ` dkwo
2023-09-10 19:04 ` classabbyamp
2023-09-10 22:07 ` Jipok
2023-09-16 15:19 ` [ISSUE] [CLOSED] " ahesford
2023-09-16 15:19 ` ahesford
2023-09-16 16:13 ` Jipok
2023-09-16 16:21 ` ahesford
2023-09-16 16:48 ` Jipok
2023-09-16 16:56 ` classabbyamp
2023-09-16 16:56 ` ahesford
2023-09-16 17:01 ` Duncaen
2023-09-16 17:09 ` Jipok [this message]
2023-09-16 17:15 ` ahesford
2023-09-16 18:11 ` Duncaen
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=20230916170944.pCZVce6h1ZoU8UZUjuP7mqXSpxQip-JoIVqBM2Ah81o@z \
--to=jipok@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).