https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291562
--- Comment #3 from Barney Wolff <[email protected]> --- Certainly belongs in relnotes, but since this issue has the potential to essentially brick systems unless or until console access can be arranged, something more prominent seems to me to be appropriate. I can understand and agree with the fbsd approach that requires user interaction to complete a major upgrade. But as a macOS user also I greatly appreciate the ability to just click ok and walk away, and come back to an upgraded system. Is there some scenario where an admin would want/need to do anything after the first reboot, before running freebsd-update install again to install the world and then reboot once more? As a safety net, that first boot could be done as a boot-once, with automatic fallback to the previous kernel if for some reason the new kernel fails to boot successfully. There will always be some failure mode where that doesn't work, but that might decrease the incidence of disaster. Oh, and just to state the obvious, turning on default-to-accept in sysctl.conf, even temporarily, is not acceptable on an Internet-connected system that's not behind a firewall. I'm not up to speed on pkgbase. Does that solve this issue? -- You are receiving this mail because: You are the assignee for the bug.
