Red Hat Acquires Netscape Server Products
KrisWithAK writes "According to a press release, Red Hat is acquiring parts of the Netscape Enterprise Suite including the directory server and certificate management system. I am definitely looking forward to more open source competition with OpenLDAP!"
but I too am definitely looking forward to more open source competition with OpenLDAP!
"I am definitely looking forward to more open source competition with OpenLDAP!"
I'm looking more for an LDAP that's easy to setup and run.
However a couple of questions.
1. How does the Netscape Directory Server compare to OpenLDAP?
2. Are the two interoperable?
Seriously? I thought the Netscape Enterprise product line fizzled out back when people thought selling pet food on the internet was a good idea.
Do you mind if I ask, how worthwhile are these products to Redhat? What kind of state are they in? How recently have they been updated, are they still in active development or just maitenence mode? Does anyone still use them? And do they offer any worthwhile features or functionality not already available in free products?
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
I read the press release, and they made reference to integrating the products into the Open Source Architecture, but they don't actually come out and say, "we're gonna make it [insert favorite license here]."
Also, is there any reference documentation for the Open Source Architecture? I'd love it, cause as it stands, sometimes open sources like a disorganized mess.
Just two years ago AOL was looking to aquire Red Hat. http://slashdot.org/articles/02/01/19/041215.shtml It's amazing how things have changed. Where AOL once wanted Red Hat to be another Netscape for them, Red Hat is now purchasing parts of Netscape from AOL. Personally, I think its great.
It work fine. Use the package for your distribution, don't try to compile it yourself if you are unsure about what to do. The man page seem to reflect the current command-line options, I don't see much problem here.
LDAP in general and OpenLDAP in particuliar is a complex subject. The initial learning curve is pretty steep. Good luck with it.
:wq
Do yourself a BIG favor and get some books on LDAP. If you don't, it's like trying to translate Klingon into Arabic using a poodle as your interpreter. I once tried setting up an LDAP server for a shared address book before I had any clue what I was doing, and I learned to regret that exercise in frustration.
There is a difference between "insightful" and "inciteful" other than spelling.
So whatever happened to Netscape's calendar server?
Way back, I installed it at an R&D facility; the client worked across platforms (solaris and windows) and provided an alternative to the nasty exchange lock-in.
Is there *any* alternative to Exchange now?
----- Documentation is worth it just to be able to answer all your mail with 'RTFM' - Alan Cox.
I didn't even realize there still was a standalone Netscape offerring. We migrated from Netscape to iPlanet to Sun Web to Sun Java One (or something like that). Anybody out there stick with the Netscape product?
This is a direct challenge to Novell/SuSE and Novell Directory Services [or eDirectory, or whatever they're calling it this week].
Red Hat must have realized that they needed a directory offering to compete in the enterprise.
That gives us four major directory vendors:
PS: Now that the Netscape browser has devolved into Firefox, and the enterprise stuff has been sold to Red Hat, does Netscape still exist as an independent company [other than some "portal" site on the web]?PPS: And are there any /. CPAs who'd care to calculate AOL's return on investment from the Netscape purchase?
About three years ago (admittedly, my knowledge is pretty old now) I tested and compared the two. The Netscape LDAP server used up a huge chunk of memory, even sitting idle, and could handle only a few authentication's / searches per second on our dual P-III 750 machine with 1 gig ram. The memory usage, if I recall correctly, was about 50 megs per process (not shared mem, individual memory usage by the way) with a default of something like 5 of them running.
OpenLDAP used about 20 megs of memory total, ramping up to 50 to 100 megs under heavy load. It could handle about 30 to 40 auths / searches a second.
Worse for the Netscape server was that it would just plain stop working after an hour or so of heavy load testing.
We went with OpenLDAP, and wrote our own edit screens for it since at the time it came with nothing very useful to a user (only ldapadd, etc... command line stuff).
After about a year of only handling the web server it was on we pointed our Peoplesoft implementation at it, which proceeded to increase our load from one auth every couple of seconds to about 10 auths a second. Other than the slightly larger number of openldap processes running, we never really noticed the load.
Hope that helps anyone looking at the two. I certainly would hope the Netscape server has gotten better, but everything I've read about it since then seems to say it hasn't.
--- It is not the things we do which we regret the most, but the things which we don't do.