Search Results: "ag"

11 November 2006

Stefano Zacchiroli: more fp in python 2.5

More Functional Programming in Python 2.5, where's the Syntax? I'm glad to read that more functional stuff is coming with Python 2.5, especially for the introduction of partial application, the heart of functional programming. Still, FP is not only about semantics, is also about fostering code reuse and implementing stuff in more elegant and concise way. For such stuff to be effective though, a nice and handy syntax is (IMO) mandatory. Anyone knowing i J. Random Functional Language (whatever Lisp dialect, ML, Haskell, ...) should be able to guess how to apply function partially in Python. Considering that Python has a long history of syntactic extensions via PEPs (think about list comp or generator expressions) I fail to understand why to apply a function partially I have to write something as ugly as:
all_evens = functools.partial(all_divided_by, x=2)

It's only me or the most natural syntax, that everyone would be able to guess out of the box, would have been:
all_evens = all_divided_by(x=2)

?

Holger Levsen: happy birthday lieber basko!

Today is the 11th of november, the day that Franzi and I decided almost ten years ago, would be your birthday ;) I wish you a very happy birthday and many many more happy days with long walks, interesting smells and lots of cakes and bones and all the other things a dog can dream of! Next week we'll go on some nice long walks and you'll get another fresh bone from me. I miss you and look forward to see you on monday! ;)

Phil Hands: MBNA's lax attitude towards security

Today I received a copy of the PIN for my MBNA credit card in the post, despite not having asked for it. In response, I've cancelled my account, and reported their incompetence to You and Yours. I suppose I shouldn't be all that surprised, since MBNA have a habit of randomly sending out unsolicited cheques (which also has worrying security implications), but I actually found it quite shocking to see the PIN that I'd chosen printed in clear text. Obviously, in the first instance they generate a random PIN, and print it out, but I was rather hoping that their systems would be set up so that that random PIN, and certainly any PIN subsequently selected by the customer, would not be available in clear text at any time. If I forget my PIN, they should generate a new one, not remind me of the old one. They should not be able to remind me of the old one. The two people I talked to seemed surprised that I would cancel an account that I've had for about 13 years over a single PIN in the post, but given that that's their policy, I don't think it's a massive leap to think that a corrupt postman might be tempted to collect these PIN letters (which are pretty easy to spot and most of which are not being expected, so won't be missed). Then, assuming that a reasonable percentage of people will match MBNA's laxness by setting all their PINs alike, the criminals will be armed with all the information they need to do a targeted mugging for the card(s), with an average return in tens of thousands of pounds, especially if they hospitalise/kill the victim to ensure they don't get to cancel the cards.

Andreas Barth: More apache chasing

Today, I continued chasing easy apache2 bugs. The following bugs seem to be easy to fix (and should be fixed in my opinion prior to Etch). Some more bugs were obviously outdated, so I closed them. I also started collecting information for the release notes about apache2.

Andreas Barth: The first apache day

On Friday, I spent most of my time on apache2. I originally didn't intend to spend so much time there, but as apache2 is an important package, and we still have lots of bug reports flowing in, I decided that spending a bit more time than the minimum effort is useful. I commited an NMU to fix a first row of 8 bug reports (which boiled down to 3 changes), but I expect to work more on apache during the weekend and on Monday.

Andrew Pollock: [tech] What, no abstracts?!

I'm currently debating whether to go to linux.conf.au or not. I'd really like to go, because I didn't make it to Dunedin last year, and it really is the most rocking conference in the world. The catch is, I've already scored two work-funded trips this year, and I will have only barely returned from the second one by the time I'd be wanting to head off to Sydney again, so I don't feel right about asking for work to fork out for this, even though it's reasonably justifiable. I also want to go to Debconf in 2007, and I'd rather that one be covered. So I'll feel more comfortable forking out for it myself. So I now have to decide whether it's worth the airfare, the negative vacation balance, the two 20 hour flights in a week joy that is flying from San Francisco to Sydney and back again. And all I have to base this on is the title of the presentation and the presenter's name. Oh, the huge manatee! That said, on the face of it, there's enough tracks with at least one presentation that look like they whet my appetite that I would be prepared to go based on the face value of the program. I'll mull it over some more.

Biella Coleman: Support Open Access in Anthro

Read and perhaps sign the letter urging discussion for open access in Anthropology!

Holger Levsen: see you later

I just left a bunch of debian IRC channels, and only stayed in the DebConf ones and some technical ones I'm really interested in. While I can sadly admit this is related to be being frustrated by the way Debian has evolved recently, it's only partly because of that.

IRC is quite a timesink (ironically thats the name of my media server at home...) and I need to focus a lot more on stuff that brings money, cause I neglected that too much since I (again) became a freelancer more than two years ago.

Last weekend I've tested d-i on powerpc and I have 6 bugs or so to file, but I could only find the time to file one bug so far. Luckily the others are less serious :) (And even more luckily for me I have done my taxes now, which was the reason I only did the tests but didn't report them immediatly.)

I also have three blog posts half prepared, but no time and/or energy to finish them. One is about my new development toy, an imac, which I use for testing d-i and debian-edu powerpc. This is nothing really special, but the nice thing, besides bringing debian-edu to more archs than i386 (please contact me if you are interested in amd64...) about it is my old friend FAI, which helps me^w^wtakes care that I have to do nothing to get the machine back into the state I want it after I erased the installation to test stuff.

The 2nd one I will actually post later today and about the third one, I don't know.

I hope this plan works out and I will also find some time in future to work on the things in Debian I enjoy and/or find important. But at the moment unfortunatly doing stuff I don't enjoy is more important, as it pays the bills... Luckily this is only partly true, two out of three of my money projects are actually (mostly) fun. Only one is a pain, but it's the biggest and the most urgent one.

/me waves, see you later :-)

10 November 2006

David Nusinow

With all the talk about binary drivers, and Ubuntu's recent decision to ship them by default, I was going to try and rant or philosophize about the various issues it raises, and how I think ripping Ubuntu a new one for this move is justified, but instead I'm going to talk about kitties and happy things.

On the XSF front, the coolest news has come from people other than me. In addition to providing compiz updates and improvements, Thierry Reding has been busy cleaning up the Debian mesa packaging in the XSF repo. Mesa's Debian maintainer hasn't been very active over the past few months, so Thierry has stepped in to help out there.

Julien Cristau, who helped in the early work moving from XFree86 to Xorg, has returned to the XSF to take over maintainance of xterm, which I've almost completely neglected. Both these packages needed more dedicated maintainance than I could provide, and it's great to see them both being beaten in to shape.

Drew Parsons has been as industrious as ever, packaging updates for drivers so we can ship Etch with driver support that is very close to what will be released upstream as 7.2. In addition, he's packaged the modesetting branch of the i810 driver. This is an experimental development branch that will become the mainline in the nearish future, and it basically allows the driver to set modelines that aren't specified by the BIOS, just like other drivers.

Christian Perrier continues to rock the translations.

I've been doing unglamorous work bringing the Xorg docs in to the late 90's, thus making sure that we ship with docs so that users can tell what's on their systems.

Finally, Thierry has put a ton of work in building infrastructure to move the XSF svn repo over to git. I've been evaluating this, and hopefully we can make the move soon so that we hit etch+1 development running. Using git will provide an easier means of pulling from and pushing to upstream. Hopefully, downstream derivatives will also use git as well to facilitate this. I'm really excited about all of this because it feels like we're active across the board.

And now for the kitties. Nicole and I have adopted a cat. We get to take her home from the shelter next Wednesday, so if some random characters start to appear from me on irc, it's probably her fault. Rest assured that when I never run for DPL, she will be a far better running mate than Zeke. As a favor I would like to ask you, all my loyal readers: if I start to talk about my cat constantly, like one would one's own child, please punch me in the kidney. Thank you.

Russell Coker: flash for main storage

I was in a discussion about flash on a closed mailing list, so I'll post my comments here.

I believe that flash will soon be suitable for main storage on most desktop and laptop machines (which means replacing the vast majority of the hard drive market). Flash survives mechanical wear much better than hard drives (flash storage in a camera will usually survive the destruction of the camera), it produces less heat and less noise, and it has better seek times. It is more expensive, although the price is coming down and the main problem now is the number of writes that can be made.

Flash is widely regarded as being slow for bulk IO (benchmark results I have seen approach 10MB/s - while 60MB/s is common for cheap desktop IDE disks). I am not sure how much of this is inherent to flash technology and how much is due to the interface used to access the flash. I often work with Gig-E networks, but for my home use I only have 100baseT, so I have little need for more than 10MB/s IO rates at home.

It is generally regarded that a sector of flash storage wears out at between 10,000 and 1,000,000 writes depending on how recent the hardware is and who you talk to (some vendors are more optimistic than others regarding the usable life of their devices).

Let's assume that you have a 32G flash module running JFFS2 with an average of 2G free (30G of long-term data that doesn't change and 2G of space that is used for new files). Let's assume that the most pessimistic prediction for flash reliability of 10,000 writes happens to be correct. So if 10,000 writes are to be made to that 2G of space that means 20T of data written! If we assume that the machine will be obsolete in 5 years then that allows us an average of just over 10G of data written per day (20,000/365/5=10.9). On my laptop iostat reports the following after 5 days of uptime:

Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
hda 1.94 9.94 20.33 4614118 9439808
I believe that this means an average of 20 blocks were written per second over the last 5 days with a block size of 4K (page size), this means 6.6G per day. Clearly something is wrong with my laptop as there should not be so many writes, but even so I wouldn't expect it to wear out within 5 years if I used only flash storage. Incidentally I do a lot of travelling and generally find that I'm lucky if a laptop hard drive lasts three years. So I could expect flash to last longer than a hard drive for my laptop use.

When flash fails I believe that only a small part of the data will be lost, which is better than the hard drive failure condition which is often to lose everything!

Also there is nothing preventing you from creating a RAID-1 of flash devices. Last time I checked the JFFS2 kernel code didn't support such things but that could be fixed if there was suitable hardware.

Note that JFFS2 is vastly preferable to using Ext3 or similar filesystems on a flash device. Flash needs wear-levelling (spreading the write load over all parts of the disk) for sane operation. JFFS2 has this built in to the filesystem, while Ext3 etc are designed to repeatedly write the same parts of the disk. This means that to use Ext3 you need a mapping layer that does wear-levelling which causes inefficiency. Also JFFS2 has compression built in (same method as gzip). This is good for smaller flash devices (EG the 32M storage that was common in iPaQs), and also reduces the wear on larger storage.

The biggest problem for me in using flash at the moment is the lack of support for XATTRs (needed for SE Linux) in JFFS2. KaiGai Kohei has been working on this, it's been a while since I checked on the progress so I'm not sure if it's got into the kernel.org repository yet.

Another problem with flash is that it is totally unsuitable for use as a swap device. This means that you need to have so much RAM that swap is not needed. Fortunately desktop machines with 2G of RAM are becoming common.

Michael Janssen: It's too late baby, now it's too late

Getting to the gym consistently is one of the biggest hurdles that I have stuck to jumping over while I'm trying to lose a bit more than a few. I seem to have no consistent schedule, except that I do end up doing it every day that I can. One downside of this is that I tend to work out late at night, almost always an hour or less before I go to bed. I've heard that this is not the best for the sleep, but I suspect it is actually better than nothing, so I continue to get to the gym at 11pm or 12pm. Unfortunately, I found myself with some extra roadblocks this week: the exercise room was half broken. The breakers on one half of the room tend to trip when the air conditioner and two machines that are on that circuit are all in use. This means that no one can use those machines until someone from the coop management goes and resets the switch. The treadmill machine, my weapon of choice for shedding a few pounds, is inconveniently on this circuit, and can't be plugged in anywhere else. This happened 3 times this week, Wed-Fri. I'm calling the office for the second time tomorrow.

It is significantly harder to exercise when I don't have the treadmill handy — the stepping machine works on semi-powered days, but it tires me out much too quickly and I cannot get enough exercise in. I'm not the kind of person to reliably run in place or do jumping jacks. My solution was to move the exercise bike to the powered side of the room. The biggest problem with semi-powered days is motivation. Usually I have the motivation to get to the exercise room and start the machine, and once I've started I can stop. Opening the door to a bunch of non-working machines is a huge motivation hit though. It's so much easier to take a roadblock like this and skip a day — in fact I did this week once. Luckily I discovered that the bike is on wheels on one side so it is easy to move to the other side of the room. However, I'd like to solicit suggestions for alternate exercises for semi-power days. The things that work in the room are a weight machine with a bunch of attachments, the stepping machine, and the exercise bike. I can't really go outside and exercise, because of the late hour and neighborhood that I live in, so it needs to be an inside task. The last requirement is that it focuses on losing weight, not gaining muscle. I'm fairly sure that I'll be gaining some muscle along this process, but the goal is to drop the weight.

I have taken Saturdays to be my day off, so that I can get a little rest and not be so stressed about things, but I'm not taking it this week as I need to "make up" for the skipped day.

This week (Nov 3 - Nov 9):
Minimum: 338.0 (-0.5) (Nov 7)
Maximum: 340.0 (-1.0) (Nov 4)
Average: 339.25 (-0.35) (139.25 to goal)
Exercise Calories: 2314 on 5 days
Average Calories per session: 462.8

Jaldhar Vyas: Who Knows What Evil Lurks In The Heart Of Postfix? The Shadow Knows.

Lamontations

Roland Mas: Exif, give or take a few hours

I finally got myself a nice digital camera. Nice as in, it fits in a pocket, it takes reasonably good-looking pictures, ant it's not a Canon so I can access it as an USB mass storage device. (For those who care, it's a Kyocera/Contax U4R.) So I've started using F-Spot (which is tremendously cool) and Gallery a bit more intensively than previously, and I noticed something curious: my pictures had wrong times. I thought that digital cameras stored them inside the picture files... Hmm. On to investigate. Time passes as I follow the threads of the information flow (use the source, Luke). Then I scream in horror. Then I go see something I hope is authoritative and therefore likely to have been well thought-out (read the spec, Luke). Then I scream some more. Let it be widely known that the Exif specification, which is the standard for embedding metadata into image files from digital cameras, encodes the date and time of the picture as a string. A fat, ugly, 20-character string. More precisely, the format is YYYY:MM:DD HH:MM:SS. I don't have anything against strings, they are rather easy to parse by humans (as demonstrated by strings /home/roland/images/photos/contax-u4r/kicx0700.jpg head). But they should be done right. In this case, it would have made a lot of sense to enlarge that string to 26 characters and add +ZZZZ or something similar. So as to be able to encode, say, a timezone, for instance, in order to, say, have dates and times that actually mean something, instead of something that may or may not be the current time plus or minus a random number of hours and minutes. I thought I could cheat by starting F-Spot with TZ=UTC f-spot (among my electronic gadgets, those that can't cope with timezones are set to UTC, with the exception of my alarm clock). The result is bizarre: the date is shown as being one hour late. I could understand if it were two (I'm at UTC+2 these days), but where does that one come from? I suppose I'll have to cheat differently, by keeping a patched version of F-Spot that interprets the TimeDate data from Exif as UTC, instead of using the current timezone. Or maybe I could do that in my hotplug script: it already rsyncs images from the digicam to the harddisk then makes sure the digicam's memory has at least $foo megabytes of free space on the card memory. I suppose it could also fiddle with the Exif tags on the fly. Anyway. People need to learn: text without encoding information is useless, cryptography without a web of trust is useless, and date/times without timezone info is useless. If one of my esteemed readers happens to be (or know) a member of the Exif specification group (I understand it's called "JEITA"), please tell them that this needs to be fixed in a future version of the spec. I suppose I'll have to live with it with my current digicam, but maybe the next one will be better in that regard. The pictures themselves are nice, though.

Roland Mas: New face, new colours

No, I didn't get a haircut, nor did I dye my hair blue (yet). I just partly un-transparentified my X-Face-based hackergotchi for Planet Debian and added that oh-so-classy semi-translucent drop shadow. And I also harmonised the colour scheme of my blog with the one on my pro site (yes, I'm a part-time free software freelance). Again, using a colour theme inspired from Manoj's script and blog article. I'm an absolute fashion victim. Must... not... put... "hacker emblem"... somewhere.

Roland Mas: Three more packages

Jens Gecius has just dropped out of the Debian new maintainer process, citing time constraints. That means he's no longer maintaining his packages, and I have agreed to adopt them. Which is a nice turn: I'm happy to maintain them, and I'm very happy that someone did the initial packaging while I only had to review it (I sponsored the uploads up until now). I'm now the proud maintainer of the dvtitler, kinoplus and timfx source packages, all three being collections of plugins for Kino (a digital video editor small and functional enough for my needs), containing effects, filters, transitions and so on. I'm not viscerally attached to them, though, so if anyone wants them more than I do, just ask. Now if the udev, sysfs and ieee1394 drivers authors could sit around a table and fix things so that the appropriate raw1394/video1394/dv1394 device nodes appear in /dev when I plug in my DV camcorder, that would be even nicer. I'm currently having to reboot to Linux 2.4 to grab the video out of it and send it back.

Roland Mas: Geekish week-end

So I spent most of the (long) week-end hacking on various things, and behaving geekishly. Gforge 4.0 packaging goes along rather nicely. Packages built from current CVS won't use LDAP anymore (except for the old gforge-mta-exim, but you really should be using gforge-mta-exim4 or -mta-postfix by now). Shell accounts, e-mail redirection and mailing-list resolution now use direct PostgreSQL lookups. No more install-ldap.sh scripts running hourly and taking forever. No more nightmares setting up slapd and trying to clean after it when it explodes. Yay! Other news, on the video front: okay, I gave in, I finally accepted the next-best-thing that so many people have sent me. My raw1394 and dv1394/host0/PAL/out device nodes are now statically created by me, and symlinked by udevd via links.conf. Urgh. It means I can grab video from the camcorder, edit it, and export it back to the camcorder, all that in the same Kino session (and under a reasonably current 2.6 kernel). Editing video is nice, but it's not very useful if you have to carry your camcorder along at all times to show people, though. So I wanted/needed a free, working encoder for a nice codec that I could use. I wanted Theora. I whined for sometime, and I finally understood that Kino wouldn't have anything to do with it, and I had to use ffmpeg2theora. Blargh. Whatever, I grabbed it from upstream and packaged it (it's at http://roland.mas.free.fr/debian/ if you want it -- someone please ITP it, take it, write a manpage, and upload it to Debian). Now Kino can export to Theora, cool. Now I just have to find one media player able to play Theora correctly, and things will be fine. Xine only wants to play the Vorbis (audio) track, and shows me a visual representation of it. VLC is fine after like fifteen seconds, but it starts by playing audio too fast, then slows down, while video takes long before coming, then it comes up too fast and slows down to a normal speed too. As for totem-gstreamer... It starts by playing audio fine, but video is about 5-6 times too slow for as long as there is sound to play. When the end of the audio track is reached, all the video is played as fast as possible (and in total silence). Oh, and I also got my ass kicked at Freeciv. I used to play Civilisation for days in the good old Atari ST days, but I seem to have forgotten quite a lot. Or maybe I was no good to start with, who knows, the AIs never told me. So I need to practice against AIs, I suppose, before I next connect to a game server. Okay, so I spent the whole weekend on a computer. So what? It was raining anyway.

Daniel J. Priem: Close to the release?

Don't forget:
After the release is before the release!
Who decided that we are *close* to the release?
potato got released at 14th of August, 2000
Woody got released at 19th of July, 2002
Sarge got released at 6th of June, 2005
I for my part will upload until i am only allowed to upload bugfixes.
The release will be ready when its ready and this is not a decision of people,
the only thing that counts are bugcounts so thanks goes to beer-tanc
and to dunc-bank that i will still able to upload my packages with new upstream releases.

Martin Zobel-Helas: Does anyone actualy read mails from the release-team?

Yesterdays statistic from debian-devel-changes: 17x “New upstream release” with only 2 packages actualy fixing bugs! 5x “Initial Release“! Guys, that close before the release, use experimental, that is what it is for. And it gets autobuilded for almost all architectures (1 buildds (s390) currently down). Thanks for helping to get the release out in time. No Tags

Thijs Kinkhorst: Proper support of application plugins in Debian

Ingo J rgensmann blogged about a bug in the Debian serendipity package. Thanks, the misspelled variable has been fixed. It should be noted that dbconfig-common does support remote databases, but only at debconf priority "low". He also writes that Serendipity does not support static pages. Well, it does, but with one of the countless available plugins. This plugin is not packaged for Debian. I had this same problem for SquirrelMail in the past and am not sure what the best way is to resolve it. Packaging plugins separately (one plugin one package) seems obvious but has been rejected by the FTP-masters for bringing too much archive bloat. An alternative could be to create one package that aggregates a number of plugins. With of course the question which plugins would and would not get into it. Any other suggestions for plugin packaging are welcome.

MJ Ray: Reduce Your Loading Times and Sell More

One of the benefits of following the various web standards and guidelines is that most browsers will show something on the screen before the page has finished loading. Avoiding unnecessary rubbish in your html and optimising graphic files can make it look like your site loads faster. This may be getting more important as networks get busier and more sites place more demands on computers. Web users may be finally getting fed up. Today's news reports: "Shoppers are likely to abandon a website if it takes longer than four seconds to load, a survey suggests" (from Websites face four-second cut-off [BBC], Akamai/Jupiter Research full report).

Next.

Previous.