Christian Perrier: DD resolution of the day
When filing an ITP, Thou shalt read Developer's Reference 6.2.2:
- leading articles suck
- capital letters suck
- sentences suck
- jargon sucks
When filing an ITP, Thou shalt read Developer's Reference 6.2.2:
The Phone Coop (agent link) will hold its workshop and annual meeting on Saturday. If anyone is going and wants to car-share from the N.Somerset/Bristol area, let me know (new comments form follows this post). I can't quite afford a 5h train trip instead of a 2h car trip, but I'd quite like to reduce the damage. Also, we've just finished and sent the official reports for TTLLP yesterday. We've also various projects which I want to get finished, including the IPC::Open3 for Koha. If I'm a bit hard to reach this week, this might be why. We are still returning calls in batches in our breaks, though, so please please please leave a voicemail. Social Source South West is next Tuesday in Bristol. I'll be there. Will you?
On January 26th 2008, the OCaml community has its first meeting in Europe. There was 5 different talks, including one from me. The meeting was pretty constructive and i think some great things should come out of it. In this post, i will focus on the Debian maintainer point of view.
The meeting was organized by me, with the help of Garbriel Kerneis and Vincent Balat. I wish to thank Mme Turgis from ENST/ParisTech who has made possible all this to happen.
Introduction:
I announce the creation of OCamlCore, a SS2L. It will provide commercial support for OCaml and related products. It will also provide community with some resources (including a GForge, a planet, some SCM repository...)
For now, i will open administration to Debian people who wish to help (for root rights) and from the whole community for other task (gforge and general administration). For now, i will choose alone who can administrate and who cannot... This is not a very open position, but this server is also for my company.
Xavier Leroy give us a nice talk that has let us see some future direction:
It’s probably impossible to get too much of Bruce Schneier, although I honestly wouldn’t mind if he stopped Friday Squid Blogging.
His latest Wired.com article on the false dichotomy between security and privacy is an excellent counterpoint to a recent Lawrence Wright profile in the New Yorker on Director of National Intelligence Mike McConnell. The Lawrence Wright article was surprisingly uncritical, considering the New Yorker’s usual zealous approach. Check out, for example, his description of the “Clipper” chip:
In the nineties, new encryption software that could protect telephone conversations, faxes, and e-mails from unwarranted monitoring was coming on the market, but the programs could also block entirely legal efforts to eavesdrop on criminals or potential terrorists. Under McConnell s direction, the N.S.A. developed a sophisticated device, the Clipper Chip, with a superior ability to encrypt any electronic transmission; it also allowed law-enforcement officials, given the proper authority, to decipher and eavesdrop on the encrypted communications of others. Privacy advocates criticized the device, though, and the Clipper was abandoned by 1996. They convinced the folks on the Hill that they couldn t trust the government to do what it said it was going to do, Richard Wilhelm, who was in charge of information warfare under McConnell, says.(emphasis added). Compare, for example, EPIC’s Clipper Chip information page. Schneier, by contrast, sees right through the core:
We’ve been told we have to trade off security and privacy so often — in debates on security versus privacy, writing contests, polls, reasoned essays and political rhetoric — that most of us don’t even question the fundamental dichotomy. But it’s a false one. Security and privacy are not opposite ends of a seesaw; you don’t have to accept less of one to get more of the other. Think of a door lock, a burglar alarm and a tall fence. Think of guns, anti-counterfeiting measures on currency and that dumb liquid ban at airports. Security affects privacy only when it’s based on identity, and there are limitations to that sort of approach. Since 9/11, approximately three things have potentially improved airline security: reinforcing the cockpit doors, passengers realizing they have to fight back and — possibly — sky marshals. Everything else — all the security measures that affect privacy — is just security theater and a waste of effort. By the same token, many of the anti-privacy “security” measures we’re seeing — national ID cards, warrantless eavesdropping, massive data mining and so on — do little to improve, and in some cases harm, security. And government claims of their success are either wrong, or against fake threats. The debate isn’t security versus privacy. It’s liberty versus control.Read the whole essay. And send it to your mother, as well. Technorati Tags: Schneier, Privacy, Security
I live in a cooperative living group, and during the fall semester a person who we’d invited to live with us who is a dwarf and relies on a scooter for most of his transportation decided he’d like to move in. Unfortunately, while he can get out of his scooter and come inside by himself, we had no stepless entrances such that he could bring his scooter inside to protect it from the angry Cambridge winter. Mmm, frozen batteries.
So, we’re a coop and we maintain the house ourselves—so we decided to build one, of course. A ramp up to the back porch! Nevermind the fact that we need to sink four-foot foundation holes in the ground in January.
We got started right away at the beginning of IAP, while people were still trickling back into town from all over the country.
First we surveyed out where the posts should be sunk:
Then it was time for excavating the holes where concrete would eventually be poured. This involved a power auger of DOOM:
It’s advertised as a 2-man tool. Two 200-pound construction workers, that is. We had to put four people on it plus one person with a shovel clearing dirt to make it manageable, and even then it was a pain. There’s a delicate rhythm you have to get into to avoid getting the bit stuck—DOWN. UP. CLEAR. And inevitably there are rocks and roots that have to be dealt with.
We lucked out with a fairly warm weekend to do the digging on, but on the first day we still had to deal with a couple inches of frozen ground:
There was also some fun stuff involving having to clear away our (frozen) mulch containers and use a concrete cutter on a weird old concrete pathway that used to run through the same area:
Next we mixed and poured concrete:
And placed hardware in the concrete to hold the posts:
Framing:
Eventually it became functional, woo:
And done! (except for metal handrail):
This all took place over the course of about three weeks. And now our scooter-bound housemate can bring his wheels inside! The house still isn’t totally accessible to wheelchairs/scooters, but at least the first floor is. It really brings me pride to see things like this go from start to finish here. We can do it! This guy who is moving in has really influenced my life—he’s really good at making people feel comfortable talking to him, and for me it’s gone from “wow this is awkward, I have no idea what to say” to “talking to a person with different physical abilities and characteristics seems normal”. And that’s made me a better person.
This article is kind of interesting - it's a claim from a conservation group that using PCs to perform climate modelling is preferable to leaving them idle. The figures they provide are based on this brouchure from Tufts University, which provides an average power consumption per computer of 120 Watts and CO2 production of 1500 pounds per year. That gives a figure of 12.5 pounds of CO2 per Watt year.
Good news everyone, first stable Gammu release in this year is out.
Since 1.17.92 only few small fixes in SMS decoding and AT engine did
happen, but there is quite big list of changes compared to 1.17.0:
As I use Drupal for Czech phpMyAdmin pages, it was only a
matter of time till I will have (or want) to add some functionality. My
first Drupal module is quite trivial, but anyway I already got positive
feedback on it just after committing to Drupal CVS :-). Today I finished
little cleanup which my initial version required and I decided to make a
first release out of it.
And what I'm still talking about? It's a module for adding measuring
code for various web auditing systems used in Czechia. I didn't wanted
to hack this somehow into templates and module which will provide block
with those looks as best solution to me. You can get it on
Drupal pages.
Main changes here are including the translations provided by Debian - thanks to all those who submitted po files.
To the people looking for a way of converting from metres per seconds to metres per days: multiply your value by 86400 (60 for seconds in a minute, times 60 for minutes in an hour, times 24 for hours in a day).
Finally making the last release of libqof1 before the imminent transition to libqof2. v0.7.4 includes a new pkg-config file that will become the default for libqof2 and later releases - qof.pc. In 0.7.4, this is installed alongside qof-1.pc to make it easier for packages to transition to the new file and to libqof2. (The transition itself simply consists of removing all the deprecated code in 0.7.4 in a single operation - use --disable-deprecated-qof to ./configure to see the effect.)pkg-config --libs qof call in ./configure (and a minimum requirement for QOF v0.7.4). GnoTime also needs to make this change (other changes for libqof2 have already been made - thanks Linas.)
In Brazilian Portuguese, "bombeiro" is the word for both a fireman and a
plumber. If someone asks you to call a "bombeiro," their statement is
usually unambiguous due to context. Usually.
Both SVG source and t-shirts are available at cost.
Apparently, the task scheduler in all Windows NT-derived versions up to (and including) Windows Server 2003 cannot run jobs under the "NT Authority\Network Service" security principal; "NT Authority\System" is the only so-called well-know security principal that can be used with it. Support for running tasks as "Network Service" or "Local Service" was only added in Task Scheduler 2.0, which is the version that ships with Vista and will be also included in Windows Server 2008.
Apparently, the task scheduler in all Windows NT-derived versions up to (and including) Windows Server 2003 cannot run jobs under the "NT Authority\Network Service" security principal; "NT Authority\System" is the only so-called well-know security principal that can be used with it. Support for running tasks as "Network Service" or "Local Service" was only added in Task Scheduler 2.0, which is the version that ships with Vista and will be also included in Windows Server 2008.
Next.