![]() ![]() But yes, you have to know the basics of LDAP. You need to know LDAP - and you need to know that anyway to use it, and your knowledge of LDAP is transferable to any LDAP-based system, not just OpenLDAP. Re: storing config in an LDAP database - no you don't need to know OpenLDAP to be able to manage it. If all you want is to store passwords for a handful of users, the config can be done in 10 lines of text. Complexity of the config is driven by complexity of the demands placed on the installation. People talking about OpenLDAP complexity - that's mostly BS. Nowadays Mozilla/Firefox has stripped out pretty much everything that made Netscape useful. There really wasn't any need to build a separate LDAP frontend. Once upon a time Netscape/Mozilla browser shipped with LDAP module callable from javascript. that bring anything of value.", you also block orgs that would bring value, but might not want to be legislated to publish everything. I hesitated even posting my original comment, but don't mind getting a potentially new read on others devs point of view on this area.īriefly, on "block companies. I tend to think of GPL as for end-user applications, like openoffice or ardour (paging 'PaulDavisThe1st) and libraries and network services as mit/bsd/isc/lgpl so they can interact with Other Software without forcing anything on that Other Software. ![]() In my opinion though, for things like libraries or "lower level" software there seems to be a school of thought where "getting it out there" is more important than "saving it" from modifications. ![]() One may say that "weeding out" those envs is part of the point. Regardless - in some environments, that "stickiness" of the GPL is a non-starter. I say "fraught" because it imposes conditions on running this on the network. I say "lightweight" in terms of text and comprehension. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |