Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 21 Jan 2002 18:07:58 -0500
From: Alex BATKO <abatko AT milquetoast DOT cs DOT mcgill DOT ca>
To: cygwin AT cygwin DOT com
Subject: Re: no output from net.exe
Message-ID: <20020121180758.V9029@cs.mcgill.ca>
References: <20020118224524 DOT M11608 AT cygbert DOT vinschen DOT de> <003601c1a0b3$59cf9110$0500a8c0 AT TheLoveShack DOT local> <20020119160703 DOT Q11608 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020119160703.Q11608@cygbert.vinschen.de>; from cygwin@cygwin.com on Sat, Jan 19, 2002 at 04:07:03PM +0100





+-------------------
| On Sat, Jan 19, 2002 at 12:34:19AM -0600, Alex Malinovich wrote:
| > >You could write a script.  That's even more fun than setting
| > >all user/group/permission info by hand.  Treat it as challenge.
| > >
| > >Corinna
| > 
| > Actually, this almost sounds fun... :) Correct me if I'm wrong here, but
| > if Perl read the attributes of a file, they'd be reported in the same
| > way as they would for ls. (i.e. Using whichever setting ntea or ntsec
| > reported.) And if it tried setting those attributes, they'd still be
| > handled by Cygwin. (i.e. Taking ntea or ntsec into account.) Seems
| > pretty simple. Or am I missing something obvious here?
| 
| Nope.  As long as it's Cygwin perl.  Just read the attrs with ntea
| and write them with ntsec.
| 
Please confirm that this recursion only has to be done for cygwin's
subtree (from /), and not for the entire c:\ tree.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/