5 ms·

Well, if you have auto-updates configured, it would be an easy mistake to make. I have, for example, installed packages and had them go missing due to this. B

Well, if you have auto-updates configured, it would be an easy mistake to make. I have, for example, installed packages and had them go missing due to this. But I'd like an "i'm aware of the risks, let me update quickly" option. The main reason I run TrueOS rather than just FreeBSD is for the boot environments. I've been screwed too much by dependency issues on port/pkg upgrades and left without something critical too many times, and the bootadm thing is the perfect solution, as you always have a working fallback.

craftkiller 10y ago
Doesn't FreeBSD also have beadm? Is there something wrong with FreeBSD's beadm? Not trying to be accusatory, its an honest question because I haven't looked much into beadm but I was planning on setting it up on my FreeBSD boxes this year and knowledge of any shortcomings you've already hit would save me the trouble.
- zvol 10y ago
  FreeBSD's beadm implementation is really nice now too, especially with its recent integration into the bootloader.
  - drewg123 10y ago
    Wow, cool! I missed this.. One of the things I dislike about TrueOS is how it uses grub for beadm management. I think I may just switch back to vanilla FreeBSD.
    - JdeBP 10y ago
      The last that I read, TrueOS was back to defaulting to the FreeBSD boot loader.
X86BSD 10y ago
That I get. That's always usually been the FreeBSD way(tm). Set a knob, sysctl, something that allows you to have that behavior if you need it. It's kind of odd that is not the case here. Also FreeBSD supports boot environments now, as well as selecting them from the loader menu if you haven't used it in a while. But reading the TrueOS website makes me think I should give it another go soon, it has some nice features. Even the Pico version seems interesting.