James Carlson wrote: > - A description of how the "safety net" might plausibly be used. > I'm not talking about trivial cases here (such as old hacks the > user might have in $HOME/bin), but rather the hard ones, such as > third party code. Just what does a user do?
Two solutions: 1. Edit the scripts which break and change #!/usr/bin/ksh to #!/usr/bin/oksh If this does not help or causes to much trouble there is... 2. ... make /usr/bin/ksh a link to /usr/bin/oksh to get the full backwards-compatibility back. IMO a script should be created for that which does the switch into both directions and tests which shell is actually currently available as /usr/bin/ksh (and even uses /usr/bin/logger to "annouce" this to the system log to log the exact moment of the switch (e.g. have an exact marker)). Maybe the idea of a switch script would solve much of the initial concerns here: We give the people (e.g. system adminstrator) the freedom to select which ksh version is used for /usr/bin/ksh (with ksh93 being the default after installation), satisfying the needs of both sides. Any comments on that ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
