From: Andrey Repin <anrdaemon@freemail.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Portable shell code between Cygwin and Linux
Date: Sat, 30 Jul 2011 12:20:00 -0000 [thread overview]
Message-ID: <1686210011.20110730161401@mtu-net.ru> (raw)
In-Reply-To: <20110729201651.GB13084@calimero.vinschen.de>
Greetings, Corinna Vinschen!
>> For every shell code that I write, I'd like it to be portable both to Cygwin
>> on Windows, and to Ubuntu Linux for example.
>>
>> It's kinda possible, but am blocked with such a use case:
>>
>> alias vpnup='exec sudo openvpn --config ~/config/client.vpn --writepid /tmp/openvpn.pid &'
>>
>> While this worked perfectly under Ubuntu, I've had to make up a customized
>> version for Windows:
>>
>> alias vpnupwin='cd c:/home/sva/config; openvpn --config client.vpn --writepid c:/cygwin/tmp/openvpn.pid &'
> Don't use Win32 paths. Use POSIX paths:
> alias vpnupwin='cd /cygdrive/c/home/sva/config; openvpn --config client.vpn --writepid /cygdrive/c/cygwin/tmp/openvpn.pid &'
Moreover, the very first line is wrong.
Must be
alias vpnup='exec sudo openvpn --config $HOME/config/client.vpn --writepid /tmp/openvpn.pid &'
that's where his problem began, IMO.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 30.07.2011, <16:11>
Sorry for my terrible english...
--
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-07-30 12:20 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 [this message]
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
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=1686210011.20110730161401@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--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).