[Slackbuilds-users] oidentd

[B. Watson]

On Sat, 7 Sep 2024, dchmelik at gmail.com wrote:

> On 9/7/24 1:37 AM, B. Watson wrote:
>> On Sat, 7 Sep 2024, dchmelik at gmail.com wrote:
>>>     If anyone uses oidentd on servers, please consider taking it over.
>> 
>> oidentd is maintained by Mario Preksavec... who appears to be an
>> active maintainer (last activity was July 2, 2024, taking over as
>> maintainer of rtl-sdr). Have you contacted him?
>
> I mentioned doing so, on this mailing list, some months/years ago, saying he 
> is thinking of no longer maintaining it, and it's some versions behind.  I 
> think you're the person who replied to that and suggested I take it over (I'm 
> not going to).

OK, yes, I do remember suggesting that. I said it because apparently
you are the only person in the SlackBuilds universe who cares about
oidentd (its own maintainer doesn't, apparently).

Also in your previous email, you stated that oident.SlackBuild can
build the newer versions of oidentd just by updating VERSION. So,
it would make sense for you to take over the script, update VERSION,
make sure the new version actually runs, and call it a day. What do
you think a maintainer *does*, exactly?

Another thought:

I have no idea what you're using oidentd for. The usual use is for
IRC, but don't think modern IRC networks actually require it. At least
libera doesn't, I know for a fact.

Slackware already ships two identd's: the regular /usr/sbin/in.identd,
and a "fakeidentd" inside the /usr/share/mkinitrd/initrd-tree.tar.gz
tarball (which is just a symlink to a busybox binary, also found in
that tarball). Maybe one of these would serve your needs?