From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: base-files: vkpurge now deletes initramfs and /lib/modules
Date: Sat, 14 Aug 2021 23:47:28 +0200 [thread overview]
Message-ID: <20210814214728.DtywLI2h9MbonU89MAXTtyk9QhslgO9RpB6rCNWN-io@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32493@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/32493#issuecomment-898961775
Comment:
`/lib` is a symlink to `/usr/lib`.
The installed initramfs tool generates the initramfs file and therefor is responsible for it and its name (they could generate `initramfs-${version}.cpio` or add a compression suffix).
This happens in the kernel.d `{pre,post}-install` hooks, it makes a lot of sense to also use the `{pre,post}-remove` hooks to remove those fails again.
dracut already deletes the file in its hook and so does mkinitcpio:
`/etc/kernel.d/post-remove/20-dracut` (https://github.com/void-linux/void-packages/blob/master/srcpkgs/dracut/files/kernel-hook-postrm).
next prev parent reply other threads:[~2021-08-14 21:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 19:32 [PR PATCH] " kingpingu
2021-08-14 19:41 ` abenson
2021-08-14 19:42 ` [PR PATCH] [Updated] " kingpingu
2021-08-14 19:48 ` kingpingu
2021-08-14 19:51 ` kingpingu
2021-08-14 19:52 ` base-files: " kingpingu
2021-08-14 20:24 ` Duncaen
2021-08-14 21:30 ` kingpingu
2021-08-14 21:40 ` Duncaen
2021-08-14 21:42 ` Duncaen
2021-08-14 21:44 ` Duncaen
2021-08-14 21:45 ` Duncaen
2021-08-14 21:47 ` Duncaen [this message]
2021-08-14 22:38 ` [PR PATCH] [Updated] " kingpingu
2021-08-14 22:39 ` kingpingu
2021-08-14 22:40 ` kingpingu
2021-08-14 22:49 ` kernel.d: preremove dkms hook now deletes /lib/modules Duncaen
2021-08-14 22:54 ` [PR PATCH] [Closed]: " kingpingu
2021-08-14 22:54 ` kingpingu
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=20210814214728.DtywLI2h9MbonU89MAXTtyk9QhslgO9RpB6rCNWN-io@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).