On Wednesday 22 September 2010 17:18:46 [email protected] wrote: > In either case, start by forcing yourself to use the command > line tools, not the GUIs, because: > 1. The command line is more similar across distros than the GUIs > are (with a few exceptions). > 2. When you're trying to administer a machine on the other side > of the planet, the command line is all you have. (or even when > doing something to a machine in a locked room down the hall!) > 3. you'll end up understanding more of what's going on.
+1 on learning the command line. The original question was being asked in the context of servers, which I assume is because the poster wants to do this for career purposes. When I used to interview potential sysadmins (before I was tempted by the dark side and became a lawyer), all the technical questions I asked during the interview were about the command line and standard configuration files (as in standard across not just Linux systems but other Unix and Unix-like systems). In my experience, the sysadmins who know these things can deal with pretty much anything they need to (and can figure out the rest in no time flat). On the other hand, sysadmins who only know the GUI will be stuck as soon as anything goes wrong. -- Regards, Troy Rollo Solicitor Parry Carroll Commercial Lawyers Direct: (02) 8257 3177 Fax: (02) 9221 1375 Switch: (02) 9221 3899 E-mail: [email protected] Web: www.parrycarroll.com.au Liability limited by a scheme approved under Professional Standards Legislation This message and any attachments are confidential to Parry Carroll. If you have received it my mistake, please let us know by reply and then delete it from your system. You must not copy the message, alter it or disclose its contents to anyone. Thank you. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
