flogsticator

Group: Members
Posts: 12
Joined: Dec. 2006 |
 |
Posted: Dec. 07 2006,17:47 |
 |
First, the mandatory very silly suggestion : check you're trying to edit the right file on the right hd (and not, say, the file on the cdrom). It helps if the HD is mounted RW (read-write) and not RO (read-only). Oh, and NTFS partitions are somwhat difficult to write to. I should know :blush: .
Then : check the file's write permissions. Change them if necessary. Edit with vi, vim, nano, mcedit, whatever is installed and you prefer. You should be able to write as root on a write enabled file on a valid mounted HD (avoid NTFS partitions).
sudo su Ok, should be root now.
ls -alFh /boot/grub/menu.lst
In the listing, rw_r means only the owner (and root) can edit it. Where _ can be anything (w or x, actually). In order to let any old putz edit it (bad idea) just : chmod uga+rw /boot/grub/menu.lst
rr__ means that even the owner can't edit it.
If that is the case, just change it with
chmod u+w /boot/grub/menu.lst
And try editing it, still as su.
You can drop back from su by using the command exit.
If that doesn't work, start looking for aliens ;) Just kidding. Keep at it. You'll win out, in the end.
Good luck.
|