[sane-devel] SUSE9.1: sane-port in /etc/services

Olaf Meeuwissen olaf@epkowa.co.jp
Wed, 26 May 2004 08:48:30 +0900

Mattias Ellert <mattias.ellert@tsl.uu.se> writes:

> Olaf Meeuwissen wrote:
>> So that leaves me with the question how this is best fixed:
>>  1) badgering IANA to change it to sane
>>  2) preparing a patch for the net backend, its manual page and any
>>     other docs that refer to the "sane" service
>>     # This sane/sane-port confusion will likely become FAQ, btw.
>> Suggestions any1?
> The correct way to fix this is to make the xinetd configuration use
> the official name. That is, the saned xinetd config file should
> contain the line 'service sane-port'.
> If the xinetd configuration does not match a service name in the
> /etc/services file it is ignored by xinetd, since in this case xinetd
> doesn't know on which port to listen for connections.

I know that much, but all the sane-backend stuff mentions the "sane"
service only, AFAIK.  If Henning went through the trouble of getting
the "sane-port" service registered with IANA (instead of "sane") then
shouldn't the implementation be patched to match?  If Henning meant to
register the "sane" service, then something went wrong in getting that
across and IANA registered the wrong service.

Question stands: what is the prefered way to fix this?
Olaf Meeuwissen                            EPSON KOWA Corporation, PF1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2