I was sad to see that in the release notes, I had not heard. I remember Kurt from the Old Days, when I went to some open houses at UUNET and attended Usenix conferences.
FreeBSD is amazing, and a major reason for that is how well it is managed. I would find it very hard to name three other open-source projects of comparable size that are so well-organized and have consistently delivered for this long. Here's a warm shoutout to the FreeBSD Foundation, as well as your reminder to donate: https://www.freebsdfoundation.org/donate/
Been running Linux servers for years. FreeBSD is what gave me back the passion to run servers.
It's such a well structured operating system. The documentation is just great and Jails are a really nice way to get lightly isolated environments to run different web services.
Thanks to all the people who make FreeBSD possible!
I hear you. TBH, most popular Linux distros feels very bloated nowadays. The other day I created a VM and there I installed FreeBSD for the first time. The process was really quick. It felt like a breath of fresh air. Much much simpler than what I had imagined. Everything felt very logical. I have thought about this before but since I already knew Linux I was hesitant to take the time to learn another Unix-like OS. But now I feel that I want to carve out some more free time to get more acquainted with FreeBSD. I’m quite sure it will pay off in the end.
TRIM has been available in FreeBSD for mounted ZFS filesystems for quite a while, since ~Sep 2012 in 10-CURRENT[1]. I believe this is just a user space command for manually TRIM'ing in cases where it doesn't have explicit filesystem support.
FreeBSD is issuing TRIM in ZFS and UFS2 for quite a while.
When I was researching the topic, I learned that how TRIM is implemented on the drives, issuing it in bulk is more efficient than individually, so perhaps that's why the tool was added? Although looking at ZFS at least it looked like it also collects blocks that supposed to be TRIMmed and issues it periodically.
Support for TRIM in ZFS, UFS (kernel), or fsck (userspace) has been in place for years, but there was no easy way to tell “TRIM all this whole device now”.
I believe it was imported so that it could be used by code-verification bits in the boot loader and exec calls. I'm pretty sure those aren't turned on by default yet, but my understanding is that Juniper uses them.
Is there a 300-page or less book that can teach practical usage of FreeBSD? Like the C book or the UNIX programming environment book. I have it installed on one of my laptops but never got around to use it.
My train of thought went "hmm, I wonder if FreeBSD would be good to use in production for running some Docker containers" and I stumbled across this https://wiki.freebsd.org/Docker
Docker became popular over FreeBSD jails the same way MySQL became popular over PostgreSQL in the 2005-ish. Not based on technical merit but because of ease of use. In case of MySQL it was a Windows installer which made for a low barrier of entry. However MySQL didn't do ACID transactions, views, etc. at that time, all things PostgreSQL had.
Similarly Docker was easy to use with images but security was a mess. The first couple of years Docker stance was actually that their container wasn't to be considered a security boundary and being able to access the host system "wasn't a bug". This in total contrast to FreeBSD jails which were always regarded as a hard boundary.
Docker in FreeBSD is not as simple as you might think. FreeBSD has a Linux ABI compatibility layer in order to be able to run Linux binaties (just like WINE is a Windows ABI compatibility layer). Docker itself, the CLI application, the API, etc. is probably the easiest part.
[+] [-] cperciva|6 years ago|reply
[+] [-] rootbear|6 years ago|reply
[+] [-] thijsvandien|6 years ago|reply
[+] [-] sebiw|6 years ago|reply
It's such a well structured operating system. The documentation is just great and Jails are a really nice way to get lightly isolated environments to run different web services.
Thanks to all the people who make FreeBSD possible!
[+] [-] cpach|6 years ago|reply
[+] [-] jandrese|6 years ago|reply
Is this replacing an older utility or is FreeBSD way behind on supporting SSDs?
[+] [-] m11r|6 years ago|reply
[1]: https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/all-ab...
[+] [-] takeda|6 years ago|reply
When I was researching the topic, I learned that how TRIM is implemented on the drives, issuing it in bulk is more efficient than individually, so perhaps that's why the tool was added? Although looking at ZFS at least it looked like it also collects blocks that supposed to be TRIMmed and issues it periodically.
[+] [-] drewg123|6 years ago|reply
[+] [-] trasz|6 years ago|reply
[+] [-] LeoPanthera|6 years ago|reply
Presumably, this utility is useful for disks that are not ZFS formatted.
[+] [-] naniwaduni|6 years ago|reply
Exciting. Is it being used for anything yet?
[+] [-] cperciva|6 years ago|reply
[+] [-] jackyb|6 years ago|reply
[+] [-] blackhaz|6 years ago|reply
[+] [-] ianai|6 years ago|reply
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/
[+] [-] MuffinFlavored|6 years ago|reply
> Docker's currently broken.
that leads to this: https://reviews.freebsd.org/D21570
[+] [-] jsiepkes|6 years ago|reply
Similarly Docker was easy to use with images but security was a mess. The first couple of years Docker stance was actually that their container wasn't to be considered a security boundary and being able to access the host system "wasn't a bug". This in total contrast to FreeBSD jails which were always regarded as a hard boundary.
Docker in FreeBSD is not as simple as you might think. FreeBSD has a Linux ABI compatibility layer in order to be able to run Linux binaties (just like WINE is a Windows ABI compatibility layer). Docker itself, the CLI application, the API, etc. is probably the easiest part.
[+] [-] kazen44|6 years ago|reply
[+] [-] gerbilly|6 years ago|reply