1. Edit /boot/loader.conf
- Add GEOM_ELI
- Add device_crypto
3. Edit /etc/fstab
- Add .eli at the end of your swap device name
Since not not everybody is able to attend (all) FreeBSD related conferences, it’s good that these presentations are uploaded so everybody can watch them later, and the rest of the online community can familiarise themselves with FreeBSD and related operating systems.
If you want to catch up on some recent conferences this weekend, have a look at the two links above.
“As you already may now, last half a year I’ve been working on making pf SMP-scalable and faster in general. More info can be found here:
Since that announce in June, I’ve been running experimental code for more than 2 months in production on several routers. Also, some brave people volunteered to be beta-testers and also run the experimental branch in last couple of months. Code proved to be stable enough.
The new code performs better in production: less CPU load, less jitter, more responsive system under high load. It performs better under synthetic benchmarks like random generated UDP flood. It performs much better when DoS comes in.”
Dimitry Andric, a FreeBSD developer, has carried out some performance tests to explore the impact that LLVM/Clang as the default FreeBSD compiler has on FreeBSD 10, compared to GCC 4.2.1 and GCC 4.7.1. He concludes that to build FreeBSD with Clang less RAM is used and the compilation finishes quicker. Clang comes out in the benchmarks mostly ahead of GCC on FreeBSD.
I recently performed a series of compiler performance tests on FreeBSD 10.0-CURRENT, particularly comparing gcc 4.2.1 and gcc 4.7.1 against clang 3.1 and clang 3.2.
The attached text file contains more information about the tests,
some semi-cooked performance data, and my conclusions. Any errors and omissions are also my fault, so if you notice them, please let me know.
The executive summary: clang compiles mostly faster than gcc sometimes much faster), and uses significantly less memory.
Finally, please note these tests were purely about compilation speed,
not about the performance of the resulting executables. This still
needs to be tested.
You can check the benchmarks here: Clang/llvm performance tests on FreeBSD 10.0-CURRENT
The development of FreeBSD ports is done in Subversion nowadays. Fy February 28th 2013 the FreeBSD ports tree will no longer be exported to CVS. Therefore ports tree updates via CVS or CVSup will no longer available after that date. All users who use CVS or CVSup to update the ports tree are encouraged to switch to portsnap(8) or for users which need more control over their ports collection checkout use Subversion directly.
Installing and configuring FreeBSD as router is something most of us won’t do daily. It’s one of those jobs you do once, and when it’s up and running, you let your server / router do its work and you don’t touch it – unless there’s a problem.
Squid and DansGuardian are some excellent tools for caching and content filtering. Squid is a caching proxy supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. DansGuardian is a web content filter. It filters the actual content of pages based on many methods including phrase matching, PICS filtering and URL filtering.
Since configuring Squid and DansGuardian is not something we daily do, the following tutorial may be useful: Installing and configuring Squid and DansGuardian under FreeBSD.
If you run pfSense, you can install Squid and DansGuardian too.