httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <>
Subject Re: [users@httpd] Locked Apache configuration file
Date Sun, 21 Mar 2010 01:06:53 GMT
On 3/20/2010 7:46 PM, Daniel Reinhardt wrote:
> --------------------------------------------------
> From: "William A. Rowe Jr." <>
> Sent: 20 March, 2010 18:18
> To: <>
> Subject: Re: [users@httpd] Locked Apache configuration file
>> On 3/20/2010 1:02 PM, Daniel Reinhardt wrote:
>>> Why not install Apache and other web serving stuff into a non-protected
>>> directory like c:\usr\local\apache
>> My c:\usr is quite locked down, thank you very much :)
>>> You can customize your installation locations.
>> We already enable that in the MSI installer.
>>> C:\Program Files is protected by the OS.
>> C:\ Root is protected by the OS as well.
>> The point isn't to run it as a unix app on windows, but to be a first
>> class
>> citizen.  To do that, it's all about respecting conventions.
>> It appears that convention is now C:\ProgramData\Vendor\Application\
>> The idea moving fowards is there is only one copy of the program, by
>> default in the usual location, but the ability to install a skeleton
>> of a service (conf, logs, htdocs) anywhere, usually ProgramData as the
>> global/system server, but optionally a private-for-one-user flavor in
>> their own \Users\[username]\AppData\Local [or Roaming?]
>> profile, if they like.  Still working this through.
>> Making win32 more unix-like doesn't help win32 folks become acquainted
>> with
>> Apache, very much.  But if you like to install everything under
>> c:\opt\httpd
>> you are welcome to do that, instead :)
>> ---------------------------------------------------------------------
>> The official User-To-User support forum of the Apache HTTP Server
>> Project.
>> See <URL:> for more info.
>> To unsubscribe, e-mail:
>>   "   from the digest:
>> For additional commands, e-mail:
> William,
> You pretty much missed the entire point of my post, as it went clear
> over your head.  You can install anything you want and have it reside
> outside of c:\program files and it would still work.

Of course, that's why the installer lets you pick a path.  [You did make the
connection that I authored the win32 installer, I presume?]

Program Files doesn't work for some, maybe they run scripts or apps that
don't respect spaces, or the (x86) trips up some parsers also.

And it's too much typing for me; besides a 'test install', all dozen or
so copies on my boxes are installed on short easy-to-type paths.

> On 64bit Windows it comes with 2 Program Files and they are: c:\program
> files which is for 64bit applications, and then there is c:\program
> files(x86)\ which is for 32bit applications.  There is no default or
> conventional way of installing things on Windows or Linux.

There are conventions.  On both.  Choose from one of several, and even some
entirely erroneous conventions (e.g. wizbang should not be in the path
c:\program files\wizbang, but under c:\program files\wizsoft\wizbang\, but
plenty of apps do such nonsense).  Conventions on Linux include /usr/local/app
or /opt/app or /usr/app, all depending on what one is trying to accomplish.
Of course you can install on c:\windows\system32, or /usr/bin, but this is
just a bad idea when it comes to migration or OS upgrades.

> Reread my reply to you a little bit slower, and you will see what I was
> trying to say.  THe directory path I was giving you as an example was
> just that an example.  I use WAMP Server, and I installed it on my D:
> drive under d:\apache2.

I did :)  We don't disagree - that doesn't mean the user who keeps their
*programs* (easily replaced or upgraded) separate from backed-up important
customizations should have to use WAMP's pile-it-on model, or fight with
the default protections against the ASF installer.  TMTOWTDI

The only thing I noticed in your comment is that I like to keep all
unix-ported apps and frameworks on the same drive letter; some more
primitive ports are just not so good with drive letters.  Apache is fine
with them, but that doesn't mean all favorite cgi apps will be.  [You
could also make a compelling argument for keeping it on a different
drive letter than the OS, for that very reason.]

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message