Hi,
On Wed, May 26, 2004 at 08:48:30AM +0900, Olaf Meeuwissen wrote:
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
Mattias Ellert mattias.ell...@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
#
On Wed, 26 May 2004 08:48:30 +0900
Olaf Meeuwissen wrote:
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
Matt mathfretw...@blueyonder.co.uk writes:
On Wed, 26 May 2004 08:48:30 +0900
Olaf Meeuwissen wrote:
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
On Wed, 26 May 2004 13:26:30 +0900
Olaf Meeuwissen wrote:
grepped for sane
Conversely though, if you had just grepped /etc/services for sane, you would
have then had the definite answer as to the port and name. This is in all
honesty an apples and pears type discussion. Documentation can be
Hi every1,
While test driving Image Scan! for Linux on the SUSE 9.1 beta, I
bumped into a little problem that all of a sudden the net backend
failed to find my (localhost) scanner.
Checking out the configuration, I found
sane-port 6566/tcp SANE Control Port
sane-port 6566/udp
This is a cryptographically signed message in MIME format.
--ms090604060909090505030408
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Olaf Meeuwissen wrote:
So that leaves me with the question how this is best fixed:
1) badgering IANA
