>It just seems to me that there is a real need for someone that really
>understands programing to write "How to do it manuals" that do not
>require years of training to understand what the manual is talking
What are you trying to do? What is the specific category of
thing that we are talking about here?
>I would really like to make use of some of these great things I read
>about, but I do not have the years of experience that it seems is
>necessary to do it.
>Why is everything to do with it so cryptic?
Really knowing Unix in the sense of being a guru takes years
of experience because there is a lot to know. However, I would
agree that the traditions for documentation of many aspects of
Unix are poor. Man pages, for instance, should be required to
have links to examples of typical usage for the major features
of each program. This would save billions of dolllars in
Quote:>Is there a straight forward guide on how to make x-window and the
>applications that are written for it work, or is it really only intended
>to be for the use of the experts or people that can afford to pay the
>experts to set it up?
There is an X Window User's guide published by O'Reilly that might
help. It is a few years old so not uptodate with the latest programs
and features. You might also want to read the man pages for
X, XFree86, and the window manager that you are running.
Quote:>I ask a few days ago about how to install Image Magick, and so far I
>only got one response from a person that either does not really have the
>knowledge to be answering the question or he did not read the whole
>question, because he suggested that I install it from root with the
>Linux cd, when I made it very clear in my question that I do not have
>root access on the server.
How to install a binary is really a distribution specific question,
or else a question about a particular source package. However, the
general sort of answer if you do not have root is that you want
to put the binaries in your own private binary directory,
e.g. $HOME/bin where $HOME normally evaluates to your home
directory (the same as ~ ), and then add this directory to
your path. The other things you would need to know about
is how to unpack the binary package to a regular directory
without installing it, and then you can just copy the executables
to the desired directory. With a Debian package I would probably
make a temporary directory, cd there, and then do a
dpkg --fsys-tarfile pkg.deb | tar xf -
If you have an rpm system then you should be able to find someting
similar on the rpm man page.
Anothere complication is that the package may have its own special
shared librarys. In that case you will want to set the environment
variable LD_LIBRARY_PATH to the directory where you put the shared
libraries. You can read about this on the man page for ld.so
If you have a source distribution for the package, you probably
want to do a
Then if you are running bash, put the lines
in your .bash_profile file.
Quote:>Now I am not stupid or even uneducated I just do not have the experience
>to do what I would like to with x-window programs.
These issues are Unix issues, and not really x-window related.
Quote:>If anyone can guide me toward a book or on line source for beginners to
>learn it would help me and a lot of other people (likely including
>yourselves because then you would not have nearly as many questions to
I think that the book _Unix For the Impatient_ is pretty good.
Also O'Reilly's _Unix CD Bookshelf_ is an excellent deal.
I'd recommend starting with one of those.