Your advice above wasn't the best I reckon. It smells more like a Windows solution, and not Linux.

Also in this post
this is linux, while you try to approach using Windows mentality

2 members found this post helpful.

WTF?

That just screams Window$ Mentality.

You won't be able to run commands/launch programs normally, but if you can get to a command line it's almost effortless to restore $PATH.

First, get to a command line. If you don't already have one open in your GUI, switch to a VT using Ctrl+Alt+F2.

Set the PATH variable.

Done.

0 members found this post helpful.

For your information I did read the materials and I'm not understanding the language or the course. So thank but no thanks
Cheers
Bernice

Bernice;

First, it is not good practice to simply cut and paste your homework assignments without telling us what you have tried. Tink's reaction is standard.

Do you mean it's not in your native language? What exactly are you not understanding?

Finally, how about acknowledging the people that have offered specific advice---including the post just before your last one?

Well that is so sad for you; how about asking a lecturer or fellow student - especially considering that you're paying for the course.

If you don't understand the language how is it our problem? You could perhaps show us what you don't understand and we can help you.

As per Tink/pixel - we are NOT here to do your homework for you. You need to show that you have at least tried to understand/answer the question for yourself so we can guide you where you are wrong.

We are a community not a one stop Q/A shop for people doing a 3-6 month course on Linux and forgetting about it. We're not paid to do this; but rather contribute in order to help educate others who actually are interested in Linux and learning it.

In the spirit of learning & teaching Linux best practice, I humbly submit that re-booting to solve a configuration problem is seldom required. Simply starting a new shell, or re-reading the shell's startup script(s) is almost always enough to restore a shell to proper operation (possibly after making the appropriate remedial edits). Restarting other individual processes (again, after making appropriate configuration edits) is usually enough to restore correct operation. Re-installing Linux should probably considered the absolute last, most drastic, nothing-else-left-to-try step. I cannot remember the last time I had to restart Linux for any corrective purpose, other than hardware failure or upgrade. My principal desktop system routinely runs for a year or more between reboots, and that is usually caused by either power loss, or need to upgrade some hardware.

To answer the OP's question: edit the shell's startup script (~/.bashrc, usually), if necessary, and then source that script from the commandline.
--- rod.

1 members found this post helpful.

Hello everyone,

Some here have pointed out that I lack a Linux perspective on solving thing. I would like to explain why then I post the post I have posted.

Yes, I have much Windows mentality left. I have just migrated to Linux.

The advice may or may not have been the best, but still it proposed a solution to the problem in hand.

What I read was a problem with the system-file, I think. My first thought is re-install the system when such a problem comes along. Yes, it may very well be a Windows solution. I am not a guru in Linux. I just try to make it work. So why did I post a solution who might not be the best? Because it gave a solution to make the system work and that is what I wanted for my-self, if I would encounter the problem with my Linux-computer. "Do for others what you want them to do for you" is the figuratively Northern Star I try to live by.

I hope I have not aggravated anyone. My intention is simple to help with best of my ability. If that is not good enough, please, explain why it is not so I can learn from it .

From a sunny Stockholm, Leopold

And with these words this topic has been discussed to death.

Closed.