Same question was posted on reddit here:
https://www.reddit.com/r/bedrocklinu..._on_voidlinux/
where I happened to see it first. Repeating the answer in case someone else comes across this thread:
I
think the initrd is a red herring. On traditional distros, the initrd eventually hands off control to the init system which is responsible for things like mounting /etc/fstab. With Bedrock, the init selection menu is thrown between the two steps, but the initrd still isn't expected to mount /etc/fstab.
There's a (poorly documented - I really should fix that) known issue with the how the current release handles /etc/fstab, and that is my guess for your issue. When setting up, Bedrock makes some directories such as /home into a mount point. When the init system goes to mount /etc/fstab, it'll see there's pre-existing mounts at some of the expected locations (like /home) and instead of mounting over those (which is what Bedrock wants) it just skips them.
There's a couple work-arounds:
- One relatively simple one is to use /bedrock/etc/fstab - Bedrock mounts that before /home is otherwise messed with, and so it shouldn't skip such directories. This is mounted by Bedrock's busybox and might not work for some more advanced features.
- Another is to mount it with the mount command, e.g. mount /dev/sda2 /home. You could probably put such lines in /etc/rc.local. If done that way, it'll mount over the mount point instead of skipping it, which is what is desired here.
If you give those a try and they don't work let me know and we can debug further.
I've got various ideas to fix this properly so /etc/fstab just works like people expect, but they probably won't be in place until the upcoming release.
