Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm new to Linux and I think I have a path problem.
Not sure what a path problem is, not sure how to solve it.
Basically this is because I'm trying to install xvnc and I want to use kde as my default window manager rather than twm.
So apparently all I have to do is replace 'twm' on the last line in the ~./vnc/xstartup script with 'startkde'
However when I start the vncserver and login on my windows machine, I get a grey background and a terminal screen.
When I look at the server startup log in ~./vnc/ there seems to be a problem with the startkde command.
It says startkde :command not found
I've been led to believe that this is a PATH problem but I have no idea as to how I fix it.
On my system the startkde command is in '/opt/kde3/bin/'
Type in 'locate startkde' to find the path to the kde executables. Then edit your ~/.profile or ~/.bash_login file to add this directory to your PATH environment variable.
be sure to run "updatedb" before you run "locate"
locate is an optimed searvh, that uses a database of your hard-drive generated by the updatedb command...
everything your system has changed significantly, and you want to use locate, re-run updatedb.
anyways.. yeah, you need to search for a /bin/startkde
Are they run when you first login?
Or when you start KDE?
What's the difference between them?
I can't find a .bash_login file in my home dir
Would it work if I added the following commands to the end of .profile...
cd /usr/local/bin
./vncserver
??
I'm trying to get the vnc server to run automatically on startup.
I must admit I'm loving Linux. Everything goes into your home dir. So you can easily backup application settings. Not like in windows with the registry. I liked windows when it kept everything in .ini files - that was good.
They are run when you log in. You don't need to use kde.
The .bash_login is bash specific while more then one shell will use .profile.
They are alternatives. You can use just .profile. Read 'info bash' for details on the startup scripts run. The login scripts will sometimes call other scripts. On some distros for instance, there is a scripts called aliases and .aliases which are run if they exist. Reading through your .bashrc and .profile scripts will help locate such files.
For things like setting the path, you don't want to use the .bashrc script because it is run every time you open a new shell. This could result in the same path being tagged on to the end of the PATH variable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.