persisting issue in picking up the noatime while chrooted

2 files changed, 17 insertions, 4 deletions

diff --git a/README.md b/README.md
index cf8876d..8fb9751 100644
--- a/README.md
+++ b/README.md
@@ -28,6 +28,18 @@ You end up with a fully functional Void Linux installation. This of course is
 pretty minimal in itself (at least compared with bloated Linux distributions).
 You can refer to [2] if you have no idea what to do next.
 
+## Issues
+* Somehow, you still need to run the following (replacing `X.XX` by the 
+installed version of the kernel) at the first boot for all the configuration
+to fall into place:
+
+```shell
+xbps-reconfigure -f linuxX.XX
+```
+
+Running it while chrooted doesn't seem to take into account the `noatime` in
+`fstab` for example.
+
 ## Partioning
 We use an encrypted `root`. We do not have the need for encrypted boot
 currently. The template we use on the disk is:
diff --git a/base-install.sh b/base-install.sh
index 88e1e55..8ccdde0 100755
--- a/base-install.sh
+++ b/base-install.sh
@@ -46,11 +46,12 @@ echo "/dev/mapper/$2-root / ext4 defaults,noatime 0 1" | sudo tee -a \
 echo "/dev/mapper/$2-swap none swap defaults 0 1" | sudo tee -a /mnt/etc/fstab \
 > /dev/null
 
-# Chroot and run final configuration script:
-sudo cp -f chroot-script.sh /mnt/home/chroot-script.sh
-sudo chroot /mnt /bin/bash -c "/bin/sh /home/chroot-script.sh"
-
 # Unmounting the boot partition to write the label
 sudo umount "$1"1
 sudo fatlabel "$1"1 "$4"
+sudo mount "$1"1 /mnt/boot
+
+# Chroot and run final configuration script:
+sudo cp -f chroot-script.sh /mnt/home/chroot-script.sh
+sudo chroot /mnt /bin/bash -c "/bin/sh /home/chroot-script.sh"