The XO Computer for Navigation

[agkirk]

All of the SD contents appear to be OK. I do have the developer key implemented, but that was done over a month back.

[phiggins]

Install locate:
su -
yum install slocate (might be: yum install mlocate)

Then issue:
su -
updatedb

then you find things by:

locate wine


Paul

[agkirk]

Paul, Thanks, that works and all the files seem to exist. The pathnames appear OK but I noticed a change in how my main screen operates. When I first received the XO I changed the HOT corners by modifying a OS file. Now the HOT corners are back. I'll have to recall how I made that change, but even if I change it again that doesn't explain the current operation or lack thereof. when I cd /home/olpc/ I don't see the .wine directory. If I cd .wine then I see 2 sub-directories and 3 files xxx.reg.
Is the .wine a hidden file? I'll look back through our past post and see where I modified file pathnames. It's like a file with critical pathnames for the added in applications has gotten deleted....but I never deleted anything....I know of!

Alan

[phiggins]

Alan,

Yes any directories that begin with '.' are hidden. to see them do a:

ls -a

You never answered the question whether you can start your SeaClear activity by issuing: wine "C:\Program Files\SeaClear\SeaCler_2.exe"

Even if wine is gone it doesn't explain Opera which is not a wine program.

Paul

[phiggins]

Alan,

Have you checked to see if any of your "disks" are full or nearly so? Do a:
df -k

and check the Use% to see if any are high, like 90%.

Also, check the log viewer after trying to start SeaClear/Opera to see if there are any errors reported.

Paul

[tyrntlzrdking]

Alan,

I had not yet attempted loading Seaclear, but the few additions I have made (Opera, Adobe flash, border popup change etc...) to my XO are all still with me. What build are you using? Mine came with 650, and I has upgrded to 656.
I read a new build is due out anyday.

[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?

[Beausoleil]

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
total 18180
-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.

[agkirk]

I found the command to show the version cat /etc/issue. I see at Update paths - OLPC
that one person has experienced the loss of use for add ins, similar to my experience, after an upgrade to 656.

And now the proof, I am apparently now running 656 after I use the above command.
To the best of my knowledge I didn't do a update, so there must be an auto update "feature"built in to the XO. I'll dig around on the web for more info on this.

Alan

[agkirk]

OK, Verrry interesting! I was updated on Wednesday night, while I slept soundly. I held the O (right game pad) down at boot and was restored to 653, then tried SeaClear and it worked fine. SOOO ! Wonder how I get 656 and the latest firmware into the XO and still preserve the operation of my add in activities? HELP!

[phiggins]

Alan,

I don't think you can. Doing an update will lose all the applicatins you have installed. The only option is to reinstall everything again. That is why I keep a script on how to install them all again.

I think this a good incentive to go to Ubuntu.

Paul

[agkirk]

I agree on Ubuntu. I updated my boot flash to Q2D14, what are you running? When I toggle back to 653 all files are still around and usable, just can't get to them via whatever pathname file is used by 656. Seems like a significant oversight the OLPC developers. What were they thinking?

[phiggins]

I'm at 656, don't know what Q2D14 is. Really strange it updated by itself. Actually because its so quiet and uses so little power, I often leave it on for days with an internet connection. So far I haven't been updated but then I guess 656 is the highest version right now.

I guess the XO developers wanted to make upgrading as easy as possible for kids around the world by doing it this way.

Anyway I'm staying on Ubuntu but I wish I could find a version of it that supports bluetooth. That's about the only thing I haven't been able to get working that was on my original list.

Paul

[tyrntlzrdking]

Bluetooth is being used with Sugar:
OLPC News Forum: Installing Ubuntu using compressed files

You can cut and paste using Sugar:
http://www.wiki.laptop.org/go/Scroll...Copy_and_Paste

[agkirk]

Wow! Thanks and I've bookmarked that bash link, that's real handy. The history is also enlightening. Thanks. So, what do you think changes when running under the 656 kernel? I could do a mc command from the home dir in 653 and it knew the path to .mc/mc.

I tried using the /home/olpc/.mc/mc with no luck. It appears the .exe for all the add ins are located in some other area. You mentioned the $PATH environment variable. I suspect this is where the difference between the two kernels resides and the 656 version doesn't contain the history of 653. Any reason I can't copy that data to the SD card and replace the $PATH in 656? And where might I find $PATH ?