From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin <cygwin@cygwin.com>, Chris Faylor <cgf@redhat.com>
Subject: Re: fetchmail/procmail/jed -- cygwin binaries available?
Date: Fri, 16 Mar 2001 05:53:00 -0000 [thread overview]
Message-ID: <20010316145311.B20900@cygbert.vinschen.de> (raw)
In-Reply-To: <3AB21626.6FB1FBC@yahoo.com>
On Fri, Mar 16, 2001 at 08:33:26AM -0500, Earnie Boyd wrote:
> Corinna Vinschen wrote:
> >
> > In theory that should be no problem. As a first hack simply
> > uncomment these calls or ignore the return value. If maildrop
> > uses strict chmod settings, open them up. If maildrop then works
> > without complaining we could care to rearranging security again.
> > I have written a function for OpenSSH which checks if security
> > makes sense, dependent of the used file system and if ntea/ntsec
> > are on or off. We could recycle that functionality as desired.
> >
>
> Or, should this become an official Cygwin specific API? Then you
> wouldn't have to recycle, it would simply be the way you do it.
Good point. Chris? Do you think that makes sense?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-03-16 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 17:56 Duke Normandin
2001-03-14 18:06 ` Michael Erdely
2001-03-14 18:16 ` Rue. SATOH
2001-03-15 3:50 ` Corinna Vinschen
2001-03-15 17:49 ` Rue. SATOH
2001-03-16 0:33 ` Corinna Vinschen
2001-03-16 5:33 ` Earnie Boyd
2001-03-16 5:53 ` Corinna Vinschen [this message]
2001-03-16 8:00 ` Chris Faylor
2001-03-16 9:00 ` Corinna Vinschen
[not found] ` <20010315074142.B121351@mandy.rockingd.calgary.ab.ca>
2001-03-15 17:41 ` Rue. SATOH
2001-03-14 21:04 ` Enoch Wu
2001-03-15 8:32 ` Malcolm Boekhoff
2001-03-15 10:04 ` Enoch Wu
2001-03-15 13:36 ` Dmitry Yaitskov
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=20010316145311.B20900@cygbert.vinschen.de \
--to=cygwin@cygwin.com \
--cc=cgf@redhat.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).