Search Results: "pollo"

24 January 2010

Steve Kemp: What the hell are you laughing at?

Slaughter
I received my first patch to slaughter today, which made me happy. (I've made a new release including it, and updated the list of primitives to actually document the file-deletion facilities which previously I'd omitted to avoid encouraging mass-breakage.)
Signing Binaries
Andrew Pollock mentions that the days of elfsign might be numbered. This is a shame because I've always liked the idea of signing binaries. Once upon a time, in the 2.4.x days, I wrote a kernel patch which would refuse to execute non-signed binaries. (This was mostly a waste of time; since it denied the execution of shell scripts. Which meant that the system init scripts mostly failed. My solution in the end was to only modprobe my module once the system was up and running, and hope for the best ...) Right now, having performed only a quick search, I don't see anything like that at the moment.
  • elfsign will let you store a binaries MD5 hash.
  • bsign will let you sign a binary with a GPG key.
But where is the kernel patch to only execute such hashed/signed binaries, preventing the execution of random shell scripts and potentially trojaned binaries? Without that I think signing binaries is a crazyish thing to do. Sure you can test that a file hasn't been modified, but even without those tools you can do the same thing via md5sums. (ObRandom: Clearly if you mass-modify all your binaries the system md5sums database will be trashed.)
Perl UTF
I've received a bug report against chronicle, my blog compiler. It seems that some versions of perl fail to run this:
     #
     #  Run the command, reading stdout.
     #
    open( FILTER, "$cmd ;utf8" ) or
       die "Failed to run filter: $!";
Removing the ;utf8 filter allows things to work, but will trash any UTF-8 characters from the output - so that's a nasty solution. I'm not sure what the sane solution is here, so I'm going to sit on it for a few days and continue to write test scripts.
ObSubject: 300

Andrew Pollock: [debian] elfsign's days may be numbered

There's a release critical bug (that severity is debateable, in my opinion) in elfsign, a package I maintain. It seems to my casual observation, that switching it to generate SHA1 signatures wouldn't be too hard, given it's using OpenSSL, and OpenSSL has a sha.h file. I really wouldn't know where to start, though, and ideally it should continue to verify existing MD5 signatures, so it's more than just changing an include and a few function calls. To boot, upstream seems to have disappeared, so it's looking like removal is the best option. The popcon numbers for this package aren't very high either, which is another nail in the coffin. So if someone reading this cares about elfsign in Debian enough to send me a patch to use SHA1 in the next month or so, I won't file a removal request.

21 January 2010

Andrew Pollock: [tech] Finding the maximum message size

This was born from a need to see how big a ZIP file I could send my accountant in Australia, and scratching the itch to write some code. The fact that most SMTP servers talk Extended SMTP makes this relatively easy, and Python has some great modules for DNS and SMTP. One gripe I do have is how long it takes the Python modules to mature. It's taken until Python 2.6 for smtplib.SMTP() to gain a timeout parameter, for example. Anyway, I was able to write something nice and generic (it works for any domain) in around 100 lines, thanks in no small part to the DNS module, which makes getting a list of MX records stupidly easy.
$ ./maxmessagesize.py andrew.net.au
daedalus.andrew.net.au: -1
$ ./maxmessagesize.py pollock.id.au
ASPMX.L.GOOGLE.COM: 35,651,584
ALT1.ASPMX.L.GOOGLE.COM: 35,651,584
ALT2.ASPMX.L.GOOGLE.COM: 35,651,584
ASPMX2.GOOGLEMAIL.COM: 35,651,584
ASPMX3.GOOGLEMAIL.COM: 35,651,584
ASPMX4.GOOGLEMAIL.COM: 35,651,584
ASPMX5.GOOGLEMAIL.COM: 35,651,584
$ ./maxmessagesize.py debian.org
master.debian.org: 104,857,600
$ ./maxmessagesize.py cameronp.com
mail1.mysmarthost.com: 30,000,000
mail2.mysmarthost.com: 30,000,000
$ ./maxmessagesize.py ubuntu.com
mx.canonical.com: 62,914,560
$ ./maxmessagesize.py clug.org.au
mx.clug.org.au: 50,000,000
$ ./maxmessagesize.py linux.org.au
morton.linux.org.au: 52,428,800
It's good to see that in most cases of domains I tried, all of the MXes had the same maximum message size. Source code is here

Andrew Pollock: [life] Fetal MRI results

Yesterday we went back to Stanford for another ultrasound and a fetal MRI. We had pretty much the same gang doing the ultrasound as two weeks ago, so that was a nice bit of continuity. A paediatric radiologist came in at the end to take a look. She was the most confident of anyone that everything was going to be okay. She thought she could see something resembling the cavum septum pellucidum on the ultrasound. I think the ultrasound report said it was an "unusual shape" or something like that. After that, we got packed off for the fetal MRI. There was a bit of a wait, as there's only one MRI machine for the children's hospital, and the studies tend to take 30 to 45 minutes, but we eventually got in. I got to sit in the room with Sarah while they did the MRI. I was hoping to be able to sit in the control room instead, so I could look over their shoulder and see how it was all done. We both got earplugs because the machine is pretty noisy. It's not the hammering sound that they seem to go for on TV, it's more various different pitches of a horn. The radiologist told us she'd probably read the MRI later that night, as there'd be a bit of a backlog with the long weekend, and that we'd get a call today. Sarah got impatient this afternoon and called her obstetrician, and he called her back shortly afterwards saying he'd spoken to the radiologist and everything was fine. Exact specifics are not known at this time, but we'll be quizzing the obstetrician at our next appointment in a couple of weeks. Needless to say, we're both extremely relieved that everything is okay, and can scrub one thing off the list of things to have to worry about at the moment. Now we can just concentrate on trying to move house this weekend.

19 January 2010

Andrew Pollock: [life] elfa rocks

We've got a walk-in wardrobe in the master bedroom of our new place, and the existing fittings were pretty crappy, so as part of the repaint, I ripped out the old stuff, and we bought some new elfa stuff from The Container Store. We did the initial design a couple of weekends ago, and went back today to actually buy the stuff. The whole process is pretty slick. You rock up with your measurements of the space, and a designer fiddles around with some special CAD software and does up a design for you, and that spits out a pick list of all of the bits you need, as well as what needs to be cut to custom lengths. A couple of hours later, you come back, and they wheel out a cart load of bits and pieces, you put it in your car and head home to put it all together. I was initially a bit worried about the assembly, but it's even easier than IKEA. You get tailored instructions for your design, and the only point at which it anchors to the wall is at the top, and then everything hangs from there, so it's pretty hard to screw it up, and it's all adjustable. Added bonus: in an earthquake, it moves with the tremors instead of toppling over or ripping itself out of the wall. I'm very impressed by the product, and absolutely love the result. It only took us a couple of hours tonight to slap everything together.

17 January 2010

Andrew Pollock: [life] A Prairie Home Companion

We listen pretty much exclusively to NPR in the car these days, and often when we're pottering around on the weekend, we catch A Prairie Home Companion. It's a light-hearted radio show, which makes us laugh. When we learned that it was coming to town, we lashed out on some tickets. We went to the recording of today's episode at the War Memorial Opera House. We had seats towards the back of the balcony on the fourth floor. The opera house is a beautiful building. The seating is incredibly steep. The stage was miles away, I wish I'd brought binoculars. The opera house normally holds 3200, but because there was no orchestra they could put in some extra seats. It was a full house. It was cool to get to see how the show is put together, and we had an entertaining time.

9 January 2010

Andrew Pollock: [life/americania] TransLink, the Bay Area's best kept public transportation secret?

We're not huge users of Caltrain, because frankly, it sucks. It's way slower than driving to San Francisco, and by the time you've paid for two return tickets, you might as well have driven and paid for parking. That said, we do use it from time to time. One of the things I noticed when we first moved over here was this intriguing box on a pole, to the side of the normal ticket vending machine. It looked all battered and faded, kind of like a deprecated form of ticketing that had been phased out years ago. Except it looked too high-tech to be phased out. Fast forward to four years later, and we're using Caltrain to get back from SFO after returning from Atlanta for Christmas, and there's this "Don't forget to tag off" TransLink poster inside the carriage. I'm now officially intrigued. I did some browsing of their website on the journey home. How could this be? Hong Kong's MTR has the Octopus Card. London's Tube has the Oyster Card, and the Bay Area has TransLink? Why the hell isn't this thing being pimped out more? It's awesome! I mentioned it to a co-worker the other day, who's been in the Bay Area for 7 years, and he'd never heard of it. So I signed up for it for myself and Sarah, and two cards promptly arrived. If you sign up with an autoload of $20 or more, there's no cost for cards at all. So from now on, whenever we need to ride Caltrain (or BART or Muni, which are the public transport networks we're ever likely to use) we can just wave these cards at something and never have to worry about a ticket ever again. It's awesome. Apparently VTA is coming on board with it later this year, so that'll round things out nicely. It sounds like it's been an epic implementation, starting back in 1999, and still rolling out ten years later. Better late than never. The added bonus will be for our visitors. When they come, we can just give them these cards, and they won't have to deal with BART's utterly confusing (for casual riders) fare system. One of my favourite things about Hong Kong was the MTR and the Octopus Card. Now we just need awesome mass transit for the Bay Area. Somehow, I think that's going to take even longer than TransLink.

Andrew Pollock: [life/americania] First encounter with the police

I was driving home from a late night at work recently, and I was almost home, when the car behind me lit up like a Christmas tree. My immediate reaction was, "Oh crap, I'm tired and I wasn't paying attention to my speed". So I pulled over. To my relief, it wasn't my speed that was the problem, my left-hand tail light was out. The officer was very nice about the whole thing, but he gave me a fix-it ticket. He told me I had until I think some time in February to fix the problem, then I had to get a police officer to sign off that it had been fixed. I thought that was the end of it, and continued on my way home. The other day, I got this official looking letter in the mail the Superior Court of California, County of Santa Clara. My initial thought was, "ha, the fools have issued me a jury summons like they did for Sarah. Can't they tell I'm an alien? Nanoo Nanoo." So I open the letter and start scanning it. It's a courtesy notice. The first actual sentences I run into start with "Failure to respond to this notice by the due date may result in your bail being increased...". Huh? Bail? What? It turns out that there's a bit more to the fix-it ticket story. Not only do I have to get a police officer to sign off that I've had the tail light fixed, to avoid going to court, I have to pay a $25 "dismissal fee" (also known as California is broke and needs every dollar it can get). Today was the first day that either of us have had any time to scratch ourselves, so we trekked off to Toyota. The guy yanked off the cover inside the boot, and was poking around to show us where to change the bulb, when lo and behold, it started working again. So it was just a loose connector. Dammit. So now I have to track down a police officer. Preferably under the cover of darkness, as we've tinted the front windows of the Prius, which is apparently cause for another fix-it ticket. Although I'm struggling to find the wording that specifically says that.

Andrew Pollock: [life] Renovations coming along

renovate
v 1: restore to a previous or better condition
  2: make brighter and prettier
remodel
v 1: do over, as of (part of) a house
  2: cast or model anew
I much prefer the term renovate to remodel. Remodelling to me feels more like tearing down internal walls and changing the actual layout of the place. But we're in America, so remodelling it is. We've had a bit of (mostly self-inflicted) scope creep. It started with just wanting to get some Ethernet cabling installed, then we decided to get recessed canned lighting (the whole lamp thing over here drives us nuts), and then we discovered that acoustic ("popcorn") ceilings are a haven for dust mites (we're both allergic) so it made sense to get the ceilings redone while they were putting the lights in. We're also getting the light switches replaced, and new childproof power outlets. We also got the electrical panel upgraded. Removing popcorn ceilings is somewhat hilarious. They put down plastic everywhere, then have at it with a garden hose, and then it just scrapes off. The ceilings they've completely finished already look a million bucks, so we're very happy with the decision to do that. The Ethernet cabling installation caused a lot of wall carnage, so we're going to get the walls repainted as well. Then we can get the carpets cleaned and stain proofed, and then we can start thinking about trying to move some non-essential stuff in. Hopefully it'll all be done by next weekend. The kitchen cabinets have a six week lead time, so the kitchen remodelling will have to be done while we're living there. Unfortunately some unexpectedly time demanding stuff has come up at work, right in the middle of this, so Sarah's had to do the bulk of the running around to sort out contractors for all of the work, and I've been stuck at work until all hours, 7 days a week. To cap it off, I've managed to come down with a cold, and feel quite crappy. NyQuil consumption is ensuing.

Andrew Pollock: [life] Twenty weeks later

Sarah hit the 20 week mark on Monday, and so we had the big anatomical ultrasound. We also found out that it looks like we're having a girl. We're now trying to come up with a name. There was also a worrying piece of news: they couldn't see the cavum septum pellucidum, while they were checking out her brain. Apparently the cavum septum pellucidum is a particular marker they look for when they're checking everything out. Now what the absence of the cavum septum pellucidum actually means isn't terribly clear. Apparently normally this is found along with other abnormalities, but the rest of her brain structures look fine. The nuchal translucency we had earlier in the pregnancy came back fine also. So we got bustled off to have a chat with the genetic counsellor (during which the 4.1 earthquake happened). We got booked in for an amniocentesis for later that afternoon, as well as a fetal MRI at 22 weeks, and trundled off home. To cap things off, when we were trying to park back at the hospital for the 2pm appointment, I managed to scrape the car up against one of the poles in the car park. (The lower level parking is notoriously tight). Note to self: always use the free valet parking service from now on. Sarah had some second thoughts about the amniocentesis, as it does carry with it some risk of miscarriage, and after chatting with with a couple of the obstetricians, we elected not to do it. The fetal MRI should definitively determine if the cavum septum pellucidum is absent, and then we can talk to a paediatric neurologist about what the ramifications of that might be. One of the reasons they wanted to do an amniocentesis now, rather than after the fetal MRI, is the amniocentesis itself takes a couple of weeks for the results to come back, and that would bring us up to the 24 week mark. Apparently if we wanted to terminate the pregnancy, once it was at 24 weeks, we'd have to go to LA to do it. Whilst I consider myself an atheist these days, I was raised a Catholic, and although I like to think of myself as pro-choice, I still have a lot of problems with abortion, so I don't think I'd be comfortable terminating unless it could be shown with reasonable certainty that our baby was going to be in a really bad way. Based on how the rest of the brain looked, and the nuchal translucency results, and the fact that the amniocentesis would only identify chromosomal and not genetic neurological disorders, I don't think we'll be aborting. From my limited research, it sounds like the cavum septum pellucidum disappears at about 3 months after birth anyway, so looking at it one way, you could say our baby's brain is developing faster. Other research has indicated a correlation with optic nerve development issues, so I don't know if that means she might be blind. We really need to chat with a paediatric neurologist. But hopefully the fetal MRI will find it, and this will turn out to be nothing. An anxious two weeks will now follow.

24 December 2009

Andrew Pollock: [life] Homeowners!

There was a minor hiccup yesterday. Our mortgage broker called me up towards the end of the day in a flap because something had gone wrong on the seller's side of things, and their bank hadn't accepted the transaction or something. I still don't know the full story. Something about them missing a mortgage payment possibly. Anyway, she was able to arrange for funding and closing today, instead of funding yesterday and closing today, so the outcome was still the same. Now the real fun starts. The first thing I did tonight was program the garage door opener into the Prius' HomeLink thingy built into the rear vision mirror. It's always nice to be able to use a feature, even if it's taken 4 years.

22 December 2009

Andrew Pollock: [life] All that's left is to pick up the keys

Yesterday morning we went to the title company to do all of the paperwork for the condo purchase. I'm still not entirely clear on the whole process, but basically we signed a ton of disclosures and the loan documents, and the whole lot got notarised. I found the thumbprint requirement rather amusing. So the loan should fund today, and the title change will register with the county on Wednesday, and by tomorrow afternoon, we should have the keys. We then had to do a walk through to sign off that the property hadn't turned into a pumpkin since we put the offer in. It was only the second time I've been able to see the place, so it was good to take another look. Sarah's been doing lots of running around to organise quotes for the kitchen renovation and measure the windows for curtains, so she's seen it many more times. There's going to be a few little odd jobs that need doing around the place. There's a few lights that aren't working (presumably just bulb replacements. There's an outside cupboard that's falling apart. There's a little water feature that I think we'll just get rid of, as the pump is a waste of electricity and it'll just breed mosquitoes otherwise. It's going to be home.

2 December 2009

Andrew Pollock: [life] We're under contract

Well that all happened rather quickly. This morning, we met with our agent to go through all of the offer paperwork, at the bright and early time of 7:30am after (for me at least) a bad night's sleep staring at the ceiling. It wasn't that bad. A lot of disclosures, a lot of initialling and signing. Here's what the stack of paperwork looked like: The paperwork for our offer on the condo The existing building reports didn't come back with any red flags. There's a little bit (around $1,000) of termite damage. We put in the contract that the sellers have to fix that. The hot water tank needs to be strapped to the wall to be in earthquake compliance. We put that in the contract too. A couple of hours later, we'd got all of the paperwork out of the way, and Nick said he'd present the offer to the seller's agent at 3pm. I got a phone call at about 5pm from Nick saying that they'd accepted the offer, with all of our conditions, so we're all ready to go for closing on the 23rd. Apparently the reason the sellers are so motivated is because they borrowed against the equity in this condo to buy a house, so they're eager to close the deal. We managed to negotiate the price down slightly to $519,000 (anything lower would have been a short sale for them, and we already know all about what that can entail). Even for that price, they've made a tidy profit on the $180,000 they paid 14 years ago. So this is working out really well, timing-wise. We'll close on the 23rd, go visit Chris, Bri and Clara in Atlanta for Christmas, and then have all of January to do any work on the place before our current lease expires. Just got to wait for the finance approvals and an international money transfer now. I'm slightly miffed that I booked it yesterday at 0.90 cents, and the AUD has risen to 0.92 cents today.

1 December 2009

Andrew Pollock: [life] I think we've been bitten by the bug...

So we pretty much gave up on the condemned house. The more we hear about it, the worse it looks. Our agent got some paperwork on the red-tagging today. Apparently the large room out the front used to be a car port, and enclosing that was done without a permit. There's also a standalone room out the back that has had a bathroom added without a permit. Apparently the owner is getting fined $2,500 a day by the city until it's either brought into compliance or reverted. No idea if that's actually being paid, or who's responsibility it would become in the event of a sale, so we'll just quietly back away from that whole mess and pretend it never happened. Sarah was poking around Redfin again last night and found this property, for less than what the condemned house was going for (granted, this is a condo, not a house). We got our agent to show it to us today, and we really liked the look of it, so we're going to put an offer in on it and see what comes of it. We have to spend about three hours with our agent tomorrow morning going through paperwork. Wee. It certainly seems like a good time to be buying. Interest rates are low, the AUD is high against the USD, and prices are down.

30 November 2009

Andrew Pollock: [tech] Review: iGala digital picture frame

Now that I'm not letting the cat out of the bag (I bought these as gifts) I can write a review. The use case was pretty simple: I thought it'd be a cool Christmas present for our parents to give them something Internet-enabled that would give them regular updates on their grandchild (when he/she arrives). I was thinking a picture a day type of thing. So I hunted around for a WiFi-enabled digital picture frame, and found the iGala being sold pretty much exclusively by ThinkGeek. The reviews seemed pretty good. I know WiFi-capable frames have been around for a few years, but they always seemed to be pretty lacking in terms of WiFi functionality. Like they wouldn't do any security, or they'd only do WEP. This particular product claimed to do the whole gamut, including WPA2. The fact that it was a touch screen and ran Linux also made it appealing. So I ordered a couple of them for a few weeks before we headed to Australia, with the intention of making sure that they'd work. Here's the highlights. WPA2 didn't work (nor did WPA) Despite the software on the frames claiming to be able to talk WPA2, the frame would not associate with my Linksys WRTU54G-TM. I had to drop it all the way back to WEP to get it to connect. For me, this was the most disappointing failure. I bought the product specifically on the strength of its claim that it supported WPA2, and it just didn't work. It was also pretty impossible to debug the failure. I downloaded the latest firmware update, and that added additional settings for TKIP or AES when selecting WPA2, but neither option helped. The automatic updates are brain-dead Speaking of downloading firmware updates, the latest firmware that I downloaded and installed on the frames added automatic over-the-air firmware updates. Nice enough feature, except for the implementation. The frame tried to make an HTTP GET request for a non-existent file, every 6 seconds. So the frequency of checking alone is totally ridiculous, but couple with this the fact that it's making a GET request (this is what $DEITY invented the HEAD request for, people!) and the website has a "friendly" 404 Not Found page that weighs in at a little over 10 Kb. By my calculations, that's nearly 150 Mb of failed update checking traffic a day. Taking these frames to a backward country like Australia, where ISP users still have monthly quotas, gives the frame a pretty horrendous running cost in terms of traffic. Not to mention the outbound bandwidth requirements for the server hosting the updates. Crikey, the mind boggles. I'd have thought checking once a day and on power on would be perfectly sufficient. Transitions are unavoidable It may be just me, but I hate cheezy transitions. Digital picture frames tend to come with a myriad of them, but they all look cheap. It's impossible to tell the frame to just change the picture, it has to use at least one transition effect all the time. It defaults to randomly choosing from all the available ones. At least you can tone it down to just one. Automatic on/off time I liked that it was possible to configure operating times. No need to have the thing chewing power 24x7. It just seems to turn off the backlight outside of the programmed operating hours, so it's still doing the lame uber-frequent and bandwidth-intensive checking for updates even when it's "off". Photo check frequency is configurable Another nice feature was the ability to check for new photos at varying intervals. What I wanted for my parents was to just update once a day, so they'd get a new photo every day (assuming we put a new one in the Picasa web album that it's checking). This was very doable, and coupled with the automatic on/off time, means they should wake up to a new photo every day (that we change it). Built in photos are a bit too sticky There's 3 or 4 in-built photos as part of the firmware. If there's nothing accessible or available online, it'll cycle through these. Somewhat annoyingly, you need to have at least two photos in your online source for it to stop wanting to incorporate the stock photos in the mix. The workaround is to put the same photo in the online album twice, so you don't realise it's switching between two images. Lame, but it works... Touch screen UI was adequate Given the alternative user interface for digital picture frames is a little IR remote control and some dinky menus, the iGala was nice to configure. A full on-screen QWERTY keyboard pops up for entering WEP/WPA/WPA2 keys and configuring the Picasa/Flickr connections. Fairly responsive support The main near-showstopper for me was the lack of advertised WPA2 support. I emailed the Aequitech support folks quite a bit during my "evaluation" period. They got back to me fairly quickly most of the time and wanted to know exact details of my setup so they could reproduce it in the lab. They'd be well served having an actual ticketing system, instead of hiding behind an email address, as it made it hard to keep track of the multiple issues I was raising with them. It's written in Lua?! I have no familiarity with Lua, other than I know of its existence as a programming language. I'm curious as to what their motivation was for this language choice. All of the Lua code shipped in the complete firmware refresh ZIP files is bytecode. I have no idea if it's possible to decompile it. The CPU architecture would appear to be a Blackfin based on the few compiled binaries included in the full firmware. Easy to update Prior to the new update "functionality" I've already railed against, it was pretty easy to update. Download a ZIP file and a shell script, put them in the root directory of a USB key, and plug it into the frame and stand back. The updates don't seem to cryptographically verified (even the over-the-air ones), so I wonder if it's possible to break into the frame by way of a cleverly crafted "update". I have no idea what breaking into the frame would buy you. I don't know what sort of computing power they have. Conclusion I still think the iGala is a reasonable, if somewhat immature product. If the software is going to be actively worked on, and the support people continue to be responsive, then I think it's got good potential. For the price, I expected a more polished product, though. I received an email from their support people shortly after returning from Australia saying that they'd fixed the WPA2 problem. Unfortunately I had no intention of trying to remotely talk my parents through how to reconfigure their access point or the frame (interestingly WPA2 didn't work with their Linksys WAG54G2 either, so I'd love to know what WPA2 devices it was tested with), so it's 128-bit WEP until I next go to Australia.

Andrew Pollock: [life] When it looks too good to be true...

Yesterday, we managed to inspect the property that was for sale that we'd discovered. I think you could best describe it as a renovator's delight that's had a bit of work done on it. The kitchen is pretty new. The bathrooms are pretty good. There's some cracking around the place, and the floating floor looks like it's a bit of a dodgy job. That said, it definitely had potential, and for the asking price, assuming it wasn't structurally unsound, was something we could see ourselves doing up and flipping when we finally move back to Australia. So our agent told us we needed to get pre-approved for finance as the next step, and hooked us up with a mortgage broker, who was able to see us today. She said that pre-approval would be no problem, and we got what seemed to be a ridiculously good rate for a 5 year adjustable rate mortgage. Our agent called us back tonight and told us that there was another offer on the table for less than the asking price, and that the property had been red-tagged. It would appear that none of the modifications had permits. He's going to check with the city tomorrow to find out exactly what the nature of the red-tagging is all about, and what would be involved to get the property un-red-tagged, but I've got that feeling that it's going to be better to just walk away from it at this stage. So that's how we've spent our weekend. Speculating on real estate.

28 November 2009

Andrew Pollock: [life] Thinking about moving

Our lease runs out at the end of January, and we're thinking about moving to a bigger place. In the four years we've been here (yeah, we just crossed the four year mark the other day) we've often thought about trying to buy as well. We go through these phases where we really feel like buying, then we run the numbers and run screaming back to the warm bosom of renting. A couple of months ago we had the most serious foray into buying. We'd just checked out the models for Mondrian and we really liked the floorplan for Bleu, and found the price to be the least breathtaking of anything we'd looked at in the Bay Area. I got as far as talking to mortgage brokers and running the numbers, and the things that killed it for us were the property taxes and homeowners association fees. The monthly repayments would have been doable, but it'd have really been a ball and chain. We're over here to see the country as much as anything else, and if the mortgage is going to be a significant impedance on our ability to travel, then there isn't really any point in doing it. So we sadly passed up on Mondrian. The three bedroom townhouses in our current complex are going for around the $2500 a month mark, which is a pretty serious jump on what we're paying now for our two bedroom one, so Sarah's been scouring Craigslist for anything better. She found a 2 bedroom plus loft condo being rented privately in Mountain View, which we took at look at on Wednesday. The immediately downsides are it's older (the kitchen and bathroom are really a bit dated) and has no data cabling (this is something I've really loved about our current place) and no microwave oven included. The upsides are it's significantly bigger (about 500 square feet larger), the kitchen has heaps of cupboards, it has a washer and dryer, a lock-up garage, a small, fairly private yard (the rent includes a gardener), and it has what looks like a communal garden bed (the thing that really caught my eye were the compost bins). So I think overall, as long as we can live with the kitchen and bathroom, it's going to be an improvement on where we are now. The windows are all double glazed, so it should be fairly well insulated. It's got a gas furnace and gas hot water, and I think the landlord pays for the water, so I think the utilities would at best come out the same as what we're paying here. We've decided to put an application in for it and see what happens. The landlord is living overseas, so we're dealing with a real estate agent for the letting. Apparently we'd be paying the rent via PayPal or something. He's got a home warranty arrangement for maintenance, which sounds like it'll be pretty good. Meanwhile, Sarah was scouring Redfin and found a house nearby that is for sale (a short sale), which is pretty reasonably priced. We've called up a real estate agent, and we're taking a look at it tomorrow, just because we can.

Andrew Pollock: [tech] mirror.linux.org.au upgraded

I took advantage of the four day weekend for Thanksgiving, and finally got around to upgrading mirror.linux.org.au from Debian Etch to Lenny. The upgrade went fairly well. Notably, Drupal completely blew up, but it looks like we were still running the package from Sarge, as Drupal wasn't in Etch at all. I cut my losses, installed Drupal 6 and put something basic together from scratch. MoinMoin upgraded fairly painlessly, and I figured out how to fix Cacti for my installation at home at the same time, so that was a general win all round.

23 November 2009

Jon Dowland: shell scripts

Russell Coker writes about shellscripts. I have a different suggestion. Whenever you think that a shellscript is the right solution to a problem, you are mistaken: do it in a proper scripting language instead. Having access to proper data structures will mean you don't have to contort your code to fit values into scalar strings, or write loads of temporary files, or call cut/awk/sed/grep etc. repeatedly on the same inputs to get at different fields, etc. etc. etc. I reckon nine times out of ten it's the right decision. But when you just have to use a shellscript, use set -e (as Andrew Pollock points out, this is safer than putting it on the hashbang line and set -u too.

21 November 2009

Andrew Pollock: [tech] LVM gaining the ability to merge snapshots

I love LWN. It's the best value for money way of keeping abreast of what's going on out there. I also love LVM. I'm thrilled to learn from a comment on this article about Btrfs, that LVM is soon to gain snapshot merging support. This is going to be absolutely fantastic for rolling back upgrades that go bad. I can't wait.

Next.

Previous.