Quote:
Originally Posted by frankbell
Did you have your Void Linux /home on a separate partition?
If not, it like was overwritten during the install process.
This article will tell you more. |
Whether /home was on a separate partition is likely relevant here, but it wouldn't be wiped either way; Bedrock should avoid wiping `/home` when hijacking a install. That fact is an important aspect of its unusual install process.
Quote:
Originally Posted by mubharad
I had void linux initially which i hijacked for bedrock install. Everything went through fine and was booted into bedrock however the original void linux home directories and files are no longer available/visible. I tried searching in documentation and internet to see if it is moved to another location or need to be remounted but haven't had any luck yet. Can anyone advise what i should be doing?
|
Like frankbell, I'm curious if your /home is on a separate partition. If so, /etc/fstab likely contains information on how to mount /home. Can you provide that?
Some background: Typically the init system mounts /etc/fstab when booting. Most /etc/fstab-mounting software skips mounting anything that already has a mount point, as it assumes if there's already a mount point the given item is already mounted. This is reasonable assumption for most situations, but not on Bedrock. Bedrock actually wants some locations to have multiple point points on them, and it will create special mount points in places like /home _expecting_ it to be mounted over. However, these mount points confuse /etc/fstab mounting software. Bedrock typically solves this by mounting /etc/fstab itself, before kicking off the init. However, its system to do this is much less sophisticated than that used by most init systems.
My guess on the issue: Maybe your /home mount point is doing something fancy Bedrock's /etc/fstab mounting logic can't handle, then when the init comes around it skips mounting /home because it already sees the special Bedrock mount point there.
If that's the issue, you can probably work around it by placing a mount command in /etc/rc.local which mounts your /home partition.
In the long term I hope to have the Bedrock use the selected init's /etc/fstab mounting logic instead of its own, but I haven't quite gotten there yet.
Quote:
Originally Posted by mubharad
Also i have been trying other distros in live session and running bedrock hijack to see if they support. I did not get any error and got the msg to reboot into new bedrock install, does this mean if i install those distros and retry hijack, everything will work fine or there is no guarantee?
|
That's not a guarantee. My bet is you didn't get any errors running the hijack script on Void either, right? It's only after you rebooted into it to try it that this particular issue arose. The issue here isn't with the hijacked distro: Void Linux gets of love from the Bedrock community. It's likely just a quirk of your specific filesystem/mount/lvm/raid setup.
A better test would be to install Bedrock in a VM or on a spare/test machine - actually install it, not just a live distro. Set it up exactly as you'd expect a potential production situation to go and exercise your expected routine with it.
If you're trying to figure out what distros Bedrock plays nicely with,
see the distro compatibility page. Note Void Linux has no distro-specific known compatibility issues, and it's used heavily in the Bedrock community.
If the above /etc/rc.local mount proposal doesn't work for you and/or you're keen on reinstalling anyways, consider giving it a try Void again but this time without putting /home on a separate partition. At least not until I get the catch-22 of using the init to mount filesystems before the init runs figured out.
Happy to help! If this isn't sufficient to get you going, we can probably work around the issue once you provide your /etc/fstab.
