14.3 to 15.0

fernandel

fernandel

My question to upgrade release 14.3 to 15 is if is /usr/loca/etc/pkg/repos/Freebsd.conf
where are my settings on 14.3 are:
Code: 
FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
and loaders-update is the same?

Thank you.
 
  • Thanks
Reactions: mro
Remove everything from each entry and only set the url (and perhaps leave enabled in there for convenience).

Then once you are done with the base OS upgrade, rename FreeBSD to FreeBSD-ports, and FreeBSD-kmods to FreeBSD-ports-kmods.
 
Once 15.0-RELEASE will be installed you will have this in /etc/pkg/FreeBSD.conf:
Code: 
FreeBSD-ports: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-ports-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_quarterly_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-base: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkgbase-${VERSION_MAJOR}",
  enabled: no
}

Look at the repos names, they have all changed.
It means that if you want to stay in the latest repos, you have to modify your file /usr/local/etc/pkg/repos/Freebsd.conf as this:
Code: 
FreeBSD-ports: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"
}
FreeBSD-ports-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}"
}

Do this before to run pkg upgrade in order to finalize the 15.0-RELEASE installation (after what you can remove the old libs). It's advised to pkg bootstrap -f before to upgrade packages, but it's not always mandatory.

Concerning loaders-update, you can use whatever version. It's just a sh script. The last version 1.2.2 has the code that allows to search for aliases in the /dev tree for scanned disks. IIRC, you had a problem with that once.
 
scottro said:
I'm gonna spam my own page on this https://srobb.net/fbsd14_15.html
Click to expand...
Unless I'm mistaken, fernandel isn't using pkgbase. He just wants to upgrade a system from 14.3 to 15 with freebsd-update.

It's time to look at pkgbase. It's what I'm doing with several VMs and I'm writting a new set of jail management scripts that use exclusively pkgbase.

But, frankly, it's not time yet to convert an existing system that you use daily as a server or even as a desktop. My point is that pkgbase isn't stable enough for the moment.
 
Emrion said:
Unless I'm mistaken, fernandel isn't using pkgbase. He just wants to upgrade a system from 14.3 to 15 with freebsd-update.

It's time to look at pkgbase. It's what I'm doing with several VMs and I'm writting a new set of jail management scripts that use exclusively pkgbase.

But, frankly, it's not time yet to convert an existing system that you use daily as a server or even as a desktop. My point is that pkgbase isn't stable enough for the moment.
Click to expand...
Yes, I will use freebsd-update.
 
No, only put the options you want to overrule in there, like the url. You don't copy /etc/defaults/rc.conf to /etc/rc.conf either. It's a similar situation.
 
Alain De Vos said:
After upgrade copy
/etc/pkg/FreeBSD.conf
to
/usr/local/etc/pkg/repos/Freebsd.conf
Then edit this latest file.
Click to expand...

Don't do that.

Code: 
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
 
I think I will do tomorrow. Thank you everyone for help.
freebsd-update upgrade -r 15.0-RELEASE
freebsd-update install
shutdown -r now
freebsd-update install
change /usr/etck/pkg/repos/FreeBSD.conf
pkg upgrade or should first run pkg bootstrap -f?
 
Is this a desktop system? During the upgrade you might want to disable kld_list. When upgrading a major version you might have issues loading kernel modules (like graphics/drm-kmod) that were installed for the previous version. The system might fail or even crash when you reboot to activate the new 15.0 kernel.
 
I'll second the "disable kld_list" before you do the shutdown -r now.
Do we need to run freebsd-update install more than once after it reboots? I think a third run cleans up libraries but going across versions may not be needed.
 
In the past I disabled "kld_list" before I start update.
In /boot/loader.conf I have acpi_ibm and acpi_call and cpu_microcode which I didn't disabled in the past.
Should I do now, please?
 
mer said:
Do we need to run freebsd-update install more than once after it reboots? I think a third run cleans up libraries but going across versions may not be needed.
Click to expand...
Minor version upgrades -> two times freebsd-update install
Major version upgrades -> three times

fernandel said:
In /boot/loader.conf I have acpi_ibm and acpi_call and cpu_microcode which I did't disabled in the past.
Should I do now, please?
Click to expand...
acpi_ibm and acpi_call kernel modules are included with the kernel update, so those shouldn't be a problem. Anything that's part of the FreeBSD kernel will get updated at the same time the new kernel is installed. It's "third party" modules (installed from ports/packages) that can pose problems.
 
mer said:
Do we need to run freebsd-update install more than once after it reboots?
Click to expand...
Each major version upgrade needs a third freebsd-update install, and actually this removes the old libs.
It's mandatory because next time you will use freebsd-update, it will ask for this pending install.
That said, there is no hurry. Before, you must be sure that all third-party software are upgraded.

You disable only third-party kmods. Those which belong to the base can remain.
 
For a (mostly) trouble free upgrade, it's always a good idea to simply disable everything you don't strictly need during the upgrade process. Kernel modules, services, etc. Strip it down to the bare minimum. After you've completely finished the upgrade (base OS, ports/packages, etc) you can enable everything again.
 
SirDice Emrion thanks. Running ZFS I've been doing major version upgrades by "create new BE, do upgrade into new BE taking advantage of chroot features in freebsd-upgrade and pkg" so my third breebsd-upgrade install returns "nothing to do" which makes sense.
Taking advantage of bectl mount for new BEs also makes it easy/nice to tweak things like kld_list and loader.conf
 
I wrote a script to help for an upgrade with freebsd-update.
Instead of using it, one can simply read the README, the conf file example and understand the logic behind an upgrade.

github.com

GitHub - Emrion/bin-upgrade: A script to make easier the FreeBSD upgrades

A script to make easier the FreeBSD upgrades. Contribute to Emrion/bin-upgrade development by creating an account on GitHub.
github.com github.com

PS: I used it to update 14.2-RELEASE to 14.3 but I did 14.3 to 15 by hand because it was too complex and too risky. The change of the repos names was the major problem.
 
You must log in or register to reply here.
Back
Top