Hi. On Sat, 22 Feb 2014 16:33:57 +0200 binary <dreamer.bin...@gmail.com> wrote:
Please refrain from top-posting on this list. > sorry, i am lost. Hmm. I believe I've just asked a couple of simple questions. Sorry those led to your confusion. > what is the solution to my problem? There's no simple solution to your problem. The filesystem layout you're using will prevent you from using read-only root filesystem. The reason is - you cannot remount a filesystem read-only if: - You have processes which write in this filesystem. - You've changed some binaries and libraries, and have processes which were launched from those binaries and libraries before the overwrite. The former is nearly always happens with syslog (which writes to the files in /var/log). You're have /var directory in the root filesystem (which you want to make read-only). The latter will happen on any upgrade. Still, while read-only root is can be done in Debian: https://wiki.debian.org/ReadonlyRoot read-only /var is impossible unless you're using some kind of livecd/liveusb. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140222194558.cf9b788611ebe3c5eecaa...@gmail.com
