From: terry white <twhite@aniota.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: authconfig defaults
Date: Tue, 3 Apr 2007 06:57:28 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0704030627000.10052@yossarian.aniota.com> (raw)
In-Reply-To: <954E3479CC27224785179CA04904214D05858CCE@0668-its-exmp01.us.saic.com>
... ciao:
: on "4-3-2007" "Kirkwood, David A." writ:
: make changes permanent in /etc/pam.d/system-auth
: since it always replaces the system-auth file with
who is responsible for YOUR system's security.
i have a hunch compiling source not your first inclination. i think
it fair to say most of this readership heen there. however, at some
point, it is prudent to to take command of your system, in lieu of
getting convenience.
in addition, when a problem noted with a package, i tend to get the
latest update from its source, rather than a backported kluge from a
distribution provider. the latter turns out to be a trap ...
--
... i'm a man, but i can change,
if i have to , i guess ...
prev parent reply other threads:[~2007-04-03 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 12:29 authconfig defaults Kirkwood, David A.
2007-04-03 13:57 ` terry white [this message]
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.58.0704030627000.10052@yossarian.aniota.com \
--to=twhite@aniota.com \
--cc=linux-admin@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).