Re: Retiring lpr and lpd

Tomoaki AOKI <[email protected]> Thu, 26 Feb 2026 08:15:48 +0900
Newsgroups gmane.os.freebsd.architechture
Organization Junchoon corps
Message-ID <[email protected]>
On Wed, 25 Feb 2026 17:42:39 -0500
John Baldwin <[email protected]> wrote:

> On 2/25/26 12:03, Dag-Erling Smørgrav wrote:
> > John Baldwin <[email protected]> writes:
> >> Dag-Erling Smørgrav <[email protected]> writes:
> >>> Let me get this straight, you intend to create a port for software
> >>> which is still in base (and is expected to remain there for at least
> >>> another year) and is known to be severely buggy?
> >> Uh, this is our standard operating procedure for moving things out of base,
> >> and Cy has helped with many of these:
> > 
> > No, it is not our standard operating procedure to create ports that
> > duplicate software which is still in base and is not expected to be
> > removed for at least a year, nor is it our standard operating procedure
> > to knowingly add vulnerable software to the ports tree.
> 
> Certainly if it is fine to defer the actual port creation until the
> software is removed.  That is fair.  However, I certainly expected in
> our earlier discussions that we would handle the removal by creating a
> port, and the resistance to that is a bit surprising to me.

It may be because removal of lpr family affects "regular users", too,
while former removal (moving to ports) of rcs affected basically
developers only, thus, can notice how they should cope with.

And on removal of r* remote shell family, there were in-base
alternative, ssh family. (Not drop-in replacements, though.)
So admins can calm them down easier, "don't worry, you can still use
ssh".

I think this resistances are because it affects "regular" users and
without in-base alternatives announced.

Regards.


> >> I'm surprised you are so out of touch with how we handle this given
> >> you are proposing removing something?
> > 
> > This is beneath you, John.  Do you want to check who maintains, say,
> > security/opie?
> 
> I was only responding in kind to your previous reply to Cy.  That doesn't
> justify it though and it was over the top.
> 
> -- 
> John Baldwin


-- 
Tomoaki AOKI    <[email protected]>