This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: vi stealing SYSTEM-owned permissions and ownership
- From: "Brian S. Wilson" <briansw at bellsouth dot net>
- To: "'D. Boland'" <daniel at boland dot nl>, <cygwin at cygwin dot com>
- Date: Mon, 4 Nov 2013 06:23:35 -0500
- Subject: RE: vi stealing SYSTEM-owned permissions and ownership
- Authentication-results: sourceware.org; auth=none
- Keywords: Miscellaneous
- References: <5274F396 dot A133C4CE at boland dot nl> <D7F32E9AFFD647458EB73E4ECBC03F3E at NCC1701> <52757448 dot 81FE6C53 at boland dot nl> <1139549616 dot 20131103022620 at mtu-net dot ru> <527698EA dot 16C8F45C at boland dot nl>
- Reply-to: <wilson at ds dot net>
> Haha, yes. But if my students have to administer remote
production-machines, most of the time they have no other option. I want them
to succeed where others fail.
If this is the case, why not use the Apache instance available through
Cygwin itself instead of implementing this Windows/Cygwin hybrid
environment? Your students would get a better feel for a Posix
implementation of Apache, and a standard set up if the environment were
consistent.
Please contact me if you have any questions or concerns.
Sincerely,
Brian S. Wilson
--
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