david_chisnall

@[email protected] Oh, does that boot now? It didn’t last time I tried: without /etc mounted, you can’t mount other filesystems. I guess the kernel is doing slightly more for ZFS mounts on boot than it used to (doesn’t work for non-ZFS systems because fstab is in /etc, it used to also not work for ZFS, I think, because something in rc.d was needed to mount additional filesystems).

@[email protected] @[email protected] There really isn’t a reason to use UFS unless your machine has less than 64 MiB of RAM. We should remove it from the installer. If you’re not building an appliance image (in which case you won’t use the installer), UFS is almost certainly the wrong tool for the job.

@[email protected] @[email protected] Yes, the problem is that this will give changes for the entire boot environment (see problem previously mentioned) when you actually just want config file changes and rollback.

@[email protected] I think 1-3 are covered by freebsd-update IDS. 4 would be nice to add.

In my ideal world, we'd separate out the bits in /etc that users touch from the ones that are provided by the system and allow /etc to be a separate ZFS dataset. Unfortunately, the lack of this separation means /etc doesn't get mounted if you try because the scripts that mount all of the non-root ZFS datasets are in /etc.

@[email protected] Does this mean that you can't finish setting up a Windows machine without an Internet connection? That's going to cause flashbacks for a lot of us who remember installing XP during Slammer and having the new install compromised before you could even try running Windows Update, so needed to install, log in, and then install updates from a CD-R before you connected the network cable.

@[email protected] If critical infrastructure is vulnerable to attacks by teenagers, I’m sure it will be totally fine against a nation-state adversary.