From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] dracut vs mkinitcpio
Date: Thu, 13 May 2021 14:42:08 +0200 [thread overview]
Message-ID: <20210513124208.BYEHaob87L0cZ2nKEBZq7LinCB0i3kjn6Phtcles50A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30813@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/30813#issuecomment-840527763
Comment:
Nothing, other than changing the dependency of `base-system`. They both just hook into the `/etc/kernel.d` hooking system.
Not sure if there is a nice way to do this change, if we don't add `replaces=dracut>=someversion`, then users will have two initramfs for each kernel until they remove orphaned packages.
If we just replace dracut then users who actually configured dracut to work with their system, but not mkinitcpio then we are going to somewhat break their system or cause an inconvenience.
next prev parent reply other threads:[~2021-05-13 12:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 8:59 [ISSUE] " dkwo
2021-05-12 11:47 ` ericonr
2021-05-12 12:23 ` dkwo
2021-05-12 12:23 ` dkwo
2021-05-12 12:23 ` dkwo
2021-05-12 13:06 ` ahesford
2021-05-13 11:35 ` dkwo
2021-05-13 11:36 ` dkwo
2021-05-13 12:38 ` Duncaen
2021-05-13 12:42 ` Duncaen [this message]
2021-05-17 13:49 ` travankor
2021-05-17 13:50 ` travankor
2021-05-17 16:04 ` dkwo
2021-05-18 8:07 ` travankor
2021-05-24 2:38 ` furryfixer
2021-06-30 8:32 ` [RFC] dracut vs mkinitcpio vs booster dkwo
2021-06-30 10:00 ` q66
2021-07-01 7:59 ` dkwo
2021-07-01 9:17 ` Johnnynator
2021-07-01 11:10 ` q66
2021-07-01 11:20 ` q66
2021-07-01 11:30 ` ahesford
2021-07-01 11:59 ` dkwo
2021-07-16 20:31 ` [ISSUE] [CLOSED] [RFC] initramfs dkwo
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=20210513124208.BYEHaob87L0cZ2nKEBZq7LinCB0i3kjn6Phtcles50A@z \
--to=duncaen@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).