Integrated by Design

The style of the blog post, with short, abrupt sentences does not captivate me. I’d like to think someone writing a book has a more interesting writing style. Or maybe LLMs have damaged me and I’m too critical of writing style now, whatever it is this doesn’t sell the book to me.

I started to read the blog post and got lost trying to shoot down all these aliens falling down from space. It's really a nice game integrated in the webpage. I was able to double my canon and even get a bigger blue laser. I wonder how much more weapon upgrades there is. Awesome game inside this blog.

No unencumbered epub, no sale.

This looks AI Slop. At first the style of the site and the cover of the book were a bit suspicious, but then digging a bit further:

- Domain was registered in February this year: https://www.whois.com/whois/vivianvoss.net

- Web archive has only a couple snapshots before this year, and it seemed to belong to an "Elite Escort": https://web.archive.org/web/20160515000000*/https://vivianvo...

- All his other domains are recently registered too, the oldest one `byvoss.tech` is from May 2025.

- GitHub has way too little projects and contributions for someone with such experience. The first project dates on the same day as the domain registration: https://github.com/VivianVossNet?tab=repositories

- As other people mentioned, too many blog posts lately (almost one a day), and a very weird writing style. Which doesn't seem at all that's because it's English as a second language. It's just plainly vague and disconnected sentences.

Here's a link to a few sample chapters https://vivianvoss.net/assets/files/integrated-by-design-pre... I enjoyed reading them - they presented a very clear arguement to select FreeBSD over Linux

I ordered the hard copy, but for those with Kindle Unlimited....it's available there.

KU is for escape not text for me, so I'll wait for the book.

This was surprisingly hard to read. Not in terms of sentence structure but in terms of coherence and meaning.

Also the book is $60 on Kindle and $80 for paperback? Who's the target audience?

The page about the earnings[0] is interesting. The Amazon share for kindle edition is higher than I expected.

[0]:https://vivianvoss.net/print/integrated-by-design

Unrelated to the article, the game on the website is very addictive )) Had to get to the top of the leaderboard.

Hardcover not available on .co.jp, shame

I have had various servers over time running FreeBSD, both physically in my home, rented bare metal servers and rented VPSes.

So I’m not exactly a newcomer to FreeBSD, but I am wondering if this book might be relevant to me anyways.

My main issue with my servers that I would like to solve better, is how to organize the file system layout and ZFS “datasets” in a better way.

I generally don’t use separate disks for system and other things. Whatever number of disks are available, anywhere from a single disk or a pair of disks up to several handfuls of disks become a zpool where both the system is installed and all my data lives too.

For example, this is the zpool setup of one physical bare metal rented server I have, consisting of ten disks all put into a single raidz3 grouping:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          raidz3-0  ONLINE       0     0     0
            ada0p3  ONLINE       0     0     0
            ada1p3  ONLINE       0     0     0
            ada3p3  ONLINE       0     0     0
            ada5p3  ONLINE       0     0     0
            ada2p3  ONLINE       0     0     0
            ada4p3  ONLINE       0     0     0
            da0p3   ONLINE       0     0     0
            da1p3   ONLINE       0     0     0
            da2p3   ONLINE       0     0     0
            da3p3   ONLINE       0     0     0

Another physical bare metal server I rent has only two disks, so I have them in a mirror setup:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada0p2  ONLINE       0     0     0
            ada1p2  ONLINE       0     0     0

This server with the mirror pool runs some actual services like a couple of websites and a PeerTube instance etc, all in separate jails.

However, in spite of the goodness of having jails it’s still a bit of a mess I’ve made, that make it somewhat difficult (time consuming) to set up a new server with a similar setup to replace it one day when the disks give up and I have to restore from backup.

In particular I have a bit of config and other files spread out in the host system itself.

I am hoping that given that this book looks to be focused in part on practical examples, that perhaps if I buy this book I can get some inspiration for how I can better set up a new server and make it so that in the future that one in turn would be quicker to move between machines.

Also, the pool on the server with the mirrored disk setup has become extremely fragmented:

    NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
    zroot  3.62T  3.18T   453G        -         -    48%    87%  1.00x    ONLINE  -

What I really would like is to have it so that one ZFS “dataset” contains only the base system as it comes from a fresh install, and to have config changes I’ve added be separately stored and somehow overlaid on top of that. While at the same time having it so that when I install updates to the system, the default config files that are updated are not written out into the overlay but instead replace what’s below in the default install. If that makes sense.

And perhaps that instead of having many pkg installs for various tools in the host system that I add a sort of management jail where I can install various tools and edit files and manage the server, if possible.

Also I am wondering if running multiple instances of PostgreSQL server each in their separate jails is better, or having a single PostgreSQL server in a single jail that all the other jails share for services I have in jails where the services use PostgreSQL.

[dead]

An interesting perspective. The tradeoffs here are genuinely complex and depend heavily on context that isn't visible from the outside. Would be curious to hear more about the failure modes encountered.