Date: Mon, 21 Apr 2003 01:15:32 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: "Jacques A. Vidrine" <nectar@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/include pwd.h src/lib/libc/gen getpwent.c src/usr.sbin/pwd_mkdb pwd_mkdb.c Message-ID: <20030421011154.G1446@znfgre.tberna.bet> In-Reply-To: <20030420230000.GB32112@madman.celabo.org> References: <200304181411.h3IEBH07088819@repoman.freebsd.org> <20030420230000.GB32112@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Apr 2003, Jacques A. Vidrine wrote:
> On Sun, Apr 20, 2003 at 02:19:55PM -0700, Doug Barton wrote:
> > I've already told Jacques that I'd look into the problem with named, but
> > more generally, I doubt this will be our only problem child. Has this new
> > code been regression tested against any other third party code?
>
> I suppose no more or less than is expected for -CURRENT.
Heh... well, I suppose what I meant was, for example, compiling a standard
desktop system from scratch on a system running this new code.
> It happens that I don't use BIND8, so I missed this issue. It
> didn't occur to me that applications would use our internal
> definitions. (Note the underscores in _PW_KEYBYNAME et. al.)
> Moreover, it didn't occur to me that applications would not use
> getpwent(3) and friends to access system databases. (I believe this
> is a bug in our BIND installation.)
Not using BIND? Heresy! :) Seriously though, what I'm trying to get across
is that while what named seems to be doing is definitely wonky, it's
probably not the only code doing it. Binary compat is excellent of course,
but things that you could compile and run prior to the nss import should
still compile and run after.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030421011154.G1446>