From: Christopher Faylor <firstname.lastname@example.org>
Subject: Re: hardware upgrade status
Date: Wed, 20 Mar 2013 14:56:00 -0000 [thread overview]
Message-ID: <20130320145548.GB1576@ednor.casa.cgf.cx> (raw)
On Wed, Mar 20, 2013 at 01:46:19PM +0000, Dave Korn wrote:
>On 19/03/2013 21:30, Christopher Faylor wrote:
>> ----- Forwarded message from "Frank Ch. Eigler" -----
>> From: "Frank Ch. Eigler"
>> To: Sourceware Overseers
>> Subject: sourceware hardware transition plan, part 1/N
>> Date: Fri, 7 Sep 2012 17:46:32 -0400
>> I would like to move from unusual/obsolete services to mainstream ones if
>> at all possible, for simplicity of administration, and to reduce exposure
>> to vulnerabilities.
>> old: new:
>> djbdns bind
> Heh. That's a questionable statement, at best:
Yeah, in the djbdns case, it's more of a situation of not wanting to
stick with an arcane file layout. Most of us have more experience
dealing with bind. I've found the djbdns stuff hard to use.
The original plan was to get rid of all of the djb utilities but you
may have noticed that we're still using qmail and ezmlm. I'm very
comfortable with them.
>BTW, was it totally irrational of me to be so chuffed to see CGF using
>the term "administering" a server rather than "administrating"? I
>really dislike the latter usage.
I'm gratificated that you approve.
next prev parent reply other threads:[~2013-03-20 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130319162805.GA5736@ednor.casa.cgf.cx>
[not found] ` <20130319194322.GE40309@justpickone.org>
[not found] ` <20130319213054.GA1821@ednor.casa.cgf.cx>
2013-03-20 13:43 ` Dave Korn
2013-03-20 14:21 ` marco atzeri
2013-03-20 14:56 ` Christopher Faylor [this message]
2013-03-20 20:06 ` Linda Walsh
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).