Computer Old Farts Forum
 help / color / mirror / Atom feed
From: akosela at andykosela.com (Andy Kosela)
Subject: [COFF] 21st Century Equivalent to 'learn'?
Date: Fri, 06 Mar 2020 10:10:36 +0100	[thread overview]
Message-ID: <5e62138c.u8jVz6HNyEAN5KpZ%akosela@andykosela.com> (raw)
In-Reply-To: <CAC0cEp9XeonwiWPa38ooWEkxXPB=Jq7FPvx40x3xPZNDbo1z6w@mail.gmail.com>

"John P. Linderman" <jpl.jpl at gmail.com> wrote:

> Marc Rochkind used to recommend reading the entire UNIX manual each year.
> That was good advice in the late 70's, but it would be hopelessly
> impractical now, quite beyond the lack of a manual to read. There are just
> too many commands and libraries. A valuable service would be to identify
> the most useful tools. Those in the old manuals would be an interesting
> starting point, but I can't remember when I last used "ar" command, which I
> mostly used to pack multiple files into a single one to save inodes and
> wasted file system space, neither of which matter any more. If there were a
> corpus of contemporary shell scripts, identifying the most used commands
> could be interesting. Perl's CPAN (comprehensive perl archive network)
> could be a corpus of scripts from which the most commonly used system calls
> could be extracted.

I compiled such a list a couple of years ago.  Most of those commands
should be available on every major flavor of Unix and I consider them
"the core Unix tools".  This is not a final list, but commands I
personally use most often.  Certainly you can't call yourself a Unix
user if you have never consulted their manuals.

as, at, awk, basename, bc, cal, cat, cc, chmod, chown, cp, cut, date,
dc, dd, df, diff, du, env, expr, false, find, fmt, free, gdb, grep,
gzip, head, hexdump, id, iostat, join, ld, ldd, less, ln, ls, man,
md5sum, mkdir, mkfifo, mv, nice, nl, nohup, od, patch, passwd, paste,
pgrep, pkill, ps, pstree, rev, rm, rmdir, script, sed, seq, sh,
sha256sum, shuf, shutdown, size, sleep, sort, split, stat, strip,
strings, stty, su, sum, sysctl, tac, tar, tail, tee, top, touch, tr,
tree, uname, uniq, uptime, vmstat, w, wc, whatis, whereis, which, who,
whoami, xargs, yes

I specifically excluded all shell builtin commands and core network
related tools like ping(8).

It is interesting to note that still most of them come from the earliest
Unix versions.  It shows the ingenuity and beauty of the original
design.

--Andy


  parent reply	other threads:[~2020-03-06  9:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  3:49 wkt
2020-03-04  6:23 ` spedraja
2020-03-04  6:55   ` thomas.paulsen
2020-03-04  9:53   ` wkt
2020-03-04 19:31 ` dave
2020-03-05  1:00 ` wkt
2020-03-05 12:43   ` jpl.jpl
2020-03-05 21:23     ` arrigo
2020-03-06  3:14       ` grog
2020-03-06  9:10     ` akosela [this message]
2020-03-07 21:50       ` dave
2020-03-07 22:05         ` clemc
2020-03-07 23:02           ` dfawcus+lists-coff
2020-03-08  0:02             ` clemc
2020-03-06  3:39   ` bakul
2020-03-12 20:53 ` rtomek
2020-03-08  3:39 rudi.j.blom

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=5e62138c.u8jVz6HNyEAN5KpZ%akosela@andykosela.com \
    --to=coff@minnie.tuhs.org \
    /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).