Talk:Linux software: Difference between revisions
(commands vs else) |
(I agree completely: there needs to be a good novice page specifically geared to using Terminal) |
||
| Line 6: | Line 6: | ||
For some reason, I think it was SUGAR_PATH or something like that, among other things, I have always used "su -p" whenever I need su permission. |
For some reason, I think it was SUGAR_PATH or something like that, among other things, I have always used "su -p" whenever I need su permission. |
||
07/23/09 16:12 MST: |
|||
There should be a list of the commands that are built in. For example it was only through consulting this WIKI that i found that "nano" is a built in command even though it is actually an editing program. I also got into trouble following the example on changing Terminal FONT size and "nano" is now oversized and unuseable to change back. |
|||
Also there is a problem with the terminology used. Just what is a Shell command vs those commands that you can only enter after entering "su -" and get the "-bash-3.2#". Also there seems to be a subtle difference when i enter just "su" and get "bash-3.2#. No - precedes "bash...". |
|||
When i install Opera per the instructions (I would never be smart enough to figure it out by myself) I then find that in terminal i can type "Opera" and it launches. Opera then has become a command. |
|||
Another interesting command is "vncviewer". I found it somewhere. When i enter this, i get a blank screen into which i can enter the addres of a server. Then it asks for the password. If i enter that i get a message that it is connected but nothing else. Give up in frustration and exit the terminal (click the STOP sign) wondering if i am screwing up the server; |
|||
The information including the above mentioned "$PATH" is very fragmented. I am a Macintosh user and have never worried about "path". If i type in the name of a file, if it is in the system, it will be found no matter where it is. Windows users are a bit more "fortunate". They used to have to know what a path is. |
|||
Well enough for now. I am following the guideline of not identifying myself; however i have included the date of entry. Wish others would do the same. |
|||
Latest revision as of 23:47, 23 July 2009
Should a distinction be made between built in shell commands and everything else?
Where should novice users learn about $PATH ?
I have witnessed users that had experienced hours of frustration because of not knowing some of the above. In the forum pages, I read entries where someone actually installed full firefox on his xo, then couldn't get it to execute (I am quite sure because it was not in his PATH), asked for help, and ended up selling or giving away his xo out of frustration.
For some reason, I think it was SUGAR_PATH or something like that, among other things, I have always used "su -p" whenever I need su permission.
07/23/09 16:12 MST: There should be a list of the commands that are built in. For example it was only through consulting this WIKI that i found that "nano" is a built in command even though it is actually an editing program. I also got into trouble following the example on changing Terminal FONT size and "nano" is now oversized and unuseable to change back.
Also there is a problem with the terminology used. Just what is a Shell command vs those commands that you can only enter after entering "su -" and get the "-bash-3.2#". Also there seems to be a subtle difference when i enter just "su" and get "bash-3.2#. No - precedes "bash...".
When i install Opera per the instructions (I would never be smart enough to figure it out by myself) I then find that in terminal i can type "Opera" and it launches. Opera then has become a command.
Another interesting command is "vncviewer". I found it somewhere. When i enter this, i get a blank screen into which i can enter the addres of a server. Then it asks for the password. If i enter that i get a message that it is connected but nothing else. Give up in frustration and exit the terminal (click the STOP sign) wondering if i am screwing up the server;
The information including the above mentioned "$PATH" is very fragmented. I am a Macintosh user and have never worried about "path". If i type in the name of a file, if it is in the system, it will be found no matter where it is. Windows users are a bit more "fortunate". They used to have to know what a path is.
Well enough for now. I am following the guideline of not identifying myself; however i have included the date of entry. Wish others would do the same.