A 7th beta has been released of M0n0wall, fixing some serious bugs that slipped in Beta6:
- fixed: kernel panic when using IPsec and the traffic shaper at the same time
- fixed: SIP proxy when using PPPoE/PPTP mode on WAN interface
After more than 1 year FreeNAS 0.686 (a FreeBSD-based operating system which provides free Network-Attached Storage (NAS) services) has been released. A lot of hard work has been put into it, bugs have been fixed and new features have been implemented.
Volker, the project leader wants to thank those who have helped out on the forums, the translators, the webmaster and those who have contributed code to improve FreeNAS.
For the future multiple branches have to be mananged, a 0.686x to fix bugs in stable (no new features) and a 0.7 to upgrade FreeBSD to 7.0 + new features.
The Vietnam BSD/Linux Mirror is the only public mirror available in Vietnam and is currently managed by the Saigon Linux Group with the bandwidth and IP address donated by GHP Far East Co., Ltd.
Source: Saigon Linux (18/12/2007)
The M0n0wall project has released BETA6 (22/12/2007). This release adds support for IPsec filtering and tunnels with (dynamic) remote host names. It also allows up to 256 concurrent PPTP VPN clients (instead of only 16) and contains fixes for the filtering bridge and the captive portal. An ipfilter update also corrects the lockup issues experienced by some users with 1.3b5.
Full list of changes:
Jan Stedehouder has finished his series on “Desktop BSD – 30 days”. Read the verdict here.
On November 1st I started with this series about DesktopBSD and we are now six weeks later. Six weeks in which I played, wrestled and worked with DesktopBSD almost every day. If there was only one conclusion I was allowed to draw it would be this: after a while I kind of forgot I was working with a FreeBSD-based operating system. Yes, there have been quirks. Yes, there were problems with my hardware but I seem to be one of the few to have those problems, which indicates it can’t be blamed on DesktopBSD. Yes, it took some more time to install new software. But the overall conclusion has to be that I could do everything I needed to do on a day to day basis.
This series was started with defining the key requirements for any open source desktop that wants to be a serious contender on the market for end-users, both at home and in organizations. I will repeat them here:
1. the open source desktop needs to a recognizable and easily understandable graphical work environment;
2. the open source desktop should have a complete set of graphical tools for systems- and software management that can be used intuitively;
3. the open source desktop should support multimedia activities and peripheral devices without too much hassle, even if this can only be achieved by a pragmatic approach towards non-free software components;
4. the users of the open source desktop should have access to business-grade professional support if that is desired;
5. maintaining and developing the open source desktop should not be dependent on a single person or a relatively small group of developers and maintainers;
6. migration to the open source desktop will require re-training of end users and some level of real time support during the process. This means that good and accessible documentation should be at hand as well as easy access to end user support;
7. the open source desktop should have a solid track record for quality, stability and solid progress over the last few years.
DesktopBSD easily meets requirements 1, 2, 3 and 7. I know that work has commenced on providing a DesktopBSD handbook that no doubt complements the excellent FreeBSD handbook. When looking at the feedback provided on-screen, the team is really making an effort to provide the user with the information he/she needs at the time of actually using a specific function.
Both the team and the community are quite small. Support for novice users leans heavily on a small group of very active people. At this stage this isn’t such a bad thing, but it will get complicated if and when a new group of novice users without prior experience in BSD starts to use DesktopBSD.
Though -at the time of writing- DesktopBSD is still working towards it’s final version of 1.6, I can only conclude that this is a stable and mature operating system that really lowers the threshold to get started with FreeBSD on the desktop. I am still in doubt whether DesktopBSD has progressed far enough to be accessible for end-users with Windows-only experience right now. Linux users should have little or no problems getting off with DesktopBSD and do whatever they used to do with their Linux desktop. I can only encourage them to do so, as it would expand the user base of DesktopBSD and provide the team with more feedback and assistance to make the final leap. The strong focus on stability for the operating system, the development and maturity of the current set of DesktopBSD tools and the clear and concise on-screen information are solid building blocks for a future DesktopBSD release that will be easy to use for people with Windows-only experience.
The post can be read in its entirity here.
Volker Theile has announced the third and final beta release of FreeNAS 0.686, a FreeBSD-based operating system which provides free Network-Attached Storage (NAS) services.
This will hopefully the last beta to become stable.
And some bugfixes.
The lasted BETA can be downloaded from SourceForge.
Today may be a good day to at least do a formal comparison between DesktopBSD and PC-BSD. I guess it can’t be avoided. Two FreeBSD-based open source desktops with similar goals, but finding different solutions.
The similarities between PC-BSD and DesktopBSD are there of course. Both use a graphical installer to assist the new user with getting FreeBSD on his/her system and both have chosen for the KDE desktop. DesktopBSD allows to boot into a live environment before actually dedicating it to your harddrive, while PC-BSD ships with Compiz Fusion.
The default software collections are different as well. DesktopBSD has chosen for Firefox, Thunderbird and Pidgin. A choice that makes sense as these applications are well-known and used on Windows and Linux. PC-BSD seems to stick more to KDE-based programs like Konquerer, Kontact and Konversation. However, these are minor differences.
DesktopBSD sets itself apart through the DesktopBSD tools and particularly the Package Manager. This graphical frontend for the packages and ports collection provides an easy tool for installing, upgrading and managing the software on your system. Working with Package Manager shouldn’t be a problem for Linux users that have experience with similar tools (Synaptic, Adept, Portage).
For PC-BSD the PBI’s are unique. The work on the PBI Build Server is progressing and that will result in a far larger collection of packages. This should contribute to a wider adoption of PC-BSD among people who used to work under Windows, since the PBI system emulates their “double-click-and-install” experience the most.
There is no need to try to figure out which one is better. I just marvel at both developments and I can see they both provide an answer to the needs of different groups of users. I can imagine a future where the DesktopBSD tools are enhanced to allow installing and managing PBI’s for FreeBSD-based systems, even if only for PC-BSD systems.