Subject: Re: setpwfile() deprecated. Why?
To: None <current-users@NetBSD.ORG>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
Date: 07/17/1996 07:33:48
> I was reading the getpwent(3) man page and there, at the very bottom
> of the page...
> in the middle of the very bottom of the page...
> away from everything ELSE at the very bottom of the page...
Heh. Alice, perchance?
> ...read the following words:
> The historic function setpwfile(3), which allowed the specification of
> alternate password databases, has been deprecated and is no longer avail-
(Actually, setpwfile allowed specification of _alternative_ databases.
Perhaps I should send-pr this.)
> I'm curious as to why setpwfile() was deprecated.
Probably about the same time networked passwd databases came in. Sun
did the same thing.
In both cases (NetBSD and Sun) I think it's stupid. It's just too
useful to be able to work on alternative databases, and deprecating it
really doesn't buy anything. (All I can see is the dubious benefit of
being able to throw away the plain-passwd-file parsing code, and that
only in our case - Sun still has it around, though we use db files.)
Yeah, you lose network databases if you setpwfile(). What's wrong with
that? Anyone calling setpwfile() presumably doesn't care about where
the system gets its live passwd data from.
01 EE 31 F6 BB 0C 34 36 00 F3 7C 5A C1 A0 67 1D