Bricked Router

Dear Lazyweb,

Last night I managed to brick my router by reflashing its firmware doing everything by the book. It was probably just one of those unlucky moments in life. It's an old 3rd revision Linksys WRT54G complete with 2.4-kernel-only Broadcom chips.

My question to you, Lazyweb, is which cheap reflashable router should I get? This one had trouble getting internet to the whole house. If I ever fix this one, I'll probably set up a more distributed network as well. What I want in a new router is a more powerful CPU and possibly Wireless-N capabilities. I know I will have it for a few years, so it will definitely be worth paying a bit more for. Are there any good Wireless-N routers that will let you put your own firmware on it? Preferably something that can handle a 2.6 kernel and that doesn't need a proprietary Broadcom driver?

Fedora 9's Name

The following is some comments posted to Planet Fedora by Fabian Affolter. I found it hilarious, and as there is always a problem when translating things from English to other languages, I thought it would be good to have it translated into something more accessible. I've taken a few liberties translating this, since German doesn't match neatly with English in direct meaning. With his permission:

Moving along, a new name for Fedora 9 was chosen. It's going to be Sulpher, or in German Schwefel. I can live with that.

Were we to continue forever with the Periodic Table of Elements, I would be very happy. From my point of view, it makes things clearer and more intelligent, if the code name came from a scientific field. There are always going to be great names in English, but when translated into other languages, they are hilarious. I would prefer not to have this problem again. Ubuntu, for example, picks names you might expect to hear in a playground. They should belong, rather, in a childrens' book. I'm looking forward for more good laughs, Crummy Cat, Dirty Dog, the Oozing Ox, and the Drunken Deer. If I say at work that I'm using the Effluvious Eel, my coworkers would roll around on the floor laughing.

[I had to use the thesaurus to find Effluvious :P]

Who the devil chose "Mayonnaise"? I'll give you joker's a few good hints about what happens when a Frenchman speaking German has no idea what that is.

-fin-

To be honest, I think one of the hardest accents in German to understand comes from French speakers. The two languages are so different in some ways, that as a foreigner, it is that much harder to comprehend. While I certainly appreciate calling Fedora after a tasty sauce to go with roast beef, you have to admit that without a large international marketing team, our name will be broadcast around the world. Many big companies pay millions of dollars to have *different* names in different countries. It also cracks me up that "Lagnese Eis", an ice cream company has an Italian name in Germany, but a German name in Israel. (I think it's either "Straub's" or "Strauss's" although I can't remember offhand.)

Smolt is awesomerester

Tonight I'm happy to announce that the SELinux features are complete. We've been collecting SELinux data for a while, but apparently the reports never got updated. Tonight they have been. Whenever we get around to updating smots.org, these new changes will be apparent.

Along with them come other new features, like superpowerful anonymity, a few database optimisations on the backend, better integration with FAS and Bodhi, and talking tigers. I knew today was a good day to wear my rocket ship underpants.

Yukon Ho!

Halp!, a Fud is eatin' my Fud

I promised a blog post about FudCon, and this is it. For starters, FudCon was awesome. Overall, I didn't get as much actual lines of code done as I would have liked, but it was very productive all the same. A big thank you goes to Max and all the others who made FudCon possible. It was great to actually meet some of the Fedora hackers I've gotten to know over the past eight months. I got the chance to sit down and talk to a bunch of different people and flesh out a bunch of different ideas, some more alcohol skewed than others, over the weekend. Hopefully there'll be alot of good coming out of them.

The Sessions

The first hacking session was great. Between everything else, I managed to get about 70% of the security features I wanted to stick into Smolt. Most of the details need to be fleshed out, but I can safely say, Smolt is very very anonymous. If you feel your identity has been compromised, just ask for a new one; it will be fully automated. Also, Lee took some of our queries to our MySQL backend, and optimized them, so I'll be integrating that work in over the weekend.

I also got the chance to listen in to the work that Paul Frields, our newest fearless leader, and the rest of the Fedora Board members are putting together. We're in good hands.

One


Michael Tiemann's talk was very interesting. One thing that struck me the most is how companies are coming on to the Open Source bandwagon wholesale. They switch their entire stack to open source components, install RHEL on every box and then ask "How can we be more open source?" To be honest, this sounds too much like a religion, and not enough like a solution. The skeptic in me wonders how much of "Open Source" is really understood by the execs running all these companies. Well, assuming they do get it, (and the optimist in me hopes they do,) we discussed how Fedora can help. Something that came up quite often is the infrastructure that Fedora has already. As a group, we coordinate a huge global development team, providing such sundry resources as file servers, application servers, development applications, IDEs, discussion forums, project management software, and even VOIP service. I'd like to coin the term "Salon Fedora", which is what I feel Fedora is going to turn into. It is a virtual salon where developers can come together and discuss ideas openly, with the chance to develop them, and see them deployed into the wild. It is a link between the business hacking community and the hobbiest hacking community. (If you don't like the name, please feel free to think up a new one.)

Two

The second talk I went to is the Pyjigdo talk given by Fedora Unity. Fedora Unity has been using Jigdo and other tools to develop their Respins of Fedora. I also went to their third talk about revisor, and between the two of them, it was great to see how the entire Fedora Unity stack comes together software wise. Also, thanks to Jon and Dutchie showing off how to write a plugin for Revisor, I have a couple of fun ideas for Wevisor which I'll go into at the end.

Four

The fourth talk is an interesting one. On one of the mailing lists, there has been heated discussion about our init system, and how we are going to move forward in the future. Casey Dahlin has a no nonsense approach to building a new init system, but I was happy for the my first chance to see how Fedora Developers resolve these conflicts in person. I suggested to Casey that he have someone record the discussion, because it seemed like it would be a great way to show the world that sometimes Fedora developers can do things amicably. Wishful thinking led to none other than Paul doing the recording, with everyone interested contributing what we needed to. Between people from the RHEL side of things to long term Fedora people to ex-Debian ethusiasts like myself, we were able to go over all the issues involved in switching to Upstart. It'll be interesting to see how one more Ubuntu tool integrates into Fedora, just like they use our tools like PulseAudio.

Five

The fifth talk was just fun. I got to meet Seth Vidal, and talk about Yum. I wish I could have seen something about writing plugins for Yum, but it it was fun to talk about why Fedora doesn't do live upgrades the way that Debian does. Funny thing is, I've stopped missing that feature in some ways.

Six

Finally, there was Luke Macken and Toshio's Turbogears session. Given the whole complexity of Smolt, it was funny to see Luke make things look easy again. Luke's got a great eye for making presentations, so if you missed it, I highly recommend you see the slides and notes. They are put together very well.

Beer

FudPub was... well... FudPub. First, we all went for various pork and other products with beer on the side at the Flying Saucer. I fortunately ducked out of the Karaoke, and hung around the bar next door having something like 10 shots of Jäger. Great way to end the day.

Hackfest Two

So Jäger in the night, very cool. The next morning, not so cool. I don't know how it happened, but I woke up to find myself talking to Bobby Frank the next morning about Wevisor, and how to make it not suck. Right in the middle of a pretty mild hangover, I find myself talking to Jon and Dutchie about how we can go about integrating Wevisor into Revisor better. I missed the chance to work on Wevisor last summer, but now I can have the opportunity to do something interesting there.

Holy Crap, I have alot to do

So for the next couple of weeks, I'll be working on Smolt and Wevisor things. Hopefully I'll have that development done by then, and somehow squeeze in working on Haskell. Following that I'll be working on more Haskell, and coordinating some tools with a few other devs, but I'll have more comments on that. Finally, I'll be working on HaPPs a little bit, getting it to work on Fedora, because we'll need something to showcase what Haskell can do.

I feel a little like I bit off more than I can chew. I'll have to try to take things one bite at a time....

KDE 4 and other thoughts

I gave KDE 4 a try today. It was very slick and smooth with all the draw of something severely underdeveloped. If there's one thing I should do, it's give the KDE team credit for being brave enough to label it a 4.0 release. I understand they are getting alot of flak for releasing something so unpolished, but they still have to release sometime.

The one item that struck me as odd though is how much reinvention of the wheel there is. The Compositing effects added a level of depth and integration into the desktop that Compiz Fusion probably wishes it could have. All this is done entirely through KDE's own codebase. I had to ask myself why didn't they just partner up with Compiz Fusion and make it work for them already? In fact, why don't they just unify their codebase with Gnome, and then we'd have one really awesome Linux Desktop.

The reality of the matter is that by unifying the code base, it would make it harder to introduce changes. Theoretically, someone could fork any free software project they want, when they want to try something experimental. But the more I thought about it, making new projects tends to lead to cleaner code, that is sometimes more competitive than the status quo. When I think about the number of tiling window managers available, and how many of them are going to disappear as XMonad becomes more developed, it becomes more obvious how this works out.

In other news, the FDA declared cloned meat safe for eating. I wonder if it's kosher.

FudPub: A Retrospective

I'll blog about FudCon later. When I've recovered, which I estimate to be sometime next millennium.

FudPub on the other hand, I have this to say. After a night of eating sausage, bavarian potato salad, and drinking enough jägermeister to kill a deer, the best cure is the hair of the dog that bit you: something sausagy. Alas, there was none to be had for this poor loup all day at the hackfest, as there was a hackfest going on. I get home tonight, after travelling all the way to Chicago just to get back to Pittsburgh, and having had not a single bite to eat, even of overpriced food from Starbucks, and ask my dad what there is to eat in the fridge. "Well, there's a couple pieces of knockwurst floating around."

It's good to be home.

(I'll be going straight back to classes after this, so it seriously will be a day or two before I can get all my thoughts together. I promise a nice lengthy report on FudCon soon.)

Smolt and FudCon

So far, FudCon has been awesome. It was very good to finally meet Mike, and go over some of the outstanding issues in Smolt. We finally have a good technical solution, so that we know Smolt is secure.

Traditionally, Smolt would store a UUID on the local system. This would be used as a key to the smolts.org database, when sending updates or looking up host information. With this UUID, anyone could remove a profile from the database. Knowing who had which UUID, anyone can find out what hardware you have. This was inherently insecure.

Over the past couple of months, I was trying to think of a way to lock down that access to the person who had control of the local client. Ideally, PolicyKit will define who is allowed access to the functions provided by Smolt, such as submitting and deleting a profile. At bare minimum, this would be root-only, with the UUID lockdown and hidden via file permissions and SELinux. Ideally, this will all be controllable via Cobber, Func, and anything else you might want to use. Let's say you want to share your profile. Just ask the server for a link. Every UUID comes with a new snazzy public UUID that you can share with anyone you want. Don't like your pubic UUID? Just ask for a new one. You will need access through PolicyKit to get this public UUID too. In the end, there is no way someone can just trace a UUID back to you, unless you want them to.

I'll blog more about FudCon later, I'm enjoying a nice look at TurboGears, courtesy of Luke.