On Wednesday 14 June 2006 10:51, Charles Hallenbeck wrote (edited): > changing the symbolic link > /bin/sh to point to /bin/zsh instead of /bin/bash. > > I changed the link to point to /bin/bash again, [ran apt commands > successfully > > But why? I do upgrades at least once a day, and they usually went > without a hitch using zsh. But evidently this was somehow the cause of > the current problem. > > It's a little vague to report it as a zsh bug just yet, I think. And I > am nervous about trying to replicate the problem. So what do I do? give > up zsh?
I believe the issue is that /bin/sh is expected to be a bourne shell, or at least closely compatible. zsh, "most closely resembles ksh but includes many enhancements." ksh has "command language [that is ] is a superset of the sh(1) shell language." While this means, in theory, ksh should do everything sh would do, there might be expected behaviors that zsh (which "resembles" ksh) does not live up to. j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
