Mail Archives: cygwin/2006/11/10/14:33:43
Eric Blake <ebb9 <at> byu.net> writes:
>
> Bret Weinraub <bretweinraub <at> yahoo.com> writes:
>
> >
> > Details:
> >
> > bash --version
> >
> > 3.2.3(5)-release
> >
> > sh --version
> >
> > 3.1.17(9)-release
>
> Evil. /bin/sh is supposed to be at the same version of bash, if you installed
> things correctly. It sounds like your postinstall scripts did not run
> correctly (perhaps you had bash or sh open when you ran setup.exe?). What are
> the timestamps on those files ('ls -l /bin/{ba,}sh')?
>
> At any rate, the fix is to rerun the postinstall scripts, or more
> quickly, 'cp /bin/bash /bin/sh'.
>
$ ls -l /bin/{ba,}sh
-rwxr-x---+ 1 NotTheRealUser Users 467968 Nov 2 19:22 /bin/bash
-rwxr-x---+ 1 NotTheRealUser Users 461824 Nov 7 16:20 /bin/sh
Next step - found bash/sh processes running under other sessions (logged in via
RDP) - terminated with extreme prejudice.
Re-installed via the CYGWIN installer (selected keep - told bash 3.2.3-5 to
reinstall) .... everything looked to be ok.
$ bash --version
GNU bash, version 3.2.3(5)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software Foundation, Inc.
$ sh --version
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software Foundation, Inc.
So maybe the post-install script has an issue ....
Took your recommended approach (with the copy).
igncr complaint went away ... but something else seems amiss from 3.1.17(6) -
will investigate when I can steal more time away from my real job.
--
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/
- Raw text -