GP2X What Safety Tips When Logged In A Bash Prompt?

[Dingo_aus]

When we are using gfoot's serial over USB program, what areas of the filesystem should one not play with for fear of bricking and/or generally clobbering useful stuff?

I presume /mnt/nand is a good idea to avoid?

Anything else?

/dev ? could playing with these cause a nasty crash/ lock up?

 

[ps_]

alias rm="rm -i"

is pretty helpful/anoying

 

[woogal]

If you don't already know which areas of the filesystem to avoid then the only advice I can give is don't touch anything. And don't start copying loads of stuff onto the nand because it might not boot if it gets full.

 

[Nickmon]

When we are using gfoot's serial over USB program, what areas of the filesystem should one not play with for fear of bricking and/or generally clobbering useful stuff?

I presume /mnt/nand is a good idea to avoid?

Anything else?

/dev ? could playing with these cause a nasty crash/ lock up?

​

Can you do a quick list of what you need to get going doing this...

Thanks

 

[BBTroll]

The funny things is that /mnt/nand is quite safe.
It is just an empty folder.

It is useful if you want something(like sterm) to always be on your GP2X, even if you don't have an SD card on.

"df -h" should tell you how much free space you have left.

 

[no_skill]

for the sake of sanity never, really: NEVER, type

dos2unix -r /* instead of dos2unix -r *

...

that little slash DOES make a difference...

...

and of course never do that while being logged in as root.

...

and never do that on a machine with suse linux and a full 6GB partition.

 

[bjimba]

Don't write to anything in the /dev tree unless you really know what you're doing. Especially things under /dev/mtdblock/ -- you can overwrite your U-Boot pretty easily there.

 

[Dingo_aus]

Thanks guys (and gals)

Thanks bjimba - that is the sort of thing I am fearful of.