Remotely Possible

Finally, after a week or so, I sat down and fired up my for some quality computer time, following one of the most active Mondays I've had in a while (my calendar for this week seems to consist almost entirely of early morning and late afternoon meetings, with a crunchy midday).

My is now safely ensconced in the server closet (replacing my dead PC) and I will be investing in more RAM for it in a couple of months (I have a strong suspicion that it will be around for a while yet, so I might as well make it a bit faster). Expect a few notes on remote monitoring of systems in a few days (Davi has a few starting points, but interpreting temperature readings seems to be a dark art).

Incidentally, I've found that OSXvnc is amazingly better than the built-in client (which includes a server of rather limited abilities). The usual tune-ups (such as tweaking color depth and font smoothing) apply, but using a standard against OSXvnc seems to be a viable proposition at rates - it's not as fast as RealVNC on (lots of extra eye candy), but it's certainly usable.

(, to my amazement, worked pretty well over , at least on the LAN).

Sadly, the keyboard mappings are completely shot, which makes it impossible to use as a "roaming" desktop - I can type any accented character that strikes my fancy using against , but OSXvnc's handling of accented characters in this day and age is just sad - and reminds me of my .

As a sidenote, following my "network computing" phase, I've been considering going fully mobile and simply running everything off my office desktop (which is still running 2003 Server, easily the most stable desktop OS I've used these past few years - yeah, you can quote me on that, provided you take into account I don't have s at the office - yet).

Some News

A few interesting things I've come across: