Search Results: "ag"

3 October 2007

Ian Wienand: POWER5 Graffiti

On the bus yesterday I noticed a graffiti etching clearly left by someone employed by IBM. In fact the guy in the row in front had an IBM tee-shirt on, and I suspect he is the culprit, or possibly one of the OzLabs people. The photo is crap (it's hard to take a photo of a blukhead in the dark from the middle of the back seat on a crowded bus with a phone camera without arousing suspicion) but it clearly says
   I
(heart)
 POWER5
Check out my CSI style image enhancement: I (heart) POWER5 If you're ever on Sydney Buses bus number 2660 it can probably still be seen on the driver side window on the back seat. Maybe what Itanium needs isn't higher clock speeds, lower power, faster FSB, etc., but a concerted tagging effort on public transport around the world!

Matthew Palmer: That Didn't Take Long

Although I predicted that I'd be a busy boy with my bushfire brigade on Tuesday, I wasn't expecting to get our first "Bush Alight" fire call so quickly. But, yesterday (Wednesday), a few minutes after 1800, off goes the pager, and off I go to the station. Thankfully the high winds that had been a major feature of the day had settled down quite a bit, so it was relatively easy to control and stamp out (we were back at the station by around 2015) I still found it a little overwhelming -- "I'm supposed to help Stop This Fire". At a couple of hectares in size, it wasn't too massive, and it wasn't visually "spectacular" (like the fires you always see on the news) but still... given that my only experience of fire in the past has been small campfires and the occasional bonfire, having an area the size of a football field in front of you glowing with embers and flaring with small clusters of flames, it was certainly a very different experience. The heat, the smoke, the noise (those truck pumps are loud), and the adrenalin, it's a hell of a mix. Being that I'm the newest and least experienced crew there, I got given the unglamourous but important job of controlling traffic, as we had one lane of the one-each-way 100km/h road closed to give our crews more working space around the trucks. Let me just say that I now have an infinitely greater respect for road repair crews, and I think that every person should do an evening of traffic control with a group of their mates on the road behind them, so that they know what it feels like outside their car. Car drivers do the darnedest things. So, I've popped my bushfire-fighting cherry now, and I'd be more than happy if there's nothing more impressive than that awaiting me for the rest of the season.

Daniel Burrows: Feline Love

Coding while a cat kneads your chest: awkward.

Coding while a cat sleeps on your face: difficult.

Coding while a cat nibbles on your fingers: painful.

Coding with a cat snuggled up against your side: adorable.

Otavio Salvador: live-helper has splited syslinux templates

To reduce the duplication and make the maintainence easier, syslinux templates has been splited. Currently both normal and menu share common templates using a common directory and the required files are copied to the image during the build. The only current know regression is PXE that needs fixing to work with this new templates however the rest should just work. I’d suggest to everyone interested on Debian Live do a try on it. The easier way is to use the snapshots of live-helper and use it normaly. Thanks to Daniel by merge all the fixes so fast and to keep this nice peace of software working :-)

Thijs Kinkhorst: Welcome back red pencil

This Monday, state secretary Bijlevelt of interior affairs finally decided that any current type of voting computer is not safe enough for elections. This decision is not a surprise for anyone who's followed along with the wedonttrustvotingcomputers.nl action group, but it's the first time the government has acknowledged the full problem. This means that on the next "election" at October 10th here in Utrecht, already the red pencils will be recovered from their long time storage. Most interesting about this whole discussion is the question I only see asked sparingly:
What problem are voting computers trying to solve?
As a data point: on the last general elections, the Amsterdam district finished their counts of pen-and-paper voting before midnight on election day.

Chris Lamb: Yet another community Xen Server

For the last month, I’ve been running a non-profit Xen server for a few friends. It’s been working really well but I’ve got three two one no slot left. I think it’s quite good value: £7.88 per month (£17.73 setup) gives you: If you’re interested, please drop in on #lamby-xen on OFTC. UPDATE: All gone. Thanks for the huge interest. :)

Steve McIntyre: Hypo Full Of Love

Went to see Alabama 3 in concert in Cambridge last night. The support act were dreadful, doing over-amped reggae mixing for far too long. Tedious. But when the headliners came on, they more than made up for it. Incredibly good fun, danceable music, a mix of gospel, techno, blues, country and good old-fashioned rock. And they're awesome to watch live - a great stage show where you can tell the band were enjoying themselves just as much as the audience. My only gripe is that they didn't play "Mao Tse Tung said", one of my favourites. Meh...

Biella Coleman: Openings

I love Susan Sontag for her crisp and biting writings. I like that she takes risks and in the process takes you for a ride through her beautiful imagery. I just finished reading Illness and Metaphor and think that her opening is probably one of my all-time favorites
Illness is the night-side of life, a more onerious citizenship. Everyone who is born hold dual citizenship, in the kingdom of the well and in the kingdom of the sick. Although we all prefer to use only the good passport, sooner or later each of us is obliged, at least for a spell, to identify ourselves citizens of that other place. I want to describe, not what it is really like to emigrate to the kingdom of the ill and live there, but the punitive or sentimental concocted about that situation: not real geography, but stereotypes of national character.

Ross Burton: Roku SoundBridge

Yesterday my new NAS arrived, to replace my aging and failing hacked Linkstation. As part of the bundle I also received a Roku SoundBridge, which was a nice surprise. Basically, it's a consumer-orientated device which plays music from iTunes or Internet radio, which you would plug into a hifi or powered speakers. I'd heard of these before but I've been using my old ThinkPad X22 for this duty for a while now, and MPD has served me well. I thought I'd give it a go, and I'm actually really impressed with it. Physically the SoundBridge is pretty good looking: a sliver and black ten inch cylinder about two inches in diameter, with a large LCD panel on the front. When turned on it found my wireless network, asked for the WEP key, and promptly upgraded its firmware. Once all that was done, it let me select from two libraries: Vicky's Music or Internet Radio. Vicky was running iTunes on her laptop which exports the library over DAAP, so I listened to Tori Amos whilst I explored the Internet Radio options. Then I listened to the most excellent Groove Salad on SomaFM (apparently the #4 station on the Roku Radio charts). At this point I discovered that there was a SoundBridge link in Epiphany, the SoundBridge uses mDNS to publish the web control panel: a useful application of clue from Roku. Then it just got better. The SoundBridge will stream from DAAP and UPnP servers (they pimp mt-daapd and SlimServer), and announces the web interface over mDNS and UPnP. There is a web site which indexes Internet radio streams, currently it has over 5000 entries. This site uses a Java applet (currently only tested in Windows though, I haven't installed Java yet) to talk to your SoundBridge so it can show the currently playing station and tell it to play another station. Then I discovered this in the manual.
Geeks - read this. The M-bridge has a command line interface that you can telnet to for piddling abut. You will need to telnet to port 4444. Type "?" at the command prompt to see a list of commands. ... M-bridge has a built-in UPnP AV "media renderer". This protocol can be used to control the M-bridge from your own software.
The SoundBridge supports both a custom protocol (documented in a 200-page PDF) and the standard UPnP protocol for controlling it. They even documented the signals the remote control uses. This is probably one of the most hackable "consumer" devices I've seen for a long time, short of the N800. Well done Roku, you've created a damn neat product which actually does just work out of the box. NP: theJazz, Internet radio

Russell Coker: Xen Memory Use and Zope

I am currently considering what to do regarding a Zope server that I have converted to Xen. To best manage the servers I want to split the Zope instances into different DomU’s based on organisational boundaries. One reason for doing this is so that each sys-admin will only be granted access to the Zope instance that they run so that they can’t accidentally break anyone else’s configuration. Another reason is to give the same benefit in the situation where one sys-admin runs multiple instances, if a sys-admin is asked to do some work by user A and breaks something else running for user A then I think that user A will understand that when you request changes there is a small risk of things going wrong. If a sys-admin is doing work for user A and accidentally breaks something for user B then they won’t expect any great understanding because user B wanted nothing to be touched! Some people who are involved with the server are hesitant about my ideas because the machine has limited RAM (12G maximum for the server before memory upgrades become unreasonably expensive) and they believe that Zope needs a lot of RAM and will run inefficiently without it. Currently it seems that every Zope instance has 100M of memory allocated by a parent process running as root (of which 5.5M is resident) and ~500M allocated by a child process running as user “zope” (of which ~250M is resident). So it seems that each DomU would need a minimum of 255M of RAM plus the memory required for Apache and other system services with the ideal being about 600M. This means that I could (in theory at least) have something like 18 DomU’s for running Zope instances with Squid running as a front-end cache for all of them in Dom0. What I am wondering about is how much memory Zope really needs, could I get better performance out of Zope if I allowed it to use more RAM? The next issue is regarding Squid. I need to have multiple IP addresses used for the services due to administrative issues (each group wants to have their own IP), having Squid listen on multiple addresses should not be a big deal (but I’ve never set up Squid in a front-end proxy manner so there may be hidden problems). I also need to have some https operations on the same IP addresses. I am considering giving none of the Xen DomU’s public IP addresses and just using Net Filter to DNAT the connections to the right machines (a quick test indicates that if the DomU in question has no publicly visible IP address and routes the packets to the Dom0 then a simple DNAT in the PREROUTING table does the job). Is there anything else I should be considering when dividing a server for running Zope under Xen? Is it worth considering a single Apache instance that talks to multiple Zope instances in different DomU’s?

James Morrison: Birthday!

I got a little older yesterday. I'm 26 now. It was a fun day. It started out by going to the Federal Police to get my temporary id. The agents who register foreigners are on strike for the last week or so, but there was someone there dealing with the registration. So my name got put in a big book and I've got a piece of paper that will let me back into the country next week.

Now for the actual birthday. A bunch of use went out to a place called Pinguin (yes, Penguin in Portuguese). We had some chopp, some very good garlic bread. Then since it was my birthday we got a cotton candy cake, and a nice little Penguin!

Michal Čihař: Gammu test version 1.13.92

I just released new version of Gammu. This is simply bug fixing release, no major new features. Full list of changes:

Andrew Pollock: [tech] Solved: The mystery of the missing Simpsons episodes

Sarah had been complaining that MythTV hadn't recorded an episode of The Simpsons in months. It was indeed strange, as you could see that it was going to record episodes if you looked at the upcoming recordings. The other night we happened to be watching some recorded TV around the time an episode was scheduled to be recorded, and sure enough, it started recording one. When we finished watching what we were watching, the episode had vanished. I didn't think I'd seen anything relevant to auto-expiry in the logs for the backend. A few days later, another episode was recorded. We even watched it. It disappeared afterwards. I was sufficiently curious at this point as to what was going on. It turned out that way back in the distant past when I set up MythTV, I misunderstood what "recording groups" were. When I set up recordings of throw-away things like the news, I created a recording group called "Short retention", assuming I could go somewhere else and make stuff in that group get expired quicker than stuff in the "Default" recording group. (Incidentally, I only in the last few months discovered the veritable cornucopia of things that you can do from the recordings listing screen when you press the Menu/M button on the remote/keyboard. The recording groups now make much more sense) I think there's the word "storage" somewhere in the user-interface around this area, which may have been what confused me. Turns out that I never went and tried to set this mythical expiry policy up, because that's not how auto-expiry works. The choices (as of 0.20) are "Oldest show first", "Lowest priority first" and some sort of weighted combination of the two. It turns out that I had it configured for "Lowest priority first", and The Simpsons had the lowest priority of all TV shows, so that it'd always lose out in the event of any scheduling conflicts. The SAN's perpetually full, so it's always auto-expiring stuff, and The Simpsons are what get expired first by this policy. Kinda funny really. So I switched the policy around to the weight combination of priority and age, and now it's going to auto-expire recordings from a year ago. Hooray.

Andrew Pollock: [tech] Double drive failure, the sequel

Today I received the replacement hard drives for the two that failed the other week. Despite me not ticking the box (or paying the $10 for the upgrade), they gave me 500Gb drives to replace the 400Gb drives that I'd shipped them. I was a little dismayed to find that they were labelled as refurbished drives though. Oh well. I plugged the first drive in, and it started exhibiting the same behaviour as the one that had failed, and I immediately thought "oh, they've shipped me a dud refurbished drive". So I tried the other one. It also did the same thing. I started to smell a rat. I have a slightly convoluted power setup for these four disks. They're all connected to minotaur via IDE-USB adapters, and they have external DC power supplies. They're just sitting on top of minotaur, which is a Pentium III 1-RU server, in the bottom of my linen cupboard. In order to reduce the number of plugs involved, I have an IEC Y-cable, which goes to two of these DC power supplies (which take an IEC cable in one end and has a Molex connector on the other end), and the Molex cable from the DC power supply has a Molex splitter cable on it. So I'm powering two drives from each DC power supply, and each DC power supply is connected to an IEC Y-cable. There's no redundancy whatsoever, and I'm not that concerned. I don't have a UPS anyway, and the whole thing has worked fine for months, and it reduces the rats nest of cables a little bit, which is good. I already have way too many things plugged into my linen cupboard. Anyway, so after both new drives appeared to be faulty, I discovered that both drives that had failed within a day of each other were connected to the same DC power supply. The plot thickened. So I dug out a standalone IDE-USB hard drive enclosure (with a separate power supply) and tried that. Everything worked. I tried it with just the enclosure's power supply and either of the IDE-USB adapters I'd been using previously. Everything worked. So I'd managed to narrow it down to the power supply. Most unusual. So fortunately I have four of these DC power supplies, as they came with the IDE-USB adapters, and I freed up two of them when I went for the aforementioned crazy power splitting setup, so I dug out one of the two spares, and tried that, and everything worked. So I've no idea why the power supply decided to go dicky after months of working. I've yet to introduce my multimeter to it to try and work out what's going on. I'm a bit embarrassed that I didn't do more homework before I declared the drives to be faulty. To be honest, they were clicking and generally looking "failed", and I've had a lot going on lately, so I just jumped to the conclusion. Oh well, at least I still haven't lost any data. Too bad I have 200 Gb that is going to go to waste.

Neil Williams: Working Balloon3 board

After quite a few struggles with power supplies, serial cables, the never-ending pain of minicom and the (almost) solved pain of ethernet over usb, my recently received Balloon3 board it up and running. (i.e. recent = less than 12hrs old. 8 hours of that was spent trying to work if I had a compatible power supply and it's been running for nearly 3 hours already). I can ssh into it from anywhere on the network, I have the basic system installed and I've set the date and time. :-)
The task ahead is now clear:
  1. Continue to work with Guillem to merge dpkg-cross into dpkg so that the dpkg-cross transition can release the rewritten apt-cross and the dependent emdebian-tools

  2. Test and fix the Emdebian rootfs packages to at least support login to a chroot on the Balloon (which I've called genesis.codehelp)

  3. Simplify the installation with sensible defaults in the Emdebian packages and improvements to the emdebian-tools scripts that create and could install the chroot itself

  4. Document the process for the CELF tutorial in Austria in 30 days time.


Busy, busy . . .

Steve McIntyre: Morons and spam

It's bad enough that we have anti-social fuckwits spamming the world. It's made even worse by morons using broken-by-design challenge-response software like Active Spam Killer to push back-scatter on to the rest of us. I'm depressed that people can be so ignorant, but not exactly surprised. I just got another challenge in my inbox today. *sigh*

2 October 2007

Frans Pop: debtree 0.7.0

Another nice new feature with debtree 0.7.0. The new version supports an option max-depth that can be used to limit the depth of a graph. I think debtree now supports all the ways to reduce the complexity of dependency graphs that can realistically be implemented in shell. A nice side-effect of this change is that it made it possible to also render other nodes in the graphs more consistently. Suggested packages now also have the diamond shape. And in sets of alternative dependencies "end" packages and unknown packages are now always marked as such. I also moved the previously hardcoded lists of "end" and "skip" packages to configuration files. These are managed using ucf which means that merging local changes with "upstream" updates in new releases will hopefully be relatively painless. If you have suggestions of packages to add to these lists, feel free to submit them. Please mail me both the command for the graph you'd like to reduce and the packages you're proposing to add to the lists. I have one issue left I'd like to implement: displaying alternative "Provides". And then I think its time to try to get debtree ported to C++.
P.S. You may encounter #443179 when using ucf. I've submitted a patch (several actually; the first two had a high "brown paper bag" ratio) that makes use of debconf's Choices-C feature, which should avoid this particular issue for future releases. Besides the mentioned advantage for substitution in templates of variables that need to be translated, Choices-C also allows developers to define a set of short aliases for choices that make the values used in a configuration script independent of the actual strings that are displayed to users. I doubt this feature is well known outside the D-I team. It was implemented in both debconf and cdebconf.

Julien Danjou: Ubuntu: not contributing to Debian, and even doing bad work

Googling around using the rebuildd keyword to find if people were talking about it, I found that patch from Ubuntu. This patch is used to ship rebuildd Debian package in Ubuntu. Wahou. First surprise! So, Ubuntu is fixing bugs and not telling me. I though that people saying "Ubuntu does not contribute back to Debian!" were exaggerating. Seems I was wrong. Nevermind: I take the patch. I read the patch. I apply the pat oh wait: the fix is wrong. lol.

Jonathan McDowell: Moving on

On Wednesday 17th October the majority of my belongings will leave Norwich, to arrive in Castlerock at some point the next week (exact day to be confirmed). I will then start work for 3par as a software developer in Belfast on Monday 29th. It's been 6 years since we moved to Norwich and I'll be sad to leave it, and all the friends I've made here, behind. I'd have stayed a bit longer but 3par were keen for me to get started. I imagine I'll be in the Fat Cat on Saturday 13th if people are around. And I expect visited in NI once we get settled in!

Neil Williams: 64bit time support

Just a note on the 2038 overflow post, libqof1 has had this support since v0.7.0 which was included in the Etch release.
pilot-qof (>=0.1.1) uses 64bit times from libqof1 and also made the Etch release so dates on all devices supported by pilot-link in Etch can be handled as true 64bit values already, as long as the relevant date is part of the main 4 Palm applets, calendar (datebook/appointments), expenses, tasks and contacts(addresses).
Note that although the Palm 'contacts' applet supports birthday reminders, this extension of the contacts database is not supported by pilot-link because it has yet to be reverse engineered. All dates entered into tasks, expenses and calendar are supported so if you create genuine appointments for each birthday (instead of using the Palm reminder support in Contacts), these appointment dates will be safe from overflow until long after our Sun has died, at which point dates based on the rotation of the Earth become irrelevant anyway.
:-)
(Sometimes, it would have been handy to have 48bit systems - if everyone adopts 64bit time, someone is going to have to come up with a calendar *not* based on the rotation of a planet or any other object as all physical matter - even the universe as we know it - becomes temporary on a 64bit timescale. It is hard enough to grasp geological time, let alone 64bit time.)

Next.

Previous.