Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 19 Jan 2002 16:07:03 +0100 From: Corinna Vinschen To: cygwin Subject: Re: no output from net.exe Message-ID: <20020119160703.Q11608@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <20020118224524 DOT M11608 AT cygbert DOT vinschen DOT de> <003601c1a0b3$59cf9110$0500a8c0 AT TheLoveShack DOT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003601c1a0b3$59cf9110$0500a8c0@TheLoveShack.local> User-Agent: Mutt/1.3.22.1i 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/