Quote:
Originally Posted by knc1
[2] is caused by [1] - I.E: it was over-written because you told it to (the writing is part of the upstart, start process).
You can't mount to a ro mount point, at least not in Linux, which this is.
The "mount --bind" operation will not persist across re-boots, unless you write code to make it happen as part of the boot process.
The directory name is /etc not /Etc
|
Sorry, was writing on a mobile device (not my kindle with a keyboard ;-) ) damn autocorrect.
Code:
[root@kindle root]# cd /mnt/us/MyProject/
[root@kindle MyProject]# echo "blahblahblah" > ./badxorg.conf
[root@kindle MyProject]# ls
Installbinaries Keyboard Uninstallbinaries badxorg.conf iptables.log
[root@kindle MyProject]# mount -o bind /mnt/us/MyProject/badxorg.conf /etc/xorg.conf
[root@kindle MyProject]# cat /etc/xorg.conf
blahblahblah
[root@kindle MyProject]#
But:
Code:
[root@kindle MyProject]# mount | grep -i etc
/dev/loop/4 on /etc/kdb.src type cramfs (ro,noatime,nodiratime)
/dev/loop/4 on /chroot/etc/kdb.src type cramfs (ro,noatime,nodiratime)
/dev/root on /chroot/etc/fonts type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
/dev/root on /chroot/etc/gtk-2.0 type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
/dev/root on /chroot/etc/pango type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
/dev/root on /chroot/etc/resolv.d type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
This is why I was so confused! It looks like it is bind mounted, but clearly that is not the case. So where is my #cat /etc/xorg.conf getting the blahblahblah statement from? Oddities
Code:
InputDevice \"keyboard"\ \"CoreKeyboard"
That was automatically generated by coplate's makexconfig script.
Let me try again with a custom xorg (just adding the keyboard to the core script) and I'll (hopefully) be able to report back that it works. Thank you for bearing with me, knc1!