Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Thank you so much, where did you find this bit of information? I have been trying to solve this problem for the past week or so, but my google foo failed me on this one. Was about to give up on this one.
I learned it accidentally trying to get root on an encrypted dataset working with systemd init without sd-zfs. This turns out to be how the
zfs
utility works internally to signal the driver "hey it's okay, I'm a ZFS utility the user isn't using mount directly", and how you deal with mounting your root dataset to the temporary/sysroot
while having its mountpoint set to/
while in initramfs before pivoting root.Obviously, don't use that other than recovering your data, if you want to use this array you should figure out the mountpoints properly so ZFS does it automatically. It shouldn't break anything but it's gross, either set
mointpoint=legacy
and use fstab or set its mountpoint in ZFS and usezfs mount
.