Search Results: "sesse"

16 November 2006

Stefano Zacchiroli: cdbs relevance

/me on the Relevance of CDBS Whoa, people discussing about CDBS, I can't help joining them. My position: I love CDBS. I started switching my packages to CDBS an year ago or so and nowadays I've almost finished. I understand that people not knowing CDBS might have trouble fixing bugs in my packages, but that's life and it's the same as having to fix a bug in a software written in a programming language you are not fond of. It's just a matter of setting a minimal standard: today people in the NM have to learn debhelper, tomorrow they will have to learn CDBS too. I think it's worth the effort, because CDBS, if used extensively in our archive, has the benefit of providing a single place where to massively make changes to potentially all packages of the archive. That's a huge win for QA in Debian. The same does debhelper, but it only takes care of technical aspects in the packaging process while CDBS also takes care of behavioural aspects. Of course CDBS has drawbacks and nuisances (the available hooks for examples are not properly standardized nor documented IMO), but I think it's a step in the right direction. In Debian we should push more and more toward the possibility of making changes in a centralized/batch manner, so that when maintainers tend to get MIA we have a quick and easy way to take over their unfulfilled duties. Collaborative maintenance is a social step in that direction, CDBS is a technical one.

15 November 2006

Erich Schubert: CDBS is NMU-friendly

Steinar H. Gunderson even threatens kittens because of it, and Steve McIntyre ranted against using CDBS for packaging, claiming that it's much harder to fix bugs in packages that use CDBS. I have to disagree. More than once I've given up on fixing a bug in a package because I couldn't decrypt the huge makefiles used for building the package. For private packages I often switch over packages to CDBS then, so I don't have to fiddle around with a build system noone except the original maintainer understands. And every now and then I fix a bug in Debian, but don't upload it because I replaced the "magic" build system with CDBS magic... While CDBS does a lot of "black magic" to build packages, it usually does quite a good job. If it doesn't, it maybe even is a bug in CDBS, that happens. debian/rules files that use CDBS are usually quite easy to read, even easier than traditional debhelper template-based scripts. And that is why I think that CDBS is a good thing: it does a good job at separating package-specific and package-independendant build scripting. Maybe all we need is more documentation on how to properly fix common issues in CDBS, starting with misplaced or misnamed files etc. CDBS has a lot of hooks, but it's not obvious which hooks to use for which fixes. (Note that sometimes the fix should maybe be done in the upstream makefile instead.) On the long run, Debian could use a more unified way of packaging. Debhelper has already unified package building a lot, and CDBS maybe goes one step too far, but ideally we would all be able to understand each others debian/rules.

14 November 2006

Steve McIntyre: aaargh! cdbs...

Steinar suggests that he doesn't like cdbs. He's not alone. cdbs may make life easy for the maintainer, but it can make it incredibly difficult for anybody trying to fix bugs and NMU a package. I've found this myself when doing RC bugfixes during the recent round of BSPs; I must admit that more than once I've started looking into a bug only to give up the moment I've seen it uses cdbs. Fixing packaging errors is much harder when all the details of the package build are hidden from you in a mass of variables and included Makefiles. Unfortunately, it seems quite a number of new inexperienced maintainers have been using cdbs with very little understanding of the magic it does behind the scenes. This doesn't bode well for the quality of their packages in my experience.

3 November 2006

Maximilian Attems: Early Userspace Fun

History
For the sarge release official kernel-images from the newly formed Debian kernel team came together with initrd-tools. initrd-tools Maintainer was jbailey. It saw some care from tbm, vorlon and me before the actual release. Remembering the flow of bugs and installation-reports it accounted for a huge number of install failures plus lacked many features the Red Hat mkinitrd had. Ubuntu got hit more directly as hoary released with a newer kernel than 2.6.8 and due to the initrd-tools devfs requirement.
initramfs-tools originated out of the need of a direct replacement. Inspired by an initramfs OLS talk jbailey had the goals of boot-time hardware detection using the nice and neat features the Linux 2.5 branch incorporated: The sysfs support of the Linux drivers allows an neat userspace daemon aka udev to coldplug them. udev is the replacement of a maze of slow shell scripts called hotplug package. The second big feature is the new initramfs format (the curious may want to read Documentation/filesystems/ramfs-rootfs-initramfs.txt of any current linux-2.6 source). For a boot loader initramfs or initrd is the same fish. The smaller and more efficient in kernel code makes the difference. The initramfs gets loaded much earlier, due to being only an cpio archive and not an fs allowing it to completely rule the rootfs search and mount. One initial assigned spec had the name "easy NFS root". The LTSP guys joined in and showed interest in incorporating their work.
Technology
initramfs-tools got default in Debian together when the first common linux-2.6 (2.6.15) package reached etch, powered all the Ubuntu releases from Breezy on and is used by the grml live-cd. Since archive inclusion almost a year ago it got much better support of all the various linux boot parameters (see man initramfs-tools or the "official" Documentation/kernel-parameters.txt), keeps an backup initrd around and has better block-based bootloader support (lilo, ..). klibc has been ported to _all_ the Debian release archs where it is in use and compiles fine on m68k and sh.
The initramfs-tools early userspace is very flexible based on it's hooks for initramfs build and boot. Thanks to alphix for the help on shaping the building blocks. There are initramfs hooks in cryptsetup, evms, dmraid, firmware-qlogic, lvm2 multipath, mdadm, usplash, .. Reviewers, uploaders and sponsors included fs, jbailey and Sesse. Most of the time it is sufficient and easy to test changes in qemu images (See slides workshop early userspace). The best wish of an early userspace is not to be remarked - aka happy booting. Nevertheless thanks a lot for the public support: Achieving Xen Disk encryption support in Etch, Popping my initramfs cherry, ..
Future
The latest initramfs-tools release seems almost ready for the upcoming etch release. The bug reports coming over from installation-reports are happily rare. Although the uuid based fstab generation solution is not yet integrated in the debian-installer. There are one or two known nitpicks left-over in the bts plus one bugger: udevsettle may exit to early, when not all the discs are ready for use. For grub there is a fail-over net, but which does not account for a to early md or lvm2 boot hook. Future initramfs-tools development will focus on an optional small klibc based Modules=dep hand walking /sys initramfs generation allowing better embedded support. grub2 will present run-time assembly challenges for the initramfs.

25 October 2006

Christoph Berg: DPL candidates wishlist

My wishlist for the next DPL election ballot: (in random order, and incomplete)

22 September 2006

Matt Brown: Requiring client certificates for EAP-TTLS with FreeRadius

For the project that I’m dealing with at work I wanted to be able to authenticate devices in a two stage process. Stage 1 should authenticate the device to the network (via an x509 certificate) and then Stage 2 should authenticate the user who possesses the device with a username and password. Unfortunately none of the methods shipped by default with FreeRadius will support this sort of configuration. A quick skim through the FreeRadius source code revealed that it wouldn’t be too hard to add support for requiring client certificates with EAP-TTLS and EAP-PEAP. The following patch adds a new configuration option to the tls section of eap.conf which if set to true will require the client to present a certificate before authentication will succeed. Example eap.conf
eap  
                default_eap_type = ttls
                timer_expire     = 60
                ignore_unknown_eap_types = no
                cisco_accounting_username_bug = no
                md5  
                 
                tls  
                        private_key_file = $ raddbdir /certs/radius.key
                        certificate_file = $ raddbdir /certs/radius.pem
                        CA_file = $ raddbdir /certs/cacert.pem
                        dh_file = $ raddbdir /certs/dh
                        random_file = $ raddbdir /certs/random
                        # This is the new option
                        # If set to no, or missing, client certificates are
                        # not required for EAP-TTLS or EAP-PEAP
                        require_client_cert = yes
                  
                 ttls  
                        default_eap_type = md5
                 
         

4 September 2006

Margarita Manterola: RC bugfixing, days 1, 2 and 3

Following Sesse's example, I decided to start bugfixing one RC bug per day, so, this is the result of my first three days at bugfixing: It's quite rewarding to think that if you fix 1 bug a day, from today till November, 30th, you can fix about 140 bugs. With a couple of us doing this, we could tackle not only the RC-bugs but also the important ones (but we have to coordinate, so that we don't overlap again).

1 September 2006

Matthew Garrett


04:02 <helix> burning man is for wankers
04:02 <mjg59> Yes
04:02 <mjg59> "HELLO I WILL SIT IN A DESERT AND MASTURBATE FURIOUSLY
PLEASE GIVE ME WATER IN RETURN"
04:02 <mjg59> It's like web 2.0 without the internet
04:03 <mjg59> And at the end everything catches fire and the investors
have nothing to show for it
04:03 <helix> haha
04:03 <helix> that is a great comparison
04:03 <mjg59> It's no wonder that the technology industry is obsessed
with it
04:03 <helix> well, jwz isn't
04:03 <helix> and he is our hero
04:03 <mjg59> jwz is post-web
04:03 <mjg59> Without being 2.0
04:04 <mjg59> Nightclub + webcams = good use of technology
04:04 <helix> word
04:04 <mjg59> Web 2.0 = BAD BAD BAD TECHNOLOGY BAD IN YOUR BED
04:04 <mjg59> NO BISCUIT
04:04 <helix> web 2.0 makes me want to die

29 August 2006

Enrico Zini: random-thoughts

Random thoughts Model Builder How are you tonight?
  1. What are the packages?
< mrvn> Sesse: cvs help commit You know you definitely are bored when you set up your own newsgroup with a hammer Bringing about the intention: which future? Should a DPL have a moustache? Brilliant. ...the solution to all problems. the point is that from Redhat Linux NT you need to forward to a GUI in order to mount a microprocessor it's about time Kindly start doing something useful and quit ignoring the policy, please let's be reasonable. Let's not drag this into another flame war!

28 July 2006

Julien Danjou: Debian Developers, you all suck

As I speak, there's now MORE THAN 300 BUGS IN ETCH. You all Debian Developer suck hard. A very good job was done by french developers and some others guys last month to reduce this number under 300 before the 15th of June. Now we should be under 200 (yes, two hundred) in 3 days. That seems totally impossible, and the french team (or maybe I should say the A team) is quite on holidays. Unfortunately it seems that MadCoder was right. Anyway, I'd like to thank people like Steinar who tries to make continuous effort to squash down RC bugs. These sort of guys really help.

15 July 2006

Simon Richter: AOL users on the lazyweb

Joining Sesse, I am also on the lookout for notebook tips. Since I'm mostly asking on behalf of my girlfriend, who is an aspiring meteorologist, having an option to choose between really long battery life (because she might be in the outback) and acceptable computing performance (for the biweekly number crunching are strong requirements, just as a tough case and at #4, screen resolution.
I'm especially wary of "unified memory" graphics, as several people have told me that a high-res display will consume a large part of your memory bandwidth, which is the bottleneck for dealing with large matrices anyway.

8 July 2006

Andree Leidenfrost: New mondo package: Fixes for some (longstanding) bugs & Ubuntu

mondo-2.08-2-2 fixes three bugs, namely #369321, #222052 and #292782.

I am particularly happy with the two latter ones even though they were only minor and wishlist, respectively. But they were fairly longstanding, and it makes me feel good that I finally got around to fixing them.

I've also gone through all the remaining bugs again, nagged the submitters where appropriate and closed some (with submitter agreement), especially the ones about LVM and RAID because I feel they have been fully addressed now. The result is that mindi has currently no open bugs and mondo is down to nine. Certainly not as cool as what Steinar H. Gunderson is doing to the RC bug count, but still not bad. ;-) Hopefully, I'll be able to get the bug count down even further.

I've also worked on Ubuntu support with the result that things should function out of the box on Dapper now, i.e. the package should build and run fine.

mondo-2.08-2-2 was tested on:
Enjoy. ;-)

20 June 2006

Martin F. Krafft: GPG keys expire

Today is 2006-06-20, and five years ago I created the GnuPG key pair that I have been using ever since. Possibly due to ignorance, I chose a key validity of one year and consequently stuck with that policy. Thus, every year on 20 June, I have to renew my master (signing) key and generate a new encryption key. And every year, on the days following 20 June, I will get several dozens (if not hundreds) of emails telling me that my key has expired, written by those who write emails faster than it takes to check for availability of the new key. Finally, my key now has hundreds of expired signatures, because it's GPG's default to expire signatures along with the master key. This year, I took a step back and reassessed the choice. The result is that I am not expiring my master key anymore, but I will continue to provide a new encryption key every year, which will be valid for just a little more than a year. Here are the reasons I found why you'd ever expire the master key:
  • the key is intended to be used only for a limited amount of time. This is not the case for me.
  • in case of loss of control and lack of revocation certificate, the key will eventually become unusable. First, I have a revocation certificate, and second, if I lose control over the key it should mean that someone figured out my passphrase, so could just extend the livetime of the key anyway.
And here are the reasons for the encryption keys:
  • if you do lose control over your key, all's lost anyway.
  • if an attacker manages to crack one key, s/he can only read communication of the year during which I used the key, but no past or future communication.
As always, I'd love to hear your input, and I'll post relevant follow-ups. In the mean time, please make sure you refresh my key:
gpg --keyserver subkeys.pgp.net --recv-key 330c4a75
wget -qO- http://people.debian.org/~madduck/gpg/330c4a75.asc.gz \
    zcat   gpg --import
(Note: you can always get my latest key from the above URL) You may also want to consider running gpg --refresh-keys from cron. I suggest doing so on a ghost copy of your keyring though and then to merge from there, or else you'll experience locking problems when trying to use the keyring at the same time.

13 June 2006

Biella Coleman: The AAA does not support open access

As soon as summer hits, my muse takes an extended vacation and I only write sparingly and occasionally (and somewhat painfully without the muse). But as soon as I read and heard from a number of places, notably Savage Minds that the American Anthropological Association is lobbying against open access, I decided to work against my disinclination to write to say a few words. Rex at Savage Minds, as well as others have already covered thoroughly and thoughtfully, the basic issues as well as why it is incredibly problematic for the AAA not to endorse what is an otherwise powerful and positive Federal initiative that would require final mauscripts based on federally funded research to be accessible to the public after 6 months. So I wont be redundant here and will keep this short, but I would like to say that in an era in which government roll-backs (and in nearly every quarter of life) are simply commonplace and causing a fair deal of social problems, any initiative in which there is a push to make scholarship, *based on federal funds*, public and accessible, seems imperative to support, not squash. Many anthropologists, as probably many scholars, I imagine,like to think that some of their work has some public import and as such, we should do everything possible to make the work as accessible as possible, which will also give access to the communities and people we work with. They mention the supposed threat open access will have to peer review. First I don’t think that arguement stands up and more important, if peer review is simply a self-referential exercise, in which it can’t happen in a context of openness and accessiblity, what good is peer review?? Given the recent AnthrSource Initiative, as well as the general open/populist/ liberal/downright radical political inclinations among anthropologists, and the fact that the discipline in the last 25 years has been somewhat obsessed with the question of ethics, I was quite shocked at this move. But apparently (and thankfully) there were very few people at the AAAs behind the decision, which is somewhat comforting. What I hope now ensues is the formation and expression of a very strong response among the members of the AAA asking for a response from our elected board and an eventual rethinking of this stance.

6 June 2006

Enrico Zini: One beer to Steinar

Steinar, you made my day! Here's a fixed version:
#! /bin/sh
WORK=" mktemp "
wget -O- "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=$1&mbox=yes" > "$WORK"
mutt -f "$WORK" # -e 'push D~=\n$'
rm "$WORK"
Now, it would be nice if it integrated with bts cache... abi on #debian-devel suggests to use:
bts show --mbox <bugid>
Wow! I didn't know it existed! And indeed it integrates with bts cache :)

27 April 2006

Christian Perrier: Back from my annual German samba break

As usually every year, I went this year to the Samba eXPerience conference in G ttingen, Germany. That conference is the only existing conference entirely devoted to the Samba project. It is a unique opportunity to meet with other users of samba, as well as nearly all member of the Samba development team (which is "only" made of 10-15 people, which always seem to surprise attendants when one knows about the quality of Samba over the years). This year, we were missing Tridge who was busy in European Commission hearings about the Microsoft case, if I got the explanations correctly. But most of others were around and I'm glad I had a few really interesting talks with several key people in the Samba project. The small samba maintenance team in Debian will probably take advantage of this as well. There were two of us over there, No l K the and myself. It's always a pleasure to spend some time with No l. We've been able to lower the number of bugs for samba in Debian a little bit as well as prepare the next release (3.0.23) packages...finding a few bugs in the upstream builds..:-) We also initiated some discussions with upstream about possible backports of the current samba code to sarge. Upstream policy is to encourage users to upgrade to the last version in the samba3 releases, so our policy in Debian does not fit well with these goals. We'll try to work closely with people who maintain the Debian packaging in the Samba Team... Of course, we also talked and listened to numerous talks about Samba 4, the Active Directory killer. In short they can be summarized to: nothing will be released "production ready" in 2006. So, we won't have samba4 in Debian etch. Steinar Gundersson and Jelmer Vernooj (member of the Samba Team AND in the Debian NM queue) will continue to maintain samba4 package in experimental (to test them, just install samba from experimental...beware, this *will* break File and Print services on your host). Also important were talk about evolutions in Samba3, the current production code. My vote goes to Jeremy Allison's talk about "Delegating administration of samba servers", introducing what I consider a killer features: user shares, ie the possibility to allow some users to create their own share on Samba server. Believe me, that feature will rock and it *will* be in 3.0.23 due out in a few weeks. I already have tons of plans for my production server at work in ONERA where the days of my NT4 domains are counted. For this, Jerry Carter tutorial about Samba 3 and Active Directory will be incredibly useful, even if I don't have any AD servers (and don't plan to). In short, great time as usual in G ttingen. I'm also very happy that I had the opportunity to visit Meike and have such long and interesting hours talking together while eating noodles. Tsch ss!

19 March 2006

Clint Adams: This report is flawed, but it sure is fun

91D63469DFdnusinow1243
63DEB0EC31eloy
55A965818Fvela1243
4658510B5Amyon2143
399B7C328Dluk31-2
391880283Canibal2134
370FE53DD9opal4213
322B0920C0lool1342
29788A3F4Cjoeyh
270F932C9Cdoko
258768B1D2sjoerd
23F1BCDB73aurel3213-2
19E02FEF11jordens1243
18AB963370schizo1243
186E74A7D1jdassen(Ks)1243
1868FD549Ftbm3142
186783ED5Efpeters1--2
1791B0D3B7edd-213
16E07F1CF9rousseau321-
16248AEB73rene1243
158E635A5Erafl
14C0143D2Dbubulle4123
13D87C6781krooger(P)4213
13A436AD25jfs(P)
133D08B612msp
131E880A84fjp4213
130F7A8D01nobse
12F1968D1Bdecklin1234
12E7075A54mhatta
12D75F8533joss1342
12BF24424Csrivasta1342
12B8C1FA69sto
127F961564kobold
122A30D729pere4213
1216D970C6eric12--
115E0577F2mpitt
11307D56EDnoel3241
112BE16D01moray1342
10BC7D020Aformorer-1--
10A7D91602apollock4213
10A51A4FDDgcs
10917A225Ejordi
104B729625pvaneynd3123
10497A176Dloic
962F1A57Fpa3aba
954FD2A58glandium1342
94A5D72FErafael
913FEFC40fenio-1--
90AFC7476rra1243
890267086duck31-2
886A118E6ch321-
8801EA932joey1243
87F4E0E11waldi-123
8514B3E7Cflorian21--
841954920fs12--
82A385C57mckinstry21-3
825BFB848rleigh1243
7BC70A6FFpape1---
7B70E403Bari1243
78E2D213Ajochen(Ks)
785FEC17Fkilian
784FB46D6lwall1342
7800969EFsmimram-1--
779CC6586haas
75BFA90ECkohda
752B7487Esesse2341
729499F61sho1342
71E161AFBbarbier12--
6FC05DA69wildfire(P)
6EEB6B4C2avdyk-12-
6EDF008C5blade1243
6E25F2102mejo1342
6D1C41882adeodato(Ks)3142
6D0B433DFross12-3
6B0EBC777piman1233
69D309C3Brobert4213
6882A6C4Bkov
66BBA3C84zugschlus4213
65662C734mvo
6554FB4C6petere-1-2
637155778stratus
62D9ACC8Elars1243
62809E61Ajosem
62252FA1Afrank2143
61CF2D62Amicah
610FA4CD1cjwatson2143
5EE6DC66Ajaldhar2143
5EA59038Esgran4123
5E1EE3FB1md4312
5E0B8B2DEjaybonci
5C9A5B54Esesse(Ps,Gs) 2341
5C4CF8EC3twerner
5C2FEE5CDacid213-
5C09FD35Atille
5C03C56DFrfrancoise---1
5B7CDA2DCxam213-
5A20EBC50cavok4214
5808D0FD0don1342
5797EBFABenrico1243
55230514Asjackman
549A5F855otavio-123
53DC29B41pdm
529982E5Avorlon1243
52763483Bmkoch213-
521DB31C5smr2143
51BF8DE0Fstigge312-
512CADFA5csmall3214
50A0AC927lamont
4F2CF01A8bdale
4F095E5E4mnencia
4E9F2C747frankie
4E9ABFCD2devin2143
4E81E55C1dancer2143
4E38E7ACFhmh(Gs)1243
4E298966Djrv(P)
4DF5CE2B4huggie12-3
4DD982A75speedblue
4C671257Ddamog-1-2
4C4A3823Ekmr4213
4C0B10A5Bdexter
4C02440B8js1342
4BE9F70EAtb1342
4B7D2F063varenet-213
4A3F9E30Eschultmc1243
4A3D7B9BClawrencc2143
4A1EE761Cmadcoder21--
49DE1EEB1he3142
49D928C9Bguillem1---
49B726B71racke
490788E11jsogo2143
4864826C3gotom4321
47244970Bkroeckx2143
45B48FFAEmarga2143
454E672DEisaac1243
44B3A135Cerich1243
44597A593agmartin4213
43FCC2A90amaya1243
43F3E6426agx-1-2
43EF23CD6sanvila1342
432C9C8BDwerner(K)
4204DDF1Baquette
400D8CD16tolimar12--
3FEC23FB2bap34-1
3F972BE03tmancill4213
3F801A743nduboc1---
3EBEDB32Bchrsmrtn4123
3EA291785taggart2314
3E4D47EC1tv(P)
3E19F188Etroyh1244
3DF6807BEsrk4213
3D2A913A1psg(P)
3D097A261chrisb
3C6CEA0C9adconrad1243
3C20DF273ondrej
3B5444815ballombe1342
3B1DF9A57cate2143
3AFA44BDDweasel(Ps,Gs) 1342
3AA6541EEbrlink1442
3A824B93Fasac3144
3A71C1E00turbo
3A2D7D292seb128
39ED101BFmbanck3132
3969457F0joostvb2143
389BF7E2Bkobras1--2
386946D69mooch12-3
374886B63nathans
36F222F1Fedelhard
36D67F790foka
360B6B958geiger
3607559E6mako
35C33C1B8dirson
35921B5D8ajmitch
34C1A5BE5sjq
3431B38BApxt312-
33E7B4B73lmamane2143
327572C47ucko1342
320021490schepler1342
31DEB8EAEgoedson
31BF2305Akrala(Gs)3142
319A42D19dannf21-4
3174FEE35wookey3124
3124B26F3mfurr21-3
30A327652tschmidt312-
3090DD8D5ingo3123
30813569Fjeroen1141
30644FAB7bas1332
30123F2F2gareuselesinge1243
300530C24bam1234
2FD6645ABrmurray-1-2
2F95C2F6Dchrism(P)
2F9138496graham(Gs)3142
2F5D65169jblache1332
2F28CD102absurd
2F2597E04samu
2F0B27113patrick
2EFA6B9D5hamish(P)3142
2EE0A35C7risko4213
2E91CD250daigo
2D688E0A7qjb-21-
2D4BE1450prudhomm
2D2A6B810joussen
2CFD42F26dilinger
2CEE44978dburrows1243
2CD4C0D9Dskx4213
2BFB880A3zeevon
2BD8B050Droland3214
2B74952A9alee
2B4D6DE13paul
2B345BDD3neilm1243
2B28C5995bod4213
2B0FA4F49schoepf
2B0DDAF42awoodland
2A8061F32osamu4213
2A21AD4F9tviehmann1342
299E81DA0kaplan
2964199E2fabbe3142
28DBFEC2Fpelle
28B8D7663ametzler1342
28B143975martignlo
288C7C1F793sam2134
283E5110Fovek
2817A996Atfheen
2807CAC25abi4123
2798DD95Cpiefel
278D621B4uwe-1--
26FF0ABF2rcw2143
26E8169D2hertzog3124
26C0084FCchrisvdb
26B79D401filippo-1--
267756F5Dfrn2341
25E2EB5B4nveber123-
25C6153ADbroonie1243
25B713DF0djpig1243
250ECFB98ccontavalli(Gs)
250064181paulvt
24F71955Adajobe21-3
24E2ECA5Ajmm4213
2496A1827srittau
23E8DCCC0maxx1342
23D97C149mstone(P)2143
22DB65596dz321-
229F19BD1meskes
21F41B907marillat1---
21EB2DE66boll
21557BC10kraai1342
2144843F5lolando1243
210656584voc
20D7CA701steinm
205410E97horms
1FC992520tpo-14-
1FB0DFE9Bgildor
1FAEEB4A9neil1342
1F7E8BC63cedric21--
1F2C423BCzack1332
1F0199162kreckel4214
1ECA94FA8ishikawa2143
1EAAC62DFcyb---1
1EA2D2C41malattia-312
1E77AC835bcwhite(P)
1E66C9BB0tach
1E145F334mquinson2143
1E0BA04C1treinen321-
1DFE80FB2tali
1DE054F69azekulic(P)
1DC814B09jfs
1CB467E27kalfa
1C9132DDByoush-21-
1C87FFC2Fstevenk-1--
1C2CE8099knok321-
1BED37FD2henning(Ks)1342
1BA0A7EB5treacy(P)
1B7D86E0Fcmb4213
1B62849B3smarenka2143
1B3C281F4alain2143
1B25A5CF1omote
1ABA0E8B2sasa
1AB474598baruch2143
1AB2A91F5troup1--2
1A827CEDEafayolle(Gs)
1A6C805B9zorglub2134
1A674A359maehara
1A57D8BF7drew2143
1A269D927sharky
1A1696D2Blfousse1232
19BF42B07zinoviev--12
19057B5D3vanicat2143
18E950E00mechanix
18BB527AFgwolf1132
18A1D9A1Fjgoerzen
18807529Bultrotter2134
1872EB4E5rcardenes
185EE3E0Eangdraug12-3
1835EB2FFbossekr
180C83E8Eigloo1243
17B8357E5andreas212-
17B80220Dsjr(Gs)1342
17796A60Bsfllaw1342
175CB1AD2toni1---
1746C51F4klindsay
172D03CB1kmuto4231
171473F66ttroxell13-4
16E76D81Dseanius1243
16C63746Dhector
16C5F196Bmalex4213
16A9F3C38rkrishnan
168021CE4ron---1
166F24521pyro-123
1631B4819anfra
162EEAD8Bfalk1342
161326D40jamessan13-4
1609CD2C0berin--1-
15D8CDA7Bguus1243
15D8C12EArganesan
15D64F870zobel
159EF5DBCbs
157F045DCcamm
1564EE4B6hazelsct
15623FC45moronito4213
1551BE447torsten
154AD21B5warmenhoven
153BBA490sjg
1532005DAseamus
150973B91pjb2143
14F83C751kmccarty12-3
14DB97694khkim
14CD6E3D2wjl4213
14A8854E6weinholt1243
14950EAA6ajkessel
14298C761robertc(Ks)
142955682kamop
13FD29468bengen-213
13FD25C84roktas3142
13B047084madhack
139CCF0C7tagoh3142
139A8CCE2eugen31-2
138015E7Ethb1234
136B861C1bab2143
133FC40A4mennucc13214
12C0FCD1Awdg4312
12B05B73Arjs
1258D8781grisu31-2
1206C5AFDchewie-1-1
1200D1596joy2143
11C74E0B7alfs
119D03486francois4123
118EA3457rvr
1176015EDevo
116BD77C6alfie
112AA1DB8jh
1128287E8daf
109FC015Cgodisch
106468DEBfog--12
105792F34rla-21-
1028AF63Cforcer3142
1004DA6B4bg66
0.zufus-1--
0.zoso-123
0.ykomatsu-123
0.xtifr1243
0.xavier-312
0.wouter2143
0.will-132
0.warp1342
0.voss1342
0.vlm2314
0.vleeuwen4312
0.vince2134
0.ukai4123
0.tytso-12-
0.tjrc14213
0.tats-1-2
0.tao1--2
0.stone2134
0.stevegr1243
0.smig-1-2
0.siggi1-44
0.shaul4213
0.sharpone1243
0.sfrost1342
0.seb-21-
0.salve4213
0.ruoso1243
0.rover--12
0.rmayr-213
0.riku4123
0.rdonald12-3
0.radu-1--
0.pzn112-
0.pronovic1243
0.profeta321-
0.portnoy12-3
0.porridge1342
0.pmhahn4123
0.pmachard1--2
0.pkern3124
0.pik1--2
0.phil4213
0.pfrauenf4213
0.pfaffben2143
0.p21243
0.ossk1243
0.oohara1234
0.ohura-213
0.nwp1342
0.noshiro4312
0.noodles2134
0.nomeata2143
0.noahm3124
0.nils3132
0.nico-213
0.ms3124
0.mpalmer2143
0.moth3241
0.mlang2134
0.mjr1342
0.mjg591342
0.merker2--1
0.mbuck2143
0.mbrubeck1243
0.madduck4123
0.mace-1-2
0.luther1243
0.luigi4213
0.lss-112
0.lightsey1--2
0.ley-1-2
0.ldrolez--1-
0.lange4124
0.kirk1342
0.killer1243
0.kelbert-214
0.juanma2134
0.jtarrio1342
0.jonas4312
0.joerg1342
0.jmintha-21-
0.jimmy1243
0.jerome21--
0.jaqque1342
0.jaq4123
0.jamuraa4123
0.iwj1243
0.ivan2341
0.hsteoh3142
0.hilliard4123
0.helen1243
0.hecker3142
0.hartmans1342
0.guterm312-
0.gniibe4213
0.glaweh4213
0.gemorin4213
0.gaudenz3142
0.fw2134
0.fmw12-3
0.evan1--2
0.ender4213
0.elonen4123
0.eevans13-4
0.ean-1--
0.dwhedon4213
0.duncf2133
0.ds1342
0.dparsons1342
0.dlehn1243
0.dfrey-123
0.deek1--2
0.davidw4132
0.davidc1342
0.dave4113
0.daenzer1243
0.cupis1---
0.cts-213
0.cph4312
0.cmc2143
0.clebars2143
0.chaton-21-
0.cgb-12-
0.calvin-1-2
0.branden1342
0.brad4213
0.bnelson1342
0.blarson1342
0.benj3132
0.bayle-213
0.baran1342
0.az2134
0.awm3124
0.atterer4132
0.andressh1---
0.amu1--2
0.akumria-312
0.ajt1144
0.ajk1342
0.agi2143
0.adric2143
0.adejong1243
0.adamm12--
0.aba1143

1 March 2006

David Pashley: IO::File-&gt;open() is broken

So you read the documentation for IO::File and see:
open( FILENAME [,MODE [,PERMS]] )
open( FILENAME, IOLAYERS )
so you write:
my $rules = new IO::File('debian/rules','w', 0755);
and wonder why it hasn't changed the permissions from 0666. Stracing confirms it is opened 0666:
open("./debian/rules", O_WRONLY O_CREAT O_TRUNC O_LARGEFILE, 0666) = 4
A bit further reading of the documentation you discover:
If IO::File::open receives a Perl mode string (">", "+<", etc.) or an ANSI C fopen() mode string ("w", "r+", etc.), it uses the basic Perl open operator (but protects any special characters). If IO::File::open is given a numeric mode, it passes that mode and the optional permissions value to the Perl sysopen operator. The permissions default to 0666. If IO::File::open is given a mode that includes the : character, it passes all the three arguments to the three-argument open operator. For convenience, IO::File exports the O_XXX constants from the Fcntl module, if this module is available.
and the correct way to write this is
my $rules = new IO::File('debian/rules',O_WRONLY O_CREAT O_TRUNC O_LARGEFILE, 0755)
Thank you very much perl for ignoring the permission parameter when you feel like it. Update: Steinar, yes sorry, I did have 0755 rather than "0755" originally, but changed it just to check that didn't make a difference and copied the wrong version. I've changed the post to have the right thing.
% strace -eopen perl -MIO::File \
   -e 'my $rules = new IO::File("foo","w", 0755);' 2>&1   grep foo
open("./foo", O_WRONLY O_CREAT O_TRUNC O_LARGEFILE, 0666) = 3
% strace -eopen perl -MIO::File \
   -e 'my $rules = new IO::File("foo","w", "0755");' 2>&1   grep foo
open("./foo", O_WRONLY O_CREAT O_TRUNC O_LARGEFILE, 0666) = 3
Incidentally, 0755 and "0755" are different:
 perl -e 'printf("%d %d\n", 0755, "0755");'
493 755

20 February 2006

David Pashley: Slef-Harming

Slef Did it ever occur to you that the comma rather than period in the email address might possibly have been a genuine mistake rather than an attempt to target you. Your excessively and increasingly paranoid and biased blog postings are starting to piss me off. You managed to suggest that Madduck thought that cookies should never be used. Reading his post you see he referenced Sesse who only said that people shouldn't use cookies if they didn't need to. As for your assertion that wikipeda has a "extreme right-wing viewpoint", I sat and read both the blog entry you posted to and the discussion page in question. You conviently failed to mention that wikipedia's problem with the FAQ is that it is the collective work of anonymous contributors and edited by a person that google ranks below the profile of some games player. (Oh sorry, forgot google is in on the anti-mjray conspiracy). Wikipedia's policy on sources clearly states that primary sources should be "made available by a credible publication". When you've finished complaining, you might want to fix the link element in your rdf to not point to itself.

Erinn Clark: Maybe not classics, but...

Steinar and Martin, you've both listed most of the classics. My personal additions would be:

Next.

Previous.