valdis(_dot_)kletnieks(_at_)vt(_dot_)edu wrote:
On Thu, 13 Apr 2017 09:55:19 -0400, Ken Hornstein said:
Normally I would suggest deprecating this feature and then removing it
after the next release, but it's impacting reasonable behavior NOW, and
fixing the core dump issue here just means trying to comprehend a pile
of code that's just a mess and that we all agree needs to go. So what
do people think of just getting rid of all of it now?
The chances that somebody is *still* relying on using /etc/groups as a
mailing list database, *and* likely to upgrade to the next release of nmh,
are vanishingly slim. I say heave it over the side and mention it in the
Changelog, and move on.
+1.
I've only been using an MH derivative since 1988,
and even back then I would have called using /etc/groups for that a totally
bonkers idea, since it's overloading group semantics with possible security
implications...
since it was the only application for getgrent other than groups(1), i
have always thought this was quaint. however, large timeshared single
instance systems will never increase in population, and will decrease.
it's far more likely that i will have 100 small system images, most of
which have only be in the /etc/groups file, then that any system image
will ever again have 100 users with mailboxes and shell access.
--
P Vixie
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers