As always, feel free to register with FirstnameLastname and tell a FreeBSD committer to add you to the contributors group for write access (you also get the benefit to be able to register for an email notification for specific pages).
Time for a new round FreeBSD Vbox’s Team called for Testing,
A few of you have probably wondered what happened to our VirtualBox
efforts for FreeBSD. Well it took a bit longer then expected and a few
problems were found that needed to be resolved first but most of the
things are looking fine now and almost all patches have been pushed
upstream with 4.0.4 so here we are now.
We will continue to work on VirtualBox for FreeBSD and upstream is also
very helpful to us but we could need a few more hands to better keep up
with the work and especially improve and fix the Guest Additions. So if
you want to help please contact us or have a look at our Todo list.
This result wouldn’t have been possible without the continuous help of
the VirtualBox Developers and a lot of people from the FreeBSD
community! (names in alphabetical order and probably missed a few,
- Alexander Eichner
- Beat Gätzi
- Bernhard Fröhlich
- Doug Barton
- Grzegorz Blach
- Hans Petter Selasky
- Julian Stacey
- Jung-uk Kim
- Jürgen Lock
- Klaus Espenlaub
- Martin Wilke
- Mattia Rossi
- Michael Butler
- Sean C. Farley
- Steve Wills
- Vivek Khera
- Wietse Venema
- many more from emulation@
Please when testing this ports backup all your virtual machines first.
Also please build the port with DEBUG option enabled and send us the
logfile when any VM crashes. Without them it’s very hard to figure out
what went wrong.
Highlights with 4.0:
- USB support (by Hans Petter Selasky)
- Asynchronous I/O
- Guest additions got startscripts and a integration into the desktop
- www/phpvirtualbox updated to 4.0-3
Alright, I know, we’re well into 2010 already, but after a couple months I’m finally settled in my new home and my computers are in good enough shape that I can actually start doing some work.
So here goes:
Bugtracker change, my choice is on Bugzilla but after Gnats, anything would be an improvement. Bugzilla also offers RSS feeds for bug queries.
Wiki change, it’s a bit the same as for the Bugtracker, except not everybody uses the wiki. Moinmoin was a good choice at the time, but really now it’s time to change. My personal choice is Dokuwiki because it’s simple to use, well maintained and has a plethora of plugins available. There are scripts on the web to do the conversion, the only thing that’s in the way is the change in the syntax (which isn’t really an issue since Dokuwiki ships with a WYSIWYG editor). Dokuwiki also provides RSS feeds. After the change, a revamp of the index has to be done, there’s far too much stuff on the frontpage and it’s not organized so well.
RSS support for CVSWeb and/or ViewVC. ViewVC supports CVS repositories, so I’m not quite sure why we still have both. RSS support apparently requires MySQL support, so I don’t see it happening. Still, having to use FreshPorts/FreshSource for RSS feeds is a bit backwards, let’s eliminate the need for the middle man!
VCS change. Just kidding, I’m not gonna go there.
That’s right, no code involved here, which makes everything a low priority task obviously. You also probably noticed that while RSS support isn’t the main reason for all these items, it goes a long way towards having everything FreeBSD-related in a single place (be it an IRC channel, Google Reader or your favourite RSS aggregator) and thus saving some time searching for information or catching up with latest development.
Some months ago the FreeBSD.org mailman web interface was getting slower and slower, and increasingly taking resources away from mail processing to the point where it started to be a problem.
Without knowing too much about how mailman works it seems like each load of the the listinfo ‘front page’, which lists all 150 or so FreeBSD.org mailing-lists, requires mailman to lock and read the config files for each list. This might not be a problem with few lists or a non-busy site, but for FreeBSD.org this resulted in the list info page taking in best case 2-3 seconds to load (this is still the case), but when the system got busy it was frequently taking > 20 seconds to load the list info page, since there were “many” request at the same time.
It is possible this could be fixed in mailman, but I wasn’t too keen on trying to optimize mailman considering I knew very little about it, and some web searching didn’t reveal any obvious solutions. This was when I remembered Poul-Henning Kamp’s goal for the Varnish reverse caching proxy project: You should be able to drop Varnish in front of an overloaded CMS or similar and be up and running in 5 minutes (OK, could be it wasn’t 5 minutes, but something like that). I had been meaning too look a Varnish for years, but never gotten around to it before.
Without knowing much about how to use Varnish I read a bit of the docs and did a basic install in a fresh jail on sky.FreeBSD.org. The setup was the most basic one which just proxied every requests it received to the ‘real’ mailman web server, and of course cached when possible. The default Varnish configuration is rather conservative and does not cache pages for that long when there is no expire information available from the backend web server. The default expiration time is 2 minutes as I recall.
Even this rather short caching by Varnish of pages made the difference between the FreeBSD.org mailman web interface being very unresponsive and unacceptably slow, to “just working” and responding as fast as can be expected. Before setting up Varnish I was getting regular (several times a day) Nagios mails about the mailman interface not responding in a reasonable time, and after installing Varnish I haven’t had a single one :-). I also haven’t needed to touch the Varnish set up – it has just taken care of itself.
Over the last couple of days I decided to learn more about Varnish and using it more which resulted in that today I switched the FreeBSD wiki over to also running behind Varnish. The wiki (MoinMoin) doesn’t support explicitly purging changed pages from Varnish, so the wiki pages can’t be cached for very long since we would risk returning out of date pages for a long time. This means I don’t expect Varnish to change responsiveness of the wiki much but it does mean that should a wiki page suddenly get a lot of hits, e.g. by a slashdotting or similar, I won’t have to scramble to prevent the wiki from stop working due to the load.
The first lecture from Kirk McKusick's full length FreeBSD Kernel Internals course has been posted to the BSD Conferences channel on YouTube. It's been about 10 years since I first took a shortened version of this course at FreeBSDCon 1999, and only a few years since I took the follow up kernel code reading course in Berkeley, and I highly recommend this unique resource to others.This makes the 24th video uploaded to the BSD Conferences channel since I created it just over a month ago. Thanks to Julian Elisher, Jason Dixon, Tomasz Dudzisz, and Kirk McKusick for uploading the conference videos and for contributing to our growing page of tips about video production and publishing on the FreeBSD Wiki.As of this writing we have 644 unique subscribers to the channel and approximately 400 daily views of these videos. To date the most popular videos have been Kris Kennaway speaking about the New features in FreeBSD 7 at MeetBSD 2007, and Jason Dixon's tongue-in-cheek BSD is Dying talk at NYCBSDCon 2006. Note to conference organizers: high level talks about the new features, or talks by speakers as entertaining as Jason Dixon are likely to be well received. The YouTube analytics to the right show the top 10 most popular videos from the channel as well as some demographic information.
This makes the 24th video uploaded to the BSD Conferences channel since I created it just over a month ago. Thanks to Julian Elisher, Jason Dixon, Tomasz Dudzisz, and Kirk McKusick for uploading the conference videos and for contributing to our growing page of tips about video production and publishing on the FreeBSD Wiki. As of this writing we have 644 unique subscribers to the channel and approximately 400 daily views of these videos. To date the most popular videos have been Kris Kennaway speaking about the New features in FreeBSD 7 at MeetBSD 2007, and Jason Dixon's tongue-in-cheek BSD is Dying talk at NYCBSDCon 2006. Note to conference organizers: high level talks about the new features, or talks by speakers as entertaining as Jason Dixon are likely to be well received. The YouTube analytics to the right show the top 10 most popular videos from the channel as well as some demographic information.
The main DNS record for the FreeBSD wiki (wiki.FreeBSD.org) has now been updated to include the IPv6 address record.
The server hosting the wiki, sky.FreeBSD.org, has been running with bz’s latest IPv6 jail patch for 10 days without issues.
See the freebsd-jail list for patches: http://lists.freebsd.org/pipermail/freebsd-jail/2008-July/000379.html
As I have been asked several times why we use moinmoin for the FreeBSD Developers Wiki and the answer is mainly “historical reasons” I decided to write the history up so I can just point people at it :-).
The history, as I recall it, can now be found on the WikiHistory wiki page.
A month or so before EuroBSDCon 2007 conference the FreeBSD.org systems at Yahoo! had gotten IPv6 connectivity with the main web server and mail servers being accessible via IPv6. The FreeBSD wiki was still IPv4 only as was (and still is) is running in a jail.
At the conference I talked to Bjoern A. Zeeb (AKA bz@) about the issue with IPv4 only jails and he was interested in making a patch so FreeBSD jails could support IPv6 and the FreeBSD wiki could be accessible via IPv6.
I should poke Bjoern regularly about making the patch, which I failed miserably at, but he got work done on the patch anyway. A few weeks ago he sent me the IPv6 jail patch for me to try out. Since life should be interesting I didn’t try it on a test server, but on the production web server sky which hosts the FreeBSD wiki and more. Just in case there were any problems I made sure I was around to recover things in case the system blew up, but none of that happened. In fact, since I installed the patch on sky a week ago there haven’t been any problems (that I know of at least). Granted there aren’t much IPv6 traffic, but the IPv4 part have been under its normal load.
So far the main FreeBSD.org DNS record for the wiki has not been updated to include the AAAA records, so people will use IPv6 if they have it, but that expected to come soon. For now people can try out the wiki using IPv6 by accessing http://v6.wiki.nitro.dk/. It has a slight (100%) likeness with the IPv4 wiki, but… IPv6!
For people interested in the patch the work is being done in the FreeBSD Perforce repository at //depot/user/bz/jail/…. I am sure Bjoern will post appropriate public patch when he think it is ready. Credit should also go to Pawel Jakub Dawidek (AKA pjd@) who made the multi IP(v4) jail patch which Bjoern based his patch on. Thanks to Bjoern and Pawel for the work making this possible!
Now I just need to actually get around to setting up IPv6 at home, so I can actually try out the IPv6 wiki myself in anything other than lynx from other hosts… any year now.
I finally got tired at looking at the hostname “wikitest”, so I decided to move the FreeBSD wiki to sky.FreeBSD.org. This also means that the wiki can now be fully “official” and has been renamed to wiki.FreeBSD.org. I took the opportunity to familiarize myself some more with how a moinmoin installation works so I did spend a good part of a weekend doing the migration but now there are fewer direct hacks in the wiki and I actually somewhat knows where the files are. The small downside to moving the wiki, and the main reason I haven’t done this before, is that I have a bit less freedom configuring the jails on sky since I now have to be a bit careful not to accidentally break the wiki. The move actually happened over a week ago, I just didn’t get around to writing about it before.
The current FreeBSD.org “monitoring system” consists of running “ruptime | grep down” from cron every hour. This is actually very effective compared to the simplicity, but it doesn’t catch e.g. when squid on www.FreeBSD.org die due to the disk being being full. To better detect this kind of errors I have I have been working on setting up Nagios for FreeBSD.org to be able to find out quickly when stuff crash. The configuration of the Nagios installation still isn’t complete, but at least it does warn me about major outages now. Thanks to the Nagios install by Erwin Lansing I also get mails if the FreeBSD Nagios crash so that part is also covered.
In unrelated news FreeBSD 4.X is no longer supported by the FreeBSD Security Team, so that is very nice that we finally could drop the support since FreeBSD 4.x has diverted quite a lot from FreeBSD 5/6/7 by now (or rather the other way around). It was getting increasingly difficult backporting fixes etc. for Security Advisories. RIP FreeBSD 4.