From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Portable shell code between Cygwin and Linux
Date: Mon, 08 Aug 2011 14:27:00 -0000 [thread overview]
Message-ID: <4E3FF23D.7040204@cs.umass.edu> (raw)
In-Reply-To: <4E3FA826.7090108@gmail.com>
On 8/8/2011 5:11 AM, Sven Köhler wrote:
> Am 08.08.2011 10:14, schrieb Andrey Repin:
>> Greetings, Sven Köhler!
>>
>>>> alias vpnup='exec sudo openvpn --config $HOME/config/client.vpn --writepid /tmp/openvpn.pid&'
>>>>
>>>> that's where his problem began, IMO.
>>
>>> I don't know, why you pointed that out. It's of no use to feed a path
>>> like $HOME/something to a pure win32 binary.
>>
>> You DON'T "feed a path like $HOME/something" !
>> The shell that run the script will expand variable before passing it to the
>> program.
>
> A win32 (non-cygwin) executable doesn't that /cygdrive/c refers to c:\.
> It also doesn't know that /home/bla is actually the same as
> c:\cygwin\home\bla. A win32 simply doesn't use cygwin, hence don't know
> about the translation from cygwin's POSIX paths to win32 ones.
>
> It turned out, that the OP was not using a cygwin version of openvpn.
> So if $HOME is a POSIX (cygwin specific) path, it won't work.
Hence my remark that you also have to know about and use (properly)
the cygpath utility, which can convert cygwin paths to ones for
Windows/DOS programs ...
Eliot Moss
--
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
next prev parent reply other threads:[~2011-08-08 14:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 19:15 Sebastien Vauban
2011-07-29 19:45 ` Larry Hall (Cygwin)
2011-08-01 6:40 ` Sebastien Vauban
2011-07-29 19:47 ` Eliot Moss
2011-08-01 6:45 ` Sebastien Vauban
2011-07-29 20:17 ` Corinna Vinschen
2011-07-30 12:20 ` Andrey Repin
2011-08-01 6:50 ` Sebastien Vauban
2011-08-01 7:28 ` Csaba Raduly
2011-08-02 11:58 ` Sebastien Vauban
2011-08-02 12:36 ` Sebastien Vauban
2011-08-05 16:05 ` Andrey Repin
2011-08-08 1:16 ` Sven Köhler
2011-08-08 2:07 ` Eliot Moss
2011-08-08 22:17 ` Gary Johnson
2011-08-08 8:20 ` Andrey Repin
2011-08-08 9:11 ` Sven Köhler
2011-08-08 14:27 ` Eliot Moss [this message]
2011-08-01 7:00 ` Sebastien Vauban
2011-08-01 7:44 ` Corinna Vinschen
2011-08-02 12:11 ` Sebastien Vauban
2011-08-02 12:23 ` Sebastien Vauban
2011-08-02 14:37 ` Corinna Vinschen
2011-08-01 9:21 ` Thorsten Kampe
2011-08-02 12:25 ` Sebastien Vauban
2011-08-02 15:41 ` Eliot Moss
2011-08-02 20:05 ` Thorsten Kampe
2011-08-02 20:45 ` Christopher Faylor
2011-08-03 16:23 ` Andy Hall
2011-08-08 1:20 ` Sven Köhler
2011-08-08 13:41 ` Eric Blake
2011-08-10 12:03 ` Sven Köhler
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=4E3FF23D.7040204@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).