lkcl vs. the samba team

I implemented basic (non-network) Named Pipes Support in the Wine project. I am investigating how to add support for Named Pipes over the network.

After reading Luke's article on the front page, i have to say i mostly agree with what he says. Despite his bitterness, he does have a point.

Samba is the NetBIOS gateway in Linux, yet the leaders of that project have provided no way for any non-samba code to access NetBIOS functionallity. Windows multiplexes almost all it's network access through ports137 and139. They should at least accept a few basic hooks so that others can get the job done. The Samba teams' attitude is basically just port-hogging.

Perhaps the best solution is to write another port 139 listening daemon that sorts through requests and passes accesses to shares to samba... to get under samba. Such a thing would cause a great performance hit, but maybe then the Samba team would get the message...

my $0.02 worth.