https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291562
--- Comment #1 from Barney Wolff <[email protected]> --- I have a couple of remote systems that I maintain with ssh, with no console access. The ipfw incompatibility would make 14.3->15.0 a disaster if I hadn't already seen chatter on the lists about it. Doesn't this deserve an erratum, or a warning from freebsd-update itself before installing the new kernel? Even knowing I'm left with unpleasant alternatives. I jiggered something in a local rc file to run the second freebsd-update install and then reboot, trusting that the update was successful with no interaction needed. That worked, with the amusing glitch that many installed files ended up with date 12/31/69 because on my little rpi4b systems the clock is unset until ntpd can do it. btw, why does freebsd-update not set the date/time of the files it installs to what the repo has? The alternative is to manually extract ipfw and its needed libraries, and then hope that ipfw works to install my intended firewall rules which will let me get in after the new kernel boots. I haven't dared to do that. Do you have advice on which to try? Will the pkg setup in 16 not be subject to the same sort of issues? -- You are receiving this mail because: You are the assignee for the bug.
