You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is root on Bcachefs detection, but that is it...
To get proper support, we need to allow installs on Bcachefs as root (or any other mountpoint) with or without compression, encryption, multi-device support, and selecting which groups/disks to be foreground/background/promote/(metadata) targets.
There are two main blockers I can think of that need special exceptions: systemd when using a multi-device pool, and 32-bit apps (this is being worked on, and can be somewhat mitigated by forcing crc32c or another checksumming algorithm? Unsure how xxhash or chacha20-poly1305 change this!).
I believe NixOS has a custom way of making systemd play nice with bcachefs involving symlinks. This is all so new and confusing to get working together, despite the theoretical benefits of an abstracted drive pool with encryption, raid, ssd cache, etc. Looks like things are coming together.
The text was updated successfully, but these errors were encountered:
I believe NixOS has a custom way of making systemd play nice with bcachefs involving symlinks.
I'm not so sure about that. Enabling systemd-initrd broke booting with bcachefs root, because it can't mount for some reason.
We are testing currently our Implentation of bcachefs into our GUI Installer.
The Erase Disk/Automatic Partioning supports currently only on Root installation, we didnt check with multi device parition or equal yet. (likely this will break).
But the base implentation is working fine in our GUI Installer and will be provided with the upcoming release for UEFI Systesm (systemd-boot/refind)
Currently, there is root on Bcachefs detection, but that is it...
To get proper support, we need to allow installs on Bcachefs as root (or any other mountpoint) with or without compression, encryption, multi-device support, and selecting which groups/disks to be foreground/background/promote/(metadata) targets.
There are two main blockers I can think of that need special exceptions: systemd when using a multi-device pool, and 32-bit apps (this is being worked on, and can be somewhat mitigated by forcing crc32c or another checksumming algorithm? Unsure how xxhash or chacha20-poly1305 change this!).
I believe NixOS has a custom way of making systemd play nice with bcachefs involving symlinks. This is all so new and confusing to get working together, despite the theoretical benefits of an abstracted drive pool with encryption, raid, ssd cache, etc. Looks like things are coming together.
The text was updated successfully, but these errors were encountered: