This article will cover a very basic setup where a FreeBSD server is configured as an iSCSI Target, and another FreeBSD server is configured as the iSCSI Initiator. The iSCSI Target will export a single disk drive, and the initiator will create a filesystem on this disk and mount it locally. Advanced topics, such as multipath, ZFS storage pools, failover controllers, etc. are not covered. Please refer to the following documentation on iSCSI for more information:
- RFC 3720 – Internet Small Computer Systems Inferface (iSCSI)
- FreeBSD Handbook – iSCSI Targets and Initiators
- Mikhail E. Zakharov’s excellent article in BSD Magazine titled “FreeBSD Based Dual-Controller Storage System Concept”
Now to get started…
iSCSI Target Test Setup
The disk drive which should be shared on the network is /dev/ada0, a 5G SATA disk created in VMWare that I attached to the system before starting it up. With FeeBSD, iSCSI is controled by the ctld daemon, so this needs to be enabled on the system. While at it, why not go ahead and enable it at boot time too?
This blog by user Bobulate writes about his work in progress with FreeBSD and CPack, a cross-platform software packaging tool that comes with CMake packing software. Read about his thoughts at the link below.
Some days of the week, I work on Free Software projects that aren’t ready to see the light yet; they live in my own git repo’s, or wherever. While I have the intention of publishing eventually, I usually want to get things somewhat working before throwing code out there.
Part of checking if things work is packaging, and installing the stuff on more than one system. Sure, I can build everywhere, or copy around executables, but it struck me that it’d be cool to have packages — you know, installable with the system package manager — for the stuff I make. O yeah, I know flatpak is the new orange, but I’m not that hip. I’ll stick with Debian and FreeBSD packages, thanks.
Original post: http://euroquis.nl/bobulate/?p=1531
MirageOS is a library operating system that builds unikernels for the purpose of high-performance network applications for cloud and mobile platforms. Recently, the developers have announced support for KVM hypervisor and FreeBSD’s bhyve. Read the full article for more information on what this capability brings.
Expanding Unikernels Support
Previously, unikernels created using MirageOS were far from being able to boot anywhere. They supported only environments hosted using the Xen hypervisor.
With the release of MirageOS 3.0, however, the platform now supports the KVM and FreeBSD bhyve hypervisors, too. That’s significant because it brings the unikernels a step closer to realizing their full potential—which is to be entirely environment-agnostic and capable of booting anywhere.
User Andy Mender tells us of his experience switching over to FreeBSD, having been a long time Linux user. You can also see his older blogs documenting his journey of using both open source operating systems.
I guess it should be no surprise that I returned to FreeBSD once more. One of the reasons I originally started learning C was to be able to help writing/fixing wireless drivers for FreeBSD. Although I haven’t reached that point of proficiency just yet, I feel FreeBSD is truly the place I belong after all. From the intrinsic order of a cathedral, through good programming practices and complete documentation to great system-level tools (jails, zfs, bhyve, etc.). Reading the most recent issue of Admin: Network & Security made it even clearer to me. GNU/Linux is growing strong in the server sector, with new GUI-driven tools and frameworks for container management. Personally, I think that’s awesome! It’s a win for the whole open-source world. However, Unix is more than just GNU/Linux – people often forget about Solaris/OpenIndiana and the various BSD-based operating systems (FreeBSD, OpenBSD, NetBSD, DragonflyBSD, etc.). They too are great server platforms, one can learn a lot from. There are scenarios in which a non-Linux Unix is more suitable for the same or similar tasks.
User eerielinux posts about updating their FreeBSD 4.11 machine. The version was released in 2005 and was end-of-life’d in 2007. Nonetheless, this article documents an interesting journey of updating a near decade old system. Check out the links below to read this blog series spanned across four posts.
Ah, weekend. And it’s a nice day, too: The sun shines on the snowy landscape! A perfect day to go out with the children – or to embark on a vastly different kind of adventure… Yes, you read that title right. This is not about four FreeBSD 11 machines. It’s about one FreeBSD 4.11 machine in 2017!
Legacy systems in general
Why even bother with FreeBSD 4.11 today? Well, most people would probably respect historical interest and in fact I was keen on tinkering with a legendary old 4.x release and see if you can have some fun with it (spoiler: Oh yes, you can!). But this would be a task for times when I have absolutely nothing else to do. So it’s fairly obvious that there’s another reason.
This post is about the first part of updating this fresh 4.11 system to a state that’s a bit less catastrophic. Remember: FreeBSD 4.11 was released in 2005 – however the ABI of each release is carved in stone with a .0 release. Which means that the software in the base system is from 4.0 and thus we venture back into the last millenium: 1999!
This post will cover installing newer software.
So far we have a pkgsrc tree from mid 2007 and things seem to be working. However that’s pretty close to 4.11’s release in 2005 and thus not too amazing. Working with such an old system there are plenty of cases which mean “game over”.
This post details some more updates until we reach the final state that’s possible with such an old system (without resorting to extreme means).
Planting a new tree
So far we’ve built some packages from 2013 and before. Using a current pkgsrc tree won’t work – the various pkgsrc tools that our system has are too old. It might not be too big a step but we can use a tree from the second half of 2014.
In this tutorial, FreeBSD Security Officer Colin Percival shows us how to set up IPv6 on FreeBSD/EC2 and provides some tips to help simplify the process. Visit the link below to read his full blog.
A few hours ago Amazon announced that they had rolled out IPv6 support in EC2 to 15 regions — everywhere except the Beijing region, apparently. This seems as good a time as any to write about using IPv6 in EC2 on FreeBSD instances.
First, the good news: Future FreeBSD releases will support IPv6 “out of the box” on EC2. I committed changes to HEAD last week, and merged them to the stable/11 branch moments ago, to have FreeBSD automatically use whatever IPv6 addresses EC2 makes available to it.
Next, the annoying news: To get IPv6 support in EC2 from existing FreeBSD releases (10.3, 11.0) you’ll need to run a few simple commands. I consider this unfortunate but inevitable: While Amazon has been unusually helpful recently, there’s nothing they could have done to get support for their IPv6 networking configuration into FreeBSD a year before they launched it.
To enable IPv6 support in an existing FreeBSD EC2 instance, you’ll need to do three things: …
This blog series by userdiscusses some security aspects of HardenedBSD, along with an Entropy Assessment of FreeBSD. The author runs various tests using DTrace and documents his findings across 2 different blogs, and more to come in the future. Check out the blog links for the full and detailed report.
The True Value of Randomness: Initial Results in Hardened/FreeBSD Entropy Assessment (Part 1 of Series)
First, touching back on some background: Currently, I am employed by Acumen Security, LLC as a Lead Security Engineer where I work on Common Criteria and FIPS consulting and evaluation testing. Most of this (especially the FIPS 140 stuff) is basically being the crypto police — verifying the correct implementation and operation of cryptographic algorithms and modules, correct implementation of encrypted communications channels, etc.
In order for a product to be accepted into evaluation these days, the product vendor and lab must first submit an Entropy Assessment Report. Essentially, this is proving that there is enough raw randomness being fed into the crypto system from the start, because if you have week or predictable initial entropy, the strength of the entire rest of the crypto system is compromised
Original article: https://www.weaponizedawesome.com/blog/?p=154
Deeper Exploration in (Free|Hardened)BSD Entropy (Part 2 of series)
So, the other day I posted some background and initial findings from a side project in attempting to measure entropy in FreeBSD and HardenedBSD systems. Rather than instrumenting the kernel with printf(9) or log(9) calls, I decided that I wanted to take the opportunity to start digging with with DTrace.
The first blog post attracted a little bit of attention, and I got into a fairly long conversation on Twitter with John-Mark Gurney that let me know that I was on the right track, but needed to get a little bit further in to really, effectively count what was being fed in.
Original article: https://www.weaponizedawesome.com/blog/?p=173
Phoronix has compiled a list of their top BSD related stories for 2016. Head on over to the link below for a list of their most popular articles.
Continuing our end-of-year recaps for the most popular stories on Phoronix, when we’re not busy covering Linux, the BSD operating systems get their share of interest on Phoronix. Here is a look at the exciting BSD advancements made in 2016.
2016 saw the release of FreeBSD 11.0, UbuntuBSD making a few splashes, DragonFlyBSD advancing on several fronts, DRM/KMS Linux drivers seeing more ports to the BSDs, the original Lumina Desktop Environment seeing adoption, PC-BSD becoming TrueOS, and much more.
Here’s a look at our most viewed BSD stories on Phoronix for 2016: …
Original article: http://www.phoronix.com/scan.php?page=news_item&px=Top-BSD-News-2016
Michael Larabel also provides us some benchmark tests of TrueOS and DragonFly against various Linux distros to wind down the year.
Last week I published various Linux workstation/server distribution OS benchmarks for ending out the year on the Linux distro comparison front (though a desktop/gaming focused comparison is coming this week) while for those curious here are some BSD operating system results compared to the Linux workstation/server performance figures.
For some end-of-year BSD benchmarking were (FreeBSD 12 based) TrueOS 20161215 and DragonFlyBSD 4.6.1 tested on the same Intel Core i7 6800K + MSI C236A WORKSTATION as used for the Linux workstation/server benchmarks from a few days ago. On the same exact system, TrueOS and DragonFlyBSD were both tested out-of-the-box to compare to our numbers from Clear Linux, Ubuntu 16.04, Ubuntu 16.10, CentOS 7, openSUSE Leap 42.2, and Debian Linux 8.6
Original article: http://www.phoronix.com/scan.php?page=article&item=bsd-eoy-2016&num=1
This blog by user Eric McCorckle documents his experience in running FreeBSD and Gentoo side by side. He has set up a ZFS volume on his Librem 15 notebook to run both of the open source operating systems. Follow the link below for his full story.
My Librem 15 arrived a while back. I normally prefer FreeBSD for just about everything, but I need access to a Linux OS running on the Librem platform in order to help me port over some remaining device drivers (namely the BYD mouse and screen brightness).
In order to facilitate this, I’ve installed a setup I developed a while back: that of a dual-booted FreeBSD and Gentoo Linux system living on the same ZFS volume. This article details how to achieve this setup.
Note that this article is based on the EFI bootloader. If you insist on legacy BIOS boots, you’ll need to adapt the procedure.
These two blogs by usertalks about his experience switching over to FreeBSD for desktop use, along with his thoughts on Debian Linux next to FreeBSD. He makes comparisons between the file systems, init systems, package management, and more. Read more at the links below:
After great, though slightly lacking experience with FreeBSD on the desktop, I decided to look for the “next best thing” in Linux Land. In the end I chose Debian, and for good reasons, I think. There is so much that Debian and FreeBSD have in common that it might be worth to anyone considering switching between the two.
After long hours of experimenting with various GNU/Linux distributions, I decided to return to the place I truly belong – FreeBSD. Whenever I feel tired of all of the inconsistencies in other operating systems, I go back to FreeBSD, as I know it will not let me down. It’s stable, reliable and secure thanks to its UNIX heritage. I especially like the fact that whatever I throw at FreeBSD, it never ceases to amaze me. Recently, I managed to compile pyMOL via Clang and get it to run on a non-Linux platform. Apparently, the fixes suggested by me were introduced and pyMOL compiled cleanly. I was simply overjoyed!