From: Larry Cashdollar via TUHS <tuhs@minnie.tuhs.org>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] A/UX [was Linux is on-topic]
Date: Thu, 13 Aug 2020 00:02:20 -0400 [thread overview]
Message-ID: <21D18F80-1F88-4380-AA24-AEE5F815ACD0@me.com> (raw)
In-Reply-To: <f082c6df-a3d3-c8b4-631e-97c6221245ae@spamtrap.tnetconsulting.net>
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@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
next prev parent reply other threads:[~2020-08-13 4:12 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:08 [TUHS] H.J. Lu Bootable Root & Base System disks Norman Wilson
2020-07-17 18:14 ` John Cowan
2020-07-17 18:19 ` Larry McVoy
2020-07-17 19:53 ` [TUHS] Linux is on-topic Warren Toomey
2020-07-17 19:57 ` Larry McVoy
2020-07-17 20:00 ` Adam Thornton
2020-07-17 20:04 ` Larry McVoy
2020-07-17 20:03 ` Dan Cross
2020-07-17 23:31 ` A. P. Garcia
2020-07-19 10:26 ` emanuel stiebler
2020-07-17 20:07 ` Warren Toomey
2020-07-17 20:12 ` Warner Losh
2020-07-17 20:19 ` Clem Cole
2020-07-19 9:54 ` Sergio Pedraja
2020-07-17 20:08 ` Michael Kjörling
2020-07-17 20:55 ` Grant Taylor via TUHS
2020-07-17 21:28 ` Michael Kjörling
2020-07-18 20:22 ` Ed Carp
2020-07-18 20:29 ` Warner Losh
2020-07-19 2:31 ` Gregg Levine
2020-07-19 3:46 ` Wesley Parish
2020-07-19 4:42 ` Grant Taylor via TUHS
2020-07-19 18:01 ` Michael Parson
2020-07-20 8:47 ` [TUHS] A/UX [was Linux is on-topic] arnold
2020-07-20 9:46 ` Arno Griffioen
2020-07-20 16:35 ` Arthur Krewat
2020-07-20 17:44 ` Arno Griffioen
2020-07-20 19:07 ` Rich Morin
2020-07-20 19:45 ` Al Kossow
2020-07-20 19:49 ` Al Kossow
2020-07-24 0:01 ` Chris Hanson
2020-07-20 20:20 ` Ed Carp
2020-07-20 21:02 ` John Cowan
2020-07-20 22:27 ` Ed Carp
2020-07-24 0:04 ` Chris Hanson
2020-07-31 23:02 ` Dave Horsfall
2020-07-31 23:12 ` Richard Salz
2020-08-01 1:36 ` Larry McVoy
2020-08-01 16:08 ` Nemo Nusquam
2020-08-01 17:01 ` Arthur Krewat
2020-08-13 0:00 ` Dave Horsfall
2020-08-13 1:47 ` Larry McVoy
2020-08-13 3:15 ` Grant Taylor via TUHS
2020-08-13 4:02 ` Larry Cashdollar via TUHS [this message]
2020-08-31 21:12 ` Dave Horsfall
2020-09-03 14:10 ` Michael Parson
2020-08-13 1:53 ` Nemo Nusquam
2020-08-13 17:14 ` Dan Cross
2020-08-13 17:19 ` Henry Bent
2020-08-13 17:58 ` Warner Losh
2020-08-13 20:04 ` John Cowan
2020-08-13 20:52 ` Dan Cross
2020-08-14 17:31 ` Paul Winalski
2020-08-15 1:24 ` Dave Horsfall
2020-08-18 13:57 ` Derek Fawcus
2020-08-18 14:11 ` John Cowan
2020-08-31 21:20 ` Dave Horsfall
2020-08-13 19:18 ` Adam Thornton
2020-08-13 19:28 ` Warner Losh
2020-08-13 20:15 ` [TUHS] AIX link repost [was " Charles H Sauer
2020-08-13 20:09 ` [TUHS] " Rich
2020-08-13 20:16 ` Larry McVoy
2020-08-13 20:17 ` Dr Iain Maoileoin
2020-08-14 1:04 ` Christopher Browne
2020-08-14 17:18 ` Jim Capp
2020-08-14 17:37 ` Jim Capp
2020-08-14 17:39 ` Jon Steinhart
2020-08-15 0:33 ` Rich
2020-08-15 1:20 ` Larry McVoy
2020-08-15 2:08 ` Dave Horsfall
2020-08-15 2:47 ` Warner Losh
2020-08-15 17:44 ` Paul Winalski
2020-08-15 12:05 ` Thomas Paulsen
2020-08-15 1:33 ` Jon Steinhart
2020-08-15 2:02 ` Dave Horsfall
2020-08-15 2:45 ` Andrew Hume
2020-08-15 16:55 ` William Cheswick
2020-08-15 3:29 ` Larry McVoy
2020-08-15 1:40 ` Gregg Levine
2020-08-13 22:24 ` Grant Taylor via TUHS
2020-07-24 0:02 ` Chris Hanson
2020-07-20 9:48 ` Andrew Warkentin
2020-07-20 11:49 ` Larry McVoy
2020-07-20 14:36 ` Clem Cole
2020-07-20 17:24 ` John Cowan
2020-07-20 22:11 ` Ed Carp
2020-07-21 1:04 ` Larry McVoy
2020-07-22 3:13 ` tytso
2020-07-22 5:40 ` Bakul Shah
2020-07-22 14:16 ` Larry McVoy
2020-07-20 12:32 ` Derrik Walker v2.0
2020-07-20 12:54 ` Andrew Warkentin
2020-07-21 1:50 ` Larry McVoy
2020-07-21 2:30 ` Gregg Levine
2020-07-22 3:44 ` Jason
2020-07-22 12:23 ` Derrik Walker v2.0
2020-07-20 14:28 ` Clem Cole
2020-07-22 3:50 ` Jason
2020-07-22 4:26 ` Henry Bent
2020-07-24 0:10 ` Chris Hanson
2020-07-20 0:24 ` [TUHS] Linux is on-topic Ed Carp
2020-07-22 3:41 ` Jason
2020-07-22 16:15 ` Michael Parson
2020-07-18 3:34 ` Tomasz Rola
2020-07-18 16:45 ` Christopher Browne
2020-07-19 7:32 ` Lars Brinkhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21D18F80-1F88-4380-AA24-AEE5F815ACD0@me.com \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--cc=larry0@me.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).