Today was my last day with Greenviolet. I've greatly enjoyed my time running Greenviolet, but it's time for me to do something else and time for Greenviolet to move on with new vision.
The past thirteen or so years have seen a lot of changes in technology, as well as lots of changes for Greenviolet. I realize how privileged I am to have spent so much time working with so many brilliant people. I hope that both I and Greenviolet will continue to benefit from those collaborations, though separately, in the future.
Posted by Matt Lewandowsky on Thu, 15 Jan 2015
If you run a heterogenous business network, there's a fair chance that you have a Microsoft Active Directory infrastructure. There's also a fair chance that you're running Linux systems.
There are a great many ways to integrate these two operating systems to use the same user database. Many places use plain LDAP to the Active Directory. Others federate an OpenLDAP server running on Linux into Active Directory. Still others use Microsoft's old and creaky NIS server support.
It's fairly well known that Samba has fairly complete Active Directory support these days, and that it can operate as an almost-fully-functional member server. It's slightly less well-known how to actually use this support for login purposes however.
So, let's take a look at how to do it! Continue Reading…
Posted by Matt Lewandowsky on Wed, 13 Jun 2012
Many people who have become tech pundits recently are actually too young to actually remember when IBM had their own operating system, and that it was at least somewhat successful. It went by the simple moniker "OS/2".
The fact that it has been mostly relegated to the dustbin of history, and that some of the supposed causes are being repeated to some extent by RIM in their BlackBerry PlayBook Tablet OS 2.0 (and upcoming BlackBerry 10) is potentially worrisome for both developers and investors. But no one's really been drawing the parallels.
One person who has made the connection, amusingly enough, is Alec Saunders, VP of Developer Relations at RIM. Alec's been around various cool technology for years. He worked at Microsoft during the DOS and OS/2 days. He worked at QNX during the "dot-com era". He did fun stuff like Internet telephony after that. He made a blog post a few months before making the return to QNX (RIM bought QNX to make it the basis of their modern products) drawing some parallels between the Android Runtime and IBM's "Win-OS/2" integration.
So, in light of the events of the past year (the release of the Android Runtime, Alec's return to QNX [and joining RIM], the announcement of "BlackBerry 10" [often abbreviated "BB10" by developers, just as "OS/2" really stood for "Operating System/2"], many announcements by their competitors [including Android], waves of new developers and applications flocking to the PlayBook, and much more), it seems appropriate to look at his post again and offer opinions and concerns from the viewpoint of someone who hasn't ever been on the "inside" of the organizations involved. :) Continue Reading…
Posted by Matt Lewandowsky on Sat, 9 Jun 2012
(Note, this is an update for our article about developing for the PlayBook using Interix. If you have no idea what this article is about, please start with the previous one. There are no guarantees you will be enlightened, however!)
Well, as predicted, the lack of a working ls got annoying. (It was using the wrong /usr/bin and causing all sorts of fun!)
So, we did what we have to. And in the process, we found an optimization that shaved nearly a half-second off the script's load time! Continue Reading…
Posted by Matt Lewandowsky on Tue, 5 Jun 2012
Update (05 June 2012): Updated script available.
If you're like many people who are developing for the BlackBerry PlayBook on Windows as it is the only choice for the full suite of PlayBook SDKs available that's installable on a standard PC (a "Hackintosh" doesn't count, sorry), and you have a UNIX or Linux background, you probably have some favorite POSIX-y toolkit. At Greenviolet, ours has been Microsoft's Interix (also known as "Services For UNIX" or "SFU" prior to Vista and "Subsystem for UNIX Applications" or "SUA" after XP). So, of course, we wanted to be able to do our cross-compilation work from within our environment of choice. Continue Reading…
Posted by Matt Lewandowsky on Fri, 1 Jun 2012