A post for the geeks in the audience.
Dec. 23rd, 2008 01:34 am1. Recent Sun Xxx00 x86 servers are really nice boxes, and actually quite cost-effective for what you buy (a decently-built x86 server with good service, at least in our experience on gold and silver contracts). However, the firmware is so awful and buggy that it simulates hardware failures when there are none. If you call Sun, the first thing they will ask is that you upgrade the iLOM and BIOS firmware to the latest version. They are quite correct in this. (The engineer who looked over our X4600M2 that wouldn't boot claiming defective CPUs and was perfectly fine after a firmware afterward was quite scathing in his characterisation of the base firmware.) The nuisance is that you have to hook up both the iLOM serial (to configure the web version) and Ethernet ports, and upgrade the firmware through the browser interface to achieve, ooh, basic functionality. But it works quite well, the iLOM is really nice and we're still big fans of the boxes in question.
2. OpenBSD doesn't do X11 on VirtualBox because VirtualBox is officially crappy and Sun don't care (and Theo is sick of dmesg logs from known-defective virtual hardware). Guess I'll be sticking to running Windows 2000 on it (and that only to play MP3s over SMB without undue annoyance).
I'm trying to help with problems with current Wine on OpenBSD — the ports version is from 1999! And current versions do work quite well on FreeBSD — and have resorted to qemu, which works perfectly in full emulation (kqemu doesn't work; see above) despite being really slow. Use -std-vga not to need an xorg.conf, though that will give you a 1280×1024 screen every time — for something else, use driver "vesa" in xorg.conf. Good Lord, the yakshaving — including setting up vsftpd on the laptop to serve install tarballs via FTP to its hosted virtual machines, so I don't have to keep re-downloading 221MB.
3. Tomorrow (today, Tuesday) I will be down t' pub with
sweh and
syringavulgaris and the BOFHs. Must get home at a sensible time afterwards, unfortunately. Feh!
(no subject)
Date: 2008-12-23 01:36 am (UTC)(no subject)
Date: 2008-12-23 01:39 am (UTC)(no subject)
Date: 2008-12-23 01:55 am (UTC)But yeah, buggy. Not as buggy as the old SAN management software used to be though. At least they seem to have made that better: CAM is actually pretty decent, at least for the couple of low-end arrays I'm managing with it.
(no subject)
Date: 2008-12-23 03:42 am (UTC)(no subject)
Date: 2008-12-23 05:06 am (UTC)But yes, iLOM is fundamentally a great idea. Just annoying finding two Ethernet patches (often on different subnets) and the right proprietary serial dongle before you can upgrade the firmware to, ooh, basic functionality and a machine you can actually trust to tell you when it's unwell.
(no subject)
Date: 2008-12-23 05:07 am (UTC)(no subject)
Date: 2008-12-23 05:08 am (UTC)(no subject)
Date: 2008-12-23 05:21 am (UTC)(We had that problem in our old datacentre. Not any more.)
The need to patch the firmware is annoying but far less troublesome to actually do than, oh, a Niagra box. If you think an X4600 is a pain, hope to never deal with a T5140... It looks like it uses iLOM but it's really more a bastard cousin that works completely differently and requires all sorts of buggering about to patch.
In any event the current generation of iLOM seems fairly stable so far. The X4600 problems I'd seen were more to do with the BIOS. Having a BIOS on a server, now that is ludicrous.
(no subject)
Date: 2008-12-23 05:22 am (UTC)(no subject)
Date: 2008-12-23 05:23 am (UTC)(There's a reason I got a 12" laptop in as absolutely soon as ordering them was my job.)
(no subject)
Date: 2008-12-23 05:24 am (UTC)(no subject)
Date: 2008-12-23 05:28 am (UTC)fvwm2 with all the pretty turned off was still about the best option, even on the U5s.
(no subject)
Date: 2008-12-23 05:51 am (UTC)(no subject)
Date: 2008-12-23 06:10 am (UTC)(no subject)
Date: 2008-12-23 06:23 am (UTC)(no subject)
Date: 2008-12-23 06:41 am (UTC)(no subject)
Date: 2008-12-23 08:03 am (UTC)(no subject)
Date: 2008-12-23 08:32 am (UTC)(no subject)
Date: 2008-12-23 10:44 am (UTC)(no subject)
Date: 2008-12-23 10:50 am (UTC)(no subject)
Date: 2008-12-23 12:15 pm (UTC)(no subject)
Date: 2008-12-23 03:50 pm (UTC)(no subject)
Date: 2008-12-23 08:32 pm (UTC)Compare debian and "aptitude update && aptitude upgrade".
(no subject)
Date: 2008-12-23 08:50 pm (UTC)(no subject)
Date: 2008-12-23 10:48 pm (UTC)(no subject)
Date: 2008-12-24 06:17 am (UTC)(no subject)
Date: 2008-12-24 06:49 am (UTC)(no subject)
Date: 2008-12-24 09:42 am (UTC)That said, I'm now compiling ports in the OpenBSD VM and it's very nice (if very slow). Seems to integrate better with its own binary package system than FreeBSD 4.x or 5.x did. Presumably because a given ports tree is release-specific, rather than allegedly coping across all major and minor versions as the FreeBSD one claims to try to.
(no subject)
Date: 2008-12-26 11:22 pm (UTC)Seems to work well for us.. Supports fully-virtualised OSs, hardware accelerated, faster than kqemu by a good margin..
(no subject)
Date: 2008-12-29 08:59 pm (UTC)The thing that annoys me with the OpenBSD ports tree is that (as I understand it), there's no way to get timely security updates without following CVS, which also requires to track CVS OpenBSD.
(no subject)
Date: 2008-12-30 05:38 am (UTC)Of course, remote VM client viewing options are important when managing from a Mac since VMware has NOT seen fit to provide an OSX Remote Console Firefox Plug-in (just a Windows and Linux one).