Package Details: mkinitcpio-sd-zfs 1.0.2-1

Git Clone URL: https://aur.archlinux.org/mkinitcpio-sd-zfs.git (read-only, click to copy)
Package Base: mkinitcpio-sd-zfs
Description: Compatibility between systemd and ZFS roots
Upstream URL: https://github.com/dasJ/sd-zfs
Licenses: MIT
Conflicts: mkinitcpio-sd-zfs-git
Submitter: muhaha
Maintainer: muhaha
Last Packager: muhaha
Votes: 0
Popularity: 0.000000
First Submitted: 2021-05-13 12:40 (UTC)
Last Updated: 2021-05-13 18:03 (UTC)

Latest Comments

kido007 commented on 2022-12-21 03:59 (UTC) (edited on 2023-05-04 16:34 (UTC) by kido007)

With the latest update, when running mkinitcpio I have:

Running build hook: [sd-zfs]

==> WARNING: Possibly missing '/bin/sh' for script: /usr/lib/udev/vdev_id

====================================

I resolved it by adding base to the following line in mkinitcpio.conf

HOOKS=(base systemd autodetect modconf sd-vconsole keyboard sd-plymouth ... sd-zfs ...)

muhaha commented on 2021-06-13 17:10 (UTC)

Hey genofire, I have made a git version of this package https://aur.archlinux.org/packages/mkinitcpio-sd-zfs-git/ there which should give you the latest version from https://github.com/dasJ/sd-zfs

genofire commented on 2021-05-14 14:01 (UTC)

i would really like to have the current version (not legacy).

Could we add an post_install output to warn users? Like in gitlab: https://github.com/archlinux/svntogit-community/blob/packages/gitlab/trunk/gitlab.install

muhaha commented on 2021-05-13 18:23 (UTC)

No worries, I felt you frustration when I was reading the code and realized that it wasn't backward compatible, thanks for reaching out

Yaro commented on 2021-05-13 18:16 (UTC)

No problem. Sorry if my tone comes off hostile. I was coming off a frustrated high at that point after spending a couple hours trying to find why my installation broke.

muhaha commented on 2021-05-13 18:08 (UTC)

Hey Yaro, thanks for the info, I thought the change was backward compatible, but after seeing your message, I took a look at the code and can see that it is a breaking change, so I have reverted it back in the hope that no-one else will have this problem

Yaro commented on 2021-05-13 16:08 (UTC)

Noticed why now. The configuration arbitrarily changed its syntax from zfs: to ZFS= which is a really nice way to break compatibility.

Yaro commented on 2021-05-13 15:55 (UTC)

The latest update (1.0.3) breaks early userspace and renders any systems with ZFS roots from booting. I had to downgrade to 1.0.2 and remake my initcpios to get my system to boot again.