Well, hostname may seem innocuous until you use it to change your hostname.
And ifconfig may seem innocuous when you only use the -a flag, but what if you take down your primary interface, you know, the one you just rsh'ed in on?
I can't and don't speak for the engineers, but I think the logic behind this is that by making you put the advanced mode in front of the command on an rsh, you're make a deliberate decision and hopefully avoiding a costly error.
Again, speaking only for me here, as an appliance, we walk the line between lots of cool features and safety and stability. To use the old rope analogy, we don't just sell rope. Rope can be very useful. So we sell pre-configured rope that while it can be formed to do neat things, it is special rope that (hopefully) won't form a neuse.
Advanced mode is one of those compromises. Most people don't use it and hopefully have no reason to use it. But for our more experienced rope-handlers, we try to provide a way to help those who say "I know I can handle my rope being more flexible and I understand that if I'm not careful, I might make a neuse or accidentally lasso myself". :)
Anyway, enough rope talk. I just thought I'd try to explain it a bit.
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
-----Original Message----- From: Julius Talbot [mailto:jstalbot@mail.com] Sent: Tuesday, August 28, 2001 10:04 AM To: toasters@mathworks.com Subject: Yet another rsh question
this I really don't get. Why are some commands available as "admin" privilege when you telnet in, and only available as "advanced" via rsh?
ie such innocent commands such as "hostname" and "ifconfig -a".
JsT
FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! http://www.net2phone.com/cgi-bin/link.cgi?143