OUs are an LDAP Concept that even OpenLDAP supported with Samba 3.

Samba 3+OpenLDAP+Heimdal Kerberos created what were often termed "Open Directory Services" by the Apple Crowd. They were mutant NT 4.0 Domains that had broken a bunch of the limitations of NT4, (such as multiple PDCs and levels of trusts.) provided LDAP and Kerberos, but to Windows, they were still just NT Domains to Windows. Not true ADs. XP and 2000 would disable Kerberos because it thought it was talking to NT4. Windows 7 dropped support for NT4 EXCEPT there was a special mode just for Samba 3 to work, and you had to edit the registry to get it working.

And I'd like a resolution that advocates regime change of these oppressive, abusive governments around the world such as in Saudi Arabia that have no legitimacy whatsoever. But hey, it's not a perfect world.

I try and run my own IT Domain services (for my own files,) I will NOT use Google Docs, or similar services. I have my own Apache servers, my own CMS, my own Domain Controllers, a Dumb Phone, my games are on my own hard drive, I run my own MySQL services, I do as much as I can myself, my connections to my friends use IPSec, if I get an (Android) tablet, it will be merely something that talks to my network, that I load my applications on from my network via 802.11.

I really would like to see organized resistance and civil disobedience to the Media cartels, and a campaign to paint them as the evil monsters they are.

I happen to think that RIAA, MPAA, CRIA, and BREIN are Scoundrels, of the same vein as the Westboro Baptist Church, and the Taliban, and other hate based organizations that use a religious or quasi-religious basis just like religion does to persuade people that they should be paid forever and ever and ever for a non-product, and for what really is an economically stilted scam meant to drain the poor, oppress other people, abuse children, ruin people's lives over a non-reason. Efforts should be taken by interest groups to dismantle these organizations.

I'm probably burning Karma here, but, I've heard alot of people say Dr. Who is becoming 'Atheist Jesus'. In the Classic series the Doctor was an Alien detective/investigator who merely lived a long time with a set number of Regenerations. He didn't always save the day. (Up until the latter part of David Tennant, he didn't save the day either.

But with Matt Smith, he's become like, a Demi-god or an Apollo type god. (River/Melody calls him 'an ageless god'. Now it's the case there are no limits on how many times he can regenerate, and he can use his regeneration abilities to heal others. The series doesn't make contiguous sense the way it did under Tennant and Eccloston. Basically, it's non-sense after non-sense plot. (The last Episode with the Angels is quite good really EXCEPT THE ENDING SUCKS.

I've only ever dealt with Oracle once and never in a Mission Critical Capacity.

Pidgin has no Skype support. You have to run real Skype to do Skype chat. There is a plugin to let you manage contacts.

I am not saying that. I am saying Samba 4 OpenLDAP backward compatibility because it uses OpenLDAP Internally. You would just change how the LDAP files are configured.

Before with OpenLDAP:
nss_base_passwd ou=People,dc=domain,dc=com?sub
nss_base_shadow ou=People,dc=domain,dc=com?sub
nss_base_group ou=Group,dc=domain,dc=com?sub
nss_base_hosts ou=Hosts,dc=domain,dc=com?sub
sudoers_base ou=People,dc=domain,dc=com?sub

With Samba 4:
nss_base_passwd CN=users,dc=domain,dc=com?sub
nss_base_shadow CN=users,dc=domain,dc=com?sub
nss_base_group CN=users,dc=domain,dc=com?sub
nss_base_hosts CN=Computers,dc=domain,dc=com?sub
sudoers_base CN=users,dc=domain,dc=com?sub

The object class data types all have to be imported from OpenLDAP.

You don't understand. AD IS LDAP. The Samba 4 AD Server runs OpenLDAP and Heimdal Kerberos.The file /etc files direct the machine to look to LDAP for configuration and policy instructions.

Samba 4 is backward compatible with OpenLDAP.

Keep in mind that "Group Policy" is, truly, is merely Windows Registry keys stored in the LDAP database in Active Directory. Samba 4 will store these in it's LDAP database. Something Samba 3.x+OpenLDAP Couldn't do.

Linux has no Registry, Linux approaches the Group policy concept differently by having application level Sub-Schemas that have to be imported into the tree. Linux applications then have to be configured to call on the LDAP Database instead of using it's local files. There are OpenLDAP Schemas for:

Sudoers
Evolution
eGroupware/phpGroupware
DHCP
Samba 3 of course
Bind (Deprecated)
Posix Accounts (/etc/password, NIS and NFS related)
CUPS (Printers)
Kerberos
Posix
Puppet
urpmi (Exclusive to Mandriva)
Apache (Can store httpd cluster information)
Zimbra ...and more.

When Samba 4 is released, you have to import all these OpenLDAP entries into the Samba 4 LDAP tree.

Yes, For all Linux networks, Samba does change things. Samba 4 is backward compatible with all of OpenLDAP's and Heimdal Kerberos's clients. In a purely Linux network, Linux machines would connect to the Samba 4 Active Directory as Open Directory Clients.

Since 2005, The combination of OpenLDAP, Heimdal Kerberos, and Samba 3 has been a staple in the Linux Infrastructure, with other services such as FreeRadius, NFSv4, and AFS being tacked on for good measure.
Many if not most Linux based utilities support LDAP. Unlike Samba 3, which functioned as an OpenLDAP based application, Samba 4 completely replaces OpenLDAP, and Heimdal Kerberos. Consider the following. Samba 3, while far beyond what Windows NT4 was ever capable of, expanded the NT4 Domain concept far beyond it' design limiations. In the most recent era, Samba 3.5 and 3.6, created an enhanced form of NT Domain Authentication just for interoperability with Windows 7. (This is very fascinating because it uses Windows 2003 Sign and Seal with NT4 Authentication, something NT4 never could do.) So it can be be said, while Windows 7 expressly drops support for Windows NT4, Windows 7 has express support for Samba 3.

Yet the sword of Damoclese has swung over the head of Samba 3.x for a long while. Vista dropped support for NT4 Style System Policies, requiring administrators to resort to registry Trickery with Wine and third party policy tools such as NitroBit.

Samba 3 brought about a form of NT Domain that supported LDAP as a backend, could use Kerberos for Authentication both for file shares and joining the Domain. (Although only other Samba clients could utilize the Kerberos aspects of Samba 3.) Could delf out policy by OU. With help from OpenLDAP, Samba 3 could overcome the single PDC limitation, and all Samba Domain Controllers could be writable PDCs because OpenLDAP supported Multi-master Replication.

Beyond Samba, FreeRadius could use LDAP for authentication, Evolution could garner configuration information from OpenLDAP, for IMAP and SMTP settings (CalDAV Support was never added, even though there were feilds in the OpenLDAP schema for the three CalDAV based Calendar, Addressbook, and Task List.) This cooperated with eGroupware. Sudo could draw Sudoers from OpenLDAP, as could NSS. Each had their own unique Schemas.

Unlike when Windows moved from NT4 Domains too AD, the movement was simple, before, you had no Directory Service, and now, boom! you do. In the Linux world LDAP has been a reality for a long time. Many applications are built to participate in Open Directory based Domains based on OpenLDAP Schemas. What happens if the Schemas conflict definitions? How will this be resolved?"

The Linux Gaming community is a different audience than the Windows Gaming community. It has to be marketed to Linux gamers properly.