Testo originale inglese: [http://behindubuntu.org/interviews/BenCollins/ qui]

Ben Collins

Data intervista: Novembre 2006

Biografia

Nickname in IRC: BenC

Località: Virginia, USA

Età: 34

Professione: Kernel Hacker

Blog: [http://ben-collins.blogspot.com]

Sito personale: [http://www.phunnypharm.org]

Attività in Ubuntu

- In che modo sei coinvolto in Ubuntu?

Mantengo il kernel Linux di Ubuntu (I maintain Ubuntu's Linux kernel.)

- Quanto tempo spendi lavorando su Ubuntu?

Cerco di non tenere il conto. Comunque più di quello che vorrei. (I try not to keep count. Way more than I should.)

- Come e quando sei stato coinvolto in Ubuntu? (How and when did you get involved in Ubuntu?)

Ho iniziato a lavorare per Ubuntu/Canonical poco più di un anno fa (appena dopo il rilascio di breezy). Questo è stato più o meno lo stesso periodo in cui ho iniziato ad usare Ubuntu. Avevo diversi amici che già lavoravano per Canonical, e fui contattato da uno di essi riguardo una posizione libera come Kernel manteiner (Fabio M. di Nitto, grazie!) (I started working for Ubuntu/Canonical a little over a year ago (just before breezy release). This was about the same time I started using Ubuntu. I had several friends already working for Canonical, and was contacted by one of them in regards to the kernel position (Fabio M. Di Nitto, thanks!).)

- Sei pagato per lavorare su Ubuntu?

Si

- A cosa stai lavorando in Feisty?

Riguardo il kernel, sto lavorando per migliorare il supporto hardware e la stabilità. Abbiamo allargato il nostro kernel team e quindi speto che questo mi dia più tempo per lavorare ai bug e alle nuove funzionalità. (In regards to the kernel, I'm working to improve our hardware support and stability. We're finally ramping up our kernel team, and I'm hoping this gives me more time to work on bugs and new features.)

- Quale funzionalità vorresti vedere o vedere migliorata in Ubuntu?

Mi piacerebbe vedere una migliore interfaccia grafica (attualmente una qualsiasi, dato che non ne esistono) per la gestione dei driver. (I'd like to see a better GUI (actually any GUI, since none exists) for device driver management.)

- Cosa comprende la pacchettizzazione e la manutenzione del kernel Linux in una distribuzione? (What is involved in packaging and looking after the Linux kernel for a distribution?)

É un'impresa immane. Buona parte del tempo lo spendo a fare il triage dei bug, raccogliendo informazioni riguardo crash di sistema e cercando di farne il debug per trovare delle correzioni adeguate.

La mia giornata lavorativa si svolge normalmente così:

• Verifica dei nuovi bug
• Ricerca di patch esistenti per i veri bug
• Integrazione delle patch
• Recupero dei sorgenti dalle fonti
• Esecuzione del compilato su tutte le architetture che supportiamo (e anche alcune supportate dalla comunità)
• Correzione di eventuali problemi
• Da ripetere finché la giornata lavorativa non è finita

It's a huge undertaking. Most of my time is spent triaging bug reports, gathering information about crashes, and trying to debug those to find suitable fixes.

My work day usually goes something like this:

• Go through new bugs
• Work on finding existing patches for legit bugs
• Integrate patches
• Pull upstream source
• Run builds on all architectures we support (and a few community ones)
• Fix any problems

• Repeat till work day is over

- Fino a che punto c'é collaborazione tra i manteiner del kernel delle differenti distribuzioni? (To what extent is there collaboration between the kernel maintainers in different distributions?)

Il kernel è molto specifico nelle distribuzioni. Distribuzioni differente hanno differenti politiche su cosa vogliono dal loro kernel. Alcune distribuzioni rimangono vicine alla versione orginale il più possibile, anche in presenza di bug conosciuti, mentre altre sono disponibili ad integrare grandi modifiche, cambiando molte funzionalità anche rilevanti, differenziandosi molto dal kernel originale. Inoltre, le distribuzioni possono avere differenti punti di vista riguardo il supporto di hardware con driver che non sono ancora integrati nel kernel originale. Quindi, mentre cerco di rendere il kernel di Ubuntu disponibile il più possibile alle altre distribuzioni, è molto dubbio che le nostre politiche coincidano con quelle degli altri. Un'area ove interagiamo molto e collaboriamo è nelle vulnerabilità di sicurezza. Debian e Ubuntu hanno un repository subversion comune per tracciare i problemi rilevanti e condividere le patch.

(The kernel is very distribution specific. Different distributions have different policies on what they do with their kernel. Some distributions will remain as close to stock as possible, even with known bugs, while others are willing to integrate large patches, changing lots of core functionality, varying greatly from stock kernels. Also, distributions have different takes on whether they support drivers in their kernels that are not in stock kernels. This could be proprietary drivers and firmware, or GPL drivers that are not yet integrated in the stock kernel. So while I try to make Ubuntu's kernel as available as possible for other distributions to use, it's very doubtful that our policies will closely coincide with others. One area where we do overlap and collaborate is in kernel security vulnerabilities. Debian and Ubuntu have a common subversion repo to track our outstanding issues, and share patches.)

- Per tanta gente il kernel è sostanzialmente una scatola nera, essi vedono il loro dispositivo hardware funzionare o meno. Come riesci a ricondurre il problema al kernel o decidere se invece si tratta di uno dei mille errori indotti dalle applicazioni? (To most people the kernel is almost a black box, their hardware either works or doesn't. How do you track down problems in it or decide if it is one of the thousands of possible programs misbehaving?)

Generalmente non è molto facile dire se il bug è relativo al kernel o meno. Vero, con i grandi progessi e l'astrazione che si è realizzata come risultato di un migliore ambiente desktop (hal, udev, ecc.), gli utenti possono penare molto per distinguerli da soli, ma gli sviluppatori che lavorano al software che direttamente si intefaccia al kernel sanno se un bug inviato sul loro pacchetto è di fatto un bug del kernel o meno. E anche per le correzioni del kernel, 9 volte su 10, un bug segnalato da un nostro utente è già stato corretto da qualche altra parte, fosse un'altra distribuzione o in una versione successiva del kernel stesso.

(Generally it's very easy to tell if a bug is kernel related or not. True, with the huge advances and abstractions that have shown up as a result of better desktop environments (hal, udev, etc), users can have a hard time making this distinction themselves, but the developers who work on software that directly interacts with kernel will know if a bug filed on their package is in fact a kernel bug or not. As for fixing problems, 9 times out of 10, a bug one of our users finds is already fixed somewhere else, whether it's another distro, or in a newer kernel version.)

- In che modo le scelte implementative fatte sul kernel impattano lo sviluppo del resto della distribuzione? (In what way can choices made in the kernel implementation affect the rest of the distribution development?)

Ci sono diversi modi in cui questo può creare problemi. Per esempio, in una distribuzione che inizi ad abbandonare i driver IDE per quelli PATA i dispositivi cambiano nome (es: /dev/hda /dev/sda). Questo ha forzato un pochetto di lavoro sul nostro lato per assicurare che questa migrazione proceda senza intoppi, specialmente considerando che noi supportiamo il cambio di versione senza reinstallazione. In generale, comunque, non ci sono molte grane per il team del kernel durante la fase di sviluppo. É raro che le API kernel/user-space cambino, e quando questo accade è normalmente conosciuto in anticipo in modo che non causi problemi.

(There's a few ways this can create problems. For instance, as distributions start moving away from IDE drivers and to PATA drivers, users' devices will change names (e.g. /dev/hda to /dev/sda). This has forced quite a bit of development on our side to ensure that this migration goes smoothly, especially considering that we support in place upgrades from one release to the next. In general, however, there's usually not much for the kernel team to worry about while in development. It's rare that the kernel/user-space API changes, and when it does, it's usually known about well enough in advance that it doesn't cause problems.)

- Quanto credi sia importante il back-porting dei driver del kernel o cose come suspend2 per le versioni LTS? (How important do you think back-porting kernel drivers and things like suspend2 for LTS versions are?)

Back-porting drivers for Dapper LTS is very important. We have a process where we are testing these patches initially in proposed-updates, in the hopes that they eventually move to stable point releases. The only patches really being considered are ones that could keep people from using LTS at all (new storage and network drivers for example). Things like suspend2 will never make it into an LTS update. While fixing suspend/hibernate support is at the top of our list, it does not prevent people from "using" Ubuntu. It's very tricky to weigh the pros and cons of patches, and not easy explaining this to users. Most just say "toss it in, it works for me", but fail to realize that the kernel is a very intricate bit of code, where even the smallest patch has the potential to regress the kernel on a large portion of machines, even if it works perfect for them. We've been bitten by harmless looking patches in the past, so we've tightened the flow of patches going in.

- What are your plans for developing a Device Manager?

First I have to get the spec done and approved Aside from that, I have started work on it. I plan to push my tree into launchpad for public consumption soon. For now, it currently will show driver information, like author, description, and module params and current values. What I still have to work out is how to manage all this information so user-space makes intelligent use of it, like udev and initramfs-tools integration. There are also some limitations in the kernel itself, which prevent this from being implemented like I want it to be. I'll be working with upstream kernel developers to iron out these details and providing patches that will hopefully be included in stock kernels.

- What are your views on binary firmware and drivers with no source code being used in the Ubuntu kernels?

My personal view is we should only be using free drivers. I have a strong dislike for hardware vendors that don't give proper support to people who purchase their products. Lack of specs is almost a sure way of locking people into using an operating system they may not want to use. However, my practical view is that as of now they are a necessary evil. Users just getting into Linux are uninformed about these issues. It's easy to just leave those users without proper hardware support, and tell them to buy something else, but that doesn't serve us at all. Those users would probably never switch to Ubuntu, or Linux in general, given that view. The approach that Ubuntu has decided to take, and that I agree with, is to make the user's system work as well as possible out-of-the-box, but to educate them about the problems. At the Ubuntu Developer Summit in Mountain View, we worked on a spec for just this issue, and as a matter of fact, devoted discussions over the period of the week to it. How do we balance our use of proprietary drivers and firmware, with our free software ideals? Our solution is to inform users that their system is using such drivers, and to point them to details about the pros and cons of this. We're hoping to see two results:

1. Users will become more informed, and hopefully make better decisions on their next hardware purchase, while still being able to start using Linux without losing functionality.
2. Hardware vendors that fall in this category will begin to see this trend as detrimental to their image, and their bottom line, especially when we are suggesting that their customers buy hardware from their competition (e.g. don't buy nVidia/ATI, buy Intel graphics). We're hoping that this, along with pressure from the rest of the community will send the right message to these vendors, while still turning users on to Ubuntu.

Informazioni legate ai Computer

- Contribuisci al FLOSS (Free/Libre & Open Source Software) in altri modi?

Not as much as I used to. I've been doing free software related things for about 8 years (back when I started with Debian). Two projects I have are sXid, and libugci. While sXid isn't really maintained anymore, it still serves a lot of folks. The libugci project was developed from my interest in xMAME, building my own arcade cabinet (http://www.phunnypharm.org/~bcollins/). I used to be fairly involved in Linux1394, but that work has also slowed down to an unnoticeable crawl. Most of my time now is spent on Ubuntu kernel work.

- Quale window manager/desktop environment usi e cosa ti piace di esso?

Up until I started working with Ubuntu, I never used X except to use firefox. I was a console junky. 12 VT's was my workflow, with vim and mutt. Even for web browsing, I prefered links over firefox. Once I started working for Canonical, I felt it was time to give X a try again, and found that I could actually make use of a graphical environment, something that wasn't true back when I started in Linux. Mainly I did this to make sure I stayed in the same environment that the users I was supporting were in. So it went from mutt to evolution, and VT console's to gnome-terminals. I still use vim

- Quali programmi usi quotidianamente?

My session includes:

Desktop 1: Firefox, xChat-gnome, GAIM Desktop 2: Evolution Desktop 3: 4 gnome-terminals Desktop 4: 4 gnome-terminals

My most used program: vim

- Com’è il tuo angolo computer?

Whoa. Anyone who knows me will tell you I'm a hardware whore, so I'll truncate this list to just the machines that stay powered on All systems are running Ubuntu, except where noted.

Build systems (kernel compiles and testing):

• zachery: UltraSPARC Enterprise 3000: 6x366Mhz CPU's, 6Gigs RAM
• frag: HP i2000 Itanium: 2x800Mhz CPU's, 2Gigs RAM
• huffy: Supermicro Xeon box: 2x2Core 3Ghz Xeon procs, 4Gigs RAM
• powder: IBM OpenPOWER eServer: 2x2Core 1.6Ghz POWER5, 8Gigs RAM
• hippo: HP A500 (PARISC): 2x500Mgz CPU's, 2Gigs RAM

Misc (desktop, etc):

• emucade: P4 system, running xMAME in arcade cabinet
• phoenix: Amd64 system, used as community desktop.
• PowerMAC G5 (ok, this one runs Mac OSX most of the time, except for testing ppc-ubuntu)

• PowerBook 17" (Blah, this one's my wife's now, so yes, it runs Mac OSX too)

• HP Pavilion dv5000 laptop. 1.6Ghz Core Duo: This is my main system. It doesn't leave my side.

http://behindubuntu.org/interviews/BenCollins/images/Hitech-Rack_wee.jpg http://behindubuntu.org/interviews/BenCollins/images/Hitech-Security_wee.jpg http://behindubuntu.org/interviews/BenCollins/images/Guard-Cow_wee.jpg

The photo probaby needs some explanation. I get a lot of flack about this from co-workers Yes, my primary systems are hosted in a barn. I live on a farm, surrounded by cow pastures (not my cows). The barn provides the best ventilation and noise reduction. Not only that, but it's surrounded by a high voltage live stock electric fence and cows. I can't think of a better security system than sending a would-be thief into cardiac arrest, or having them trampled by Lucky, the 1-ton bull

Informazioni Personali

- Dove sei nato e cresciuto?

Born, raised, and still living in Virginia, USA. I've never lived more than 60 miles from where I was born.

- Che ricordi hai della tua infanzia?

I remember this hot teacher I had in 4th grade...wait, you probably want something computer related, right? Anyway, I grew up around the time of the technology boom. My computer interest started with an Atari 400, and soon moved to an Apple //e. One thing I remember about this was getting in trouble at school and having to write a sentence about 100 times. Instead, I went home and wrote a BASIC program that printed the sentence 100 times, complete with incremental numbering (a small feat by today's standards, but was way cool back then). Teacher was none the wiser of my short cut. You wouldn't be able to get away with this today. Wasn't long before we upgraded to a Mac Plus. The things I have the best memories of is figuring out how these machines all worked. I rarely played games, and mostly took them apart and did a lot of programming. With my Apple //e, I built a plotter out of some old DC motors and stuff from the hardware store, and interfaced it through the printer port. Never wrote a proper printer driver, but I could control it programatically. I also built a light pen, and actually did make use of that in some programs. This was my first taste of hardware level programming.

- Sposato, fidanzato o disponibile?

Married for almost 12 years.

- Hai figli o animali?

Three boys, 10, 6 and 2 years old. One dog. My wife will tell you she has 4 kids, though. I don't think I've grown up yet

- Che posti consigli di vedere a chi visita il tuo Paese?

There's so many great places, it's hard to point at just one. If you have the heart of child (like me), you have to go to Disney World. One of my favorite places to go is a drive down the Blue Ridge Parkway, through the Apalachian Mountains, during fall. It's very scenic.

- Il luogo preferito dove andare in ferie?

Camping, just about anywhere.

- A cosa sei appassionato?

One of my favorite pastimes is poker. Some people see this as strictly gambling, but I play it for different reasons. For one, poker is a very social game. I love interacting with people, and playing games of wit and strategy. Poker requires making educated assumptions based on very little information, and usually on the smallest of details that may need to be recalled from hours prior to the decision. It also requires skills in math, figuring odds, and quickly calculating probabilities. I love studying the game. It's one of those things you never master, but have lots of fun trying to.

- Che cosa significa per te il successo?

Success to me now is very different than what it used to mean to me. My only guage is my kids. I want them to be proud to say I'm their Dad. If I've succeeded in their eyes, then I'm happy.

- Chi ammiri di più?

This might sound kind of typical, but I really admire Jobs and Wozniak. They were a rare combination of innovation and the foresight to bring it to the masses. No matter what you may think of one or the other, Apple most likely wouldn't have gotten off the ground with out both of them together. Most of my career I've been hoping to be a part of something as great as that. Probably one of those things you don't realize while it's happening...maybe I'm part of it right now

- Citazione preferita?

Random quote from a friend of mine on why girls don't have hair on their butts: "It's not in their hygene."

- Cibo preferito?

Anything you can cook on a grill. Doesn't matter if it's hotdogs, hamburgers, steaks or seafood. I love cooking out, and drinking a few beers with friends.

- Cosa fai nel tuo tempo libero?

I fish, play paintball, and like to build things (potato gun anyone?). Mostly, I just love being out doors. I listen to all kinds of music. Favourite genres are rock, metal and rap. Love to watch movies. Recently watched "Let's go to Prison". My reading is restricted mostly to technical documents. Unless you're interested in the latest IEEE specs, or hardware documentation, you probably wouldn't care about my reading list.

- Suggerisci un sito che non sia di Ubuntu.

Random link from my bookmarks: www.homelandstupidity.us This is basically a site dedicated to how dumb the US government can be. Not news to most people, but interesting none-the-less.