4 ms·
install it as /bin/sh, At first glance, I think that's your problem. Fundamentally, though, you can't always point to "it's this one component that is broken.
by danielweber 12y ago
install it as /bin/sh,
At first glance, I think that's your problem.
Fundamentally, though, you can't always point to "it's this one component that is broken." There is the classic example that was used to criticize Authenticode, which was Microsoft's way of dealing with mobile code back in the 1990's. It said "all the code is signed, so if something breaks, you know who to sue."
Well, imagine two programs:
1. One of them formats your hard drive, and on installation puts itself into your Quick Start list.
2. One of them runs every single program in your Quick Start list at start up.
Which piece of code is responsible for formatting your hard drive?
- scintill76 12y agoIt does indeed seem wrong to put magical behavior into /bin/sh, but that's exactly what's going on in this bug. bash is often installed as /bin/sh and is doing extra, non-standard, sparsely-documented behavior. I don't know that it really violates POSIX et al, but it definitely goes on the list of factors at fault. And yes, I agree it's difficult to assign blame.