• Migration guide?

    From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Thu Nov 5 16:04:44 2026
    From Newsgroup: muc.lists.freebsd.stable

    Hi, all,

    With the 15.2 release cycle starting, I'm looking at starting to
    migrate from 14.5 to 15.2 this winter. Has anyone written a good
    guide to changes between 14 and 15 that would be helpful? I'm
    particularly interested in features and non-default build options that
    may have changed or been removed between the two branches. The
    release notes aren't really great on this (they don't really describe
    the differences between different -stable branches except when a .0
    release comes out).

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Doug Hardie@bc979@lafn.org to muc.lists.freebsd.stable on Thu Nov 5 13:28:47 2026
    From Newsgroup: muc.lists.freebsd.stable

    A good place to start is /usr/src/UPDATING. There is a lot of info there on changes since 14.0. The big change I see is pkgbase. There are instructions available on how to convert to it, but not much on how to maintain it afterwards. The list of available packages is elusive. I don't have enough info to make the change.
    -- Doug
    On Nov 5, 2026, at 13:04, Garrett Wollman <wollman@bimajority.org> wrote:

    Hi, all,

    With the 15.2 release cycle starting, I'm looking at starting to
    migrate from 14.5 to 15.2 this winter. Has anyone written a good
    guide to changes between 14 and 15 that would be helpful? I'm
    particularly interested in features and non-default build options that
    may have changed or been removed between the two branches. The
    release notes aren't really great on this (they don't really describe
    the differences between different -stable branches except when a .0
    release comes out).

    -GAWollman


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Thu Nov 5 17:18:43 2026
    From Newsgroup: muc.lists.freebsd.stable

    <<On Thu, 5 Nov 2026 13:28:47 -0800, Doug Hardie <bc979@lafn.org> said:

    A good place to start is /usr/src/UPDATING. There is a lot of info
    there on changes since 14.0. The big change I see is pkgbase.
    There are instructions available on how to convert to it, but not
    much on how to maintain it afterwards. The list of available
    packages is elusive. I don't have enough info to make the change.

    That really has the same problem as the release notes: it shows
    changes between 14.x and 15.x interspersed with changes to 15.x that
    were later merged to 14.x anyway.

    I may end up having to write something myself just to get some clarity
    for my upcoming upgrade cycle, but I was hoping that someone else had
    already done this work.

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.stable on Thu Nov 5 20:15:04 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/5/26 13:04, Garrett Wollman wrote:
    Hi, all,

    With the 15.2 release cycle starting, I'm looking at starting to
    migrate from 14.5 to 15.2 this winter. Has anyone written a good
    guide to changes between 14 and 15 that would be helpful?

    Context matters here. There is not a single unique migration technique.

    Starting with the "old" side of things:

    ) Do you update 14.5 via the experimental pkgbase that more recent 14.*
    have? (Only 15.* releases have officially supported by release
    engineering pkgbase releases.)

    vs.

    ) Do you use freebsd-update to update 14.5?

    vs.

    ) Do you do something else, like building from source code? What way?

    As for the "new" side of things:

    ) Going forward, do you want to update 15.2 via pkgbase?

    vs.

    ) Going forward, do you want to use freebsd-update to update 15.2?

    vs.

    ) Going forward, do you want some other way of doing 15.2 updates?
    What way?

    Instructions/notes for the various combinations of "old" vs. "new" are
    going to vary and some combinations might not be reasonable at all,
    short of starting over. Some would have no official process, such as
    starting from an experimental vintage of pkgbase use as the context.

    I'm
    particularly interested in features and non-default build options that
    may have changed or been removed between the two branches.

    That wording suggests that you are not intending on using official
    distribution materials for 15.2 ("non-default build options") and you
    may not be for 14.5 either.

    Is your compatibility interest:

    ) Limited to World (User Space) compatibility issues?

    ) Interested in what misc/compat14x (and before) provide as compatible
    old library and binary versions if such is installed? (That is one
    category of what-areas-changed information.)

    ) Do you have specialized kernel modules involved might break that you
    are worried about? (Internal kernel interfaces are more subject to
    incompatible changes.)

    Is this an amd64 context? aarch64? Something else? Booting i386 is not supported by releng/15.* --same for booting powerpc (32-bit) and booting
    armv6. lib32, chroot, and jails would still work in a matching 64 bit
    context as before. I'm guessing you are not using armv7, powerpc64, powerpc64le, or riscv64 but I do not really know your context. Those 4
    are Tier 2 in 15.* and so should still be bootable.

    The
    release notes aren't really great on this (they don't really describe
    the differences between different -stable branches except when a .0
    release comes out).

    -GAWollman




    In general, you likely need to specify more about the context you would
    be dealing with (old and new). You are not likely to get answers
    covering all possible 14.5 to 15.2 possibilities.
    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Thu Nov 5 23:25:17 2026
    From Newsgroup: muc.lists.freebsd.stable

    <<On Thu, 5 Nov 2026 20:15:04 -0800, Mark Millard <marklmi@yahoo.com> said:

    In general, you likely need to specify more about the context you would
    be dealing with (old and new). You are not likely to get answers
    covering all possible 14.5 to 15.2 possibilities.

    This was a really unhelpful, not to mention condescending, reply to
    someone who was literally on the first core team and has been involved
    in FreeBSD since before it was called that.

    *Someone* out there knows what system build options were changed or
    removed and what defaults were altered, or maybe a collectivity of
    someones, so that I don't have to read through a year's worth of `git
    log` to figure out how to adapt my configurations to the new OS. But
    if that's what I have to do, that's what I'll do.

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.stable on Thu Nov 5 21:26:45 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/5/26 20:25, Garrett Wollman wrote:
    <<On Thu, 5 Nov 2026 20:15:04 -0800, Mark Millard <marklmi@yahoo.com> said:

    In general, you likely need to specify more about the context you would
    be dealing with (old and new). You are not likely to get answers
    covering all possible 14.5 to 15.2 possibilities.

    This was a really unhelpful, not to mention condescending, reply to
    someone who was literally on the first core team and has been involved
    in FreeBSD since before it was called that.

    Sorry. My knowledge base is way to narrow, I'm afraid.


    *Someone* out there knows what system build options were changed or
    removed and what defaults were altered, or maybe a collectivity of
    someones, so that I don't have to read through a year's worth of `git
    log` to figure out how to adapt my configurations to the new OS. But
    if that's what I have to do, that's what I'll do.

    -GAWollman



    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=@des@FreeBSD.org to muc.lists.freebsd.stable on Fri Nov 6 16:35:33 2026
    From Newsgroup: muc.lists.freebsd.stable

    Garrett Wollman <wollman@bimajority.org> writes:
    With the 15.2 release cycle starting, I'm looking at starting to
    migrate from 14.5 to 15.2 this winter. Has anyone written a good
    guide to changes between 14 and 15 that would be helpful? I'm
    particularly interested in features and non-default build options that
    may have changed or been removed between the two branches.
    The most noticeable change in terms of build options is that CLEAN now
    defaults to off, meaning incremental builds are the default. PROFILE,
    which was default-off in 14, is no longer supported. The logic that let
    you use the old NO_FOO names for certain build options (including CLEAN
    and PROFILE) has been removed, so only WITHOUT_FOO is now supported. LLVM_BINUTILS now defaults to on, which means we now default to the LLVM versions of tools such as ar(1), nm(1), ranlib(1), strip(1) etc. GH_BC
    has been dropped, so you no longer have the option of using OpenBSD's
    bc(1) / dc(1) instead of Gavin Howard's. INIT_ALL_PATTERN and
    INIT_ALL_ZERO have been merged into INIT_ALL which can be set to rCLnonerCY (the default), rCLpatternrCY, or rCLzerorCY.
    In terms of features, it's really hard to answer. Most prominently,
    packaged base has graduated from rCLexperimentalrCY to rCLtechnology previewrCY,
    which means it works and is close to its final form but is still missing
    some polish and tooling. You still don't have to switch if you don't
    want to (and since you asked about build options, I assume you're
    building from source, so it does not really affect you). We no longer
    ship ftpd, so if you were using that you'll have to pick one from ports.
    If you're using Kerberos, we've switched from an outdated Heimdal to a
    recent MIT. A lot of work has gone into hardware support, particularly
    wifi and graphics, but presumably your kit is already supported.
    Hope this helps,
    DES
    --
    Dag-Erling Sm|+rgrav - des@FreeBSD.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2