From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] mkinitcpio: update to 30, add mkinitcpio-zfs subpackage
Date: Sun, 16 May 2021 20:30:00 +0200 [thread overview]
Message-ID: <20210516183000.eh1p31ZowCts6xgQVUeIrAxEfTZC2hreIgEnYxnYF08@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: 787 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/30930#issuecomment-841857020
Comment:
Compression is not the issue I'm having. I tried gzip and no compression (`compression=cat`) but haven't yet been able to boot with these images.
I thought about fetching the ZFS hook files rather than keeping them in tree, but I am already patching to pull in `/etc/hostid` and am giving thought to some other changes. (For now, the only definite change I'm thinking about is dropping their `zfs=pool/file/system` syntax for root specifications and moving to the dracut-style `root=zfs:pool/file/system` so that mkinitcpio and dracut images can be interchangeable. As we may evolve these further, it's probably easier just to take ownership.
next prev parent reply other threads:[~2021-05-16 18:30 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 [this message]
2021-05-16 18:30 ` ahesford
2021-05-17 3:39 ` [PR PATCH] [Updated] " ahesford
2021-05-17 3:47 ` ahesford
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=20210516183000.eh1p31ZowCts6xgQVUeIrAxEfTZC2hreIgEnYxnYF08@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).