> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stewart Stremler > Sent: Wednesday, January 18, 2006 6:01 PM > To: Main Discussion List for KPLUG > Subject: Re: Sed > > begin quoting Jon Wahlmann as of Wed, Jan 18, 2006 at > 11:52:30AM -0800: > > > One reason would be that not all UN*Xs have perl installed by > > > default, and some orgs don't let you install it just because it > > > would be useful. > > > Sed and awk are always there. So albeit a better tool, > doesn't mean > > > it is a tool you have. > > > > If you have shell access, install it in your home directory. > > With no quotas, and with /home mounted exec (something that > arguably shouldn't be done on production systems). > > If I said "no, we're not installing $tool" and the user did > so anyway, not only would it be silently removed in the > night, a cronjob would check for further breaches of policy. > (And if you object to that and you aren't running telnetd and > the r-services, you're a hypocrite.)
I guess I should have clarified... Assuming you are also given permission to install tools for your own use in "your" home directory. I have in the past compiled and installed perl in my home directory, even when I had root permission and could install it as I pleased under /usr/blahblahblah, just so I could test it out in a somewhat confined environment. One could do this (once again, assuming it's ok with the powers that be) so that it's just another tool in the specific user's toolbox (ie. $HOME/bin). That way Lan, or whomever, can still use Perl for their "Pattern Extraction and Reporting" needs without interfering with the "standard toolset" provided by the organization. -Jon -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
