[NBLUG/talk] why is Samba so bloody awful

Bob Blick bobblick at covad.net
Mon Nov 17 12:57:01 PST 2003


Thanks for replying.

ME said:
> I think that documentation that is "to the point" and "complete" are
> polar opposites. If you have truely complete documentation, there are
> users who will find the format is not to the point. If you have
> documentation that is to the point for some users, other users may deman
> more background on the limited information....

If it's well done it can be both. A good "for the impatient" section with
minimum "test" configuration followed by the detailed documentation. And a
diagnostic section. Good stuff, when you find it.

> There are only a few ways that Windows machines find new machines in the
> network.
>
> One method existed with the MS Windows 9X share-based model where a
> Master Domain Browser would claim to be the keeper of machine names on
> the network. Then, when new machines came up, they would ask the network
> via broadcast, "who is the master domain browser" to which only one
> machine should reply. If no machines reply, then a machine may become
> one and/or force an election, where by each machine states how manly it
> is via OS Version, hardware speed, etc. The master browser keeps tracks
> of names of machines and stuff necessary such that when a person hits
> the network neighborhood to see computers near them or workgroups, the
> master browser will be the only one to respond.

This is how it is here.

> Though it may be some work to setup, why not go with WINS for your
> network?

I don't want to break a functioning system. However, for giggles, I
isolated two machines and tried it with the new linux box as the WINS
server. No errors, but no work either.

> If you are using the share-based model, make sure all of the machines
> are: 1) Using "Workgroups" and not "domains" or "active directory"
> 2) Are in the same workgroup

Yes, this is how it is.

-Bob






More information about the talk mailing list