From: "Mack, Daemian" <DMack@Tickets.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: cygwin Registry Entries and Scriptability?
Date: Thu, 14 Feb 2002 13:05:00 -0000 [thread overview]
Message-ID: <AA200D15A29A574DA33D98B75E6E5D990452EF8A@syrs-mail.back.tickets.com> (raw)
> On Thu, Feb 14, 2002 at 03:27:04PM -0500, Mack, Daemian wrote:
> >I do realize this. What I'm asking is no more than this: is
> a full Cygwin
> >installation required in order for bash.exe to use rsync.exe
> to read from
> >and write to the local Windows filesystem? Or are these two
> files -- plus
> >the cygwin.dll -- sufficient for this purpose?
>
> Hmm. Didn't my response suffice?
Judging by the evidence before us, the answer here is clearly no. But thank
you for trying.
> If you are finding that the three files
> work, then obviously you don't need anything else.
Well, that's what two hours of tinkering on a couple of Windows boxes have
suggested. I'd obviously require independent confirmation before I go
mucking about with customers' production data. I think I've gotten it now;
I appreciate your input.
Daemian Mack
--
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/
next reply other threads:[~2002-02-14 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 13:05 Mack, Daemian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 13:04 Cygwin " Mack, Daemian
[not found] <AA200D15A29A574DA33D98B75E6E5D990452EF86@syrs-mail.back.ti ckets.com>
2002-02-14 12:36 ` Larry Hall (RFK Partners, Inc)
2002-02-14 12:28 Mack, Daemian
2002-02-14 12:36 ` cygwin " Christopher Faylor
[not found] <AA200D15A29A574DA33D98B75E6E5D990452EF85@syrs-mail.back.ti ckets.com>
2002-02-14 12:20 ` Cygwin " Larry Hall (RFK Partners, Inc)
2002-02-14 11:52 Mack, Daemian
2002-02-14 12:13 ` cygwin " Christopher Faylor
2002-02-14 12:25 ` Larry Hall (RFK Partners, Inc)
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=AA200D15A29A574DA33D98B75E6E5D990452EF8A@syrs-mail.back.tickets.com \
--to=dmack@tickets.com \
--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).