• Re: FreeBSD 15.2-BETA1 Now Available

    From vermaden@vermaden@interia.pl to muc.lists.freebsd.stable on Thu Nov 12 16:07:53 2026
    From Newsgroup: muc.lists.freebsd.stable

    This is a multi-part message in MIME format. --------------CPWpSqLR92v58vpMwU1LXvRl
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit

    Hi,

    On 11/12/26 7:52 AM, Mark Millard wrote:
    for updating either kind of system!
    Yes its possible - but I while pkgbase-update(8) does

    everything in one step + reboot
    Any update/upgrade technique that does not reboot into the new kernel
    before having some new world code become active risks the new world code
    used failing for lack of kernel updates/upgrades it depends on.

    It the same reason that the source upgrade document has that reboot
    between the 2, the instructions being intended to allow for UFS. Nothing about pkgbase of itself removes the technical issue.


    If You first create new ZFS BE and then do the upgrade

    inside - I do not see any 'risk' here - You are basically

    replacing or extracting new files into that ZFS BE. In

    the next step You 'activate' that ZFS BE and reboot into

    it. It was possible even with freebsd-update(8) command

    as shown for example below and its possible with PKGBASE:

    https://vermaden.wordpress.com/2021/02/23/upgrade-freebsd-with-zfs-boot-environments/



    Of course, UFS contexts are more constrained by not having alternate
    boot environments as a way to not run the newly installed world at
    all until rebooting after the world is installed.

    While I use a ZFS system, I use a lot more UFS systems. (It is a
    deliberate mix.)



    On UFS You can use UFS Boot Environments - they work slightly

    different but the end results is mostly the same - even on ARM.

    Details here:

    https://vermaden.wordpress.com/2021/04/02/ufs-boot-environments/

    https://vermaden.wordpress.com/2021/04/05/ufs-boot-environments-for-arm/


    Regards,

    vermaden

    --------------CPWpSqLR92v58vpMwU1LXvRl
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: 7bit

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <p><font face="Ubuntu">Hi,</font></p>
    <div class="moz-cite-prefix">On 11/12/26 7:52 AM, Mark Millard
    wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:b1f62a02-9068-48c6-9efd-6ed03640e026@yahoo.com">
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">
    </pre>
    <blockquote type="cite">
    <pre wrap="" class="moz-quote-pre">for updating either kind of system!
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    Yes its possible - but I while pkgbase-update(8) does

    everything in one step + reboot
    </pre>
    </blockquote>
    <pre wrap="" class="moz-quote-pre">
    Any update/upgrade technique that does not reboot into the new kernel
    before having some new world code become active risks the new world code
    used failing for lack of kernel updates/upgrades it depends on.

    It the same reason that the source upgrade document has that reboot
    between the 2, the instructions being intended to allow for UFS. Nothing
    about pkgbase of itself removes the technical issue.</pre>
    </blockquote>
    <p><br>
    If You first create new ZFS BE and then do the upgrade<br>
    <br>
    inside - I do not see any 'risk' here - You are basically<br>
    <br>
    replacing or extracting new files into that ZFS BE. In<br>
    <br>
    the next step You 'activate' that ZFS BE and reboot into<br>
    <br>
    it. It was possible even with freebsd-update(8) command<br>
    <br>
    as shown for example below and its possible with PKGBASE:<br>
    <br>
    <a class="moz-txt-link-freetext" href="https://vermaden.wordpress.com/2021/02/23/upgrade-freebsd-with-zfs-boot-environments/">https://vermaden.wordpress.com/2021/02/23/upgrade-freebsd-with-zfs-boot-environments/</a><br>
    <br>
    <br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
    cite="mid:b1f62a02-9068-48c6-9efd-6ed03640e026@yahoo.com">
    <pre wrap="" class="moz-quote-pre">Of course, UFS contexts are more constrained by not having alternate
    boot environments as a way to not run the newly installed world at
    all until rebooting after the world is installed.

    While I use a ZFS system, I use a lot more UFS systems. (It is a
    deliberate mix.)</pre>
    </blockquote>
    <p><br>
    </p>
    <p><br>
    On UFS You can use UFS Boot Environments - they work slightly</p>
    <p>different but the end results is mostly the same - even on ARM.</p>
    <p>Details here:</p>
    <p><a class="moz-txt-link-freetext" href="https://vermaden.wordpress.com/2021/04/02/ufs-boot-environments/">https://vermaden.wordpress.com/2021/04/02/ufs-boot-environments/</a></p>
    <p><a class="moz-txt-link-freetext" href="https://vermaden.wordpress.com/2021/04/05/ufs-boot-environments-for-arm/">https://vermaden.wordpress.com/2021/04/05/ufs-boot-environments-for-arm/</a><br>
    <br>
    </p>
    <p><br>
    </p>
    <p>Regards,</p>
    <p>vermaden</p>
    </body>
    </html>

    --------------CPWpSqLR92v58vpMwU1LXvRl--


    --
    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 12 08:00:33 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/12/26 07:07, vermaden wrote:
    Hi,

    On 11/12/26 7:52 AM, Mark Millard wrote:
    for updating either kind of system!
    Yes its possible - but I while pkgbase-update(8) does

    everything in one step + reboot
    Any update/upgrade technique that does not reboot into the new kernel
    before having some new world code become active risks the new world code
    used failing for lack of kernel updates/upgrades it depends on.

    It the same reason that the source upgrade document has that reboot
    between the 2, the instructions being intended to allow for UFS. Nothing
    about pkgbase of itself removes the technical issue.


    If You first create new ZFS BE and then do the upgrade

    inside - I do not see any 'risk' here - You are basically

    replacing or extracting new files into that ZFS BE. In

    the next step You 'activate' that ZFS BE and reboot into

    it. It was possible even with freebsd-update(8) command

    as shown for example below and its possible with PKGBASE:

    https://vermaden.wordpress.com/2021/02/23/upgrade-freebsd-with-zfs-boot- environments/

    It is certainly true that appropriate use of ZFS BE's can avoid
    executing new world code with the old kernel despite having only one reboot.




    Of course, UFS contexts are more constrained by not having alternate
    boot environments as a way to not run the newly installed world at
    all until rebooting after the world is installed.

    While I use a ZFS system, I use a lot more UFS systems. (It is a
    deliberate mix.)



    On UFS You can use UFS Boot Environments - they work slightly

    different but the end results is mostly the same - even on ARM.

    Details here:

    https://vermaden.wordpress.com/2021/04/02/ufs-boot-environments/

    https://vermaden.wordpress.com/2021/04/05/ufs-boot-environments-for-arm/

    I do not know how common it is for folks to use your UFS technique. I
    have only more classical UFS contexts, deliberately following more
    classical upgrade sequences.

    The standard images for the few small board computers that get such are
    not set up for your UFS technique and pkgbasify does not convert such to
    a context with your technique.

    Not that such would matter to folks wanting to use your technique and
    are willing to manually set up for it.



    Regards,

    vermaden

    --
    ===
    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 John D Groenveld@groenveld@acm.org to muc.lists.freebsd.stable on Thu Nov 12 11:09:17 2026
    From Newsgroup: muc.lists.freebsd.stable

    In message <04f8bdff-3ab3-466b-acec-99b738692c13@yahoo.com>, Mark Millard write s:
    It is certainly true that appropriate use of ZFS BE's can avoid
    executing new world code with the old kernel despite having only one reboot. When/how does pkg-post-install code get invoked? <URL:https://docs.freebsd.org/en/books/porters-handbook/pkg-files/>
    John
    groenveld@acm.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
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.stable on Thu Nov 12 09:04:56 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/12/26 08:09, John D Groenveld wrote:
    In message <04f8bdff-3ab3-466b-acec-99b738692c13@yahoo.com>, Mark Millard write
    s:
    It is certainly true that appropriate use of ZFS BE's can avoid
    executing new world code with the old kernel despite having only one reboot.

    When/how does pkg-post-install code get invoked? <URL:https://docs.freebsd.org/en/books/porters-handbook/pkg-files/>

    Good question: Are such scripts are deferred to after the reboot or not.
    If not, does the procedure in use has them executing via a chroot into
    the BE being updated --vs.: using the live soon-to-be-old BE. Not that
    such a chroot would deal with old kernel vs. new world code execution
    issues absent deferral.

    Sorry for the incompleteness.

    I also implicitly assumed the FreeBSD OS upgrade was via, say,
    -rFreeBSD-base (so: just pkgbase) so that port-packages would not be
    involved prior to the reboot into new kernel and world combination.


    John
    groenveld@acm.org


    --
    ===
    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 vermaden@vermaden@interia.pl to muc.lists.freebsd.stable on Sun Nov 15 23:59:56 2026
    From Newsgroup: muc.lists.freebsd.stable

    Hi,

    Checking how my UFS context would be handled: fails.

    For Reference:

    # mount
    /dev/gpt/PBaseUFS on / (ufs, NFS exported, local, noatime, soft-updates) devfs on /dev (devfs)
    /dev/gpt/PBaseEFI on /boot/efi (msdosfs, local, noatime)

    # mount | awk '/ \/ / {print $1}'
    /dev/gpt/PBaseUFS

    # mount | awk '/ \/ / {print $1}' | grep -q '^/dev/label' 1> /dev/null 2> /dev/null
    #

    # mount | awk '/ \/ / {print $1}' | grep -o -E '[a-z]+[0-9]+' | head -1
    #

    So it looks like the UFS handling in my context would fail in:

    . . .

    # FIND SYSTEM ROOT
    BOOT_ROOT=$( mount | awk '/ \/ / {print $1}' )

    # CHECK IF WE HAVE ZFS OR UFS SYSTEM INSTALLATION
    if echo "${BOOT_ROOT}" | grep -q '^/' 1> /dev/null 2> /dev/null
    then

    echo "INFO: detected UFS based FreeBSD installation"

    # UFS DETECT glabel(8) LABEL
    if echo "${BOOT_ROOT}" | grep -q '^/dev/label' 1> /dev/null 2> /dev/null
    then

    # UFS ON glabel(8) DEVICE
    BOOT_LABEL=$( echo "${BOOT_ROOT}" | sed -e s./dev/..g )
    BOOT_DISK=$( glabel status | grep "${BOOT_LABEL}" | awk '{print $NF}' )
    BOOT_DISK=$( echo "${BOOT_DISK}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    else

    # UFS RAW DISK DEVICE
    BOOT_DISK=$( echo "${BOOT_ROOT}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    fi

    else

    . . .


    There could be /dev/ufs/ with ufs file system labels in use, if I
    remember right, not that I have such.

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


    I tested pkgbase(8) against all possible 'Auto' options in bsdinstall(8) command - like 'Auto (ZFS)' and 'Auto (UFS)'. Is it possible to do such install as You have with 'Auto (UFS)' or its purely custom command by command FreeBSD installation?

    To be honest - I also plan to 'support' these 'custom' installations - its just I have 'access' to such systems only if someone 'shares' their setup - like You - so I (probably not today) will look into command outputs You provided - thank You for that - and plan to add needed changes to pkgbase(8) tool.

    Regards,
    vermaden



    --
    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 Sun Nov 15 16:19:52 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/15/26 14:59, vermaden wrote:
    Hi,

    Checking how my UFS context would be handled: fails.

    For Reference:

    # mount
    /dev/gpt/PBaseUFS on / (ufs, NFS exported, local, noatime, soft-updates)
    devfs on /dev (devfs)
    /dev/gpt/PBaseEFI on /boot/efi (msdosfs, local, noatime)

    # mount | awk '/ \/ / {print $1}'
    /dev/gpt/PBaseUFS

    # mount | awk '/ \/ / {print $1}' | grep -q '^/dev/label' 1> /dev/null 2> /dev/null
    #

    # mount | awk '/ \/ / {print $1}' | grep -o -E '[a-z]+[0-9]+' | head -1
    #

    So it looks like the UFS handling in my context would fail in:

    . . .

    # FIND SYSTEM ROOT
    BOOT_ROOT=$( mount | awk '/ \/ / {print $1}' )

    # CHECK IF WE HAVE ZFS OR UFS SYSTEM INSTALLATION
    if echo "${BOOT_ROOT}" | grep -q '^/' 1> /dev/null 2> /dev/null
    then

    echo "INFO: detected UFS based FreeBSD installation"

    # UFS DETECT glabel(8) LABEL
    if echo "${BOOT_ROOT}" | grep -q '^/dev/label' 1> /dev/null 2> /dev/null >> then

    # UFS ON glabel(8) DEVICE
    BOOT_LABEL=$( echo "${BOOT_ROOT}" | sed -e s./dev/..g )
    BOOT_DISK=$( glabel status | grep "${BOOT_LABEL}" | awk '{print $NF}' )
    BOOT_DISK=$( echo "${BOOT_DISK}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    else

    # UFS RAW DISK DEVICE
    BOOT_DISK=$( echo "${BOOT_ROOT}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    fi

    else

    . . .


    There could be /dev/ufs/ with ufs file system labels in use, if I
    remember right, not that I have such.

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


    I tested pkgbase(8) against all possible 'Auto' options in bsdinstall(8) command - like 'Auto (ZFS)' and 'Auto (UFS)'. Is it possible to do such install as You have with 'Auto (UFS)' or its purely custom command by command FreeBSD installation?

    To be honest - I also plan to 'support' these 'custom' installations - its just I have 'access' to such systems only if someone 'shares' their setup - like You - so I (probably not today) will look into command outputs You provided - thank You for that - and plan to add needed changes to pkgbase(8) tool.

    Regards,
    vermaden




    Official arm small board computer images use ufs labels (but are not
    pkgbase generated yet as far as I know): pkgbasify use would likely be
    needed to convert.

    For reference:

    /usr/src/release/tools/arm.subr: echo "/dev/ufs/rootfs / ufs rw 1 1" \


    Last I knew, bsdinstall did not attempt to deal with arm small board
    computers and the like directly: For example: no U-Boot. Or things like
    the RPi* firmware related files. These are from the ports tree, not the
    base system. (There have been recent efforts associated with the .efi
    loader files that FreeBSD does produce of itself.)

    Another result is that these sorts of contexts tend to have more manual configuration when they are not from release/snapshot images.


    There are also other examples of gpt and ufs and iso9660 labels (that
    may not be for contexts your tools would be used with but are official contexts):

    /usr/src/release/tools/vmimage.subr:ROOTLABEL="gpt" /usr/src/release/tools/vmimage.subr: ROOTLABEL="ufs" /usr/src/release/tools/vmimage.subr: echo "/dev/${ROOTLABEL}/rootfs /
    ${VMFS} rw,noatime 1 1" \ /usr/src/release/tools/vmimage.subr: echo "/dev/${ROOTLABEL}/efiboot0
    /boot/efi msdosfs rw 2 2" \

    and:

    /usr/src/release/amd64/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/amd64/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"
    /usr/src/release/arm64/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/arm64/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"
    /usr/src/release/i386/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/i386/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"
    /usr/src/release/powerpc/mkisoimages.sh: echo FreeBSD Install=\'/boot/kernel/kernel
    vfs.root.mountfrom=cd9660:/dev/iso9660/$LABEL\' >
    "$BASEBITSDIR/etc/kboot.conf"
    /usr/src/release/powerpc/mkisoimages.sh:echo "/dev/iso9660/$LABEL /
    cd9660 ro 0 0" > "$BASEBITSDIR/etc/fstab" /usr/src/release/riscv/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/riscv/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"
    --
    ===
    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 Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.stable on Sun Nov 15 16:50:26 2026
    From Newsgroup: muc.lists.freebsd.stable

    On 11/15/26 16:19, Mark Millard wrote:
    On 11/15/26 14:59, vermaden wrote:
    Hi,

    Checking how my UFS context would be handled: fails.

    For Reference:

    # mount
    /dev/gpt/PBaseUFS on / (ufs, NFS exported, local, noatime, soft-updates) >>> devfs on /dev (devfs)
    /dev/gpt/PBaseEFI on /boot/efi (msdosfs, local, noatime)

    # mount | awk '/ \/ / {print $1}'
    /dev/gpt/PBaseUFS

    # mount | awk '/ \/ / {print $1}' | grep -q '^/dev/label' 1> /dev/null 2> /dev/null
    #

    # mount | awk '/ \/ / {print $1}' | grep -o -E '[a-z]+[0-9]+' | head -1
    #

    So it looks like the UFS handling in my context would fail in:

    . . .

    # FIND SYSTEM ROOT
    BOOT_ROOT=$( mount | awk '/ \/ / {print $1}' )

    # CHECK IF WE HAVE ZFS OR UFS SYSTEM INSTALLATION
    if echo "${BOOT_ROOT}" | grep -q '^/' 1> /dev/null 2> /dev/null
    then

    echo "INFO: detected UFS based FreeBSD installation"

    # UFS DETECT glabel(8) LABEL
    if echo "${BOOT_ROOT}" | grep -q '^/dev/label' 1> /dev/null 2> /dev/null
    then

    # UFS ON glabel(8) DEVICE
    BOOT_LABEL=$( echo "${BOOT_ROOT}" | sed -e s./dev/..g )
    BOOT_DISK=$( glabel status | grep "${BOOT_LABEL}" | awk '{print $NF}' )
    BOOT_DISK=$( echo "${BOOT_DISK}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    else

    # UFS RAW DISK DEVICE
    BOOT_DISK=$( echo "${BOOT_ROOT}" | grep -o -E '[a-z]+[0-9]+' | head -1 )

    fi

    else

    . . .


    There could be /dev/ufs/ with ufs file system labels in use, if I
    remember right, not that I have such.

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


    I tested pkgbase(8) against all possible 'Auto' options in bsdinstall(8) command - like 'Auto (ZFS)' and 'Auto (UFS)'. Is it possible to do such install as You have with 'Auto (UFS)' or its purely custom command by command FreeBSD installation?

    To be honest - I also plan to 'support' these 'custom' installations - its just I have 'access' to such systems only if someone 'shares' their setup - like You - so I (probably not today) will look into command outputs You provided - thank You for that - and plan to add needed changes to pkgbase(8) tool.

    Regards,
    vermaden




    Official arm small board computer images use ufs labels (but are not
    pkgbase generated yet as far as I know): pkgbasify use would likely be needed to convert.

    For reference:

    /usr/src/release/tools/arm.subr: echo "/dev/ufs/rootfs / ufs rw 1 1" \


    Last I knew, bsdinstall did not attempt to deal with arm small board computers and the like directly: For example: no U-Boot. Or things like
    the RPi* firmware related files. These are from the ports tree, not the
    base system. (There have been recent efforts associated with the .efi
    loader files that FreeBSD does produce of itself.)

    Another result is that these sorts of contexts tend to have more manual configuration when they are not from release/snapshot images.


    There are also other examples of gpt and ufs and iso9660 labels (that
    may not be for contexts your tools would be used with but are official contexts):

    /usr/src/release/tools/vmimage.subr:ROOTLABEL="gpt" /usr/src/release/tools/vmimage.subr: ROOTLABEL="ufs" /usr/src/release/tools/vmimage.subr: echo "/dev/${ROOTLABEL}/rootfs /
    ${VMFS} rw,noatime 1 1" \ /usr/src/release/tools/vmimage.subr: echo "/dev/${ROOTLABEL}/efiboot0
    /boot/efi msdosfs rw 2 2" \

    and:

    /usr/src/release/amd64/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/amd64/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab" /usr/src/release/arm64/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/arm64/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab" /usr/src/release/i386/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/i386/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"
    /usr/src/release/powerpc/mkisoimages.sh: echo FreeBSD Install=\'/boot/kernel/kernel
    vfs.root.mountfrom=cd9660:/dev/iso9660/$LABEL\' > "$BASEBITSDIR/etc/kboot.conf"
    /usr/src/release/powerpc/mkisoimages.sh:echo "/dev/iso9660/$LABEL /
    cd9660 ro 0 0" > "$BASEBITSDIR/etc/fstab" /usr/src/release/riscv/make-memstick.sh:echo '/dev/ufs/FreeBSD_Install /
    ufs ro,noatime 1 1' > ${BASEBITSDIR}/etc/fstab /usr/src/release/riscv/mkisoimages.sh:echo "/dev/iso9660/$LABEL / cd9660
    ro 0 0" > "$BASEBITSDIR/etc/fstab"



    I expect my ZFS context may not be as currently expected as well:

    # zpool status -PL zoptb | less
    pool: zoptb
    state: ONLINE
    scan: scrub repaired 0B in 00:00:54 with 0 errors on Mon May 5
    23:40:50 2025
    config:

    NAME STATE READ WRITE CKSUM
    zoptb ONLINE 0 0 0
    /dev/gpt/OptBzfs ONLINE 0 0 0

    errors: No known data errors

    (so: /dev/gpt/NAME use) vs. the likes of:

    echo "${BOOT_DISK}" | awk '{print $1}' | sed -e 's.p[0-9]*$..' | tr '\n' ' '

    Imagine alternate NAME's after gpt/ that might have a suffix matching:
    p[0-9]*$ vs. ones that do not.
    --
    ===
    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