6 ms·

If you can, you should consider updating to 11.1 instead.

by Bino 9y ago

iamtew 9y ago
Why?
- hultner 9y ago
  One reason could be built in IPSEC (11) and NAT_T (11.1) but I see cases where people would like to stay on 10.x. I couldn't find anything about those extensions being enabled by default in 10.4.
  - Mister_Snuggles 9y ago
    This is my number one reason for moving to FreeBSD 11.1. FreeBSD 11.0 was weird because they enabled IPSEC, but did not enable NAT_T in the GENERIC kernel.
- vertex-four 9y ago
  At least partially because you only have another year of support for FreeBSD 10.x, whereas FreeBSD 11.x is expected to be supported until 2021. This includes security fixes.
  - hhw 9y ago
    11.x may supported until 2021, but 11.1 itself will only be supported up until 11.2 is released + 3 months. So if 11.2 is released before the end of July 2018, then 10.4 which has an EOL of October 31st, 2017 would actually be supported for longer. Generally speaking, more conservative users will wait at least until the xx.1 point release before switching to that major version, but if you're on the very conservative side you may want to wait until xx.2. However, there are numerous updates even between minor point releases which you could apply if any errata are discovered if you don't mind.
    - vertex-four 9y ago
      Yes, but the point of point-releases is that they're largely about maintenance and hardware support - so moving from 10.x to 11.x might take some testing, maybe rewriting some management scripts, etc, but 11.1 to 11.2 should be easier since nothing major changes about the system. Having a year's buffer to migrate means that if there are issues, you can fix them or get them fixed before 10.x EOLs and you're stuck running an unsupported OS.
    - kchoudhu 9y ago
      You're supposed to upgrade to point releases pretty much immediately.
gkya 9y ago
I guess that's kind of obvious.
- justin66 9y ago
  Nothing about FreeBSD release versioning is obvious.
  - ksec 9y ago
    If we use Windows Versioning Perspective. 10.4 = Versoin 10, Services Pack 4 11.1 = Version 11, Services Pack 1 At least that is how i think of it. Am I missing something? What isn't obvious about it?
    - ddhfdvsfji 9y ago
      Wtf is a services pack?
    - howard941 9y ago
      The 10 and 11 kernel ABIs differ
    - justin66 9y ago
      > At least that is how i think of it. Am I missing something? What isn't obvious about it? I think the number of times I've witnessed discussions over the decades regarding "which version of FreeBSD should I use?" numbers in the hundreds.
      - takeda 9y ago
        The official answer to this is to use latest stable version for any new server. That means 11.1 right now. 10.4 is intended for individuals who are still running 10.x
      - kqr 9y ago
        As far as I understand it, that is nothing more than an urban legend based on the fact that 5.0 was a terrible, rushed release and not meant for production (it was also marked as such). That mistake has not been repeated since, to my knowledge.

If you can, you should consider updating to 11.1 instead.

by Bino 9y ago

If you can, you should consider updating to 11.1 instead.

iamtew 9y ago

Why?

hultner 9y ago
One reason could be built in IPSEC (11) and NAT_T (11.1) but I see cases where people would like to stay on 10.x. I couldn't find anything about those extensions being enabled by default in 10.4.
- Mister_Snuggles 9y ago
  This is my number one reason for moving to FreeBSD 11.1. FreeBSD 11.0 was weird because they enabled IPSEC, but did not enable NAT_T in the GENERIC kernel.
vertex-four 9y ago
At least partially because you only have another year of support for FreeBSD 10.x, whereas FreeBSD 11.x is expected to be supported until 2021. This includes security fixes.
- hhw 9y ago
  11.x may supported until 2021, but 11.1 itself will only be supported up until 11.2 is released + 3 months. So if 11.2 is released before the end of July 2018, then 10.4 which has an EOL of October 31st, 2017 would actually be supported for longer. Generally speaking, more conservative users will wait at least until the xx.1 point release before switching to that major version, but if you're on the very conservative side you may want to wait until xx.2. However, there are numerous updates even between minor point releases which you could apply if any errata are discovered if you don't mind.
  - vertex-four 9y ago
    Yes, but the point of point-releases is that they're largely about maintenance and hardware support - so moving from 10.x to 11.x might take some testing, maybe rewriting some management scripts, etc, but 11.1 to 11.2 should be easier since nothing major changes about the system. Having a year's buffer to migrate means that if there are issues, you can fix them or get them fixed before 10.x EOLs and you're stuck running an unsupported OS.
  - kchoudhu 9y ago
    You're supposed to upgrade to point releases pretty much immediately.

gkya 9y ago

I guess that's kind of obvious.

justin66 9y ago
Nothing about FreeBSD release versioning is obvious.
- ksec 9y ago
  If we use Windows Versioning Perspective. 10.4 = Versoin 10, Services Pack 4 11.1 = Version 11, Services Pack 1 At least that is how i think of it. Am I missing something? What isn't obvious about it?
  - ddhfdvsfji 9y ago
    Wtf is a services pack?
  - howard941 9y ago
    The 10 and 11 kernel ABIs differ
  - justin66 9y ago
    > At least that is how i think of it. Am I missing something? What isn't obvious about it? I think the number of times I've witnessed discussions over the decades regarding "which version of FreeBSD should I use?" numbers in the hundreds.
    - takeda 9y ago
      The official answer to this is to use latest stable version for any new server. That means 11.1 right now. 10.4 is intended for individuals who are still running 10.x
    - kqr 9y ago
      As far as I understand it, that is nothing more than an urban legend based on the fact that 5.0 was a terrible, rushed release and not meant for production (it was also marked as such). That mistake has not been repeated since, to my knowledge.