OpenBSD
Upgrade Guide: 7.4 to 7.5
[FAQ Index] |
[7.3 -> 7.4]
[7.5 -> 7.6]
Upgrades are only supported from one release to the release immediately
following.
Read through and understand this process before attempting it.
For critical or physically remote machines, test it on an identical,
local system first.
Before using any upgrade method
- Check available disk space in /usr.
Verify that the
/usr partition has a size of at least 1.1G.
With less space the upgrade may fail and you should consider reinstalling
the system instead.
- Read configuration and syntax changes and the
package upgrade instructions.
There were several configuration changes
and changes in packages that may
require planning before starting the upgrade.
Upgrade Methods
- Unattended Upgrade:
The easiest method is an unattended upgrade using
sysupgrade(8).
The program will download all the install sets, verify their signatures, and
reboot to perform the upgrade automatically. Once the unattended upgrade has
completed, continue below.
- Interactive Upgrade:
If you insist on leaving out some of the install sets, you will want to
perform an interactive upgrade. (sysupgrade
upgrades with all install sets.)
- Manual Upgrade:
The final option is using the manual upgrade process.
(This is not recommended as it is the most error-prone method.)
Interactive Upgrade
After the Upgrade
After upgrading the sets, the system will reboot with the upgraded
kernel and run sysmerge(8)
during boot. In some cases, configuration files cannot be modified
automatically. Run
# sysmerge
to check and perform these configuration
changes.
Next remove the old files.
Finish up by upgrading the packages using pkg_add -u.
You may wish to check the errata page for
any post-release fixes.
Manual Upgrade (without the install kernel)
This is NOT the recommended process.
Use the unattended or interactive upgrade methods if at all possible!
Sometimes, you need to perform an upgrade of a machine for which the normal
unattended or interactive upgrade process is not possible.
Preparation
- Place install files in a good location.
Make sure you have sufficient space!
Running out of space on a remote upgrade could be...unfortunate.
Note that using softdeps can exacerbate the situation as deleted and
overwritten files do not release their space immediately.
Consider disabling the
softdep mount option in
/etc/fstab and rebooting before undertaking a manual upgrade.
Having at least 500MB free on /usr would be recommended.
- Become root.
While using
doas(1)
before each command is generally a good practice, the command will likely
be broken by the last steps, so you should become root before starting
this process.
It might be good to verify your access to root using a method other than
doas at this point, i.e., direct login or using
su(1).
- Stop and/or disable any appropriate applications.
During this process, all the userland applications will be replaced but
may not be runnable, and strange things may happen as a result.
You may also have issues with DNS resolution during the first reboot, so
PF rules and NFS mounts dependent upon DNS may cause boot-up problems.
There may be other applications which you wish to keep from running
immediately after the upgrade; stop and disable them as well.
- Install new boot blocks.
This should actually be done at the end of any upgrade.
If this has been neglected, then failure to do this now may break serial
console or other things, depending on your platform.
Use
installboot(8), assuming
sd0 is your boot disk:
# installboot sd0
Upgrading manually
- Install new kernels.
The extra steps for copying over the primary kernel are done
to ensure that there is always a valid kernel on the disk.
If using the multiprocessor kernel:
# cd /usr/rel # where you put the release files
# ln -f /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsd
# cp bsd.rd /
# cp bsd /bsd.sp
If using the single processor kernel:
# cd /usr/rel # where you put the release files
# ln -f /bsd /obsd && cp bsd /nbsd && mv /nbsd /bsd
# cp bsd.rd bsd.mp / # may give a harmless warning
- Enable KARL.
Store the kernel's checksum:
# sha256 -h /var/db/kernel.SHA256 /bsd
- Install new userland.
Save a copy of reboot(8), extract and install the release tarballs, reboot.
Install
base75.tgz last, because the new base system,
in particular tar(1),
gzip(1) and
reboot(8),
will not work with the old kernel.
Either untar the needed filesets manually:
# cp /sbin/reboot /sbin/oreboot
# tar -C / -xzphf xshare75.tgz
# tar -C / -xzphf xserv75.tgz
# tar -C / -xzphf xfont75.tgz
# tar -C / -xzphf xbase75.tgz
# tar -C / -xzphf man75.tgz
# tar -C / -xzphf game75.tgz
# tar -C / -xzphf comp75.tgz
# tar -C / -xzphf base75.tgz # Install last!
# /sbin/oreboot
or, if you use
ksh(1), you can do:
# cp /sbin/reboot /sbin/oreboot
# for _f in [!b]*75.tgz base75.tgz; do tar -C / -xzphf "$_f" || break; done
# /sbin/oreboot
Note that tar(1)
can expand only one archive per invocation, so a simple glob won't work.
- After reboot, update
/dev.
Run
MAKEDEV(8):
# cd /dev
# ./MAKEDEV all
- Update the boot loader.
Still assuming
sd0 is your boot disk:
# installboot sd0
- Update system configuration files.
Run sysmerge(8):
# sysmerge
- Update firmware.
There may be new firmware for your system.
Update it with
fw_update(8):
# fw_update
- Finish up.
Review the console output from boot (using
dmesg -s)
and correct any failures as necessary.
All the steps following configuration changes
below also apply to manual upgrades.
Finally, remove /sbin/oreboot and update packages:
pkg_add -u.
Reboot once more to make sure you use the newest firmware files
and run on your own kernel generated by KARL.
Configuration and syntax changes
- Nothing of note this release
Files to remove
- Nothing to remove this release
Special packages
- databases/postgresql.
There was a major update to PostgreSQL 16.1. Use
pg_upgrade
as described in the postgresql-server pkg-readme or do a dump/restore.
[FAQ Index] |
[7.3 -> 7.4]
[7.5 -> 7.6]
$OpenBSD: upgrade75.html,v 1.3 2024/10/03 00:53:36 pamela Exp $
¡®Yes, sir. I felt sure you understood that. She said she had told you.¡¯ "Why, eh,--I--I don't know that my movements need have anything to do with his. Yours, of course,--" "Ah, but if it saved your life!" "No, I'm not," grumbled the Doctor, "I've had enough of this wild-goose chase. And besides, it's nearly dinner time." "I am coming to that," Lawrence said, lighting a fresh cigarette. "As soon as Bruce was in trouble and the plot began to reel off I saw that it was mine. Of course there were large varyings in the details, but the scheme was mine. It was even laid on the same spot as my skeleton story. When I grasped that, I knew quite well that somebody must have stolen my plot." Judy In a coach-house, through which we passed on our way to see the prince's favourite horses with the state carriages¡ªquite commonplace and comfortable, and made at Palitana¡ªwas a chigram,[Pg 68] off which its silk cover was lifted; it was painted bright red and spangled with twinkling copper nails. This carriage, which is hermetically closed when the Ranee goes out in it, was lined with cloth-of-gold patterned with Gohel Sheri's initials within a horseshoe: a little hand-glass on one of the cushions, two boxes of chased silver, the curtains and hangings redolent of otto of roses. "Are you certain of it? You have seen so very little of him, and you may be mistaken." "And your wife?" "I drawed on my man's bundle o' wood," said Gid, "and then dropped a little, so's to git him where he was biggest and make sure o' him." HoME²¨¶àÒ°½áÒÂ×óÏßÊÓƵ
ENTER NUMBET 0016www.lftdsl.com.cn
hbcxwm.com.cn
hilegua.com.cn
www.himalia.com.cn
www.syfyfz.com.cn
www.tnupcg.com.cn
www.room79.com.cn
pear168.com.cn
szwallet.com.cn
wkjsj.net.cn