OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Why can't I edit this file?
post Mar 14 2004, 01:20 AM
Post #1





Group:
Posts: 0
Joined: --
Member No.: 0



Hi all, I'm tearing my hair out trying to edit my kismet.conf file...
I keep getting a write failed message. when using the text editor.
(opie enhanced) I have tried a couple of other editors and all give the same result...can't do it!
I have tried "su" but this doesn't make a difference.
Am I missing somethin here?
I really dont know anything about "vi" so I'm trying to avoid using it to edit this file, but when I had a go at it I got the same result...
any help or comments welcome>
Andy
Go to the top of the page
 
+Quote Post
Synfin0
post Mar 14 2004, 01:39 AM
Post #2





Group: Members
Posts: 32
Joined: 12-March 04
Member No.: 2,279



Have you checked the file permissions? A "ls -l" should show something like -rw-r--r-- beside your file. What kind of device is it (mounted with what permissions)? SD cards have read-only switches. There might be other factors I have ignored, anyone?

It is possible to make a file read-only even to root (though vi asks if you want to override, I'm not sure the other editors would). Does the editor declare the file is read-only? Can you make a new file in that directory?
Go to the top of the page
 
+Quote Post
Zuber
post Mar 14 2004, 11:17 AM
Post #3





Group: Members
Posts: 277
Joined: 26-December 03
From: UK
Member No.: 1,289



Assuming the above did not help ...

Have you tried using a terminal based editor (sorry, don't know opie enhanced). I've found some files simply refuse to cooperate unless you use a command line editor. I fond Easy Editor (ee) to be quite good.
Go to the top of the page
 
+Quote Post
Ethereal
post Mar 14 2004, 12:27 PM
Post #4





Group: Members
Posts: 236
Joined: 17-February 04
From: Gainesville, FL
Member No.: 1,914



Is the file you're trying to edit on the readonly filesystem? If the "real" (not symlinked) path to it isn't /home/<everything else> and you're using a Sharp-based ROM, it's on a filesystem that is mounted read-only. If this is the case, make very sure it's really something you want to be editing--Sharp made that FS readonly to safeguard against catastrophic mistakes.

Then,

mount /dev/root / -o remount, rw

This will remount your "ROM" as a writeable filesystem. (I had to do this recently to edit the "real" copy of rc.sysinit to make it run rc.local.)

Once you've finished editing and saving the file, either reboot or

mount /dev/root / -o remount, ro

to put your ROM back out of harm's way.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st May 2013 - 01:46 AM