The new drive (and video card) came today; but without data or power cables, causing me to make a trip down to College street to pick up the power cable (Ken had found a data cable after ordering one yesterday). So much for paying to get the drive delivered to avoid impinging on work-time. To add insult to annoyance I just assumed I still had some regular "Y" power connectors. Nope, apparently I put my last one into someone's machine... which means I have no CD-R or DVD until I get one.
When I hooked the drive up to the motherboard something got seriously karked in the BIOS (It's a Soyo Dragon motherboard). After an hour or two of cursing and trying every key combination and drive combination I could think of I just lay down in frustration and left the dratted thing stuck at the BIOS splash-screen. 10 minutes later whatever it was trying to do finally timed out and it booted (much to my surprise). So far nothing has made a difference to that 10 minute delay/pause on reboot. I'm considering flashing the BIOS, but I may leave it for now (I seldom reboot the box, and it's a 10 minutes to sit and contemplate).
I went with a Stage 3 + GRP installation, which basically consists of un-tarring a stage-file, setting up a few config files, chrooting into the new system then telling it to install whatever binary packages you want (KDE, FireFox, Thunderbird, that kind of thing). I'll likely rebuild them incrementally once the new instance is running, but this should get me to a functional 2005.1 install that I can use to work while it's doing the rebuilding.
I could just go ahead and do the rest of the building while in the old instance, but I'm hesitant to invest too much in the new environment before I know it will become a valid, bootable instance.
For now I'm leaving my GRUB install on the older first hard disk with just a pointer to the new install. Hopefully everything will be happy with that arrangement. Probably reboot in an hour or two when I'm done the day's work and see.
Anyway, just struck me that it's really cool that you can build a new instance of the machine while you're still running the old instance. Not cool in a Zaphrod way, but cool nonetheless.
Comments
2010-07-25 14:02
> and would have no Trac integ ration The trac-bzr plugin[ 1] seems to provide good integ ration between bzr and t [...]
2010-07-13 21:47
I've always been fascinated wi th the Asterisk AMI interface. So much so that I married tha t fascination with the [...]
2010-07-03 21:32
Yes, only references in dicti onaries are replaced, so hold ing references in lists, tuple s, etceteras keeps them alive.
2010-07-03 11:18
They hold references to remove and install?
2010-06-24 08:34
There's higher-level objects w hich are tracking what is repl aced (the actual Mock objects) . They hold references [...]
2010-06-24 08:23
I haven't tried it, but it see ms to me like this approach ha s one fundamental problem: If you replace all refs o [...]
2010-06-24 08:22
That's the "magic" that made m e go "ooh shiny"
2010-06-24 06:03
That's even more evil than the mock patch decorator...
2010-06-06 18:33
blush Oh.
2010-06-06 11:07
That's what the module does (a utomatically), but on a per-te st-run basis, and only for the process being tested (i [...]
2010-06-06 02:43
Maybe I'm missing something im portant here, but why not just write small scripts to mimic whatever dangerous utili [...]
2010-06-05 15:17
I thought about stubbing out t he python call to the process in the current process, but I want something which stu [...]
2010-06-05 14:47
Hmm... if Mock isn't flexibl e enough to handle mocking pro cesses adequately then I'd lik e to know how it could b [...]
2010-05-19 10:27
Hey, maybe it's a stupid new bie question, but where and ho w exactly should the patching of the core take place? [...]
2010-05-04 14:36
I used Qemu and VirtualBox pre tty extensively back when I wa s working for the OLPC, but mo st of the stuff we were [...]