Quote:
Originally Posted by knc1
It depends on what your true purpose is.
If you wish to give the user a chance to escape from a bad file or other incompatible change with a simple re-boot . . .
Then use a bind mount.
Making sure it is not automatically created by the start-up code, only by the menu entry to enable it.
If neither you nor the computer never makes an in-compatible file change that someone might need to escape from, then change the system file.
|
Hmm. I think that either I don't understand the situation well enough, or I'm not articulating my problem well enough. Let me try again:
Situation:
#mount -bind /var/local/xorg.conf /etc/xorg.conf
#restart X
/Etc/xorg.conf is overwritten by makexconfig
If / was mounted rw, then bound, then ro - /etc/xorg.conf would still be overwritten by makexconfig because makexconfig would need rw privs in order to write xorg.conf in the first place, no?
And if not, then wouldn't a reboot leave you with the edited xorg.conf? I think this is why coplate is suggesting the 'mount bind and edit makexconfig route.'
Or I'm completely wrong and confusing the situation.