Older blog entries for Svartalf (starting at number 38)

Well, well... New year, new posting.

Haven't gotten back to any of my stated Open Source projects, but it looks to be that I'm going to be duffing about with some new ones as a consequence of my contract job (the one that pays the bills), LGP (Fun job...), and Coollogic (The "longshot" that I'm sharing spare time with LGP on (mostly on this one at this time...)... Won't bore you all with the details- suffice it to say, things should be a lot rosier by end of February no matter HOW one were to slice it.).


In the case of LGP, I'm going to resurrect a networking library that worked, worked well, looked similar to DirectPlay on an architechtural level, and was used to produce over 20 commercial titles and was used in several Linux ports done by Loki Games that interoperated across Linux, MacOS, and Windows machines. Once modernized, while it won't be the greatest, it'll be a good arrow in the quiver of game developers and porters that will work across multiple OS platforms comfortably.

Various Embedded Linux Projects

In the case of Coollogic, I'm expecting to further several different user space drivers and create a few new ones as well. Current C/C++ based X10 control libraries do not include support for the LynX10-PLC interface (Something we need to at least get to a demo stage with some of our projects we're working on right now) which is purportedly suported in MisterHouse, so I'm going to add code to the C/C++ libraries because I need those instead of Perl. I'm also planning on coming up with some API libraries for several previously unsupported sensor devices, including some 2D MEMS based accelerometers available from SparkFun in Colorado. I have some other plans in mind, but our budget at Coollogic will probably have to allow for another developer or two dedicated to embedded distribution development to be able to honestly do them as I'm kinda stretched thin (When am I not, right? :). However, if things pan out the way they should, Coollogic's expecting (and this is the CTO speaking on behalf of his company here...) to provide a couple of nice gems for embedded Linux development, pooled from the amazing work people have done on minimalistic LiveCD's and other work we've done in the past and in the present on things.

On my contract side, we're looking at some JXTA based stuff to backfill some of their services offerings. Can't say more than that at this point in time on that part of things

Wow... Has it been all that long? Well, I was unable to find the memory issue in the code that was the long tent pole in the release schedule for Ballistics- due to time constraints more than anything else, so I handed off the code to one of the other developers. We should be seeing some results shortly on that front- if not, never fear, I will be coming up with something other than OpenPlay, from which I believe the cause of some of the last issue stems from. OpenPlay's got it's place in the world, but I don't know if it's with LGP or anyone else. You see, the thing's got issues with Firewalls, and there's better solutions available for nothing or next to nothing that do a better job of things AND allow us to do a better job of making things look like DirectPlay. We should be seeing Ballistics, hopefully within the next couple of days.

Coollogic was supposed to have gotten the funding, but it did not happen yet. Should know a lot more by this evening- supposedly, the big bridge from the VC is due to be wired into our account by this Friday. If so, things get a whole lot easier for me and everyone else at Coollogic. If not, well, we've got alternatives to keep things going a while longer. I'll believe it all when I see it happen, but I'm hoping that I'll be pleasantly surprised this evening with the update from our CFO.

Hopefully, I will be getting back to my Open Source and other pet projects once things settle down... (Me, have things settle down- not bloody likely mate! :-)

22 Jul 2004 (updated 22 Jul 2004 at 21:12 UTC) »

Well, well, well...

A good month to say the least.

I survived another year on this Earth.

I'm about to close out the last issue in Ballistics. (This means it goes gold soon).

Coollogic is about to close on it's funding (Finally!!! YES!!! :-)

On another note, I got a lesson in why one should be careful about blogging- I had to excise a few ill-advised comments from this diary (I will say that I had reasonable cause in my defense- but it's still causing me to work just a little bit harder than I should have to because of the rather stupid things I put on here.) and go about asking Google, etc. to purge their caches...

I'm convinced.

The current means for providing AMD64 32-bit support within a 64-bit Linux environment is a BAD thing.

Split directories, one set for 32-bit (/lib, etc.) and one set for 64-bit (/lib64, etc.). It confuses the hell trying to make a cross-compile setup. It leaves it open for you to miss libraries on either side, causing you to not be able to do the stated thing, run 64-bit binaries alongside 32-bit ones. And it confuses the hell out of each and every automake setup.

We all need to really, REALLY re-think this idea. There's a need/desire for someone to run 32-bit applications- but this isn't the way to do this. Do I have answers for this? Not yet- I've not had the time to think about it seriously.

Here's a little gem of wisdom that I wish other coders and developers would figure out:

Pointer Values != DWORDs

Reinterpreting them to DWORDs causes no end to problems. Yes, on a 32-bit platform, they're DWORDs. On a 16-bit or 8-bit, they're not- they can either be DWORDs or WORDs depending on architechture. On a 64-bit machine, they're QWORDs. If you want to make a handle, in other words, an opaque pointer, declare a typedef for void * and go to town. If you're recycling something that was intended for use with DWORDs or INT32s to handle indexing or tracking pointers, you might want to take the time to think about and re-think your design to use the right data types.

These are the same silly things that I saw with migrating DOS applications to Windows. It's the same silly things I saw with migrating Win16 to Win32 applications.

It's so easy to write code in a manner to avoid this stuff, I guess that I'm amazed that I keep finding gems like this in modern code.

I just thought I'd make an entry for this. I just found out (it's apparently not hit Slashdot or any of the other regular sites...) that SuSE is offering the base distribution for download without install support, etc. Better yet, I've found a mirror that appears to provide AMD64 versions of the ISO's. Guess I'll be testing SuSE in another day or so- hopefully, they've done a little better job in handling the issues I outlined in my previous diary entry.

24 Nov 2003 (updated 24 Nov 2003 at 13:36 UTC) »

A comment on things Athlon 64-ish...

I've been tinkering around a little further with Mandrake 9.2 AMD64 and it's definitely "okay". The install made it feel a little rougher around the edges than I thought, but there's still some issues that are lingering that I'm not 100% sure they're Mandrake's, but not having any other reference (Gentoo was an interesting failed 1st and 2nd attempt. Maybe three tries is the charm, but I'm not sure about it at this point. Pretty damn complex setup if you ask me...) I can't say either way. Boils down to how they accomplished 32 and 64-bit support all in the same runtime environment. They have seperate /lib and /lib64 directories for all .a's and .so's on the system. What's more obnoxious is that your source builds can't assume where the libraries are- they have to dynamically choose the right one, and at least Mandrake opted to not have all of the development or runtime binaries for some libraries in 32-bit (which is the assumed pathway based on them placing all the 32-bit stuff in /lib, /usr/lib, etc.). A good example of this is Source Navigator. It will not build in the Mandrake AMD64 world without some hacking of the makefiles in the source tree so that the thing will find the available (64-bit only) X11 development stuff.

This has me wondering if supporting 32-bit in this manner is really worth it. Stuff's breaking unpleasantly because of the way they made it all work. While I admit it relegates the AMD64 to the same role as the PPC if you went nothing but 64-bit, it might be better for everyone involved as it would be exactly like everyone expects things to be.

20 Nov 2003 (updated 20 Nov 2003 at 02:16 UTC) »

Well, things have changed, hopefully for the better.

I have a job as a contractor for Texas Instruments. It's not for what I should be getting as a contractor with the years of experience I have- but, it's pretty much guaranteed money for the next 6 months at a rate that'll help get me back on my feet well enough.

The previous employer's morphed into just business partners working on some important projects after hours while they get their house in order. When it's all said and done, I'll be a part owner in the reorganized company if they get their funding (which will actually be some small recompense for all the agony they put me through these past two years)- IF they get their funding. The projects and the potential contracts lined up, plus the fact that they're still paying me a salary even though I'm on a contract elsewhere has me still talking to them at this point.

Athlon64. 64-bits. Nice. If you're wondering what I'm prattling on about, someone gifted me with an Athlon64 to do some work on their behalf. It's nice. It's pretty fast. Mandrake 9.2 for AMD64 is okay, but it's really rough around the edges for a release candidate. SuSE appears to currently be the way to go, but I don't have budget for a copy of Professional (Which, I believe is the only version set up for AMD64 right at the moment...) and they want $1500 for a developer relations arrangement (definitely NOT in the budget, either for me or for LGP...). So, that's kind of out of the question. Gentoo's an option, but I've not gotten around to doing the deed on another partition of the main HD yet.

On a slightly different note, I got a reminder about living for the moment today. Someone rear-ended me as I was getting on to I-35E in Lewisville. Pretty hard, in fact. Had the experience of being put in a cervical collar and put on a back board and carted off to the hospital in an ambulance. Nothing to speak of wrong with me that they can see, thankfully. It could have been worse. It was the, "it could have been worse" that kept going through my head- trouble has a way of finding you and you never know when your time is up.

At approximately 6:30 this evening, my father finally passed on to the Lord.

I'll miss you a lot Dad.

18 Oct 2003 (updated 22 Jul 2004 at 20:41 UTC) »

I wish I had good news to report, but October's not playing out well either.

It's with deep sadness, that I publicly announce that my beloved Father suffered a cardiac arrest on last Saturday evening, sometime around 9:10 or so. While the paramedics arrived quickly, they couldn't get a good solid rhythm in his heart for some 6+ minutes after they had arrived (3 minutes after his breathing had stopped)- this means he was anoxic (I used to make jokes about holding one's breath and Anoxia being a hell of a way to go- I doubt I'll ever do that again...) for some 9 or so minutes. We just pulled him off the ventilator last night after determining that there was no possibility of any substantive recovery from the coma he was in- he has not passed on yet, but it's only a matter of time. I have the joy of stating that we DID have a good relationship and his last two weeks of what was his normal life was a happy time. He had all of his immediate family present and spending the entire day with him on his 62nd birthday. He spent the entire following week with his grandchild (my nephew...) and his wife. His last day was spent tinkering around with the various and sundry stuff he'd accumulated over the years and having fun and laughter with his wife while watching Trading Spaces on TV. When he actually passes, I think I'll be putting up a memorial page on my website- whether or not anyone cares, I think everyone ought to know a little more about one of the men that helped make me who and what I am in this day and age.

Cherish the time you have on this earth with the people you love and care about- life's far, far too short to be spent merely existing. Plan for the future, but live for the moment.

29 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!