Search Results: "Andrew Pollock"

22 November 2005

Christian Perrier: Bayonet

Thanks to Andrew Pollock, I now know how to write "ba onnette" in English. "now know how": nice....probably wrong but nice. Andrew, continue with your life experience of weird things happening to Australian people left in Californian jungle.

Andrew Pollock: [life/americania] My kingdom for a bayonet light bulb

So, they're obviously very proud of the fact that Thomas Edison invented the light bulb, as they're all Edison Screw over here. Nary a bayonet to be found anywhere. Difference illustrated here. On Sunday we went to Home Depot (the one we walked into at Milpitas could have been Bunnings at Fyshwick if it were green instead of orange), and when I asked someone about light bulbs with bayonet fittings, he made noises about auto shops and stuff, which suggests that they just don't do house lighting with them at all. Why do I want a bayonet light bulb so badly? I have a lamp that was made by my late grandfather, which is one of the few non-dual voltage items I didn't jettison (probably the only one actually), and I was rather keen to actually use it. I don't expect the bulb that was in it to survive the shipping process, and even if it did, if it didn't instantly blow up at 110V, I suspect it would be a bit dim. If anyone knows of any bayonet-to-edison adapters, please let me know. Update: Google is my friend

Andrew Pollock: [life/americania] Australian to American translation #2

ta
thank you
manchester
sheets and towels and things of that ilk

20 November 2005

Andrew Pollock: [geek] Debian saves the day again

I'm already over punching in over thirty numbers to call people back home with the prepaid phone card I've bought, so I did a quick apt-cache search dtmf, happened upon dtmfdial, and in five minutes had a quick and dirty shell script making my laptop do all the button pushing for me. So as to not drive anyone in earshot insane, I just hold the cordless phone's microphone to my headphones. Of course, if the phone had a speed dial, all this would be unnecessary.

Andrew Pollock: [life/americania] Australian to American translation #1

(Despite what I said, I'm still going to feed this to Planet Debian as I've actually had one person ask me not to stop)
feature wall
accent wall
ensuite
confused look from apartment leasing salesman (Australian for the bathroom attached to the master bedroom)

Andrew Pollock: [life] Hello America!

Where do I start? It's been an eventful couple of days... The flight to LA was uneventful. Qantas is certainly orders of magnitude more pleasant to fly with than United, even though we were seated in a bulkhead area. I had a 13-month old baby seated next to me (no, Mikal was on the other side), and he was about as well behaved as you could possibly ask a 13-month old baby to behave. Mikal also behaved himself. I had the intention of trying to get something approximating 8 hours sleep, as we arrived at LAX at 7am local time, but I only managed about 4 hours. I did spend about 8 hours with a mask on and my brain in idle, so I arrived at LAX being mostly coherent. Entering the US via LAX was a much less traumatic experience than I was expecting. The E-3 visa was accepted fine, and I now have an I-94 stapled into my passport. Quarantine involved getting looked up and down by a guy in a booth, who waved me through. We had 3 hours to spare (or about 2 by the time we cleared all the immigration/customs queues) and then hopped on a 50 minute American Airlines flight to San Francisco, hired a car and drove to Santa Clara. The accommodation we're staying in for a month is very spiffy indeed. It's a largish gated community of units. Mine's got a ground floor entry, but everything else (except the garage) is upstairs. When Sarah gets here, we'll put up some photos. The weather is lovely as well. Our first outing was to the Social Security office to attempt to get social security numbers. This wasn't as successful as I'd hoped, as we were too freshly in the country to show up on their systems, so we left with letters saying we'd get one within four weeks, when our details had been verified. Yesterday evening, we went for a general recce of the surrounding area, and checked out a supermarket. That was less disconcerting than I expected, although I don't think it was a terribly huge supermarket. Having a GPS certainly raises one's confidence when navigating significantly. Last night I discovered that all the keys in my apartment were not created equal, and that the two loose in the lock box on the front door were the only two that opened the unit, and the two sets on key rings on the coffee table only opened the amenities and my mailbox. So I got to spend a bit of time sitting on my front doorstep until the nice man from Synergy Relocations came out to let me in (except his key didn't work either, so he got to make conversation with a legal alien while we waited for someone else to come out with a key). Today, we drove around to see a shopping mall, and the first set of shops we found happened to be around the corner from an enormous (by my standards) apartment complex, which had some signage implying that it had vacancies, so we decided to get the low down on how renting worked before we did our rental tours. Casey drove us around in a golf buggy and gave a tour of what two different floor plans looked liked. It seems that in this part, it's standard for an apartment to include the refrigerator, dishwasher, microwave, washing machine and clothes dryer, which is good to know. Let me just say that if this is what living in an apartment complex is like, it's more like living in a resort. The place had pools everywhere, tennis courts, two gyms, a community centre, it was just unreal. It was also cheaper than I was expecting. We then went to a massive shopping mall to do some window shopping. Discovered Wetzel's Pretzels. Hope they're not too fattening... Tomorrow, I'm going to avail myself to the complex's gym, and generally get ready for the week ahead. Future posts will be in a new category, which I won't be feeding to Planet Debian as not to bore people. I will inflict Planet Linux Australia readers with them until someone asks me to stop. If you'd like a custom feed that excludes my American adventures, please let me know. I wonder if adjusting Blosxom's idea of timezone buggers up existing posts and aggregators like Planet in general?

18 November 2005

Andrew Pollock: [life] Farewell Australia

Well, this is it. I'm in the Qantas Club with Mikal, the flight to LA boards at 12:35 or something. I ticked the "not coming back box" on the departure box. This is going to be one hell of an adventure. Bring it on!

17 November 2005

Anthony Towns: Afraid of your Neighbour's Disapproval

Continuing on from the SCC stuff, which I should probably get in the habit of calling the mirror split, then… At the same time as I’ve been trying to work out ways to fit the mirror split stuff into the AJ market concept, I’ve been pondering on and off what can be done to improve the security situation. My thinking’s probably still biassed by my long time wish for official security updates to testing, but I’m somewhat inclined to think that if we can figure out a way of integrating the testing security team and the official security team we might end up closer to a solution – at the very least that’d provide us with a decent number of people who can actively help out with security updates that aren’t secet and get a few more people familiar with the technical aspects of how security updates are released, who’ll then have less of a learning curve if they end up being added to the security team proper. And heck, even if that doesn’t work, it at least gives people running testing an easier url to remember for security updates. Of course, integrating the teams isn’t that easy, or it would’ve already been done. So after thinking about it, I had a chat with Joey (aka Martin Schulze, aka the guy who’s issued 317 of the 340 security advisories in the past 12 months) about the problems:
<aj> so, the other thing i wonder is what you think of the testing-security-support split?
<Joey> need more input
<aj> as in separate host, funny domain name, not available on security.debian.org/, extra effort to mirror, etc
<aj> i think it sucks :)
<Joey> there are a lot of sucking things…
<aj> it’s true
<aj> so, i figure the reasons for the split are (a) you don’t want to add a bunch of people to team@ and hence vendor-sec, and (b) there’s no way to make it so they can use dak-security without being full team/vendor-sec members; and maybe (c) you don’t want them officially associated with debian security coz they’re newbies
<Joey> a) and b) are true
<Joey> However, with security.debian.org being a push mirror, it would be possible to let it be pushed from a second source into a different directory, such as /testing-security/
<aj> hrm
<Joey> However, that would require all architectures to be supported and not just some.
<Joey> all as in “all that are in testing”
<aj> ah, that’s (c) then – they don’t do enough for the official debian stamp
<Joey> ah ok
Assuming those really are the key factors (which might or might not turn out true, but they seem likely) then that’s something that can be worked on. The first point is completely out of my domain – I’ve never been on vendor-sec, and it’s not likely something that ought to be tweaked much anyway; vendor-sec’s a very closed list by design, and for most security work it’s probably a distraction (testing security as is currently operates without concerning itself with vendor-sec, AIUI); the second points purely technical; and the third point is a combination of technical issues and an issue of training, both of which will be hopefully helped a lot by integrating testing-security and security.debian.org. So the easiest point of attack is obviously the second one, since it’s “just” a matter of expanding dak’s featureset. The problem here is embargoed fixes – the security team needs to be able to prepare fixes for vulnerabilities revealed on vendor-sec, but then keep them secret from everyone not on vendor-sec until the publication date. Which is fine, except that dak takes an all or nothing approach to that sort of secrecy: secuirty uploads go into accepted, get built, and then the security team run “amber” to publish the update. But what that means is the accepted directory and its contents can only be visible to people with vendor-sec access, which means only people with vendor-sec access can do security updates. But we do actually have a different queuing mechanism that allows us to keep some things secret, while not hiding everything: thanks to the crypto-in-main transition, the NEW queue acts like that, more or less, only allowing ftpmaster to see the contents of NEW packages until they’ve passed license inspections and the appropriate export notifications have taken place. And actually, we’d already considered extending that sort of behaviour to add an “unapproved” queue that would prevent uploads from entering proposed-updates without the stable release manager’s prior approval. The idea then, would be to have a couple of queues for the security team: an embargoed queue, accessible only to those with vendor-sec access that would store embargoed fixed ‘til they’re ready to be released, and an unembargoed queue for preparation accessible by a wider group, for preparation of fixes that don’t need to be secret. Both queues would need to be autobuilt (and the build logs for embargoed uploads would need to stay restricted, while the build logs for unembargoed uploads would not), which is an added difficulty, since only accepted can be autobuilt presently. But otherwise, it seems basically plausible, both to myself and Joey. Conveniently, Andrew Pollock’s been interested in throwing some money through the AJ Market to see what happens, and since the initial idea we were tossing around fell through due to his move to the US, he’s put up the dosh to make the above happen. Well, strictly the dosh to make me make the above happen, or something. Anyway, I’m already running behind both in implementation and blogging about it, so back to the grindstone… (Okay, perhaps it’s not quite the feature Mark Twain would most like added to dak, but it’s still nifty.)

15 November 2005

Andrew Pollock: [life] An uplifting experience

So, as of sometime this morning, most of our worldly possessions were (in cartons) loaded into a shipping container bound for the US. Unfortunately, I don't finish work until Wednesday, so my lovely wife was charged with supervising the packers yesterday and today. My one word of advice with respect to packers is to be extremely careful, and assume that they will assume nothing. If you don't want something packed, don't leave it unsupervised or anywhere where it may be packed. My electric toothbrush was left unattended for slightly too long, and is in a carton somewhere. As was half of the bike rack until we raided a few cartons last night and rescued it. Obviously literacy doesn't rate very highly as a requirement to be a packer either. We had "stools" spelt as "stulls" and "wine rack" spelt as "win race" on some of the items packed. I'd also never seen a couch bubble-wrapped until yesterday. Pretty much no item was left exposed. Everything is either in a carton or bubble-wrapped with funked brown-paper-backed, branded bubble wrap.

14 November 2005

Andrew Pollock: [tech/security] Is there a new BIND vulnerability lurking in the wings?

In recent times I've started seeing something in my logs that I haven't seen before. I'm yet to do any further investigation, but I suppose the next steps would be some packet captures and BIND source code poking...
Nov  8 02:13:16 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov  8 02:13:16 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov  8 02:13:16 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov  9 01:08:33 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov  9 01:08:33 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov  9 01:08:33 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov  9 10:01:13 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov  9 10:01:13 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov  9 10:01:13 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov  9 10:01:13 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov  9 10:01:13 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov  9 10:01:13 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov  9 10:01:13 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov  9 10:01:13 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 11 00:02:35 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 11 00:02:35 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 11 00:02:35 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 11 00:02:35 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 11 00:02:35 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 11 00:02:35 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 13 02:05:47 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 13 02:05:47 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 13 02:05:47 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 13 02:05:48 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 13 02:05:48 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 13 02:05:48 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 13 23:03:05 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 13 23:03:05 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 13 23:03:05 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 15 02:37:32 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 15 02:37:32 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 15 02:37:32 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 15 02:37:34 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 15 02:37:34 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 15 02:37:34 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error
Nov 15 02:37:34 daedalus named[6933]: errno2result.c:109: unexpected error:
Nov 15 02:37:34 daedalus named[6933]: unable to convert errno to isc_result: 14: Bad address
Nov 15 02:37:34 daedalus named[6933]: dispatch 0x80f6970: odd socket result in udp_recv(): unexpected error

10 November 2005

Andrew Pollock: [code] Distributed code reviews are cool

Thanks Sam for your even more compact (but harder to follow) PHP code to find a specific instance of a given day in the month I haven't tested your first function rigorously, but it seems to hold up to the second and fourth Thursdays of the month, which is mainly what I'm after. The second function, which avoids function calls, appears to suffer from a partial off-by-one bug.

Andrew Pollock: [life] And it's not even summer yet!

My friend Kim, who's done the Brisbane → Melbourne → Brisbane thing (like I've done the Brisbane → Canberra → Brisbane → Canberra thing) is finding summer back in Brisbane a bit uncomfortable. When I moved back to Brisbane I did it around this time of year, and coming from Canberra's late spring (which actually behaves like a late spring) to Brisbane's eternal summer of a spring is a bit of a shock to the system. The humidity was the prime factor in me wanting to return to the blissful dry heat of Canberra's summer. Kim, I feel your pain, furthermore, I'll be in Brisbane this weekend to feel it in person.

Andrew Pollock: [code] Finding a specific instance of a given day in the month in PHP

When I took over organising the CLUG meetings, I managed to replace most of myself with a small shell script (I even have the t-shirt). Now that I'm leaving Canberra, Steve Walsh has kindly taken over the running of the script. So I've done a bit more work on the script, and added a public front end to it, and made an RSS feed (my very first). So until yesterday, to work out the fourth Thursday of the month, I'd been calling a Perl script that used Date::Manip, when I decided to investigate doing it with PHP natively. Tony gave me some initial code, but I ended up with this:
function nth_day($instance, $dow, $month, $year)

    
$first_dom = date("w", mktime(0, 0, 0, $month, 1, $year));
    
    if (
$first_dom <= $dow)
        
$first_instance = date("j", mktime(0, 0, 0, $month, 1 + ($dow - $first_dom), $year));
     else
        
$first_instance = date("j", mktime(0, 0, 0, $month, 8 - ($first_dom - $dow), $year));
    

    
$instance_we_want = $first_instance + (($instance-1) * 7);

    
$date = date("j", mktime(0, 0, 0, $month, $instance_we_want, $year));

    return
$date;

7 November 2005

Andrew Pollock: [debian] Ouch

Greg Kroah-Hartman did say:
If you have a problem with the way Debian handles udev, I'll point you to the proper place to complain about that. Debian is slowly sinking into the muck and it's fun watching it happen.
That hurts.

6 November 2005

Andrew Pollock: [code] Obfuscating email addresses with JavaScript

So I got pet peeved by Carlos Laviola in relation to by recent pondering about how MacOS X's SSH agent starts up on login. Perfectly reasonable grounds for complaint. I have had people contact me in relation to blog posts in the past, so it's obviously not impossible. People know I'm a Debian developer and can put two and two together and wind up at db.debian.org. Anyway, I'm the first to admit that my blog probably has too many of the Weblog Usability Top Ten Design Mistakes (something for me to work on). To date, I've been avoiding plastering my email address on my website because I didn't want to get it harvested. I try and use a per-list email address for this reason as well, and I haven't enabled blog comments because of comment spam, and because I haven't been clever enough to implement comments with Blosxom full stop. So I started getting an idea for reversibly encrypting my email address on my blog after reading about Hashcash for Wordpress the other day. I first started playing around with the Vernam cipher in High School, when I wanted to easily reversibly obfuscate some data for something. I'd read about this cipher in a magazine or something and seen it implemented in Pascal (it's not exactly hard). So I happened upon the idea of encrypting my email address with the Vernam cipher. Turns out another chap's already got a page for encrypting and decrypting on the fly with JavaScript. It even generates the JavaScript for putting in your own web pages. I had to use a different key to avoid getting dollar signs in the encrypted string, as this confused the tripe out of Blosxom (and me for a while when I tried to figure out what was going wrong). Then I thought it'd be nice to explain to people who had JavaScript disabled what they might be missing out on, so I fiddled around with some DOM stuff, and had some text get displayed if JavaScript was disabled. When JavaScript is enabled, this text is replaced by the decrypted text. So of course, like the Wordpress Hashcash, this is largely relying on the inability of spam bots to grok JavaScript. Once they can, this obfuscation technique is all for naught. Meanwhile, you can email me bit more easily now if you get the urge. View the source of my blog for an example of the implementation.

Andrew Pollock: [code] Canberra Perl Mongers meeting

The Canberra Perl Users Group is having one of its extremely irregular meetings next week. If you're in Canberra, or will be on November 2, let me know. The last one wasn't too bad. http://mail.pm.org/pipermail/canberra-pm/2005-October/000146.html

2 November 2005

Andrew Pollock: [tech] The quest for IPMI LAN access over down interfaces continues

Today I upgraded daedalus to 2.6.14. I had to backport yaird to stable, which wasn't a big deal. It's available here if you're interested. The kernel package for 2.6.14 from unstable worked fine otherwise. I had two motivations behind upgrading - inotify and another look to see if the situation with IPMI had changed. Well inotify just works, and is the bomb. I'm going to have lots of fun with it. IPMI, on the other hand is still broken, which makes me sad. As I've previously pointed out by way of example, LAN access to the base-board management controller via IPMI is impossible after Linux shuts down the interface. It's supposed to work, but the way Linux does it seems to stop it from working. I'd read that the problem was resolved in 2.6.12, and so dutifully tested it out on daedalus to my detriment. I also tested it on 2.6.14, but again, had the same problem (I remembered to schedule a deferred reboot this time). So IPMI with a box running Linux is all good as long as the box is actually running. I suspect if the box panicked and/or hung itself, it'd also be useful for rebooting it, but if you shut the box down and remove power, IPMI won't allow you to turn it back on again.

30 October 2005

Andrew Pollock: [tech] How does MacOS X (Panther) start ssh-agent?

Dear Lazyweb, Ever since I reinstalled my PowerBook a few months ago, after I'd put back on all my software (including the lovely SSHKeyChain), I couldn't get the same SSH agent behaviour I used to have. Specifically, the first time I'd SSH somewhere after logging in (or after awakening the laptop), I'd be prompted (in a nice GUI kind of way) for my SSH passphrase, after which the private key was loaded into my SSH agent, and life was good from then on. That is no longer the case. I get prompted for my SSH passphrase in the terminal window and on a use by use basis, i.e. the key isn't being loaded into my agent after the first time I get asked for my passphrase. I think the root of the problem is that my ssh-agent is being started with the -c option (generate C shell commands) when I'm actually using Bash. So, the crux of my question is where the hell does ssh-agent get started from, and how can I change how it is started? Love and sloppy kisses, Andrew

28 October 2005

Andrew Pollock: [tech] The FAI FAQ has been obsoleted by the FAI wiki

For a few years I've hosted a Faq-o-Matic instance for FAI. I received an email today from someone saying that all of the content in the FAI Faq-o-Matic had been merged into the FAI wiki, so I've just reconfigured my web server to redirect visitors straight to the wiki. I'll give this a couple of weeks or so for the search engines to all get with the program, then I'll completely decommission the web server.

27 October 2005

Andrew Pollock: [clug] Last CLUG meeting for a while

Tonight was my last CLUG meeting for a while, and it was a pretty good one. We didn't have a whole lot of structure to the meeting. Bob gave a couple of short talks. I gave a short talk off the cuff about the wonders of LVM. Hugh showed off some virtual reality goggle things. Alex tried to have a bit of a hackfest on Coda, but I think there was a general lack of Coda fu, so that didn't get very far unfortunately. Steve Walsh has kindly offered to take over as the person behind the shell script that schedules the meetings, and I've moved it from caesar (in the cupboard at home on the end of an ADSL connection) to daedalus in Brisbane, so it will continue to be accessible while I'm relocating. I'm looking forward to checking out SVLUG and BALUG (which seems to have fallen off the Internet (from home) at time of writing, looks like someone needs to read the IETF's BCP #16).

Next.

Previous.