Oh,
I remember the Smitty person running at the top that would fall down when the command
failed. Good times.
-LC$
On Aug 12, 2020, at 11:15 PM, Grant Taylor via TUHS <tuhs(a)minnie.tuhs.org> wrote:
On 8/12/20 7:47 PM, Larry McVoy wrote:
The SMIT I had did*not* show you what files it was
editing
My recollection is that smit(ty) did /not/ show you the commands that would be run /by/
/default/.
That being said, there was a (P)F key you could press prior to executing, one of the many
(P)F keys smit(ty) used, that would show you the command and all of it's arguments
which would be run.
I didn't like /using/ smit(ty) for much. But I did find it /useful/ for learning
things which I didn't know by using the menu a few times and analyzing the command(s)
that it would generate and run.
I think it was a really advanced form of "<bla> command example" searches
that I see people doing on the regular. The BIG advantage is that you used the menu
interface to tweak parameters for your configuration.
smit(ty) also had the added advantage that it could look up possible values of things to
put in the fields for you.
I don't know any seasoned AIX admins that use smit(ty) for their day to day, week to
week, or even month to month activities. Though I think many of them end up using
smit(ty) once every year or two to look at a particularly obtuse command. Sort of like a
contextual aware man page.
--
Grant. . . .
unix || die