I recently installed cygwin with some problems. This is the fourth installation of Windows where I have installed cygwin, and this has happened with this Windows installation twice now. I don't think it's a fluke. My guess is that it is only noticeable for new installations.
I was first greeted by a shell prompt like this: 'bash-3.2$' I notice there is no '/etc/profile', nor are there any home directories. Upon investigating /var/log/setup.log.full, I came across this: 2007/02/18 01:18:51 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/aalib.sh /usr/bin/bash: /etc/postinstall/aalib.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:18:55 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/autoconf.sh /usr/bin/bash: /etc/postinstall/autoconf.sh: No such file or directory 2007/02/18 01:18:58 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/autoconf2.1.sh install-info: No such file or directory for gzip.exe -cd </usr/share/info/autoconf2.13.info.gz 2007/02/18 01:19:00 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/autoconf2.5.sh install-info: No such file or directory for gzip.exe -cd </usr/share/info/autoconf2.61.info.gz install-info: No such file or directory for gzip.exe -cd </usr/share/info/standards.info.gz 2007/02/18 01:19:07 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake.sh /usr/bin/bash: /etc/postinstall/automake.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:07 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.10.sh /usr/bin/bash: /etc/postinstall/automake1.10.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:08 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.4.sh /usr/bin/bash: /etc/postinstall/automake1.4.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:09 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.5.sh /usr/bin/bash: /etc/postinstall/automake1.5.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:10 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.6.sh /usr/bin/bash: /etc/postinstall/automake1.6.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:12 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.7.sh /usr/bin/bash: /etc/postinstall/automake1.7.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:12 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.8.sh /usr/bin/bash: /etc/postinstall/automake1.8.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:14 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/automake1.9.sh /usr/bin/bash: /etc/postinstall/automake1.9.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:14 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/base-files-mketc.sh /usr/bin/bash: /etc/postinstall/base-files-mketc.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:15 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/base-files-profile.sh /usr/bin/bash: /etc/postinstall/base-files-profile.sh: /bin/sh: bad interpreter: No such file or directory 2007/02/18 01:19:15 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/bash.sh So to fix my problem, I typed this: $ export PATH=/bin:/usr/bin $ cd /etc/postinstall $ ./base-files-profile.sh.done This appeared to fix the problem without any errors (after starting another login shell), but to be certain I re-ran all the scripts above that failed. I am hosting the relevant files here for all who are interested: http://www.itlabs.umn.edu/~pelo0036/cygwin/cygcheck.txt.bz2 (6 kB) http://www.itlabs.umn.edu/~pelo0036/cygwin/setup.log.bz2 (10 kB) http://www.itlabs.umn.edu/~pelo0036/cygwin/setup.log.full.bz2 (328 kB) Mark -- 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/
