ROOTFS installation guide has issues #899
Description
Activity
Agreed, right after "Unpack the tarball into the newly configured filesystems:" seems like the appropriate time to provide instructions to chroot to the newly untarred environemt. Since xchroot is not available, likely instructions on how to bind mount /dev, /proc and /sys may be needed too.
Glad to see this issue being raised. I've installed void before using the "live" w/wo the installer, but this was my first time using the ROOTFS tarball method. From an arch linux host. The instructions as given simply cannot be followed. In my case, fortunately, the AUR had a static binary xbps which I installed on arch and was then able to execute the update commands specified in the guide. I used arch's genfstab instead of xgenfstab (though it's overkill to use just to create an fstab fw/ a couple of simple entries). I then followed void's manual chroot instructions since xchroot wasn't available. I too suggest that immediately after the unpacking of the tarball instruction, there should be instructions to chroot and/or that link to the manual chroot instructions. Really just needs a bit of reorganizing. An earlier chroot for the ROOTFS method, and then change the "common section" to start from further along, where the hostname part begins.
Yes, if you come from Arch, it is simpler. You can not only use genfstab, but also arch-chroot. Meanwhile I have had a look at the static xbps and seen it indeed misses the xtools package. Perhaps, the most universal fix for the issues may be, if the provided static xbps included these scripts. Without them, a part of the first method
The XBPS method requires .., or any Linux installation running a statically linked XBPS.
does not work either. Including xtools in the static package and referencing it for both methods should (theoretically) fix it for users not starting the install from Void. The alternative would be linking in the chroot instructions along what was described above accordingly.
Why bother with xgenfstab for the ROOTFS install method. At most, why not just put a little example code block on how to create the fstab for the 2 partitions in the example? The same way that there are already instructions on formatting and mounting the partitions correctly. This is in the ADVANCED installation guide section. The order should be simple: download the tarball, unpack the tarball, chroot, update, create fstab, configure, reboot.
@svg1234 It's the beginning of the advanced guide and it's great the static xbps is provided, just a matter of bridging it into the guide. Users of the guide will have all sorts of objectives, but not know the inner workings of the distro well enough to implement them right before the first boot. In my case, for example, it was a laptop (needing encryption) with an externally managed /boot (kernel updates are signed outside void). I chose a pragmatic way of installing with the TUI installer and a separate /boot partition. Before chrooting again into the finished installation, I manually ran cryptsetup reencrypt --encrypt on the just installed root void, mounted the outcome and the separate /boot to rerun xbps-reconfigure -fa in the chroot, then took the resulting initramfs/kernel to sign for the laptop's default /boot. Hackish, works(TM).
But this issue is just to state that the options of the advanced guide don't work as intended. I believe it is easier and more universal to fix them than to abolish the guide.
Hi,
I searched but did only find mentions of the ROOTFS method in your scoping issue #85.
Following through this ROOTFS method described in https://github.com/void-linux/void-docs/blob/master/src/installation/guides/chroot.md has caveats:
If this intent is to be kept, it misses guidance how to acquire theVoid package manager and installation tools.
It mentions being able to enter a chroot as pre-requisite, but never instructs the user when to do so. The user will encounter the issue first, when instructed to use xbps-install, which is no requisite for this method, at https://github.com/void-linux/void-docs/blob/master/src/installation/guides/chroot.md#the-rootfs-method.
Yes, one can chroot /mnt and manually fix its resolv.conf at that point, but then the xbps-install commands given (with -r /mnt) are nonsensical to me.
It continues at the point where both methods are supposed to be identical. The host still has no xgenfstab/xchroot to follow through with this guide.
Maybe the pre-requisites for this guide miss the same static xbps as the first (xbps) method?