You are not logged in.
Pages: 1
When I edit a configuration file, whatever it may be does not save. For example: If I 'sudo vim /boot/grub/menu.lst' make changes and save, then re-open it goes back to default. This happens with every text file/editor. /boot/grub/menu.lst is directed to the wrong kernel and I have to manually change it at boot everytime because the file will not save.
[edit] - It works some times but most of the time it doesn't.
Last edited by pharcyde (2009-04-04 03:20:50)
Offline
Your file system isn't mounted as read only, is it?
Offline
Your file system isn't mounted as read only, is it?
LOL, yeah that was it. Somehow I didn't notice this:
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/1548fb65-e0d0-489b-bac7-c4dc7a0719a0 RO
Must have happened when I updated kernel.
Last edited by pharcyde (2009-04-04 03:32:15)
Offline
That 'ro' in the grub line should be there, and doesn't mean that you're ultimately mounting your filesystem as read-only. The 'ro' flag in the grub line only mounts the root filesystem read-only initially so that filesystem checks can be performed. Might want to check your /etc/fstab and see if a read-only flag is set there. (Did removing the 'ro' from the grub line actually fix things?)
Last edited by RedSocrates (2009-04-04 03:37:05)
Offline
That 'ro' in the grub line should be there, and doesn't mean that you're ultimately mounting your filesystem as read-only. The 'ro' flag in the grub line only mounts the root filesystem read-only initially so that filesystem checks can be performed. Might want to check your /etc/fstab and see if a read-only flag is set there. (Did removing the 'ro' from the grub line actually fix things?)
It appears to have. Here is fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=1548fb65-e0d0-489b-bac7-c4dc7a0719a0 / ext3 defaults 0 1
UUID=8d4c7698-d94c-403f-85b2-ad21a9f351a5 /home ext4 defaults 0 1
UUID=acd92ae6-b7a1-4d0b-9211-725e991dac59 /var reiserfs defaults 0 1
UUID=c3f1db01-3d79-45bb-9175-69749fc3e8aa swap swap defaults 0 0
/dev/sr0 /mnt/dvd iso9660 ro,user,noauto,unhide 0 0
/dev/sr1 /media/dvd1 iso9660 ro,user,noauto,unhide 0 0
/dev/sda1 /mnt/windows_d ntfs-3g users,uid=1000,gid=100,fmask=0113,dmask=0002 0 0
/dev/sdb1 /mnt/windows_c ntfs-3g users,uid=1000,gid=100,fmask=0113,dmask=0002 0 0
Offline
You don't have a /boot filesystem that you're not mounting, do you? I had this happen to me. I installed lots of stuff into the /boot directory on /, but it didn't make anything change since it was booting from a separate /boot that I wasn't even seeing.
Offline
fstab looks fine. I don't have any additional suggestions, so I'll let others answer and/or wait to hear the response to ataraxia. EDIT: Actually, I lied; I do have one other consideration. Is it possible that your /boot/grub/menu.lst file is being occasionally "restored to defaults" because other packages are sometimes actually overwriting the one you have when they're installed? I have "NoUpgrade = /boot/grub/menu.lst" in my /etc/pacman.conf file. Do you?
Last edited by RedSocrates (2009-04-04 03:59:52)
Offline
You don't have a /boot filesystem that you're not mounting, do you? I had this happen to me. I installed lots of stuff into the /boot directory on /, but it didn't make anything change since it was booting from a separate /boot that I wasn't even seeing.
No, I do not.
Offline
Pages: 1