This is the mail archive of the
mailing list for the Cygwin project.
RE: Executable links?
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: "Buchbinder, Barry (NIH/NIAID)" <BBuchbinder at niaid dot nih dot gov>
- Cc: "'chris'" <caj at cs dot york dot ac dot uk>, cygwin at cygwin dot com
- Date: Tue, 11 May 2004 18:26:48 -0400 (EDT)
- Subject: RE: Executable links?
- References: <F76C9B2DA2FC4C4CA0A18E288BBCBCF7082178DD@nihexchange24.nih.gov>
- Reply-to: cygwin at cygwin dot com
On Tue, 11 May 2004, Buchbinder, Barry (NIH/NIAID) wrote:
> WFM on XP:
> /bin> ln -s bash.exe b
> The following opens bash in a new window.
> /bin> cygstart b.lnk
> But in case you are worried that cygstart is doing some cygwin-type magic,
> the following also opens bash in a new window.
> /bin> cmd /c start b
> Opening explorer and double clicking on "b" opens bash in a new window.
> Perhaps you have the CYGWIN environmental variable a set to include
> "nowinsymlinks". See http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
Cygwin setup creates old-style symlinks by default, independent of the
> "use a proper shell" is likely to raise some hackles on this list. Perhaps
> you meant "use a 'native' shell".
FWIW, one can always run <<bash -c "awk 'commands'">>...
> -----Original Message-----
> From: chris
> Sent: Tuesday, May 11, 2004 4:21 PM
> Cc: cygwin<at>cygwin<dot>com
> Subject: Executable links?
> Just a couple of tiny questions / thoughts.
> A number of people (myself included) have been "caught" over the fact
> that cygwin shortcuts can obviously not be executed from a windows
> shell. There appears to me to be 4 ways of dealing with this
> 1) Ignore the problem, use a proper shell
> 2) On NTFS, use hard links. I did this for a while, then I thought I
> heard that it could cause problems when programs were updated
> 3) Have option to duplicate linked files. I've been doing this for a
> while now, and the loss of disk space is minimal
> 4) Replace links to executables with a very small executable which does
> the linking process. I've been experimenting a little with this and it
> doesn't seem like a bad idea, except a) it involves hacking where you
> want to link to into the executable (not too bad), b) the shortcut is no
> longer reckonised by ls / ln / etc (would this be hard to fix?) and c) I
> can't make a cygwin executable <10kish (this is still not that large,
> and I'm sure someone better than me could make it smaller.
> Any comments / suggestions?
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html