https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215143
--- Comment #13 from Jason W. Bacon <j...@freebsd.org> --- Finally got around to fully testing this. I did a full install with my custom ISO on a MacBook Pro 2,2. I'm using it right now to send this update. I then did a freebsd-update fetch install which updated the kernel and it did not cause any problems. Clearly from previous posts, "freebsd-update upgrade" can render the system unbootable, but I'm not sure what other conditions could cause problems. I don't understand the details of the boot process well enough. Might it be possible to patch the generic ISO to prevent the EFI boot path from being used on 32-bit EFI systems? Is there an easy way to fix an installation following "freebsd-update upgrade"? I'm not so concerned about this one as I prefer to do fresh installs when I upgrade. ( A little OCD about bit rot and keeping my installations pristine. ) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"