Originally Posted by agkirk
I did try the wine path and got a "wine: command not found". Looks like I still have about 55% of the FLASH unused. I think I am running 653, but I've forgotten how to get the version out of terminal. This whole problem has got to be something I did wrong when I was moving the .wav files using Midnight Commander. That is another thing that doesn't run out of the terminal. Using locate mc I see it is as /home/olpc/.mc . When I try to run out of the [olpc@xo-10-C8-41 ~] directory it get mc: command not found. What is the difference between the use of / and \ as separators?
While I don't have an XO, you can try the command "uname -a", which should tell you what kernel you're running, at least.
The slash (/) is the directory separator. The backslash (\) is used as an "escape" character, which removes any special meaning of certain characters.
For example, if you type "ls -a" at the terminal command line, the command interpreter sees the "-" as a command line switch - that is, run the command "ls" with the switch (or option) "a", meaning to tell "ls" to list all the files in the current
directory - even the hidden ones (ones beginning with a period - "."). If you type "ls \-a", the backslash removes the special status of "-", that is, it tells the "ls" command you want it to list a file called "-a".
Another common switch/option of the "ls" command is "l", or long format. "ls -l" will show something similar to
[jon@bigmax ~]$ ls -l
-rw-rw-r-- 1 jon jon 19 2007-11-30 10:03 autoexec.bat
drwxrwxr-x 2 jon jon 4096 2008-02-06 19:13 bin
drwxrwxr-x 5 jon jon 4096 2008-01-01 16:08 builds
drwxrwxr-x 2 jon jon 4096 2008-02-09 19:30 CD
It shows information about file rights, individual and group ownership, size, edit date/time, and file name. The example above is from my home directory on my Fedora 8 Linux PC.
Way back when Microsoft was creating DOS, they decided to use the "/" as a command line switch to differentiate it from the then-popular CP/M operating system and from Unix. And when they finally got around to using hierarchical directories in DOS 2.0, they used the backslash (\) in place of Unix's forward slash (/). And from what I remember, DOS (and now the CMD window in NT/XP/Vista) doesn't use the concept
of an escape character like "\"in Unix and Linux
. We've been confused/cursed ever since...
When you try to run "mc" from your home directory (that's what the tilde "~" signifies), it won't be found. Why? Unlike DOS, Unix/Linus doesn't default to looking in the current directory (~, or home, in this case). It only checks the $PATH environment
variable to see what directories to search. It's a protection against self-imposed stupidity
. You need to be explicit. If you change the command string from just "mc" to "/home/oplc/.mc/mc", it should work. Or you can use the tilde, as in "~/.mc/mc".
And to further confuse you, the dot (.) and double dot (..) also have special meaning. When used with directory separators, the dot indicates the current directory, and the double dot represents the parent of the current directory.
So in your case, lets say your command prompt says [olpc@xo-10-C8-41 ~]. That means you're in the "/home/oplc" directory. If you type "ls .", it's the same thing as just "ls" - list the files in the current directory. You could be explicit and type "ls /home/oplc" and get the same thing. If you type "ls ..", then you're telling "ls" to list the files in the parent of the current directory - "/home". You could get fancy and try "ls ../..", which means list the files in the parent of the parent of the current directory. Which in this case, means the parent of the parent of "/home/oplc", which happens to be "/", or the root directory.
Clear as mud?
If so, try looking into the "bash" command shell (the "Bourne again shell, a descendant of the popular Bourne Shell, or "sh") here