Posts tagged ‘Arch Linux’

Arch Linux Handbook 2.0

Over a year ago, I released the Arch Linux Handbook, a print copy of the Arch Linux Beginners’ Guide. It proved to be far more popular than I expected, with nearly 400 copies in print.

Of course, the Beginner’s guide is a community edited document for a rolling release Linux distribution, and after a year, the Arch Linux Handbook became somewhat dated. So I’ve created a second edition. It is currently available directly from the eStore and will be available on Amazon within a couple weeks. The International Amazon sites, other booksellers, and brick and mortar stores should have the book available for order after about six weeks.

I would like to extend a huge thank you to both Jules Pitsker and Branko Vukelic. Jules is the motivating force and primary maintainer behind the online Beginners’ Guide. His tireless and thankless contributions have turned it into the exceptionally well-written and comprehensive document that it is. Branko is the best designer I know, both for print and web based materials. He did a terrific job on this handbook cover.

ArchCon 2010: A tale of beer

Arch devsI don’t normally write public journal-like entries, but I’d like to describe my experience at ArchCon as an advertisement to attract more attendees next year!

As co-organizer of the conference, I felt a lot of pressure for it to go well. People had paid registration fees to attend, as well as their travel arrangements and accommodation costs. I wanted it to be worth the time, effort, and money they spent to attend.

I think it was. I feel quite confident that no-one was disappointed.

My trip started a week before the conference. Dieter came over from Belgium around the same time as me. We did some touring around Toronto and down to Niagara Falls, and I had the dubious pleasure of introducing him to Canada’s own special recipe: poutine.

On Wednesday, the day before the conference, my best friend, fellow arch user, and ex-developer, Jason Chu flew in from Victoria, BC. I navigated my way to Humber College, where the conference was hosted and where we were rooming together on campus. Our room very closely resembled a prison cell with cement walls, floors and ceilings. We each got a private bedroom; mine was especially private (and prison-like) as my magnetic key card tended to need frequent resetting.

We met up with Ricardo Alvez who gave us a tour of the college and classrooms and then drove us to a nearby Mr. Greek for supper. We were all thoroughly entertained and swapped a variety of stories, information, and ideas.

Ricardo dropped us off at our dorm where we impatiently waited for our third roommate, Dan McGee (veteran pacman hacker, patch rejector, and expert freelancer). Jason and Dan had never met before, but they quickly became old friends and we spent the weekend insulting each other just like old friends who have far too much respect for each other always do.

We failed in our first mission of Archcon: Find a pub near campus. Dan and Jason were less than impress when we settled for Tim Horton’s (A Canadian coffee/donut chain) instead. Conference consensus is that, wherever Archcon 2011 is held, it must be in proximity to multiple pubs. No beer that night, but it wasn’t for lack of trying!

We went to bed slightly too late, but got up in time. I had meant to be at the conference early and get set up before anyone arrived, but there were already several attendees in the room when I walked in. People seemed a bit nervous and reluctant to allow me to draw them into conversation, but this didn’t last. People became very animated and everyone had something to contribute.

I haven’t presented anything since I was in school, and I have always been an awful presenter with massive public speaking anxiety. So I was surprised, as I set up my introductory speech, to find I felt relaxed and comfortable and was looking forward to the talk. I don’t think the talk was terribly well done, but I was happy with it, and most importantly, enjoyed it. The best part was, having my talk over first, I was able to enjoy the rest of the conference completely anxiety free!

We all experienced a fair amount of anxiety to begin with, though, as wireless was not immediately available. We had an ethernet port in the room, but no wireless routers. This was eventually resolved when Jason set his laptop up as an access point.

We had arranged scheduled talks in one room with various versions of free form discussion in a second room. With the small number of attendees, the second room didn’t get much use on day one, although a small collection of us got together for an informal bug squashing. I had intended to run this in parallel with an online bug squashing in IRC, but I had trouble getting into IRC and had previously thoroughly forgotten to advertise the session! I wrote a patch for an archweb bug, but I’m sure Dan will be rejecting it.

The conference was catered with pastries and drinks at breaks, and burgers, hotdogs, and way too much salad at lunch.

I am writing this as I upload and encode videos, so I won’t describe individual talks. The presenters were all game and presented well. The talks really made the conference, and I think a lot of enthusiasm for Arch development was generated among the participants, even (or especially) those of us who have basically left the community.

Day one ended with a trip downtown to find food and, more importantly, beer. I’d say about half the attendees went out, and I’m pretty confident fun was had by all. If laughter is the best medicine, we should all be very healthy for some time to come. Matt and Jason’s argument about…. well, I’m not sure what they were arguing about, but it was entertaining to watch them argue.

Day two started about 15 minutes late. Most people showed up surprisingly close to on time in spite of the late night. Coffee was consumed. After the scheduled talks wrapped up, several attendees presented “lightning talks” (5-8 minutes on whatever topic makes you happy). These forced a lot of variety into a short amount of time and were quite entertaining.

I was sad that we missed out on the development sprints. These were scheduled to occur in parallel with the last talk, but I think we were all a bit too tired and decided to watch the talk instead. I had in my mind we’d have time to do development after the lightning talks, but instead we ended the conference early. Some people left, having to catch planes, buses, or other commitments, but a large group of us stuck together. Dan and Jason coerced Kevin into chauffeuring them through a beer run while the rest of us borrowed Dan’s disc to play a game of three on three ultimate. Given Toronto’s humidity, we were soaked with sweat in short order. I still managed to cause grievous injury to my right thumb, though. It’s still hard to type and even harder to text as I write this.

Once Dan, Jason, and Kevin returned, and Jason had fixed a problem with his company’s web servers, we headed over to a Chinese buffet for dinner. The group kept shrinking as people left.

Next, the beer was consumed in our prison-like dorm. The number of beer-consumers was disproportionate to the amount of available beer, and we ran out quickly. Alex and Eric showed up shortly after all beer cans were empty. We had to switch to alternate forms of entertainment, and rotated between exchanging friendly insults and compliments, modifying and discussing playlists, discussing the history and future of Arch Linux, and planning ArchCon2011. Jason was repeatedly asked why he wasn’t carrying his Nexus one. Apparently this question annoys him.

That was the official end of ArchCon, but not for me. Jason, Dan and I spent Saturday touring Toronto in the rain. I didn’t go up the CN tower, but they had a wireless lounge that allowed me to write a python script to create the archcon image thumbnails page you’ve seen. I wrote it on my android cell phone over SSH with my injured thumb.

Dieter and a local friend of his met us at the bottom of the CN tower and we made our way to the Cloak and Dagger for more beers. We were all hungry, but didn’t realize that their kitchen was closed on Saturday. Jason and I grabbed a pair of pizzas which disappeared to quickly. So Dieter and I picked up a couple more. Loui showed up and further Arch discussion ensued with, of course, an adequate consumption of beer. I’m told it was one of the best place to get beer in the city.

I wouldn’t know. I don’t drink.

Upcoming Schwag Shipping Delays

I’d like to thank all my Arch Schwag customers for being the best schwag customers ever! Sales are steady and brisk, and I’ve been able to donate several hundred dollars to the Arch Linux project this year. Laptop stickers are, by far, the most popular item, but handbooks, t-shirts, lanyards, and pens are also well-liked. The occasional laptop bag and piece of jewelery are also ordered.

In a few days, I will be headed to Toronto for a vacation, tai chi training, and ArchCon. This means that orders for any items I ship personally will not be shipping until the end of the month. I apologize for the inconvenience, but I’m the only person involved in these items. If you are making an order and planning to move, it may be wise to have your items shipped to an alternate permanent address.

The items affected include laptop stickers, case badges, pens, and lanyards. Orders from the Zazzle store will not be affected, nor will orders for the Arch Linux Handbook. Orders for laptop bags and jewellery will likely only suffer minor delays, as I simply have to contact the people who create them; it will depend how slow I am to deal with my e-mails.

Schwag Shipping

Canada Post recently raised its shipping rates. Again. I think it’s the third time in a year, and the increase was substantial. I have considered their rates to be unfair for quite some time, and have tended to keep my shipping rates lower than my actual costs (handling fees, such as envelopes, printer ink, and tape are other costs I face). However, I had to raise the rates on most of my products today in order to cover more of the costs. Some of my more recent shipments have cost me more than the amount I was making on the products themselves.

As a government-run corporation, I believe Canada Post should be making more of an effort to keep it’s rates low and facilitate the moving of mail across this rather large country. I find it insulting that it costs so much for me to ship items to my Canadian clients. I understand the costs associated with international shipments, but with the unique size, geography, and climate in this country (it’s a tough place to live), I feel it is very important to have the infrastructure for getting both people (it is costing my $1000 for return flights to ArchCon in Toronto and back. I can fly to Vegas with 5 nights included for half that.) and parcels across the country as cheaply, efficiently, and easily as possible.

That said, most of my schwag customers are not located in Canada, and I am taking even bigger hits on my shipments to those customers. I have investigated some alternatives, such as travelling to the US to mail orders in bulk, but less often, but USPS has also been steadily raising their rates, and the savings to my customers wouldn’t cover the gas to get down there, the hassle at the border, or the added delays.

I anticipate reduced sales from these raised prices, and I apologize to those who feel it is too expensive to order Arch Schwag products. I will continue investigating cheaper forms of logistics, and hopefully I will be able to reduce the rates someday!

ArchCon 2010 Registration Deadline Is Here

There are only four days left to register for ArchCon 2010 in Toronto, Canada. Don’t miss it!

We’ve been busy getting organized, and are excited to be hosting the first ever ArchCon, a conference for Arch Linux users.

We’ve got some great talks lined up, catering is almost in place, and the schwag is nearly ordered. Everything is coming together.

And don’t forget to register!

ArchCon 2010 Earlybird Registration Fast Approaching

For those that don’t know, the first ever ArchCon will be held in Toronto, Ontario, Canada on July 22 and 23. Ralvez and I are the primary organizers. We’ve got some great presentations lined up and are becoming more confident that we’ll have enough attendees to fund conference activities.

The earlybird registration deadline is fast approaching; you have four days to register for only $100. Register at the registration page:

For more information, visit the ArchCon website:

Dieter has set up a couple of wiki pages to help people collaboratively plan the conference, and more importantly, social and vacation activities around the conference. He’s coming all the way from Belgium, and is looking for other Archers to do some road trips and tourist attractions with while in North America.

Finally Shipped

Arch Linux Case BadgesAfter far too many delays, I’ve finally shipped all the outstanding case badge orders. The badges arrived today, after a delay in production and mailing, and all envelopes have been packaged; they’ll be in the mail tomorrow. I spent a lot of time stuffing envelopes this evening!

I would like to apologize to everyone who has been waiting for badges; the preorder form has been up since early December. I originally said they’d be shipping in early January, and a 1.5 month delay is truly unacceptable. Thanks to everyone for their patience; I will try to perform better in the future. I’ve certainly learned not to rely on shipping estimates!

The new badges are a more modern looking than the old ones; I’ll try to update the pictures on tomorrow.

Death of Arch Bounty

Last September I posted about Arch Bounty, a project I’d written to allow people to post ‘bounties’ to have specific ArchLinux bugs fixed. I didn’t promote it and interest faded quickly. I’ve been thinking of pulling the plug on it for a while now, but it happened unexpectedly yesterday when I accidentally killed half a dozen of the sites on my webhost. I’ve recovered most of them, but I decided that ArchBounty won’t be coming back.

There was one donation to the project; I will be forwarding it directly to the Arch Linux Donations fund.

Arch Linux Pens

I’d like to announce the arrival of Arch Linux Pens to the Schwag shop. These are nicer than I imagined, very opulent’ I’m very happy with them and hope you will be too.

Pens are deep blue and gold with “Arch Linux” and “” engraved on them. They have a soft black grip and fine ball-point black ink. They are available for $5 individually, or as low as $3.50 in bulk.

Order them now from


Copyright Dichotomy

In the so-called “copyright wars,” we see a spectrum having the MPAA, RIAA, Jack Valenti, and “all rights reserved” on one side, with the Pirate Parties, Pirate Bay, Rick Falkvinge, and “no rights reserved” on the other side. In the middle, we have Creative Commons, Lawrence Lessig, and “some rights reserved”.

I’d like to momentarily expand this line to one that places “no rights reserved” in the middle, in a way that shifts Lessig closer to Valenti, and opens up a whole new area of creative exploration beyond the pirates, who are no longer extremists.

First, a disclaimer: I don’t claim to have any answers. I don’t even believe what I’m suggesting is the right path. I am simply suggesting an idea that frames a long-standing and long-term discussion in a different light.

The spectrum above defines the opposite of a right as “the absense of a right.” This only goes halfway. The opposite of a right is a responsibility.

Image, for a moment, a society where there is no such thing as, “the right to my creation,” but there is a massive, “responsibility to create.” In this society, people would have free access to all the materials of the world, all the patents, blueprints, and software, all the films, songs, and books, all the photos, paintings, and sketches the world has ever seen. In exchange for this free access, individuals would be required (responsible) to create a certain amount of new material every year. Some of this material would be innovative and fresh, some would be a new presentation of old stories and ideas, some of it would be interpretations of those old stories in new media. We’d see new designs for existing products, we’d see new products that merge old technologies. We’d see Android phones with iphone gestures, and we’d see Mickey Mouse saving Princess Peach from the evil Bowser the Hedgehog.

Such a world may excite some, bore others, and scare many. Would these same people be less excited, bored, or scared by the Pirate Party? by Creative Commons? Maybe those deals aren’t so bad after all (to those demanding rights)… or maybe they aren’t so good (to the promoters of creativity).

This responsibility to create idea seems radical in the context of entertainment media, but it is not new. It’s a long-standing scientific tradition, best encompassed by Newton’s overused quote about giants. Academics have “free” access to the entire compendium of academic knowledge; in exchange for this access, they are expected (responsible) to generate new ideas and innovations. Some are good and some are bad, but if a scientist neglects to publish a few new papers a year, they fade from the academic community.

This idea is also an unofficial motivator in open source communities. Within the Arch Linux community, my home, I’ve made some effort recently to verbalize this norm. The story goes thus: Arch Linux has had contributions from many thousands of users. Each of us that uses the distribution is somehow indebted to all those other users. Further, we can never, as individuals, pay off the debt in its entirety. Even the well-known user with 8000 posts on the forum, thousands of package updates to his name, and dozens of Arch Linux tools under his belt has contributed but a drop in the bucket compared to the efforts of the entire community. And Aaron is aware of this debt. So should we all be.

Yes, in the academic and open source world, the implied responsibility to create is known to work. Creativity in both worlds spreads more quickly than anywhere else. Compare to the communities creating ideas whose soul purpose is entertainment. Even the liberated Jamendo is mired way over in the (Some) Rights Reserved end of the scale.