Sun VirtualBox has been in the FreeBSD ports for a few weeks now. The FreeBSD Handbook has been updated to include VirtualBox on FreeBSD as host OS.
I’m sure this is written tongue-in-cheek, though there may be some truth in it here and there:
How many FreeBSD hackers does it take to change a lightbulb?
One thousand, one hundred and seventy-two:
Twenty-three to complain to -current about the lights being out;
Four to claim that it is a configuration problem, and that such matters really belong on -questions;
Three to submit PRs about it, one of which is misfiled under doc and consists only of “it’s dark”;
One to commit an untested lightbulb which breaks buildworld, then back it out five minutes later;
Eight to flame the PR originators for not including patches in their PRs;
Five to complain about buildworld being broken;
Thirty-one to answer that it works for them, and they must have cvsupped at a bad time;
One to post a patch for a new lightbulb to -hackers;
One to complain that he had patches for this three years ago, but when he sent them to -current they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive;
Emmanuel Silvério Francisco has translated the FreeBSD Handbook into Brazilian Portugese.
The PDF can be downloaded here
Murray Stokely has an interesting post on Ohloh.net:
I’ve written previously about Ohloh.net and how I’d like to see more of the dynamic code metrics calculated there available on the FreeBSD web site. I am happy to report that today I noticed after several years of attempts, the ohloh repository import servers have finally managed to get through the entire FreeBSD source repository. Their software setup previously had difficulties dealing with a project with as long of a history as FreeBSD.
You can now view the top level code metrics about FreeBSD from the FreeBSD Project Page on Ohloh.net. This page indicates that there are over 10 million lines of code, that more files are licensed under GPLv2 than any other license.
The committer totals do not quite match up with Peter’s Commit Counters.
The PC-BSD Team has announced the availability of PC-BSD 7.1.1
Version 7.1.1 contains a number of bugfixes and improvements from PC-BSD 7.1, including KDE 4.2.4, improvements to printing support, Xorg Server 1.6.1, and much more.
For a full list of changes, please refer to the changelog. Users who wish to upgrade from PC-BSD 7.0.x / 7.1 are able to do so via the upgrade / repair option during the installation.
In this article by Christer Edwards, we will explore FreeBSD Jails. FreeBSD Jails are a kernel-level security mechanism which allows you to safely segregate processes within a sandbox environment. Jails are commonly used to secure production network services like DNS or Email by restricting what a process can access. In the case of a malicious attack on one service, all other Jailed processes would remain secure. FreeBSD Jails securely limits, in an administratively simple way, the amount of damage an attacker can do to a server.
Is it possible to easily run a half-dozen internet services on a single piece of hardware and make sure that if one is compromised the others will remain unharmed? Can this be done without a mountain of administrative overhead and customization? Can I configure my services the way I have grown accustomed? Absolutely! This article will outline how to achieve this, through the use of FreeBSD Jails.
Over the course of this article I will outline how to install a list of production services on a single piece of hardware, securing each one from the next, all with only one additional administrative tool: ezjail
Before we get to the ezjail tool we need to define FreeBSD Jails. What are they? What do they do? Why do I care?
FreeBSD Jails are a kernel-level security tool used widely in the FreeBSD community to segregate processes. An easy way to think of a Jail is that it is very much like a chroot environment, but much more hardened. While a standard chroot environment can often be escaped, FreeBSD has added code to their kernel which hardens the chroot environment into a “Jail”—Inescapable. Within this Jailed environment processes are unable to identify, access or otherwise communicate with processes on the outside of the Jail. Networking is limited within the Jail as well. A Jail cannot affect any underlying network configuration other than that which it has been assigned. A Jail can also be thought of in many ways like a virtualized machine in that the virtual “guest” cannot interact with the physical “host”. Jails allow us the opportunity to run processes in a secure manner separate from our host environment.
If that sounds appealing to you may be wondering how to activate and use this Jail system. That, my friend, is the focus of this article. Get settled because by the time we’re done here you will have all the tools you need to segregate processes for security, sandboxing or even create custom environments for other users.
By default the Jail system is part of the FreeBSD kernel. The kernel customizations to make the system possible have such a minimal footprint that it was decided it should be a default, always-on feature of FreeBSD. Your FreeBSD installation already has the ability to do everything described above, you just need to know how to use it. Continue
Read the whole article on setting up, configuring and running FreeBSD Jails
It is beyond the scope of this guide to teach you how to install the FreeBSD OS.
To make this tutorial even simpler, I remove the Digium PCI Card with 4 FX0.
- Running FreeBSD OS (I’m currently using FreeBSD 7.2)
- Root Access to install from ports
- Basic Unix Commands
- Win32 X-lite SIP Phone
letters/words in red must be change
1. Install from ports
2. edit rc.conf to start asterisk on boot
3. Modify the Asterisk config files.
4. start asterisk service
Full howto here (cebuitsolutions.com)
Ed Schouten has been awarded a grant to write a new console driver for the FreeBSD project. We are excited to support Ed in providing a more efficient and user friendly console driver.
This project will allow Ed to add an additional abstraction layer to the kernel. This new layer, the terminal layer will be a layer that sits between the TTY layer, the kernel console (cngetc, cnputc) and the actual console driver. Right now we have a terminal emulator (libteken) that is part of Syscons. This terminal emulator will be moved into this
The advantage of having such a layer, is that the console driver itself does not have to care about any TTY semantics, streams of bytes, processing escape sequences, etc. It will just receive a set of character drawing, filling and copying actions. This should also make it easier to implement Unicode.
“During this project I’m going to continue the work I did with the TTY layer, by developing a new console driver for the FreeBSD kernel,”
said Ed Schouten, FreeBSD Developer.
“By moving towards a graphics mode console driver, it will be much easier to make the boot process look nice on desktop systems (i.e. PC-BSD). It will also make it possible to support the industry-standard Unicode character sets by default.”
This project will be completed by the end of December.
The U.S. Commerce Association recently announced that the FreeBSD Mall has been selected for the 2009 Best of Concord Award in the Computer Services category by the U.S. Commerce Association (USCA).
Each year, the USCA identifies companies that they believe have achieved exceptional marketing success in their local community and business category. These are local companies that enhance the positive image of small business through service to their customers and community.
Various sources of information were gathered and analyzed to choose the winners in each category. Winners were determined based on the information gathered both internally by the USCA and data provided by third parties.
says Theresa Garner, Manager, FreeBSD Mall, Inc.
“FreeBSD Mall takes its commitment to customer service very seriously, and will continue its current tradition of providing outstanding software, documentation, and support to the FreeBSD community.”