Older blog entries for jgg (starting at number 26)

Ah, it has been a long time since posting here. Good thing nobody cares.

I had to forsake the DVORAK bit again, since I started a job, and it just wouldn't do to sit down at a QWERTY keyboard and type really slowly. So, as the message below suggests, I am actually employed now, at an Edmonton company called YottaYotta. We make storage system. Big Storage. I think I pass a couple terabytes of disk on the way to my desk, internal test systems. Heh.

So now, I am a 'Hardware Designer' which in practice means I get to write VHDL and think Big Thoughts about Big Storage.

Debian's BTS is killing our servers, and we lost a few more machines for various reasons that are still in the process of being recovered.. Debian Elections draw nearer, I think I might interview the candidates again, like all the past years!

I can almost type at a reasonable pace on a DVORAK layout, but still no touch typing action.

I had my first ever job interview today (at a local company called YottaYotta). My poor expectations were shattered, I was expecting to find an interesting but generally failing company, but instead they actually seem fairly reasonable. So now I may actually have to make some sort of choice and I'm not entirely sure how you go about doing that..

Finding a place to work always seemed so abstract, but now confronted with the brutal reality that there is a choice things seem rather dire. .

Being very indesicive sucks.

My forsaking the world continues at a good pace.

For no particular reason I thought I'd achieve something by learning the DVORAK keyboard layout. Several days into the madness and I aw still trudging along. This makes communication difficult which explains the forsaking

Perhaps eventually I can rejoin the world of the typing - it took several mins just to enter this diary entry!

It has been another month so I guess it is time to post something.

Debian had another disk crash and got a new box (klecker.debian.org) in order to replace the failed one. Lots of data was lost but nothing irreplacable. We still have two boxes that won't stay up more than a month, watchdog works good on one so the downtime is only about a half hour, the other nothing seems to work for. Sigh.

I never got to start my document, apathy rains supreme around here. Plus I'm feeling a major amount of aprehnsion about the future. How odd.

When did the diary entries turn into a chat line?

It has been brought to my attention that people have written processors to convert docbook reference pages into nroff suitable for man. I am overjoyed.

Years ago I sought this exact thing and came up empty so I decided to use yodl. Now I'm converting 1600 lines of yodl into docbook SGML - and overall the output result is much nicer but there are still problems - I will have to adjust the stylesheets and things.

I think I will also tank debiandoc-sgml and put those texts into a docbook format as well. Wee, unified documentation, I only need to remember one markup! What could be better?

So, I'm really doing all this so I can sit down and write an absolutely huge guide on how to use libapt. I'm doing that because I wrote some Python bidings (and bod is writing perl ones..). I can expect C++ programmers to grok the source, but not Ptyhon folks - so a big ole doc is the only answer.

I love writing documents, I expect this will take a good week to finish, have copious diagrams and things. I'm targeting something between 50 and 100 printed pages so we will see how that goes.

Xfree 4 won't stay up on my box. It hangs hard occasionaly, usually during screen bitmap copies. I guess the Matrox Mysitque support is slightly untested. That said, X4 is ungodly fast on this card. It is easially faster than some fast PIII's at pure graphic ops and it is just a P166!

Still have to add some framework for abstracting the things Conectiva added, the differences are quite small, but I'm going to clean some crap up in the process. rpm has some weird notions, like versioning order differs for depends and 'newness' , but otherwise it is an amazingly clean fit - one new dependency type, Obsoletes, which is really just Conflicts+Replaces rolled into one. The fact that APT can represent both systems fully (it actually will represent RPM more fully that most RPM tools!) is fairly interesting. I wonder what other packaging systems out there have the required structure. If RPM wasn't so ungodly expensive to generate all the meta data it might be fairly nice.

So, I think I fount out what is causes saens to die, it isn't OOM as I thought, but it seems the process table is full. I installed watchdog+softdog and the machine sucessfully crashed and rebooted with log messages from watchdog indicating that it was unable to fork due to EAGAIN which kernel source seems to indicate no more task entries.

The question is why - which is why I wrote this single process pid logger thingy jiggy to watch out. Some buggy daemon is creating excessive processes, bets are its proftpd. I had forgotten that I ulimited the hell out of proftpd ever so long ago, so OOM it aint.

Why do we use this? Why do all FTPd suck? All I want is a bullet proof, fast anon-only ftpd that meets the DFSG. Sigh.

Of course with my luck it will be apache or some weird ass kernel bug. At least it reboots itself now.

Debian got a /48 of IPv6 addresses yesterday and I used them to create a couple tunnels and bring more of our machines onto the 6bone. For those that are not familliar with IPv6.. a /48 is large enough to hold about 64000 subnets if you use the usual configuration scheme. Each of those subnets can contain the largest switched ethernet network you can build (> 10000 hosts).

Debian Potato will have quasi usful IPv6 support in many packages, woody should be even better. The problem is getting upstream to accept patches. I wish more people writing socket/network applications would look at RFC2553 and visit the Man Page viewer at OpenBSD.org and look up getaddrinfo - that will enable their App for IPv6 pretty much right off. glibc since 2.1 has supported the functions, but there are no man pages since it is GNU.

At work today we got a new Printer/Copier/Fax. A Canon imageRunner 210. Apparently it costs quite a large amount of money new, something like 10k$ CDN or more. Really nice device, it has a built in 3G disk, postscript, 11" paper path and all digital copying with the usual bells and whistles. We even got the 12 tray finisher+duplexer with the stapler :> It is completely self supporting, you don't need a server to baby sit print jobs too it or anything!

Trouble is the Windows Drivers SUCK, the printer has so many capabilities they simply don't cover because they are stuck in the model of uni-directional communication with the printer :<

What I thought was kind of remarkable, they included a program that would download PDFs to the printer, it was supposed to take them internally as PDFs and rasterize them with the built in PostScript engine and the internal fonts. The docs say it is faster than printing from Windows and gave better results than the PCL driver.

Trouble is, Linux and this printer is worse :> Sure it speaks protocols that linux handles like SMB and LPR, but the totally balkanized way printing is handled on unix makes using the finisher exceedingly difficult. For TeX I need to add an arcane set of options to get duplexing and stapling, Netscape/Mozilla just doesn't have any hope and I imagine a2ps and enscript need another nasty set of options.

So I read the linux printing articles that have been floating around after the summit and it sounds very interesting, particularly the PPD programs - which will take care of the finisher, but it is still just as bad as the windows drivers WRT to font handling, programs pretty much have to download vector fonts with every job, even though I have 3G of storage that is quite capable of persistantly caching fonts! (only thing it is good for :P)

I hope the people involved with linux printing can get really good support for these expensive buisness class printers, it would make the MS office replacment' idea feasable...

It seems I did attend OLS and just got back. I think I saw everyone there that I knew, certainly a fair number of people.

The HP guys were especially nice, I think we will soon see a nice PA-RISC port for Linux.

It seems I will be attending OLS, leaving Tuesday. Hopefully through some magical means other Debian people will magically find me!

Otherwise, not much is going on.

17 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!