Re: [OT] Alternative, supplement to Perl for sysadministration?

After i learned the hard way that Perl is "mainly" designed to manipulate text (and fine for cgi) and as a "glue language" i wonder what else should i maybe learn ...

Yes....

"Python"? for sysadmin tasks in alternative or supplement to shell/bash/perl?

Wait. What do you mean "glue language" means? I've been doing sysadmin tasks for over 20 years. Sysadminning is mostly glueing.

I don't know any language that's more suitable for sysadminning than Perl, and I don't think there's an area that's more suited for Perl than sysadminning.

I read some wikipedia articles

Wikipedia articles usually tell the opinions and beliefs of the last person editing it.

Comment on Re: [OT] Alternative, supplement to Perl for sysadministration?

Replies are listed 'Best First'.
Re^2: [OT] Alternative, supplement to Perl for sysadministration? by matze77 (Friar) on Jan 07, 2009 at 00:28 UTC
Nice arguments. Thanks. The other point which i meant "hard way" was not so easy to complete for me (at the beginning) was to move some files around it felt a little (forgive me) like shooting myself into the knees, so i went back to bash where i knew how to do it. Meanwhile i learned i have to use cpan and function like File::Copy http://perldoc.perl.org/File/Copy.html TIMTOWTDI is something a beginner has sometimes his difficulties with (like i had with Linux a few years back, which i never regretted to dig into) to see the trees ... I like Perl and its definitive worth it Thanks in Advance MH	[reply]
Re^3: [OT] Alternative, supplement to Perl for sysadministration? by JavaFan (Canon) on Jan 07, 2009 at 00:37 UTC
Odd that you mention File::Copy. As a sysadmin, I care about file permissions. 'cp' cares about them too. Hey, even POSIX cares about them enough to specify how 'cp' should behave with respect to file permissions. File::Copy doesn't care about file permissions - the permissions it creates for a newly created file are independent of the original file. Hate! A copied executable should be executable, but File::Copy disagrees. Therefore, I always use `system 'cp', $source, $destination`. Not to mention that `system 'cp', @sources, $destination` just works.	[reply]