On Tue, 5 Jul 2005, Igor Pechtchanski wrote: > On Tue, 5 Jul 2005, Eric Blake wrote: > > OK, then, does anyone else have ideas on how to determine if /bin/sh > > is ash with resorting to running it, and without resorting to packing > > an ever-increasing list of known md5sums of all prior versions in the > > bash postinstall script? > > I do. :-) Run "cmp /bin/bash /bin/sh" in the preremove script, when > you're guaranteed that if /bin/sh is bash, it's the exact same bash that > is currently installed.
I second that method. It's the only thing that makes sense to me. > Why all this effort of avoiding removing /bin/sh? The two times the > preremove script would be run are on uninstall and on upgrade. Uninstall > should be disallowed by other means (e.g., explicitly checking in setup > when packages in Base are uninstalled), and upgrades are harmless, IMO. > So why try to avoid removing /bin/sh in a preremove script? FWIW, I agree with this too. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
