🚀 go-pugleaf

In article <4ep20g$8mh@oznet11.ozemail.com.au>,
	pbrosnan@scorpion.cowan.edu.au writes:
>My desire is to have a webserver running,  so to this end I
>downloafded the NCSA server using the one-step downloader.
>I then ungziped the file through tar and was left with what
>looked like a web server directory structure. After configuring
>the conf files I excitedly typed in the command to run the 
>binary. But what was this, I kept getting the message :httpd
>no such file or directory.

Half the problem with pre-compiled and pre-configured packages is
that you often have no clue as to what the packager used as values
when configuring, and more often than not they don't even think to
tell you, fully expecting that you'll be just as "sensible" as they
are and somehow automatically 'know' exactly how it is being set up,
and quite often omitting any important documentation that came with
the original package.

The "no such file or directory" does not refer to the httpd program
itelf, but something else it is trying to access. Probably the config
file, or the logs directory. Httpd uses a specific directory structure,
most (but not all) of which can be overridden in it's configuration
file.

You might be able to get that binary to work if you can work out
the directory structure it is configured/compiled to use. If not,
then my advice is to download the source code, read the documentation
on installation, then configure and (if necessary) compile it yourself.
If you're not familiar with such things then I'd further advise that
you *get* familiar with it - you don't last long with Linux as a
"clueless newbie". :-) It is a case of learning how to do things or
losing patience with it altogether.

-- 
David Nugent: davidn@blaze.net.au, davidn@unique.blaze.net.au
Unix/Linux/DOS/Win/Os2 Microsystem Technical Support [FOR HIRE!]
http://www.blaze.net.au/~davidn