That was such a success that it was repeated in Monterey CA in October 2000, now as the BSDCon. Again I reported in the December 2000 Dæmon News. So now it's time to report on the BSDCon 2000, right? Well, yes, but there's a little difference: after last year's BSDCon, Kirk McKusick suggested to the board of USENIX to take over running the conference, and USENIX decided that February would be a better time to hold the conference, so the next BSDCon will be from 11 to 14 February 2002.
In the meantime, however, a group of European hackers decided that it was a little expensive to have to go to the USA for this kind of conference, and indeed there were a large number of potential delegates who couldn't afford the two previous conferences. As a result, they organized the first BSDCon Europe in Brighton, England, in mid-November. Like the first FreeBSDCon in Berkeley, this was an experiment to a certain extent. Unlike the first FreeBSDCon, sponsorship levels were much lower, making it a lot riskier.
The conference was a great success. In comparison with the US events, a larger proportion of the attendees came from outside of the country, so there was an element of tourism as well as the traditional activities involved in a conference. The organizers recognized this, and it was part of the reason they chose Brighton, a well-known tourist destination which also happened to closer to some parts of France than it was to London.
We took a large number of photos of the event. A number of the photos remain without adequate titles; if you can help fill them in, contact the people who took the photos.
The Con was spread over a long weekend, from Friday to Sunday. On the Friday there were a number of free tutorials. I did a whole day tutorial on kernel debugging, so I didn't get to see any of the other tutorials. Mine was successful, at least for me: I covered the material I had in the time allocated, and was even able to ``accidentally'' panic a machine with exactly the same panic as one on one of my slides. That turned out to be a bug in memory allocation which only affected laptops, and Bodo Rueskamp and Ian Dowse promptly attacked it and fixed it:
iedowse 2001/11/09 15:58:07 PST Modified files: sys/kern subr_prf.c Log: Properly sanity-check the old msgbuf structure before we accept it as being valid. Previously only the magic number and the virtual address were checked, but it makes little sense to require that the virtual address is the same (the message buffer is located at the end of physical memory), and checks on the msg_bufx and msg_bufr indices were missing. Submitted by: Bodo Rueskamp
Tripped over during a kernel debugging tutorial given by: grog Reviewed by: grog, dwmalone MFC after: 1 week Revision Changes Path 1.73 +7 -4 src/sys/kern/subr_prf.c
It's always nice to have real life problems at tutorials.
On Friday evening we had an English ``pub-style'' quiz show, which proved to be lots of fun, and O'Reilly and Associates donated a number of books as prizes. It quickly became evident that my team wasn't going to win, so we decided to go for the booby prize instead, which turned out to be 100 sticks of ``Brighton Rock'', a kind of foam sugar rolled into sticks, with lettering down the inside, in this case FREEBSD SERVICES. The organizers had had to buy 1000 sticks of it, and there was still plenty left over.
The following night was the conference dinner. I may be an old fogey, but I think that the purposes of these dinners is to get together and talk, not to listen to music, especially if it's loud. Unfortunately, the organizers had hired a band which was loud enough to make conversation impossible, so we didn't get very much done.
I didn't go to many of the talks: I've found that most of them are more tuned towards the casual user, which is almost certainly the correct focus, but I personally found it much more interesting to talk to people.
Within the week, FreeBSD core had agreed to the position of Bugmeister, which may not sound very remarkable until you understand the speed with which we usually get things done. Dag-Erling is now collecting his bug busters. He can do with plenty of help. If you want to help, send him mail.
People didn't complain too much about the second and third issues any more. But the black hole syndrome was still an issue, and though nobody complained about the fourth problem, it was an issue: one of our members had been sick for some time, and since recovering we hadn't heard from him. Even repeated questions to him went unanswered. What to do?
Well, it was pretty clear that we knew what we had to do, but it's painful. Finally, however, we removed him from the core team, as our statutes demand. It's a sad thing to have to do, but it's probably a good thing we did it: it shows that we can live up to our promises. It in no way reflects on the ability of the core team member in question: in a volunteer project like FreeBSD, other commitments are frequently much more important than the project.