State of the SysAd art (was: vi or emacs for editing Python on Linux?)

[Steve Holden]

"Cameron Laird" <claird at starbase.neosoft.com> wrote in message
news:2E48C714A6E1FBA1.19DE5ADEBF7F088A.DF90F2C1E6CC9E7C at lp.airnews.net...
> In article <slrna2f8n3.b4n.grey at teleute.dmiyu.org>,
> Steve Lamb  <morpheus at here.not.there> wrote:
> .
> .
> .
> >    *sigh*  Fine,you had to bring it up.  Michael, I *do* work on unix
> >systems scattered across the nation and my personal workspace is not on
every
> >single one.  You know what is, though?  ssh.  That means scp is there so
when
> >I need to get something to/from that machine I can always scp to another
> >machine, edit, scp back.
> >
> >    Furthermore, when it comes to programming, I would hope that a
company
> >that has machines all over the world would have learned the joys of a CVS
> >server which would also fill in on the above.  Edit on one machine,
commit,
> >ssh to the machine that needs it, cvs update.
> .
> .
> .
> Does this match others' experience?  I continue to
> run into plenty of production hosts which have barely
> been maintained for up to four years, let alone
> outfitted with such new-fangled decorations as a
> properly-installed ssh.
>
> Do I hang around industrial environments too much?


Well, you probably do, but your experience and mine agree fairly closely --
several clients would rather retain a system configured and working as it is
than cope with the pain of re-establishing normal operations after an
upgrade.

Of course, now that more systems are on the Internet, Microsoft can also use
their crappy security as an excuse for getting customers to upgrade, rather
than selling them on features, sometimes of dubious value...

regards
 Steve
--
http://www.holdenweb.com/