On Wed, Dec 23, 2015 at 2:05 PM, Greg Wooledge <wool...@eeg.ccf.org> wrote: > [..] > On the one hand, we have draconian control-freak admins who want to > impose their policy on every user unconditionally, through things > like /etc/bash.bashrc (or /etc/bashrc or however the vendor chooses > to spell it). And now apparently even that's not enough for them. > They want to control SCRIPTS too. > > On the other hand, we have users like Rob, and like me, who just want > a vanilla environment with no interference and no surprises. > > Now, as I said, I'm on the second team, so clearly I am biased, but I > can't think of any good outcomes from a control-freak admin deciding to > inject code into every single script that runs on a system. That's going > to break things. A *lot* of things.
As a developer, sysop, and who knows what else I am also on your side. If the super user wants to break your script he will not have any difficulties with or without global initialization file. Maybe there is third alternative: restricted sourcing. Lets see what are the exact use cases, and maybe we can introduce a limited and restricted way to influence global bash behaviour. sincerely, pg
