public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "D. Boland" <daniel@boland.nl>
To: cygwin@cygwin.com
Subject: Re: vi stealing SYSTEM-owned permissions and ownership
Date: Wed, 27 Nov 2013 18:11:00 -0000	[thread overview]
Message-ID: <529634BE.C59ADC76@boland.nl> (raw)
In-Reply-To: <52788702.B100AA7A@boland.nl>

Again, thanks for the input. I's now about three weeks later. I made all of my
students re-install Apache in:

/cygdrive/c/Apache2

and made them symlink this location on:

/usr/local/apache

For me, Achim Gratz's comment on the "Program Files" folder made perfect sense:

>If you are operating as a normal user on this folder, you aren't
>actually editing the files you think you see there, the whole contents
>is virtualized by UAC and redirected to your own personal copy on edit.
>If you want to keep your sanity, do not place anything that you intend
>to edit / change as a normal user into system directories on Win7 (that
>includes Cygwin itself).

I am also a software developer, and most of my releases are installed on MS Citrix
servers for remote desktop connections. I initially made the mistake to put all
files in the "Programs Files" folder, including the executable, the database and
configuration files (.ini).

This works fine on a stand-alone XP/Win7 PC, but in a Citrix environment this
crashes the application, because of lacking write permissions on the .ini files.
Then I found out about the "Application Data" folder. Releasing my database and .ini
files to that folder solved the problem. MS has an article about it:

http://msdn.microsoft.com/en-us/library/windows/apps/jj553522.aspx

This would mean that in order to install Windows native and avoid virtualization of
the conf files the Apache Group should release Apache for Windows into both "Program
Files" and "Application Data":

Program Files
-------------
bin
error
icons
include
lib
manual
modules

Application Data
----------------
cgi-bin
conf
htdocs
logs
proxy

Thanks again for the comments,
Daniel

-- 
Sent by my Altair 8800


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2013-11-27 18:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 12:55 D. Boland
2013-11-02 13:36 ` Brian S. Wilson
2013-11-02 18:42   ` Andrey Repin
2013-11-02 21:58   ` D. Boland
2013-11-02 22:35     ` Andrey Repin
2013-11-03 18:47       ` D. Boland
2013-11-03 22:05         ` Andrey Repin
2013-11-04 11:23         ` Brian S. Wilson
2013-11-04 14:54           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 17:05             ` Larry Hall (Cygwin)
2013-11-05  5:54 ` D. Boland
2013-11-05 17:38   ` Achim Gratz
2013-11-08 14:25     ` D. Boland
2013-11-08 15:59       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-08 20:20       ` Andrey Repin
2013-11-27 18:11   ` D. Boland [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=529634BE.C59ADC76@boland.nl \
    --to=daniel@boland.nl \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).