Some of the overlay filesystems do support writing tomb markers to handle deletions as well. I'm sure you know that, though, so I'm mostly wondering why that was not a good option? Performance?
On Fri, Sep 13, 2013 at 3:15 PM, Oliver Grawert <[email protected]> wrote: > On Fri, 13 Sep 2013 17:42:36 +0200 > Michael Zanetti <[email protected]> wrote: > >> On Friday 13 September 2013 17:33:47 Oliver Grawert wrote: >> > it is currently not possible to switch on ssh in a persistent way, but with >> > the next image in the daily-proposed channel (build number >46) this should >> > be fixed. due to the nature of the readonly image you can not just remove >> > the .override file but instead will have to empty it to make it not take >> > effect: >> > >> > echo | sudo tee /etc/init/ssh.override >> >> At the risk of blaming myself... How come I cannot delete, but still modify a >> file on a read only file system? I mean... modifying a file is still write >> operation, no? > > writability of files on the ro image is achieved by bind mounting the files > from the ro side to a writable area of the filesystem ... if you delete it, > it will just come back on next boot since the bind mount is newly created ... > > which is kind of defeating the purpose :) > > ciao > oli > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : [email protected] > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp > -- gustavo @ http://niemeyer.net -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
