From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] mkinitcpio: update to 30, add mkinitcpio-zfs subpackage
Date: Mon, 17 May 2021 05:47:27 +0200 [thread overview]
Message-ID: <20210517034727.iqgAxDz-wWopZMf5xbOSnfWeaEQ94F9vObUN85iodYM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30930@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/30930#issuecomment-841962709
Comment:
OK, this now boots my ZFS setup and should be ready to merge.
New changes:
1. ZFS hook recognize `root=zfs:` Dracut syntax.
2. ZFS hook imports pools `rw` by default.
3. Package tests work.
4. Kernel hook sets `umask 0077` because some setups (like that recommended by ZFSBootMenu) may place in the initramfs image secrets that should not be accessible to non-root users.
5. `mkinitcpio-udev` has been dropped and merged with `mkinitcpio`. As upstream strongly advises against disabling the `udev` hook, there is no reason to separate this hook into a standalone package.
next prev parent reply other threads:[~2021-05-17 3:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 12:42 [PR PATCH] " ahesford
2021-05-16 15:31 ` ericonr
2021-05-16 18:30 ` ahesford
2021-05-16 18:30 ` ahesford
2021-05-17 3:39 ` [PR PATCH] [Updated] " ahesford
2021-05-17 3:47 ` ahesford [this message]
2021-05-17 13:55 ` [PR PATCH] [Updated] " ahesford
2021-05-17 13:56 ` ahesford
2021-05-17 13:58 ` thypon
2021-05-17 14:02 ` ahesford
2021-05-17 14:04 ` thypon
2021-05-17 14:09 ` ahesford
2021-05-17 14:16 ` thypon
2021-05-17 15:25 ` ahesford
2021-05-17 16:02 ` thypon
2021-05-17 16:02 ` [PR PATCH] [Merged]: " thypon
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=20210517034727.iqgAxDz-wWopZMf5xbOSnfWeaEQ94F9vObUN85iodYM@z \
--to=ahesford@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).