To whom it may concern :) ....
I gave my notice to TurboLinux. I'll leave all the ugly bits out. By September 1st, I'll be devoting the majority of my time to my system management project. Yes, it is OpenSource... www.open-it.org still needs to get the backend up, and it will have to wait for my arrival at my new work place in September. Where? Stanford University.
I worked there for 5 years in EE/CS, and while at TurboLinux kept some involvement. I hope that along with the directory services project I will regain some stake in Stanford's own Linux distro, SULinux. I helped put it together with one other staff member there, and with my credentials at TurboLinux, I don't see why I shouldn't be somewhat involved :) Founders/ authors rights, right?
Now that I will be "free" corporate wise, my diary entries from hence forth should be meatier, and more frequent. Running your own OS project tends to give you complete freedom of expression, not just in code, but in true ability to speak your mind. I'm tired of having too much in my head but alas not being able to speak to a soul.
(Joe does a little dance to demonstrate)
Ever get that sour feeling in your stomach...
Urgh, I hate when shit happens. In any case, Open-IT will receive a glorious make over as soon as the back end servers are up and running. Still waiting for some connectivity. The current server for Open-IT is a static place holder. Give it another month...
Sad to see that I couldn't spark enough interest in my article. Oh well. That's what happens when you leave it too vague. I just didn't want to pollute it too much with my ideas.
Hello to Adam Shostack and Elise Shapiro. Its a conspiracy I tell ya (grin)
I've also started up project site. Nothing there yet, but its a modest beginning. Check Open-IT out!
Thought for the day: Always follow the path that maintains one's level of motivation and momentum.
For all of those who have asked about how things are at TurboLinux, the simple answer is as busy as ever, with an added bit of focus. The industry and the markets always help on focusing a company as well as the individual.
Onto more important things...
I'm still floundering on one bit. LDAP makes for a great top-down heirarchically controlled directory service with centralized control. However, there is a lot of fore-thought required, and seeding an ldap server for an organization is daunting. Its even more daunting to figure out how to seed a low leaf among multiple ldap servers (say a workgroup server). The only effective bottom-to-mid upward solution to date has been Netinfo, which lets the local cluster define domains and then one can tie them together after the fact. For a NOS -- management tools are key, but you have to be able to aptly manage your local data. Otherwise you end up with complex tools to manage impossibly complex data. One can only hope for an extremely high degree of centralization in an organization to limit this problem.
My feelings (which to a degree have been related to Luke Howard -- lukeh here), are that maybe a combination of the two is necessary. The equivalent un*x workstation/server mayhap needs an improved, secure Netinfo style authentication and management system, with adapters and tie-ins into higher level LDAP directory services. Agents must exist to help propogate loosely managed info into the larger centrally controlled LDAP DSes, and likewise global sentings can by profile be approved into the local realms of the clusters.
This could get ugly. But unless the end user or group manager can effectively manage his applications and data, directory services are a large undertaking that can quickly become a hindrance and would be summarily dropped.
What do you think? You can email myself as always with your ideas.
I'm also hoping to apply these a bit more back at Stanford. Should get more involved in my co-authored Linux distribution, SULINUX . I've wondered off from that for quite a bit...
Keep up with the latest Advogato features by reading the Advogato status blog.