Some quick links for week 5 that you may want to check out:
I blogged before that there were plans of creating a FreeBSD Magazine. Just to let you know that the first issue can be expected around April 2008. It won’t be just about FreeBSD, but also about other BSD OSses, incl. OpenBSD and NetBSD, hence the name BSD Magazine. The website is now live at bsdmag.org. If you want to contribute or find out more about BSD Magazine, visit the website or contact Kate or Caroline.
The FFS File System driver for Windows enables you to read BSD (FreeBSD, NetBSD, OpenBSD) FFS partitions from Windows 2000/XP/2003.
More info, downloads and source code on this SF site.
In December 2003, I wrote a script for remotely upgrading a linux system to FreeBSD. I gave it a catchy name (‘Depenguinator’, inspired by the ‘Antichickenator’ in Baldur’s Gate), announced it on a FreeBSD mailing list and on Slashdot, and before long it was famous. Unfortunately, it didn’t take long for changes in the layout of FreeBSD releases to make the Depenguination script stop working; so for the past three years I have been receiving emails asking me to update it to work with newer FreeBSD releases,
Colin Percival wrote on his website. If you want to ‘kill’ some ‘penguins’, download the Depenguinator and let it do it’s job ;-)
Yesterday I came across a study done by Diomidis Spinellis about the development of FreeBSD. It was written in 2006 but it still gives some useful insight in and statistics about the FreeBSD Project (How the FreeBSD Project works).
FreeBSD is a sophisticated operating system developed and maintained as open-source software by a team of more than 350 individuals located throughout the world. This study uses developer location data, the configuration management repository, and records from the issue database to examine the extent of global development and its effect on productivity, quality, and developer cooperation. The key findings are that global development allows round-the-clock work, but there are some marked differences between the type of work performed at different regions. The effects of multiple dispersed developers on the quality of code and productivity are negligible. Mentoring appears to be sometimes associated with developers living closer together, but ad-hoc cooperation seems to work fine across continents.
FreeBSD is a sophisticated operating system available for a number of modern architectures. It is a complete operating system (rather than just a kernel, like Linux) derived from BSD Unix, the version of Unix developed at the University of California, Berkeley. FreeBSD, known for its stability and reliability, runs the servers of large portals like Yahoo and hosting providers like the Host Department; parts of it also form the basis for Apple’s Mac OS X. Given the global nature of the FreeBSD development model, the objective of this work is to examine its extent, determine its effects on quality and productivity, and explore how geographic distance affects cooperation among the project’s members.
Would be nice to hear who’s going to attend. I’m not sure myself yet whether i’m going or not. Would be nice to meet up with some of you guys.
To a lot of computer users, especially MS Windows users, FreeBSD is still covered by a cloud of “geekyness”. If people have heard of FreeBSD at all, they often think it’s a server operating system (which is not wrong) and that it comes with server software only (which is not correct).
Admitted, FreeBSD’s hardware support is not as good as Window’s or Linux’, but there’s no shortage of software for this operating system. It’s not only mail server, ftp server, network monitoring software etc that’s available for FreeBSD, but also video editing software, programs for creating PDFs, utilities to convert wav files to mp3’s etc etc. There’s an absolute wealth of programs, tools and utilities available; currently 17,968 so called FreeBSD ports (programs).
With this post I just want to point to a few sources that may help you can find software if you’re interested in using FreeBSD (incl. PC-BSD and DesktopBSD).
Those of you who are new to the “world” of open source software, have a look at the following two websites for an overview of open source equivalents for Windows software: linuxalt.com and linuxrsp.ru. Most, if not all, of the packages listed on these websites are also available for FreeBSD (as ports).
The actual FreeBSD ports directory can be found on freebsd.org or freshports.org (with search facility). To view the ports categories listed by groups have a look at this page on freebsd.org, this one on freshports.org or this one on freebsdsoftware.org. BSDapps.org lists a lot of commercial software packages, but the website doesn’t seem to be quite up to date.
You will gather from these links, that there are so many programs available that it can even be overwhelming. Hardware incompatibility may hold you back from adobting FreeBSD on the desktop, but the objection “there’s so little software for FreeBSD that I can use” is not valid ;-)
Very Grumpy Bunny has written a post comparing the GPLv2 and the BSD licence and explaining the difference when applied to Amarok.
There are several BSD licenses, so many that you’ll typically see any particular license under BSD terms listed as a BSD-Style license. Example, the Vorbis and Theora codecs. The terms themselves are fairly simple.
#1: Anybody can access the source code
#2: Anybody can copy the source code
#3: Anybody can modify the source code
#4: Anybody can use the source code
#5: Anybody can relicense modified code
Sounds pretty simple, at least compared to the Gnu Public License. Here are the terms of say the GPLv2.
#1: Not everybody can access the source code.
#2: Everybody who can access the source code can copy the source code
#3: Everybody who can access the source code can modify the source code
#4: Everybody who modifies the source code must submit the changes back to the original author
#5: Everybody who modifies the source code must maintain the original license
That does seem a little bit more complex. Immediately we see that the GPL has restrictions placed on what can be done with the code. Ergo, the BSD-style license is more free… or is it?
Read the simplified terms of the BSD-License again. Note anything missing? Well, if you didn’t, here’s what is missing. Any changes that are made to the BSD code don’t have to be given back to the author. Anybody can take a segment of BSD code, do whatever they want with it, and never post any changes back, tell the author what they did, or anything else.
So, there is a critical difference between a BSD license, and a GPL style license. The BSD license adopts a care-free attitude about written software, while a GPL style license enforces restrictions around that software to make sure everybody benefits.
Whole post can be read here.