samba netbios / namedpipes domination: a comparison with linux having a proprietary web server built-in
Luke Kenneth Casson Leighton
lkcl at samba-tng.org
Wed Jan 9 17:11:08 GMT 2002
On Wed, Jan 09, 2002 at 05:53:44PM +0300, ntb at mts.ru wrote:
> I didn't compare samba's rpc parser with tng's one. I'm talking about freedce.
> Best thing we can get is samba's superior filesharing code (which improved
> by many developers by long time)
> working together with freedce's
> (not TNG!)
> rpc server. Which allow, in particularity, running some nice domain controller
> things from Luke Leighton. I didn't say from tng, he rewrite that code completely
> with freedce.
yep. projects are listed on dcerpc.net.
you can check them _all_ out at one time by checking out the
"meta" project named "tng". follow the cvs instructions
on http://dcerpc.net/cvs, using a project name of "tng".
it will grab tng/samrd, tng/netlogond etc etc all for you.
> > why don't you write the code yourself instead of arguing ?
> What do You offer me to write myself? file and print sharing server equivalent to samba?
> It take more than one century to do it alone for me. So it isn't an potion.
it's going to need cooperation from _everyone_ to tackle
that's the point of the TNG architecture: split the job
down into many smaller [sadly, still heavily interdependent]
sub-projects of less than an average 8 to 10,000 lines of code,
then people don't feel overwhelmed, and _can_ do their
bit in a three month period or six month part-time.
and, the point of the "named pipe" API is that whilst
you're implementing your own replacement samrd daemon,
you can either use samrd from samba-tng, or you can use
samrd.so from SAMBA-3, or you can answer the RPC calls
by typing out the hexdumps over a telnet connection,
or you can "proxy" the Samr requests to your very own
NT Primary Domain Controller.
the options - with the "named pipe" API - are unlimited.
the options _without_ the "named pipe" API are very, very
and limited to having detailed prior working knowledge
of the SAMBA-3 development enviroment.
More information about the samba-technical