|
Lines 257-263
_Major version_ upgrades increase the major version number. An example:
Link Here
|
| 257 |
|
257 |
|
| 258 |
Both types of upgrade can be performed by providing `freebsd-update` with a release version target. |
258 |
Both types of upgrade can be performed by providing `freebsd-update` with a release version target. |
| 259 |
|
259 |
|
| 260 |
[WARNING] |
260 |
[NOTE] |
|
|
261 |
==== |
| 262 |
An upgrade to FreeBSD does *not* automatically upgrade the separate area that is typically used to boot the operating system. |
| 263 |
|
| 264 |
Some upgrade situations require an link:#updating-bootcode[update to the EFI System Partition (EFI) or bootcode]. |
| 265 |
==== |
| 266 |
|
| 267 |
[NOTE] |
| 261 |
==== |
268 |
==== |
| 262 |
After each new `RELEASE`, FreeBSD package build servers will, for a limited period, *not* use the newer version of the operating system. |
269 |
After each new `RELEASE`, FreeBSD package build servers will, for a limited period, *not* use the newer version of the operating system. |
| 263 |
This provides continuity for the many users who do not upgrade immediately after a release announcement. |
270 |
This provides continuity for the many users who do not upgrade immediately after a release announcement. |
|
Lines 272-278
For example:
Link Here
|
| 272 |
So, with any minor or major OS upgrade, if your package requirements include any kernel module: |
279 |
So, with any minor or major OS upgrade, if your package requirements include any kernel module: |
| 273 |
|
280 |
|
| 274 |
* *be prepared to build the module from source*. |
281 |
* *be prepared to build the module from source*. |
| 275 |
|
|
|
| 276 |
==== |
282 |
==== |
| 277 |
|
283 |
|
| 278 |
[NOTE] |
284 |
[NOTE] |
|
Lines 510-518
Kernel modules may differ as `freebsd-update` may have updated them.
Link Here
|
| 510 |
To exclude specific files or directories, add them to the `IDSIgnorePaths` option in [.filename]#/etc/freebsd-update.conf#. |
516 |
To exclude specific files or directories, add them to the `IDSIgnorePaths` option in [.filename]#/etc/freebsd-update.conf#. |
| 511 |
|
517 |
|
| 512 |
[[updating-bootcode]] |
518 |
[[updating-bootcode]] |
| 513 |
== Updating Bootcode |
519 |
== Updating EFI System Partitions (ESPs) or bootcode |
| 514 |
|
520 |
|
| 515 |
The following manuals describe the upgrade process of bootcode and boot loaders: man:gpart[8], man:gptboot[8], man:gptzfsboot[8], and man:loader.efi[8]. |
521 |
Related manual pages include: |
|
|
522 |
|
| 523 |
* man:gpart[8] -- control utility for the disk partitioning GEOM class |
| 524 |
* man:gptboot[8] -- GPT bootcode for UFS on BIOS-based computers |
| 525 |
* man:gptzfsboot[8] -- GPT bootcode for ZFS on BIOS-based computers |
| 526 |
* man:loader.efi[8] -- UEFI kernel loader. |
| 527 |
|
| 528 |
The https://man.freebsd.org/cgi/man.cgi?query=loader.efi&sektion=8&manpath=freebsd-release#EXAMPLES[EXAMPLES] section of loader.efi(8) shows how to copy the [.filename]#loader.efi# file: |
| 529 |
|
| 530 |
* from an installation of FreeBSD |
| 531 |
* to the proper path within an EFI System Partition (ESP). |
| 532 |
|
| 533 |
[WARNING] |
| 534 |
==== |
| 535 |
Do *not* use the `bootcode` command of gpart(8) on a UEFI-based system that will run FreeBSD 13.0-RELEASE or greater. |
| 536 |
==== |
| 537 |
|
| 538 |
If a system uses multiple disks for redundancy: include the ESP, or bootcode, in redundancy. |
| 539 |
For example: |
| 540 |
|
| 541 |
* if a partition with a UEFI-based installation of FreeBSD is mirrored from one disk to another, then both disks should have equally capable ESPs. |
| 516 |
|
542 |
|
| 517 |
[[updating-upgrading-documentation]] |
543 |
[[updating-upgrading-documentation]] |
| 518 |
== Updating the Documentation Set |
544 |
== Updating the Documentation Set |
| 519 |
- |
|
|