bash vs sh: parameter not set

Reminder: We're an English-only site.

The onus is on the OP to translate to and from English.
 


Grazie per avermi costretto a usare Google Translate...
Sorry, i'm not english, and i forgot to translate in english
I file nascosti sono preceduti da un "." . I file nascosti esistono per distinguerli dai file non nascosti e non vengono visualizzati a meno che tu non ne faccia esplicita richiesta.
But I knew this
Dato che ovviamente non vuoi provare a interagire con me in una discussione, usa Google per cercare "hidden file" e impara a fare ricerche da solo.
As I said at the beginning (my fault)...
And anyway there is no need to be touchy.
 
Trying things (setting variables, editing the ./bashrc) and then applying them is one way to learn how things work with Linux. If you don't like the results you get, you can always undo what you've modified.
You're right, but sometimes I happen to not be at the computer, or not have time to try.
 
As I said at the beginning (my fault)...
And anyway there is no need to be touchy.
since you are asking for help and information, you need to respect our need for clear and convenient posts. People tend to get annoyed and bewildered when you talk to them in ways that are hard to deal with, it's just a fact of life, get used to it. This computer stuff is already confusing enough as it is, I am very experienced with linux and command line stuff but nobody knows everything.

Variables are just ways for the shell (and computer programs in general) to remember and re-use information. They also allow computer users to go back and change the information, if the value needs to be set to something else. Three of the variables you posted must have PROBABLY "worked" because they are set by default, as a lot of variables are.

If you're getting "parameter not set", that means the variable is not set, and whatever command you entered needs it to be set to work.

if you get a value like "1000" (value for non-root users), that means it is set. Users on a linux system typically get assigned values in the thousands. The root zero has a value of 0.

if you get nothing at all, that also indicates the variable is not set.
 
You're right, but sometimes I happen to not be at the computer, or not have time to try.
Thanks, and, I get it.
Life is busy to say the least.
 
since you are asking for help and information, you need to respect our need for clear and convenient posts. People tend to get annoyed and bewildered when you talk to them in ways that are hard to deal with, it's just a fact of life, get used to it. This computer stuff is already confusing enough as it is, I am very experienced with linux and command line stuff but nobody knows everything.

Variables are just ways for the shell (and computer programs in general) to remember and re-use information. They also allow computer users to go back and change the information, if the value needs to be set to something else. Three of the variables you posted must have PROBABLY "worked" because they are set by default, as a lot of variables are.

If you're getting "parameter not set", that means the variable is not set, and whatever command you entered needs it to be set to work.

if you get a value like "1000" (value for non-root users), that means it is set. Users on a linux system typically get assigned values in the thousands. The root zero has a value of 0.

if you get nothing at all, that also indicates the variable is not set.
Good confirmation, thanks.

Does the variable have to be set in the ./basrc?
 
Thats just if you want it set after you restart your computer or end your shell session, otherwise you can just type:

variable=value

At the command line
Thanks!
 


Follow Linux.org

Staff online

Members online


Top