freebsd 14.3

R

rshad muhammad

i did make world n make kernel on freebsd 14.2 stable n noticed this.

uname -aKU
freebsd 14.3-PRERELEASE FreeBSD 14.3-PRERELEASE stable/14-ee7a874557f4 MYGEN amd64 1402505 1402505

freebsd-version -kru
14.3-PRERELEASE
14.3-PRERELEASE
14.3-PRERELEASE
 
Keep in mind that STABLE is essentially a developer snapshot, just a little less bleeding edge than CURRENT so... yah, anything can happen here.

(edit) => It's not uncommon for developer snapshots to go ahead in time. For example.. if you were to build CURRENT right now you'd get this:
Code: 
peter@bsd:/home/peter $ uname -aKU
FreeBSD bsd.intranet.lan 15.0-CURRENT FreeBSD 15.0-CURRENT #14 main-n276448-a1adefb139b3: Wed Apr 16 21:18:51 CEST 2025     root@bsd.intranet.lan:/usr/obj/usr/src/amd64.amd64/sys/HYPER-KERN amd64 1500037 1500037
peter@bsd:/home/peter $
Livin' on the edge, indeed ;)
 
ShelLuser said:
Keep in mind that STABLE is essentially a developer snapshot, just a little less bleeding edge than CURRENT so... yah, anything can happen here.

(edit) => It's not uncommon for developer snapshots to go ahead in time. For example.. if you were to build CURRENT right now you'd get this:
Code: 
peter@bsd:/home/peter $ uname -aKU
FreeBSD bsd.intranet.lan 15.0-CURRENT FreeBSD 15.0-CURRENT #14 main-n276448-a1adefb139b3: Wed Apr 16 21:18:51 CEST 2025     root@bsd.intranet.lan:/usr/obj/usr/src/amd64.amd64/sys/HYPER-KERN amd64 1500037 1500037
peter@bsd:/home/peter $
Livin' on the edge, indeed ;)
Click to expand...
i tried 15 CURRENT, the last build custom kernel today, i was not able to build or install drm-66-kmod. issue was drmn.
 
A */stable branch going from -STABLE to -PRERELEASE (and the minor version incremented) means releng/X.Y will be branched off soon. Once it's been branched off it will return to -STABLE (and keep the minor version incremented).
 
I'm setting up a semi-old machine with a KABY_LAKE i7-7700K CPU to use for 14.3 beta testing.
Im moving /home , /usr/local ,/usr/ports & /usr/src off the system SSD zroot pool to the HDD unit in the box.
this should allow to install consecutive BETA releases on to the system SSD without needing to reinstall
the Desktops and the Applications.

After installing a New Beta on the SSD I plan to re-establish the paths to the re-located directories
this should allow for installing a new Beta in less than an hour I think,

how is this type of operations usually done ?
 
drsnx60 said:
Im moving /home , /usr/local ,/usr/ports & /usr/src off the system SSD zroot pool to the HDD unit in the box.
this should allow to install consecutive BETA releases on to the system SSD without needing to reinstall
the Desktops and the Applications.
Click to expand...
If you are using ZFS and Boot Environments (BE), be careful what you do with /usr/local. By default from install /usr/local is actually part of the BE so before doing anything with it check zfs list and see if there is a separate dataset mounted at /usr/local. If it is a separate dataset then you may be ok. If not, just use bectl to create new BEs before doing BETA installs.
 
You must log in or register to reply here.
Back
Top