Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Use Xnest to run X11 sessions in a window' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use Xnest to run X11 sessions in a window
Authored by: jimhill on Feb 10, '04 05:56:58AM
vikingshelmut:

It's likely that xinit is not in your PATH. Type echo $PATH at the prompt and see if /usr/X11R6/bin is in there. If not, you'll need to add it or specify the path explicitly. If that sounds like gibberish, you really need to read a basic unix tutorial because you're getting into waters that are over your head. (However, it's easy to learn to swim!) I'm sure Rob has some hints that point to such tutorials...

---
Mac OS X: Because making UNIX simple is easier than debugging Windows.

[ Reply to This | # ]

PATH doesn't seem to be an issue for me
Authored by: vikingshelmut on Feb 10, '04 11:18:04AM

I am familiar with adding directories to my path, however if I just cd into the /usr/X11R6/bin directory and try to execute the command, bash says xinit is not a command. This is what I don't understand. Again, my previous post has what was originally listed as a script:

xinit ~/.xinitrc.kde -- /usr/X11R6/bin/Xnest :3 -geometry 800x600

If bash won't let me execute this command from within /usr/X11R6/bin, then what is wrong?



[ Reply to This | # ]
PATH doesn't seem to be an issue for me
Authored by: nobody on Feb 10, '04 12:19:31PM
the more modern unix variants wont execute a file if its in your current working directory ( because its not in your PATH by default ). Only commands which are in your PATH are searched and executed. You have to explicitly tell the system where it is:

./xinit ......
You can, however add the current directory to your PATH. Then it will work like you expected, example for tcsh:

setenv PATH {$PATH}:./


[ Reply to This | # ]
PATH doesn't seem to be an issue for me
Authored by: Detrius on Feb 15, '04 12:18:37PM

Take note, however, that adding the current working directory to your $PATH is a serious security risk. If someone finds a way to put a file named 'ls' somewhere on your drive (maybe through guest access/file sharing), and you type ls in that folder as root, then you have excecuted their script as root. This is not a good idea. Just put ./ in front of the filename if you want to run something in the local directory.



[ Reply to This | # ]