Search Results: "andy"

17 October 2006

Russell Coker: which blog and syndication server to use?

I'm currently working for a company that in the past has not embraced new technology. One of my colleagues recently installed a wiki which did a lot of good in terms of organizing the internal documentation.

The next step is to install some blogging software. What I want is to have every sys-admin run a blog of what they are doing and have an aggregation of all the team's blogs for when anyone wants to see a complete list of what's been done recently. The security does not have to be particularly high as it's an internal service (probably everyone will use the same account). The ability to store draft posts would be really handy, but apart from that none of the advanced features are really needed.

Also it would be handy to be able to tag posts. For example if userA did some work on the mail server they would tag it with SMTP and then at some future time it would be possible to view all posts with the SMTP tag.

I've done a search on google for this topic and there are many pages comparing blog software. But all the comparisons seem based on Internet use, they talk about what versions of RSS are supported etc. But I don't need much of that. An ancient version of RSS will do as long as there is a single syndication program that can support it. Performance doesn't have to be great either, I'm looking at less than a dozen people posting and reading and a fairly big Opteron server with a decent RAID array.

For the minimal requirements I could probably write blog and syndication programs as CGI-BIN scripts in a couple of days. They wouldn't support RSS or XML but that's no big deal. But I expect that if I use some existing software that someone recommends in a blog comment it will be faster to install and have some possibility of future upgrades.

Russell Coker: what's a good blog server for serious blogging?

I'm getting sick of blogger. The main thing is that I'm simply not a user. Taking what someone else gives me and just putting up with any failings doesn't suit me at all. I can deal with bugs in things I control (such as Linux distributions) because I can fix the bugs I consider important at any time.

So now I'm looking for a serious blogging program. Wordpress was strongly recommended to me after my previous post on the topic of blogs, but that was in regard to a simple blog program for Intranet use. I am now after a blog program that is designed for Internet use, it must have good security, support multiple users (some of my friends will probably want to use my blog server machine), and not be overly difficult to customise (I am resigned to the fact that I will have to learn another programming language - probably re-learning PHP or Java as that is where web programming is at nowadays).

One thing that I want to do is to have the main web page that displays all recent posts display each post in a frame with a separate Adsense section. The topics of my posts vary a lot so I want to have adverts that match.

Another feature I want is to have multiple RSS feeds with different settings. One use for this is to have tags for each post to specify which channel(s) the post will end up on, another is for Adsense for feeds functionality which I want on for some feeds but off for others. I also want to generate multiple feeds for different syndication services. Ideally a syndication service such as Planet Debian or Planet Linux Australia would use a unique feed for sucking it's own data and also have a unique feed address advertised on it's site for the users (if this isn't supported or desired at the syndication level then I can do tricks in the web server to serve different content for different IP addresses). That way I can track use by the different services, work around bugs in syndication services that matter to me, and change settings for post summaries, etc to suit the syndication service.

In terms of HTML editing I only need the most basic functionality. I would be entirely happy to write blog entries in raw HTML, my friends would probably desire line breaks to be converted to paragraph or break tags and basic linking functionality, but they could probably deal with entering bold and italic tags themselves (the few of my friends who couldn't manage this would probably only want to write plain-text in paragraphs).

I also want to run my own syndication software. I guess I have to consider blog server and syndication server at the same time as there may be some dependencies (EG having them both written in the same language might be handy - I don't want to re-learn BOTH Java and PHP). The syndication software would ideally automatically collect the feeds from other syndication services that I specify (although I'm sure I could write a simple Perl script to scrape them from the Planet web sites). Then I want to provide an RSS feed of that content for anyone who wants it.

Please let me know via email or comments if you have any suggestions about which software to use.

16 October 2006

James Morrison: Awesome ride

Yesterday, I had an awesome ride to Santa Cruz, the clipless pedals were very nice to use. The ride was pretty simple, get to the top of Skyline (take redwood gulch) to down to big basin, get our water refilled, go to the top of empire grade (Jamison Creek, or some fireroad) and then down to Santa Cruz. On the way to Redwood gulch I we were stopped at a stoplight, then all of a sudden I leaned slightly towards the pedal I was still clipped into. So, yup, my first day with the clipless pedals I fell. During this fall, I managed to loosen the clips on my shoes, so I needed to stop shortly afterwards to adjust my shoes. The next adventure came when 3 of us decided to take the fireroad up to Empire Grade. The fireroad starts somewhere in HP's Little Big Basin area, and is a nice trail to hike. It was rather steep, it was sandy, it was rocky and everything in between, so we had to walk our bikes up this trail. I took my shoes off and simply wore my wool socks to hike up the trail. Coming down Empire Grade was a lot of fun, not too many cars, and one of those cars even decided that passing me was a bad idea and got out of my way.

To top off such a fun day, when I finally got back to my apt, I discovered that I had the wrong set of keys. I had my one set of keys that didn't have an apt key. Oops.

14 October 2006

Russell Coker: more about Fedora

In a comment on a previous blog entry I was described as an active Fedora advocate, I don't think that is an accurate description. I advocate it to appropriate people, which is mostly non-programmers - but as I mentioned that means a larger proportion of the population than to whom I can advocate Debian. It's not that I'm trying to advocate Fedora, just that it fills a need for many people. I believe that the term Fedora advocate means someone has an objective of increasing the use and to use Fedora, I don't have such an objective. I am a Linux advocate, a Free Software advocate, and sometimes a Unix advocate (Unix meaning the entire family of Unix-like operating systems). Merely promoting something does not make you an advocate for it. I don't think of myself as a Debian advocate at this time, but as I am a Debian developer this may change.

It seems that the people who run the Fedora Planet think that my blog has suitable Fedora content, it's been added to that planet. Also the Fedora Planet appears to be running an older version of the Planet software as it has the same problem with my blog that Debian Planet had before the upgrade.

Now on the issue of gratis vs libre: As I am not a Red Hat employee I can't maintain a kernel-xen-nopae package and give it the same status as the kernel-xen package. Even when I was a Red Hat employee I couldn't have done that - it would require some amount of management approval. I believe that this fundamentally makes Fedora less of a libre distribution. There is no room in Fedora for someone who is an upstream developer and who just wants to maintain their own package. There is Fedora-Extras, but that has a second-class status. Only Red Hat employees can maintain packages in Fedora Core. This makes Fedora fundamentally less libre than Debian. I am not trying to suggest that Red Hat change things in this regard, I believe that Fedora is meeting all it's goals and that making Fedora as libre as Debian is not possible given the goals of making a profit on selling support of RHEL.

Chris made a good point. I also believe that MP3 codecs should not be in Debian/main. But I believe that people making mistakes about some issues is not a factor in judging the entire project. I believe that Debian is more libre although some bad decisions were made - largely due to lack of overall management. Fedora has hierarchical management, so when the legal team declares that some software can not be distributed then it gets removed without debate. I guess I could propose a GR to exclude MP3 codecs from main.

Also it should be noted that RHEL Extras has some of this software that is not in Fedora (RealPlayer for example). The Red Hat legal advice was that MP3 codecs need a license, so they ship a licensed version in their commercial distribution. This is the right thing to do for their customers (it's handy to have and I'm sure that they get a good deal by paying license fees for all their customers) and removing such things from Fedora is the right way to offer a gratis product without unreasonable legal liability.

Naturally Fedora is much more libre than any secret-source OS. Every user has the option of downloading the Fedora source and recompiling it as they wish. I could compile Fedora with a Xen kernel that runs on my hardware and with SE Linux policy that is more restrictive than that which Fedora currently has. I could build custom Fedora install CDs to install things the way I want (which I considered doing when I worked for Red Hat). But the liberty to fork a project does not compare to the liberty to join it, and the liberty to create your own packages in extras does not compare to the liberty to add your own packages that do things differently to the default package.

There are of course positive and negative aspects to this. I started work on SE Linux in Debian in 2001. In 2003 I joined Red Hat to work on SE Linux, in Red Hat I was not the only person dedicated to SE Linux work and other people spent part of their time working on it. The SE Linux work in Red Hat soon eclipsed that of Debian because there was management support. There was no possibility for a package maintainer to refuse to fix a bug that affected SE Linux simply because they didn't care for it. The positive side of this is that the SE Linux work proceeded quickly and efficiently. The negative side of this is that things which don't have management support don't appear in Fedora Core. Exim is a fine MTA but is not in Fedora Core. Some people think that AppArmor is a better option than SE Linux, they are wrong - but in Debian any developer has the option to add AppArmor support and neither I nor any other DD can prevent them. The libre nature of Debian means that as long as basic technical criteria are met DDs can add any package that they wish to the distribution.

These issues however are all related to people who are actively involved in Free Software development. For a typical Free Software user it often doesn't make much difference, until of course your favourite program doesn't get management approval to appear in Fedora Core. But the counter argument is that the quality of some of the >10,000 packages in Debian is not so high. You can install a Fedora Core package and have a reasonable expectation about how well it works, but Debian packages are sometimes rather experimental.

I also don't believe that Debian is a very functional Democracy. Some of the problems of Direct Democracy are demonstrated in Debian. In many ways it is more anarchistic, anarchy gives you liberty for good and bad. Maybe we should consider a Representative Democracy model for Debian.

Thijs Kinkhorst: Squashing on the Etch

The general freeze for Debian Etch has been postponed because of too many open RC bugs. This is handy because ones packages can be even more polished, but only once the archive is frozen it will really stabilize. There's also some people who think now is a good time to do an automated search for RC bugs (instead of a year ago...?), bringing the number even further up. More effort is required here to squash those bugs, and squash them sooner rather than later. That's why Jeroen, Bas and I have decided to work on this together the upcoming Wednesday evening. A small-scale BSP, but everyone is welcome to come along and join in! In other news, my iBook is broken again, it might have been stocked with refurbished parts after its previous breakdown according to the Apple Store. Although it's October, I spent the better part of yesterday afternoon with Stefan on a sunny terrace . I booked tickets to Stockholm, and a very good looking hostel.

9 October 2006

Daniel Jacobowitz: ALSA: Disasters, frustration, hacking, progress, and education

I have had, ever since I got my current desktop, been frustrated with ALSA support for it. The machine is an Shuttle SN25P (with ice1724 onboard 7.1 sound card); it's otherwise very nice. I've had it for a bit over a year. When I got it, I lost several long weekends to hacking on ALSA and peering through asoundrc files, gstreamer and gnome-control-center source code, and other such things. There were two basic problems. One was that no matter what I did, I couldn't get the back speakers to play independent channels. Generally they mirrored the front speakers. The other was they adjusted volume based on the headphone mixer, rather than the master mixer - especially aggravating because muting the master mixer left my music still pouring out of the rear speakers! I filed a bug in the ALSA tracker, but didn't get much feedback, and eventually gave up. Last week, someone else seconded the bug. A helpful fellow responded and pointed us to a couple of basics, like the ALSA datasheet archive (very handy, since as far as I can tell a lot of them aren't available elsewhere, at least without NDAs). We spent some time poring over those. One of the interesting things I learned this weekend: there's a bunch of independent chips involved in onboard sound, in my case three. One seems to do communication between the computer and the analog-digital convertor, another handles the actual conversion (AC97 compatible in this case), and a third (I think...) handles the remaining two channels for 7.1 support since the second one only seems to do six. Digression time. Unfortunately one of the things he asked us to check was physical connections between the chips, and whether there was an onboard EEPROM... and somehow, in lightly applying enough compressed air to dislodge the dust, I got something wedged into the fan of my video card. Which began making a horrible rattling noise. And then when I attempted to clean it, I made it even worse. So at this point in my Saturday afternoon I had to go out and buy another one. The new one is marginally crappier than the old one, which was also pretty cheap, but the new one has the advantage of not needing a fan at all. Digression part two. While I was at the store, I picked up a Slug. I haven't unboxed it yet or gotten a drive for it, but I think I will in a week or two, and see if I can pick up some of Martin's excellent work in running Debian on one. I see that the IXP ethernet driver isn't working at the moment, maybe I can give Lennert a hand... At this point it was clear ALSA had eaten my weekend. So I came back to finish the job. The other reporter of the bug noticed a very interesting bit in the manual for the VT1617A (Via-manufactured AC97 codec) - which affected volume control and routing for the rear surround channels. I poked around in the kernel driver for a while, and discovered that the similar VT1616 chip exposed that bit as an ALSA mixer control (boolean switch)! So, wiring the two together was the next logical step. And suddenly I'd made a world of progress. I could hear things out the back speakers. Apparently - as far as I can tell anyway - no one has good solutions to this problem. I fumbled around with it for a while, wrote two more ALSA patches, and got manual configuration to use a software volume control (the "softvol" plugin) and mute switch which govern all channels. But I'm taking a break from that while I fish around for how this works on other chipsets. It's so immensely awkward that I can't believe there's no standard solution. I mean, is wanting your volume control to affect all your speakers such a rare thing? Anyway, this paragraph summarizes about six hours of beating my head on the wall. Most of this was at the asoundrc format, which is immensely picky, underdocumented, and seems like it really oughtn't to be needed at all. But apparently it is. During the course of this I got to learn how different applications decide which volume control to use, which was exciting in an exasperating and insanity inducing sort of way. You see, ALSA exports basically everything on the card as a "mixer control". There's some things which recognize volume controls by name, and some basic sorting by usefulness. xmms allows you to select any one control to use for its volume slider, which is nice. The GNOME mixer applet allows you to select any arbitrary _set_ of volume controls for the panel applet, which is even nicer. But it's at this point that, both last time and this time, I gave up in general rage. You see, the mixer applet is completely disconnected from the other and more useful way I deal with volume - the hotkeys on my keyboard, which GNOME also handles. But those go to gnome-settings-daemon, and a bunch of code labelled "acme". And this just adjusts the volume on the track which gstreamer (the GNOME audio management libraries) have marked as "MASTER", and that's done based on the order ALSA supplies the controls, which is done by a name-based sorting deep within the bowels of the ALSA library (it's in mixer/simple_none.c). And if you have two with similar enough names, it slaves them together. And nothing has a higher priority than the hardware supplied "Master Playback" controls. The best I could manage was to get the software volume control listed right after the master (in which case it wouldn't get adjusted at all), or adjusted in lockstep with the real master channel (which causes the front speakers to drop at a different rate from the rear speakers, messing up depth). Like last time, this was the point at which I gave up for the weekend. But this time I've learned a lot more and made a whole lot more progress! And written more of it down, so hopefully I have to rediscover less of it next time. I really was going to do a bunch of other things this weekend... but it just didn't happen.

8 October 2006

Biella Coleman: ABILIFY THIS

Yesterday I was catching up with my magazine reading at Chapters (the Canadian equivalent of Border) when I came across an ad for a drug ad for bipolar disorder that struck me as slightly different less euphoric, more cautious to be exact compared with the ads that have been bandied loosely in all sorts of magazines in the last decade in the US. The ad was for a drug called Abilify which must be some verbal riff on Ability (no?) and there was a very clear pronouncement on that ad that admitted they had no idea how the drug even worked. It went like this: ABILIFY may work by adjusting dopmamine activity instead of completely blocking it and by adjusting serotonin activity. However, the exact way any medicine for bipolar disorder works is unknown. I find this interesting because its tone seems to depart from other ads that seem somewhat more confident (or if they were less so, it was probably kept in the fine print). But when I went to the webpage, this caveat was a little harder to find, as it was a few clicks away within a page entitlted The Brain, Bipolar I Disorder, and ABILIFY . It provides a “handy” pictoral representation of what may be going on with your brain with bipolar disorder/treatment. I found the series somewhat odd and amusing, especially the one that used a magnifying glass to see” all the neurons and nerves or whatever they are in your brain. update: so you know, the US and New Zealand are the only 2 countries that allow drug direct to consumer advertising so I am not sure what the ad was doing in this magazine. It was American magazine but in Canada. I would think they would make them get rid of ads like that. Anyone know why it can slip through the border like that?

Ian Murdock: Google Reader gets it right

Google Reader relaunched a few weeks ago, and for the first time since my initial foray into blogging with Radio Userland in 2003, I’m actually enjoying using an RSS reader. Why? River of news. Most feed readers inexplicably model the email workflow, presenting feeds like folders and feed items like messages. Given the state of most peoples’ inboxes, why on earth would you model email when you’re writing one of these things? Google Reader does river of news right. Simply click on “All items” and scroll through the items with the mouse wheel, clicking on the interesting stories (or reading them inline when the feed is full text). Google Reader takes care of marking the items read as they scroll past. Automatically. The praise doesn’t stop there. There are handy keyboard shortcuts (”n” for next item, “r” to refresh, etc.). Performance is excellent, as feed items are loaded on demand using AJAXy techniques. The look and feel is clean and simple, reminiscent of Gmail, down to easy to read timestamps like “9:53 AM (7 minutes ago)”; and, also like Gmail, there’s a mobile version. Intriguingly, you can sort by “auto” in addition to by newest, which presumably applies some sort of relevance algorithm to the feed items. However, it isn’t clear how it determines relevance (does it track my clicks as I scroll through the feeds, examine my broader search history, what?). Google Reader is a good platform citizen too. There’s a gadget you can add to your personalized Google home page, and gadgets, in case you missed it, are becoming full fledged web components as of last week. Oh, there’s an API too. Finally, in concert with Mozilla Firefox 2, subscribing to feeds finally no longer involves configuring a bookmarklet or, worse, the complex gymnastics of right click/copy link location/go to the appropriate URL/paste/subscribe. With Firefox 2, you can configure the feed subscriber to use Google Reader. As a result, you can now click on the feed icon in the address bar to subscribe to the site’s feed. In most cases, you can even click on a link to an RSS/Atom feed, for those sites that don’t have autodiscovery configured properly. My only complaint here is that it doesn’t remember that I want to subscribe in Google Reader; rather, it asks whether I want to “Add to Google Homepage” or “Add to Google Reader” every time. Ideally, it would show me a preview of the feed instead. I’ve seen Google Reader do that before, so perhaps it’s just a matter of configuring it to go to a different URL, though I’m not sure how to do that. So, what’s not to like here? As with most Google products, it’s not particularly well integrated with the Google platform. Indeed, in that particular post, I complained that there were three different ways of creating a bookmark in the Google platform. Well, there now appear to be four. If all of these mechanisms were integrated, that would be enormously powerful. See something interesting in the Google Reader? Click on the star and, optionally, add tags. See something interesting on the search results page? Ditto. See something interesting on a random webpage? Pull down a menu on the Google Toolbar and do the same thing that way. Want to add free form notes to any of the above bookmarks? Pop into Google Notebook. Naturally, all of these actions should result in the bookmarks/tags/notes/etc. being added to a single stream that can be shared with other users, with all of the resulting social network functionality. Etc. etc. etc. Sigh. I guess I have to be patient a little bit longer. Fortunately, Google sees the problem and is finally doing something about it.

6 October 2006

Julien Danjou: Bitlbee 1.0.3 + MSN6 patch

I have just ported the latest msn6-akke patches for the 1.0.3 version of Bitlbee, and it's available here. I've ported and tested the latest patch with MSN 7.5 support also, but it doesn't work well (disconnected at the first event) so you won't get it.

5 October 2006

Randall Donald: swan unable to fly

So I've been hitting my head over the last few days trying to set up an VPN at work. I'm using openswan on both ends. One side is the NAT gateway and I think that's where the problem lies. The tunnel does establish and I can ping both hosts.The layout is basically:

192.168.72.0/24 --- [ NAT / FW / VPNleft ] -- Internet -- [VPNright]


I'm sure many people have done this but I can't get access to the priavte subnet via the right side or access the right side from the subnet. If anybody has a similar setup and wouldn't mind sharing ( randy@khensu.org )their ipsec.conf and firewall script it would be appreciated.


4 October 2006

Clint Adams: If she were a proctologist, she would have noticed that he was a giant anus

He rattled on, She's half-Turkish and half-Spanish--as in Spain. She grew up in the Dominican Republic but went to American schools there, so she has no accent. She's 6 feet tall, which means she's on my level, but when she puts on heels she's taller than me. She's very, very pretty... it's hard not to be when you're half Turkish and half Spanish and athletic... and to boot... here's the kicker... she's a doctor. Is she a proctologist? she inquired. Ha, no, he replied, but her subspecialty is GI. She did offer to perform my next colonoscopy. Wait, she said. Your next colonoscopy? Something about that seems so wrong. No girl who wants to sleep with you should be itching to see the inside of your intestines. So, anyway, he continued, she's got a wicked sense of humor and happens to love the opera. She's great elbow candy. Really, what this means is that I'm setting myself up for a big disappointment. I dunno, she said. The potato girl still seems like she was the prime catch. Opera schmopera. Oh, god, he groaned. You are so many years out of the loop. The potato chip girl? Beth? You realize that our daughter turned 10 on Sunday? Holy shit! she exclaimed. 10! Yeah, he grunted. I'm old! No, no, she insisted. You're not old. Just your children are.

30 September 2006

Erich Schubert: Dancing like crazy

Swing dancing (i.e. Lindy Hop, Balboa, Boogie Woogie) is my big hobby these days. It started with Rock'n'Roll dancing some years ago, and when I was in Berkeley I picked up some Lindy. Since February I've been going to social lindy dancing every couple of weeks. This month I've become a member of Boogie Bären (yes, that is "boogie bears"), a Munich dance club, and started taking classes in Lindy Hop, Boogie and Balboa every week, in addition to my usual lindy social dancing on sunday. Right now I'm right in an "extreme dancing" phase. It started tuesday with the Lindy classes (yes, both of them, over 3 hours), followed by the boogie beginners class on wednesday and the balboa beginners class on thursday. Friday there was a great balboa and swing party in a bar, with top attendees: the teachers of the workshops on saturday and sunday (which I have attended and will continue to attend tomorrow), Andy & Christelle from Lyon and Marty & Valerie from Cleveland. They've been great teachers so far, and their skills are very impressive. And they showed us some really cute moves. After the second half of the workshop on sunday, there will be social lindy dancing in the evening again, monday evening there is swing dancing in another bar in Munich [Update: with live music, Route 66, in addition to the usual singing DJ], tuesday will likely feature a liveband and boogie dancing (it's a holiday, so no regular lindy classes that day), followed again by boogie beginners course on wednesday, balboa class on thursday, maybe balboa and swing dancing in a bar on friday. Maybe I'll then watch the German championships in Boogie Woogie and Rock'n'Roll on saturday, social dancing on sunday and monday again, and so on. It's getting somewhat out of hand, as you can see. I should focus more on my diploma thesis instead... so I'll skip saturday. ;-) [Update: did I mention that Munich has a fantastic Lindy/Balboa scene? Upcoming events include a big balboa weekend 11./12. november, the new years swing ball and the Rock that swing festival in February.]

22 September 2006

Enrico Zini: gr

Lots of happy GRs! It's GR season, and everyone is rushing to produce a nice GR that would make Debian oh so much better than it already is. But some of us either lack the fantasy, or the grammatical competence, or just the time to contribute to this important effort. For those people, I prepared a handy polygen grammar that they can use. Here is today's GR:
  1. After the release, the Donors widly do not take the Community in order to overruling this resolution in the interest of the Debian Release Managers for the purpose of promoting more prompt action.
  2. The Debian Project Leader has the support of Debian for apologising the funds as seems subsidiary and reasonable for the purpose of promoting cooperation between Debian and the Debian Release Managers.
  3. The Delegates broadly fund the swift funds for funding the Debian FTP Masters for the duration of the mandate for the purpose of the RMs.
  4. For the purpose of being 100% Free Software, the Debian Project subsidiaryly can overrule the core proprietary drivers in main in order to apologising the needed funds for the Cabal promptly in the benefit of having a more harmful Project.
  5. As seems harmful and experimental, the Debian Release Managers are devalued by the Debian FTP Masters in order to disbursing the copyright holder for the duration of the mandate for the purpose of Debian.
  6. The Leader lets it be known that the Developers are approved by the Donors to reasonably revoking the Developers-controlled plan during the forthcoming release in the benefit of promoting more potential action.
  7. Promptly, the Debian FTP Masters can be approved by the Delegates to establishing the reasonable Developers following internal discussion in the interest of our users and Free Software.
  8. Effectively, the Delegates have the reasonable support of the Developers for neededly cooperating with the firmware in main with immediate effect, during the forthcoming release of Debian for the purpose of Everyone.
  9. Debian reasonably funds the Community for broadly revoking the donations in the interest of Everyone for the purpose of having a more appropriate Debian Secretary.
  10. In the interest of promoting more needed action, Everyone is of the core opinion that the Developers cannot be authorised by the Delegates to establishing the Developers-controlled Debian Release Managers as seems reasonable and needed for the purpose of reducing the delays of the New Maintainer queue.
I wish this GR generator helps to satisfy all our GR needs, and will finally free some time for people to work on making etch a really great distribution for all of us to run and love.

21 September 2006

Simon Richter: Wacky ideas #8: package manifests

It is very difficult to install only parts of packages if you don't need all of it. For locales, there is localepurge, which removes files after installation; it is also possible to define a hook script that deletes certain things (such as documentation) after each installation run. However, all of these methods rely on a heuristic. It would be a nice thing if I could include a manifest file into a package that describes which roles a set of files or directories has, so that you can filter at installation time. This is most useful for embedded systems, but also comes in handy when doing incremental updates of a package.

20 September 2006

Edd Dumbill: Quick! Get a discount on XTech WebDev London

There are just three days left to get discount registration for XTech WebDev London: our new one-day training event on Rails, Ajax, REST and web application design and development. It will be held in London on 31 October 2006. It's a great opportunity to get yourself and your team up to date with the latest web development technologies. Our speakers are real world practitioners who will tell you about the pitfalls as well as the promises. You will hear: Additionally, everybody gets a copy of Cal Henderson's Building Scalable Web Sites, a buffet lunch and plenty of time to talk with the speakers and other attendees. We start at a developer-friendly time of 10am, which also gives plenty of time for those coming from further than London. There'll also be social events in the evening where you can continue networking and learning in more relaxed surroundings. Register now to attend at the cheaper price of 275.

Russell Coker: War On Terror - the game

TerrorBullGames has just released the board game War On Terror. The first I heard of this was a short article in a local news paper about how much the game has offended some people (quoting someone who was injured in the London bombings). A co-creator of the game Andy Thompkins said "We accept that some people think this is in poor taste and may see it as puerile. But we would say that launching an illegal war on Iraq is in poor taste".

It's not as if profiting from terrorism is anything new. Governments in Australia, the UK, and the US have profited from it at the ballot box and also used it to stifle opposition parties to get unpopular legislation approved. An example of this is the attempts of the Bush regeime to legalise torture, see the Washington Post and The Age (Australia).

Shortly after 9-11 almost every computer company that had anything to do with backups or disaster-recovery was advertising heavily. Oil companies have done particularly well with high prices, they would have done even better if the plans for Iraq had succeeded.

TerrorBullGames appears to have an aim to draw attention to the lies of politicians, which makes them better than everyone else who has profited from 9-11. Maybe if they draw enough attention to the bad things that our governments are doing they can influence the results of elections, and we can get governments that don't promote terrorism.

Here's a review of the game.

4 September 2006

Simon Richter: Why we don't need a steering committee

Debian has always defined itself as "the universal operating system", which to me means that, given two options A and B, each with their own advantages and disadvantages, we will incorporate them both, because there are people for whom A is better, and people for whom B is better. This is one of Debian's greatest strengths, and this is what makes it the "universal" distribution. Now there has been discussion lately about whether Debian needs some sort of central authority to pull the project into a certain direction. The thing is, while everyone seems to agree that we lack direction, we cannot disagree more on which direction it would be if we had one. At present, we have a number of groups pulling in different directions:
The "release" group
Debian's primary goal is/should be to make stable releases. In the time between releases, people should run the release candidate and iron out bugs, so we can release faster; new features are to be added only right after a release.
The "usability" group
Debian does not have any use if we do not support every user. As the admin users can already help themselves, we should focus more on the average user and make the system more simple to use and administer. Integration is a must, as is closed-source firmware.
The "hacker" group
Debian's purpose is essentially to give us a distribution we can use for ourselves, where all the tools that exist are there.
The "freedom" group
Debian is supposed to be only free software so I don't accidentally come into a situation where I'm in breach of a license.
The "large installations" group
It should be as easy as possible to deploy Debian to a set of boxes and remotely administer them. It should be easy to install the software the users need and to customize it for our organization. Users are not supposed to administer machines, and non-free software and drivers need to be clearly marked and easily avoidable so as to not put us at legal risk.
The "supermarket" group
Debian is a repository of packages that makes our lives easier when we build either a system or a distribution, but we don't really care whether stuff is integrated already, because in order to feel comfortable with it, we need to redo it anyway.
The "small but beautiful" group
The system should be as modular as possible, allowing me to leave stuff out that I don't need. I don't mind installing stuff later on.
There are others, and I have represented each only with their most extreme positions. These groups are not usually disjunct, and in some places, some groups share goals. But, for example the "usability" group and the "small but beautiful" group will always disagree on what should be in a base installation. All of this is not new. What is new is that people are asking for a strong leader to strike down the unbelievers rather than discussing stuff on the mailing lists. This is generally a thing I wouldn't like to see happen in Debian, because anyone you pull into the discussion is either uninformed (so not qualified to answer) or already has an opinion (which will most likely conflict with either party's opinion). By forcing a decision, you essentially give one party the right to dismiss arguments with "we've already had this, it has been decided" and do not solve the problem at all, because the other party is still unhappy. You might want to argue that a committee evens things out a bit as more groups are represented there. That is true to a certain extent, however you'd have to have a way to determine who gets to be on the committee, and to do so in a manner that noone is left out (even if there are new groups forming all of the time) and without giving any group too much power. We might just include everybody, which brings us to status quo, except that everyone got a job title now and people might feel more inclined to decide things by majority vote (because that is what committees do after debating, right) instead of based on actual merit. Scott writes that implementing the same thing he just did in Ubuntu would have taken him ages to do in Debian because there are so many more people to coordinate in Debian. I have to disagree here, the number of people to coordinate is probably the same if not higher, except that the Ubuntu model seems to be that every core team member has commit access and is supposed to read up on the changelog when touching a package, making the coordination more implicit. I happily give out Ubuntu CDs, which do have non-free drivers, firmware and documentation, to users. Telling them that they cannot use that driver or have a manual because it's not free will not help anyone, and it is unlikely that they will be taken to court over it. This is all fine and dandy considering Ubuntu's target audience. However, Debian has a much larger target audience, including Ubuntu itself. If Debian were to interpret licenses less strict for some perceived benefit for the users (cdrecord springs to mind here), then all derivers, including Ubuntu, would have to carefully cross-check all of the licenses for possible violations. Thus, I oppose GFDL documentation in Debian main, because when we say "our priorities are our users and free software", that includes all of our users, not just end users. So, what I ask of you people reading this via Planet Debian is the following: Ask your "opponent" whether he'd be interested in finding a common solution that fits both use cases. Present it as a technical challenge. Accept that the outcome of such an endeavour might be that the other person is right. Accept that not everyone shares your views and/or priorities. It is hard to accept for me that a lot of people still think that svn is superior to git, or emacs is superior to vi. So if you have a different opinion on some matter, keep in mind that the other person may be looking at things from a different angle, where his choice is the only "logical" choice. Oh, and that goes for both of you. To conclude: Debian's strength is its lack of a clear direction. If we were to decide that the end users are what matters, we'd become another Ubuntu, which would be quite unnecessary because we already have one, and they are pretty good at being Ubuntu. If we decided only releases mattered, we'd probably release more often, but right after a release, unstable would be really broken (the elders might remember how it was before the "testing" distribution was introduced). In the same way, the release team takes care to include your pet project in the release if at all possible. Every package that is added delays the release because they have to wait for autobuilders and make sure that everything is internally consistent. So, they are already respecting your goals. Are you going to respect theirs, and join the release effort even if all your machines run unstable? So in my opinion it is a good thing that we did not decide on a direction, because there is no right one. We'd always leave some people behind if we had to make a choice. What needs to change is our attitude that software is to be used in one particular way, because the people actually using it would disagree. After all, free software is (also) about being able to do things your own way, and Debian as a whole should be supportive of that.

3 September 2006

Martin F. Krafft: Never give up

Scott, the first thing I want to say in response to your post is that you are not alone. I did not know someone was attacked for wearing an Ubuntu shirt in Helsinki, but I did witness at least one "Fuck Ubuntu" incident, and it seemed that Ubuntu jokes and snaps at the new distro were very common. I find this utterly childish and stupid. I am sorry for everyone who was offended. But please don't blame or condemn everyone in Debian or the whole project for the actions of some of its members or followers. You've already linked to my thoughts on the Ubuntu-Debian situation, so I need not cover any of that anymore. I wouldn't want to either, because believe it or not, this article got me flamed by Ubuntu developers just way too many times, in personal mails as well as in forums. Instead, let's look at the now and then this time. I've heard a few developers express their unhappiness with Debian in the past year, much in the same way that you did. Not always was it related to Ubuntu, but quite often it was. There are newcomers to Debian who shake their head in disbelief how anyone can work in a project such as Debian, and there are the veterans among us who seem to concede that Debian has slipped away from their ideals and it's just not fun anymore. It's not hard for me to understand each of them. I've followed Debian for nearly a decade now and thus tracked how it changed over time. We are one of the largest free software projects, and size never comes without problems. So while the Debian project used to be an association of geeks enjoying their focus on technical excellence, the sheer growth of our project called for many other fields to be managed, and we did not always handle this increase in complexity very gracefully. After all, we are all just geeks who want to have fun, aren't we? As a result, several aspects of our project have been said to "stagnate", and parts (and parties) have diverged. As a volunteer developer, it's not always fun to run up against walls and find that your innovativeness is met with stubborness or simple silence. I say "not always" because I think it's really just a matter of perspective. Over the years, Debian has seriously affected my life, the way I look at things, the way I interact with people, and the way I do stuff. I am eternally grateful for much of that. But the learning process has not stopped. What Debian needs is a stronger grasp of the big picture. In joining all the other developers who are already doing excellent work in that direction, what better learning opportunity could there be to approach large-scale project management, away from academia and the corporate world. For me, this is a very interesting perspective of a fascinating project, one that directly relates to my current research endeavour. I was asked recently how we "control the anarchy", and the first thing I said was that "control" was not the right word. Debian is not about control, it's about the flow. If it's not going your way, you can swim against it, you can pull out, or you can try to find ways to change that flow, bottom-up rather than top-down. I think David's idea of a steering committee is an excellent one, and I'd be happy to dedicate time to such an effort. I wouldn't call it "steering" though, as that seems too active. Rather, I envision a group of people dedicated to keeping track of the big picture (obviously in close contact with the release team) to which developers can turn if they need advice. In the last few years, I've often asked myself why the heck I don't just give up, instead of continuously running up against problems that seemed hopeless. Even now, I sometimes think that I should have just pulled the plug, but my answer has always been no, and it looks like it'll remain that way. Why? Because we've come an incredibly long way, and that by itself provide for a lot of motivation. Mostly, however, I decided to hang in there because I tend to like challenges, even if at first I have no idea how to conquer them. When I then look at what some of the people are doing for the project, I come to realise that there are solutions, even if the road is a long one. You (Scott) strike me as a very innovative person, and not only because the problems you and I are looking at tend to overlap to a large degree. I strongly respect you for your work, and Canonical certainly deserves a tip of the hat for providing you with the environment to do so. Sometimes, I even envy you a little, simply because I haven't been able to get down to coding solutions as much as I would have liked to and you've beaten me to the punch on things like HCT or upstart -- even though my work in that area has been mostly vapourware, so there was no real punch to which you've beaten me... I think you'll know what I mean. Yet, scanning some of your older blog posts, I got the impression that you weren't always happy with the way you have to do things at Canonical. And still, you're enthusiasm for working on your projects is astounding; it wasn't hard to come to that conclusion just a week ago, even though we've only talked briefly in Cambridge. Have you asked yourself why that is? I'll go out on a limb and postulate it's because of your innovativeness, because of your urge to push technology further, to implement cool things, and to break free of the cruft that comes with 13 years of Debian and several decades of standards la POSIX and SysV. Debian is too conservative for you, and all the cruft weighs heavy. Ubuntu, on the other handy, is "fluffy" and not afraid to forge ahead, and you've been an active part of it from day one. As much as I hate to see you "with them" rather than with us, I think you've found your place. And so have I. I'm less about coding than I am about integration, and there's work to do. Debian is a massive project with an amazing track record of achievements to look at. And it has problems. Well, great! Let's attack them. Never give up. Another reason why I've stayed with Debian is because there are people who think alike. Three years ago, I would have been able to give you a long bullet lists of hopeless problems in Debian. If you ask me today, I would have problems arguing their hopelessness, for I've seen plenty of developers taking it up with these problems, and in the meritocratic way. Our release team is doing a fantastic job and I've never felt so positive about the promise we made with the next release. People like J rg, Zobel, Rapha l, the two Alex, Meike, Christoph, and the many others I'll leave out only in the interest of brevity (the list is longer and doesn't only span Germany and France) are doing great work, and that is truly motivating. And I ought to mention explicitly our leader, Anthony, who's been doing an excellent job so far. I hope he can keep it up. Also, take a look at our IRC channels. I would have to be lying if I'd say nothing has changed. And the same applies to mailing lists. We still have a reputation to deal with, but if you stop listening to what people say and actually take a look, I think we've come a long way. I'd even say it's become more fun to work on Debian again! I think we owe a lot of that to Debian Women. I am definitely proud to be a member of this community (with which I mean Debian as a whole, not just Debian Women). I think I could continue this blog post endlessly. Let's not. You (Scott) may not be a fellow DD any longer, but you remain a fellow D, and I hope we'll continue to let our cooperation prosper. Now if only you had told me that "getting upstart installable required changes to twelve different packages, including sysvinit itself" when you approached me with what sounded like a simple sponsorship request... I've started to have a go at the "herculian effort", step by step. Seems like an interesting experiment. NP: Eels / Daisies of the Galaxy (it's really hard to find a better band for a grey Sunday morning) Update: Maybe our reputation isn't all that bad, or Slashdot posts suddenly became all useful. A lot of insightful and interesting posts in the first batch of comments...

2 September 2006

Michael Janssen: Weekend Weeviews: Brewster's Millions, All That Jazz

Brewster's Millions

Richard Pryor and John Candy in a classic story retold many times. I had seen parts of this movie on TV or in the background and thought I should give it a try all the way through. Spending lots of money isn't quite as easy as it should be in this comedy directed by Walter Hill (48 Hours). I thoroughly enjoyed the story as much as is really possible in this type of plot. I thought that the acting was somewhat over the top and the main plot meandered a bit, but at 101 minutes it never went too far off the mark. The payoff at the end, even though it was obvious and expected, left me smiling while the credits rolled. I give it a 8.

All That Jazz

Life is not normal for Joe Gideon (Roy Scheider) in this foray into the backstage of directing and coreography directed by Bob Fosse. In a setting where the only normal part of life seems to be the morning wake-up routine, a duality of mind and reality appears in the beginning. There is also a great interplay between Gideon and his daughter. I was dissappointed to continue on through the ending, which was completely flat leaving me wishing I had hit the back button on the remote and watched the first half over again. A fascinating tale of the struggle between personal and professional life turns into a disaster of an ending. It scores a 4.

Michael Janssen: Late at night when the wires in the walls

After my iBook problems last week, I tried to install Debian on the thing. I have narrowed down the problem to something with the hard drive inside, because the machine seems to run fine and go through most of the installation without any trouble, but once I start using the hard drive, it completely freezes. I successfully ran the hardware test disc which came with it a couple times in extended mode, but I'm not sure that it uses the hard drive in it's tests long enough for it to exhibit the problem. The failure seems to be somewhat random in nature, occuring at different times in the install process. Now I have the unhappy decision of trying to save this laptop which is more than 3 years old, or to attempt to buy a new one. Right now I am leaning toward buying a new one.

Honeywell seems 1.5 times as long this week, mostly because I'm making up for a day which I missed a couple weeks ago. Things have settled down there in terms of software failure, so I'm back at the normal coding which I am doing. The code uses Ogre, which is a handy 3d engine, making it much easier than learning something like OpenGL, and as a bonus adding portability. I am considering building some play applicaitons with the toolkit at home just because it would be fun.

Tonight I need to build a couple presentations covering some papers which were in CVPR this year to present at a reading group at Honeywell. It would be fine except that I am completely unaware of any of the recent history of vision research, so it makes it much harder to build the presentations. I hope I can finish them in a reasonable amount of time so I can watch Eureka tonight.

The TiVo Diet is still working out as expected. I discovered that I don't really have anything to watch on Sunday or Monday of the week. I'm getting much more productive work done than I used to. One downside of the diet is that I tend to not want to just sit and veg at the end of the work day - I think it frustrates [info]ceilingsarecool a bit because I'm always going off to the office to do something on the computer.

I recieved and watched the Studio 60 on the Sunset Strip yesterday. Being an Aaron Sorkin fan, I am excited for another of his shows to broadcast. Judging by the pilot, it should be a decent show.

Sidenote: Planet Debian seems to like one of my weekend weeviews a little too much, and is regrabbing it for the front page every so often. I can't figure out why this is happening, so any help would be greatly appreciated. Otherwise, in a couple more posts it should be off the RSS feed.

Next.

Previous.