I have installed emacs with yum and now I'm trying to create a .emacs file and put some commands in it, but I can't type anything in the emacs buffer. It says the buffer is read-only. I exited emacs and did touch .emacs and I get a message that it can't do that on a read-only file system. I googled around to see why this might be, but I can't see any links on this. Any tips why this might be doing this? I've heard that centos is strict on changes, but I don't know the extent it restricts changes. I followed a page where I did echo 0 >/selinux/enforce . But this is only good until reboot. But shouldn't I be now able to make changes in ~*
Thanks,
-wes
usually a disk failure when that happens out of the blue. try writing to /dev/shm/ if you have to save a file. (That's a virtual fs in memory, so be advised it will disappear on reboot.) check dmesg for errors.
On Fri, Nov 1, 2013 at 5:36 PM, Wes James comptekki@gmail.com wrote:
I have installed emacs with yum and now I'm trying to create a .emacs file and put some commands in it, but I can't type anything in the emacs buffer. It says the buffer is read-only. I exited emacs and did touch .emacs and I get a message that it can't do that on a read-only file system. I googled around to see why this might be, but I can't see any links on this. Any tips why this might be doing this? I've heard that centos is strict on changes, but I don't know the extent it restricts changes. I followed a page where I did echo 0 >/selinux/enforce . But this is only good until reboot. But shouldn't I be now able to make changes in ~*
Thanks,
-wes _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, Nov 1, 2013 at 4:39 PM, Billy Crook bcrook@riskanalytics.comwrote:
usually a disk failure when that happens out of the blue. try writing to /dev/shm/ if you have to save a file. (That's a virtual fs in memory, so be advised it will disappear on reboot.) check dmesg for errors.
On Fri, Nov 1, 2013 at 5:36 PM, Wes James comptekki@gmail.com wrote:
I have installed emacs with yum and now I'm trying to create a .emacs
file
and put some commands in it, but I can't type anything in the emacs buffer. It says the buffer is read-only. I exited emacs and did touch .emacs and I get a message that it can't do that on a read-only file system. I googled around to see why this might be, but I can't see any links on this. Any tips why this might be doing this? I've heard that centos is strict on changes, but I don't know the extent it restricts changes. I followed a page where I did echo 0 >/selinux/enforce . But this is only good until reboot. But shouldn't I be now able to make
changes
in ~*
Thanks,
-wes __
That was it. This is an old mac pro that I put centos on yesterday. It had 4 disks in it and this is the 3rd that has died. A faculty member had it for 5-6 years and it was on 24/7. It's been in the junk pile for several months. I guess long enough for the disks to go south from sitting on so long then going off for a period... maybe.... Anyone heard of this?
Thanks,
Wes
On Sat, Nov 2, 2013 at 4:21 AM, Wes James comptekki@gmail.com wrote:
That was it. This is an old mac pro that I put centos on yesterday. It had 4 disks in it and this is the 3rd that has died. A faculty member had it for 5-6 years and it was on 24/7. It's been in the junk pile for several months. I guess long enough for the disks to go south from sitting on so long then going off for a period... maybe.... Anyone heard of this?
It is hard to predict hard disk failure. I have had "sealed" Seagate enterprise grade disks DoA.
Install smartd (smartctl) and watch the logs for impending failures and take corrective actions when you start noticing failures in the smart report; even this is not full proof. RAID gives some comfort level but do keep backup of important data in multiple places.
On 11/01/2013 06:36 PM, Wes James wrote:
I have installed emacs with yum and now I'm trying to create a .emacs file and put some commands in it, but I can't type anything in the emacs buffer. It says the buffer is read-only. I exited emacs and did touch .emacs and I get a message that it can't do that on a read-only file system. I googled around to see why this might be, but I can't see any links on this. Any tips why this might be doing this? I've heard that centos is strict on changes, but I don't know the extent it restricts changes. I followed a page where I did echo 0 >/selinux/enforce . But this is only good until reboot. But shouldn't I be now able to make changes in ~*
Thanks,
-wes _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[mlapier@mushroom ~]$ ls -al | head -2 total 704896 drwx------. 120 mlapier mlapier 4096 Nov 1 18:31 .
Your home directory must belong to you and have write permission as shown by the "w" in the drwx at the beginning of the line above.
You can open up your permissions if you feel so inclined but I wouldn't suggest it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/01/2013 06:55 PM, Mark LaPierre wrote:
On 11/01/2013 06:36 PM, Wes James wrote:
I have installed emacs with yum and now I'm trying to create a .emacs file and put some commands in it, but I can't type anything in the emacs buffer. It says the buffer is read-only. I exited emacs and did touch .emacs and I get a message that it can't do that on a read-only file system. I googled around to see why this might be, but I can't see any links on this. Any tips why this might be doing this? I've heard that centos is strict on changes, but I don't know the extent it restricts changes. I followed a page where I did echo 0 >/selinux/enforce . But this is only good until reboot. But shouldn't I be now able to make changes in ~*
Thanks,
-wes
As you found, SELinux was not at fault,
echo 0 > /selinux/enforce
Is immediate, it will put the machine into permissive mode. setenforce 0, is a better command to do this.
On reboot SELinux would be back to the original state. If you want to alter the default state of SELinux, you do this through /etc/selinux/config.