- (113) “Permissive licensing is wrong?” – No it’s not! (2/2)
- (114) [ ! -z ${COC} ] && exit 1
- (115) Introduction to email (pt. 1): Email basics
- (116) Introduction to email (pt. 2): Mail dialog / the “mail” command
- (117) Modern-day package requirements
- (118) Ravenports: A modern, cross-platform package solution
- (119) Ravenports: Status update and the Dragonfly case
- (120) A look beyond the BSD teacup: OmniOS installation
- (121) Exploring OmniOS in a VM (1/2)
- (122) Exploring OmniOS in a VM (2/2)
- (123) One year of flying with the Raven: Ready for the Desktop?
- (124) Ravenports explained: Why not just join XYZ?
A comprehensive answer to the people who claim that you shouldn’t be using permissive licenses and that the GPL is the only one true license. It’s written in dialog style to make it less boring to read.
My view on FreeBSD’s new COC – it doesn’t mean the end of the project but definitely is a turn in the wrong direction. What matters now is to keep cool and reject this folly in an objective way. The basic idea is not even wrong, but the details are.
A general introduction to what email is (terminology, daemons involved, etc.). The post also shows how to setup a mail test VM using vagrant and FreeBSD.
Part two of the series explores the classical mail command and talks about concepts like inbox and mbox.
This post discusses the why and what of today’s *nix package management.
An introduction into the new universal packaging system Ravenports that already runs on DragonflyBSD, FreeBSD, Linux and Solaris/Illumos
An update on Ravenports as well as a bit of background on Pkgsrc and DPorts for DragonflyBSD and how they lead to Raven.
This post is about trying out OmniOS, an Illumos distribution. It gives a little background from a *BSD perspective and details the installation process.
In this post I write about my first ever contact with the Solaris world. I cover the topics manpages, services and user management.
Part two of my OmniOS exploration is mainly about network configuration and a conclusion of my first impressions.
This post is a reflection of the Ravenports project after I’ve been involved with it for one year.
Ending the year with one more Ravenports article, this one details the reasons why Ravenports exists and what are some of its benefits over other package solutions (especially Pkgsrc).
eerielinux 