Stuck in a loop/vicious circle 14.4-p3 -->14.4-p4

loveydovey

loveydovey

I'm stuck in a vicious circle/loop.

#1 freebsd-update fetch + install from 14.3 -> 14.4 (shows kernel and .ko will be updated) = still showing p3 when running uname -a & freebsd-version -ukr for the kernel.

#2 Compile 14.4-p4 in a separate git checked out folder (not in /usr/src) compiles great, installs, uname -a and freebsd-version -ukr show p4 is installed.

#3 freebsed-update fetch is starting to update from p3 to p4 all over again (and doesn't update). GOTO #1

****
Note: /usr/src errors out when compiling now. I don't know how that came about and how to fix it. It did compile several months ago, now it errors out, and I just didn't invest time figuring out why, ESPECIALLY since downloading src and compiling it separately works.
 
Should I convert /usr/src to a git repo so I can pull down stuff from git? Would that jive with and hum along with freebsd-update stuff? It's just so weird that all of a sudden /usr/src doesn't compile while the separately pulled down repo does.

I converted /usr/ports to a git repo...but that doesn't have anything to do with freebsd-update stuff.
 
You're really struggling with understanding how and when the version of the kernel changes, don't you?

P4 is an issue with freebsd-update(8), has nothing to do with the kernel. So only the userland is updated to p4, the kernel isn't updated therefor stays at p3.


When you recompile the kernel from updated sources, the sys/conf/newvers.sh script determines which version the kernel string should get baked in. That's the only thing that changes, it's purely cosmetic.

Just for giggles, in your source tree[*], change BRANCH="RELEASE-p4" to BRANCH="DOVEY-p1", then compile and install the kernel.

loveydovey said:
in a separate git checked out folder (not in /usr/src)
Click to expand...
[*] Source tree can live anywhere, it's not required to be compiled from /usr/src/.
 
SirDice said:
When you recompile the kernel from updated sources, the sys/conf/newvers.sh script determines which version the kernel string should get baked in. That's the only thing that changes, it's purely cosmetic.
Click to expand...
Then why is freebsd-update fetch is telling me to update to p4 again, even though I *am* on p4 already - both userland and kernel? sys/conf/newvers.sh says p4 too.
 
loveydovey said:
Then why is freebsd-update fetch is telling me to update to p4 again
Click to expand...
It shouldn't. More often than not the message is incorrectly interpreted. But there have been genuine issues in the past.
loveydovey said:
sys/conf/newvers.sh says p4 too.
Click to expand...
freebsd-update(8) updates the source code (if you have it installed). That file not only determines the version of the kernel, it applies to the entire system. The BRANCH in that file was bumped, freebsd-version(8) and whatever was wrong in the userland gets recompiled, then distributed through freebsd-update(8). Interesting tidbit, the userland version is baked in the freebsd-version(8) executable. It's not some variable that's dynamically read from somewhere on the system.
 
You must log in or register to reply here.
Back
Top