Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:I do not understand (Score 1) 249

You claim you don't understand, so let me spell it out for you:

The /. community generally looks favorably on increased liberty, privacy, free software and innovation. Software patents are disfavored because, being developers, Slashdotters know that it doesn't take a whole lot of time to implement such patents.

So, by that measure:

Apple releases Darwin: good
Google unifies user agreement and user data: bad
Apple sues Samsung on design patents: good
Apple refuses to pay for hardware patents: bad
Apple bricks jailbreakers: bad
HTC restricts modding: bad
Samsung allows modding: good

Comment Re:I do not understand (Score 1) 249

You'd have a point if these were totally worthless patents being used against Apple. That would be a what's good for the goose is good for the gander situation.

But these are hardware patents, real stuff about interacting with physics, like radio waves, not the shape of a rectangle that a dev can hack out in a few hours.

Comment Linux-based shares (Score 4, Insightful) 388

Well, OK, granted for personal machines.

But you should at least be able to browse the available servers, right? What I see is the community will continue to put out buggy Windows interop software because M$ can't just hand over the AD source.

Anyway, like I said in another place in the discussion, the Linux community seems to have went about this wrong.

It would have been better to come up with a networking addon for Windows clients to allow them to easily browse and connect to resources provided by Linux servers in a hierarchical domain arrangement (basically, Domain Name System). So: ibm.com, fl.ibm.com, miami.fl.ibm.com, files1.miami.ibm.com, etc.

Auth handed by OpenLDAP and Kerberos. Remote login by RADIUS.

Some of that stuff would need some polishing around the edges plus integration, but again, writing your own Windows client DLL should seem to be much easier than divining and decoding messages passed around an AD network.

Also: it would have been nice to really think outside the box. Like, how about allowing users to browse resources instead of being concerned with which server a resource happens to reside on?

Comment Re:No (Score 3, Interesting) 388

It seems that it would almost be easier drop reverse engineering the Windows network server to allow standard Windows clients to use Samba, and instead:

Create a new Windows client network DLL which can be installed on Windows clients to be able to access resources provided by Linux servers running LDAP and friends.

Comment Re:No (Score 3, Informative) 388

Your link itself noted glitches in Samba4:

No More Network Browsing
In Windows based AD you can still browse a network, Samba3 had this but Samba4 does not. So, you will not see your domain, or browse machines in the domain.

Samba4 and Homes
The [homes] share and the browseable directive don't work as expected.

Cannot contact any KDC for requested realm: unable to reach any KDC in realm $DOMAIN
This is a DNS related issue, it's likely the above SRV records are not present, fix your DNS.

The first one is kind of major, I would think: You can't even browse a network?!

Slashdot Top Deals

Beware of all enterprises that require new clothes, and not rather a new wearer of clothes. -- Henry David Thoreau

Working...