-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Alexei Alexandrov on 12/7/2006 9:32 AM: >> >> Also, could you send the output of: >> >> $ grep -C5 00bash.sh /var/log/setup.log/full >> >> to see if it captured any error messages from the attempted cp? >> > > The grepped setup log is attached (it is from setup.log, by the way - > setup.log.full is surprisingly small).
Actually, it was setup.log.full that I wanted, since that is the file where the postinstall script redirects the output from 'cp -v' - really, what I'm looking for from someone who has a failed /bin/sh upgrade, is the reason for the failure (for example, whether it was because sh.exe was in use, or because of permissions issues, etc.). Until I know why it failed, I can't work around it, since I haven't been able to reproduce a failure in my tests so far. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFeN0s84KuGfSFAYARAiLJAJ908CzEjWOq4yvYwkhJ/0mmVJwZawCePtL0 JODdl6NkxGaLIN7BSuyLLHA= =OzzO -----END PGP SIGNATURE----- -- 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/
