On Sun, Jul 17, 2005 at 11:07:04PM -0700, Brian Dessent wrote:
> Igor Pechtchanski wrote:
> > Umm, why should rebaseall require a PATH setting at all? Wouldn't
> > it be easier to specify full paths for every command instead of
> > telling users to set their PATH?
>
> Well, if the user does not have /usr/bin in their Windows path
> (instead relying on /etc/profile to add it) and they try to run "ash
> rebaseall" from a command prompt, they will get an error about not
> finding cygwin1.dll unless /usr/bin is the CWD.
Actually, "ash rebaseall" will not work even if the user's PATH is set
correctly. Unlike bash, ash does not seem to search the PATH to find a
script to execute:
$ ash foo.sh
foo.sh: Can't open foo.sh: No such file or directory
But, the following work:
$ ash /home/jt/bin/foo.sh
foo
$ ash -c foo.sh
foo
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
