David,
>The one bit in your
>article that could do with a bit more detail is to do with permissions and
>the various checkboxes/combinations that fetch and other graphical
>interfaces allow?
For the time beginning at least, set all the READs to true. (you, the
group and the world) Same with EXECUTABLE but keep the WRITE function
just for yourself.
>My problem is that I have installed Linux, downloaded Metacard, and tried to
>add users, and passwords, and have probably succeeded in totally screwing
>Apache up.
Don't worry, Geronimo can take care of himself.
>The thought I have at the moment is that something is going on with Apache,
>and how it's configured. The path to the cgi-bin specified in the
>scriptalias, can't even be seen by the browser "File does not exist
Getting a screen full of important looking stuff back from echo.mt is the
goal--as Scott gently, but firmly pounded into my head. His patience is
astounding. Persist until you get that magic screen.
To achieve this requires ALL of the following:
1) the correct flavor of mc is installed (matches your ISP server
software) in your cgi-bin folder
2) echo.mt is installed in your cgi-bin folder
3) the script of echo.mt is unchanged.
4) the permissions for echo.mt and mc are both set to executable
5) echo.mt is a text file and mc a binary file
6) the pathname you're using to reach echo.mt is correct
Do all that and the problem isn't on your end. My difficulties could all
be traced to the last four items.
I still haven't quite figured out the pathname business.
I actually use http://www.navaching.com/"myusername"-bin/echo.mt
--rather than cgi-bin. I don't know if this is specific to my ISP or not.
Too many things to find out, so little time to do it.
Nelson
