dalto8
dalto8
> There is definitely an explicit read-only mount somewhere. Which raises the question, what is mounting it ro? I just looked at both the bootloader and fstab and there is...
If you are using the EndeavourOS automation, it is using the `hostonly` option for the normal initrd.
@armujahid did you choose systemd-boot or grub in the installer? systemd-boot is the default.
In that case the script is located at `/usr/share/libalpm/scripts/dracut-install`. Alternatively, you can view it in [github](https://github.com/endeavouros-team/PKGBUILDS/blob/master/eos-dracut/dracut-install).
> assuming `dracut-rebuild` will set `hostonly`. It will. Or, more accurately, it builds 2 initrds. The primary with `hostonly` and a fallback without.
Release cadence is a difficult balance. Making the release windows longer will help some distros as it will lower the amount of testing that will be done for each release....
It wouldn't be typical to explicitly mount all the subvolumes `rw` in `/etc/fstab`. I don't think many(any?) distros are doing that.
The use case is you take a snapshot. The snapshot is read-only by design because we never want it to change. You make a change that breaks the system and...
That seems *too* generic to me. What if someone wants their rootfs ro for some other purpose? Also, if we don't handle the remount, it would break our use case.