Paul Neuwirth PaNe Foto Paul Neuwirth Postfach 45 04 54 80904 MüNCHEN DEUTSCHLAND Fax: +49 89 35819624 https://www.swabian.net/ UST-IdNr. (VAT): DE314867715 On Thu, 5 Mar 2020, Adam Mizerski wrote:

W dniu 05.03.2020 o 18:50, Paul Neuwirth pisze:

...

Hi,

I like that idea/concept with the transactional servers very and I am currently testing it. Especially during setting up everything, it would be a great help to remount the current mounted snapshot with write access, so you could use a package manager with UI, like yast. It leads to many reboots, to find out, there are other packages necessary, etc. The shell command of transactional-update is a big help, but in that chroot environment, many tests cannot be done (complexer software/services, kernel modules, etc etc). So is there any way to get the current system (temporarily) r/w? mount -o rw doesn't work, even the command seems to succeed, but it still says "Read-only file system" on opening a file with write permission. If it is currently not possible, would it be hard (or discussable) to implement?

Regards

Paul

1) `mount -o remount,rw /` works (remounting back to ro does not, because it says "mount point is busy"). 2) you can use `transactional-update shell` - it creates a new snapshot and opens a shell in it. You can do everything you need in there, exit shell and reboot to your changes.

Thank you. But unfortunately as I wrote, both does not (really) work (for me): # mount -o remount,rw / # echo $? 0 # touch /foo touch: cannot touch '/foo': Read-only file system mtab shows also rw after remount. the chroot environment created by the shell command has many limitations. But I cannot recall/verify why I came to the conclusion that this had a big impact. One point was stopping/starting services, since systemctl refuses to work. But of course I can stop service in the old system and start it manually in the chroot... Maybe I am going to be happy with that.