On Thu, 27 Jan 2011, Michael Ryder wrote:
If the "magic" doesn't happen, why would I spend my time trying to reverse
engineer it? I'd rather let the programmers who wrote the program fix their
code, and get back to my primary concern of managing systems.
and here I think is part of the great divide.
on unix systems, the tools to manage systems are written by system
administrators, some at other companies, many were written years ago and
are good enough to not change, others may have been written by you. This
allows you to automate multiple changes to fit the workflow that makes
sense for your organization.
on windows systems, the tools to manage systems are written by the vendor,
usually designed to be easy for new people to figure out, and to
accomplish the things that the vendor's people expect you to want to do.
if you need to do something other than what the vendor's people expected
you to do, or you need to do one thing many times, you still have to try
and make it work through the GUI tool.
when I was getting started with *nix many years ago, one of the people
helping me said
"A GUI is like training wheels on a bicycle. On Unix you can take the
training wheels off, on Windows they are welded on"
David Lang
Mike
http://www.lostinthedetails.com
On Jan 27, 2011 4:52 PM, <[email protected]> wrote:
Jefferson Cowart made the following keystrokes:
I think this may explain a bunch. I have certainly seen many admins who
know how to do things i...
Before reading on, seperate concept from implementation.
While bringing with it a case of nightmares, anyone else recall the
button "smit happens"? How many GUI's out there go to the extent of
having a button to expose the command-line? I'm not saying that
smit or smitty was a great tool, but it shows to some extent that there
are people concerned about how things are done and the opertunity to
learn more about it so you can get to the point you don't ever want to
see that "running man" again.
The main point here is that this goes to show the mentality of people
dealing with *nix systems. There is a need, or at least strong desire,
to know what is going on. I don't think I've ever seen a windows gui
that presented the underlying command, or even an info box explaining
what was going to be done if you pushed that button.
Some could say that if the windows gui told you what it was doing, then
someone would try to do it without the gui and break things. Less calls
to he help desk if you restrict things to least breakable options. Others
would see this as a possibility to determine what didn't work right
when you pushed the button and magic didn't complete. Smoke but no
rabbit coming out of the hat.
/~\ The ASCII Gene Rackow email: [email protected]
\ / Ribbon Campaign Cyber Security Office voice: 630-252-7126
X Against HTML Argonne National Lab
/ \ Email! 9700 S. Cass Ave. / Argonne, IL 60439
_______________________________________________
Discuss mailing list
[email protected]
https:/...
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
