From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Stupid kernel question
Date: Tue, 29 Aug 2000 21:12:16 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0008292105280.25675-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0008292042330.4017-100000@wb2flw.octothorp.org>
They probably use cat because the author just does it that way. Perhaps he
uses it to overwrite what is there and doesn't want to bother with forcing
or confirming it. And so he wrote the book with how he does things.
I have been around too long and seen too many such things to believe that
this would be much different. I hope that the certification will be such
that one need not learn the test writer method of doing business. But I
don't hold out a lot of hope. The certification would certainly be out on
its own if that is pulled off. (I recall one particular stupid M$
certification question that if you failed to use the search command to
find a server you missed the question.
To me that would be like assuming you don't know the idiosyncracies of
your distribution. Let's face it, all distributions have them. But if you
are a competent administrator, you will know them, or learn them if faced
with a machine from an unfamiliar distro.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Buddy Brannan's message of "Tue, 29 Aug 2000 14:41:21 -0500">
` Buddy Brannan
` Kirk Wood
` Kirk Reiser
` Buddy Brannan
` Frank J. Carmickle
` Kerry Hoath
` Brent Harding
` Kerry Hoath
` William F. Acker WB2FLW +1-303-777-8123
` Kirk Wood [this message]
` brian Moore
` Buddy Brannan
[not found] ` <Pine.LNX.4.21.0008291413280.25675-100000@localhost.localdo main>
` Brent Harding
` Geoff Shang
` Brent Harding
` Geoff Shang
` Brent Harding
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=Pine.LNX.4.21.0008292105280.25675-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).