means set the path to what ever it is now ($ means "the current value of") and also ("and also" is represented by the colon) "/var/lib/install/usr/bin".
The PATH statement is only going to persist if I put it in my .profile file?
And would someone (OK, Crossbow, you did a good job — up for a little more?) spell out how to make a .profile file (in the right directory) with just this one line about the path, from the command line?
Hi everyone. Thanks again for all the posts. I do appreciate it.
I was able to create the necessary files to get vim running without the very long command string. Although, I do have experience reflashing my device now.
The commands will overwrite any existing .profile, and add 3 lines to the new file: the first updates the PATH (so commands can be found), the second updates LD_LIBRARY_PATH (so a command's libraries can be found) and the third ensure that things now about LD_LIBRARY_PATH (PATH has already been exported).
Once this is done, a reboot would be needed for the environment changes to be picked up.
And would someone (OK, Crossbow, you did a good job — up for a little more?) spell out how to make a .profile file (in the right directory) with just this one line about the path, from the command line?
Uh - No. But I will try to help with a little more background for those that are interested, and I explain why I cannot just answer the question below.
Someone else, in this tread, already gave a fine description of working directories, and how to change your working directory.
As those readers new to this whole Linux/UNIX thing are finding out from this thread, Linux is almost totally controlled by coded lines in plain text files.
This is "bad" for the following reasons:
1. It just seems kinda primative.
2. There can be hundreds to literally thousands of them in a single linux installation.
3. The syntax, language, conventions, etc. are different in different files. In different distributions (versions or applications of Linux), the files that control a given fuction can have different names, reside in different directories, and sometimes use different conventions.
4. Some files reference others in a seemingly chaotic tangle.
5. Often the correct syntax, language, etc. is either poorly documented or possibly not documented at all.
This is "Good" for the following reasons:
1. It makes the system extreemly powerful and customizable.
2. It simplifies administration - just backup the controlling file, and a new machine or update should behave just like the original. I can easily compare settings files to determine why one system works differently than another.
3. Most such files (including .profile) allow comments. This is a fantastic administration tool. The files can be "self documenting". A user/administrator can also put notes, dates, records of changes, etc. right in the file.
4. Having seperate files minimizes the damage that can be done (intentionally or accidentally) to other parts of the system. For example, there is no way that messing with a webserver configuration file can keep the system from booting (even if I do so as root).
5. These files are individually controlled by the UNIX permissions systems. As I mentioned, nothing a user can do can alter system files.
6. This is (IMHO) a far better model than the Windows registry, where registry corruption (again intentional, or accidental) can have effects on many parts of the OS.
7. I do not need to write GUI control panels for every function I wish to allow the user (or administrator) to customize. I can always write a GUI if I want, but I do not need to. The GUI would have to be extreemly complex to allow the level of customization available in some settings files.
8. (This is the most important for this topic) A user/administrator can use any text editor they would like to edit the files.
#8 is why I can't/won't answer the question on how to create the .profile file. Use what ever you want. Making a non-geek learn vi (vim) is akin to torchure. Hypothetically, you could use MS Word on your desktop if you would like. Just save the file as plain text (If you take me litterally, you may have a problem with encoding, but it should work with the proper settings), save the file to a MMC, and copy it to the proper place. As one poster correctly pointed out, you can do it with no editor, just by echo'ing the lies to the appropriate file. I would rather just get the point across that it does not matter how you create the file, just that it:
1. Has the correct syntax
2. Is named correctly
3. Is in the right place (directory)
Some options include:
vim
joe
The editor in mc (which generally works fine on my 770.)
using the echo command
MaemoPad
various ways of creating the file elsewhere and copying it to the 770.
One last fact: Files that start with a dot (period):
Linux/UNIX does not really have "invisible" files. In Linux/UNIX, files that start with a dot (period) are simply not shown in default directory listings, and should not be shown by default in GUI file managers. This is NOT done to hide anything. It is done to reduce clutter. User preferece settings files often start with a dot so that when we look in our home directory, we see the files we want - our Documents, Pictures, Music, etc, and not dozens of settings files.
The command:
ls
('list' with every other letter removed) will not show files that start with a dot.
Sorry to bump this thread, but I am looking for very basic help and this one came up as the best candidate. Unfortunately, I didn't find the answer to my stupid question, which is: how do I activate CTRL on the 770 virtual keyboard? I have edited a file in Joe's Own Editor and am stuck-- I can't see how to save it and exit! Documentation has been no help because everything I've read assumes this is not an issue (written for other devices I guess).
how do I activate CTRL on the 770 virtual keyboard? I have edited a file in Joe's Own Editor and am stuck-- I can't see how to save it and exit! Documentation has been no help because everything I've read assumes this is not an issue (written for other devices I guess).
For that matter, how is Escape accessed as well?
CTRL can found from X Terminal menu. Just select Terminal -> Send Ctrl-<some key>.
ESC is hardware Escape key (located below scroll key).
Sorry about little confusing first try Texrat. I had never used Joe and I did write my last message quite quickly.
Lets try again now when I have actually installed Joe in my 770 and even tested it little bit.
1. You can have help for Joe by selecting "Send Ctrl-<some key>" from X terminals "Terminal" menu and after that pressing "k" and "h" from the keyboard.
2. As you can see from help page save and exit command is CTRL+K+X. After you have made all changes to file just press CTRL+K+X just as above. After that file is saved and Joe is closed.
3. In the 770 manual hardware key below Dpad (Scroll key) is called Escape key and it works as ESC at least for VI-editor.
I hope this helps. By the way VI is much beter editor and it just works .
.