Note that this won't upgrade your system, this will only fetch the latest patches for your current version (12.2?).I am trying to upgrade from release 12.2 to 12.3, the first step i.e.freebsd-update fetch
is running from last 19 hours & has not completed!
root@localhost:/usr/sbin # [CMD]freebsd-update fetch[/CMD]
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 12.2-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files will be added as part of updating to
12.2-RELEASE-p15:
/usr/share/zoneinfo/Pacific/Kanton
/usr/src/contrib/tzdata/SECURITY
(END)
Done!less(1)Code:q or Q or :q or :Q or ZZ Exits less.
freebsd-update has always used a pager - it used to be more but think from 12.0 onwards it switched to less. But after a page of output it always stopped, waiting for user input.Have done release upgrade many times previously, faced this output for the first time!
freebsd-update fetch > freebsd-update_fetch.txt
cat freebsd-update_fetch.txt
freebsd-update install
does not invoke any pager. freebsd-update upgrade -r newrelease
as specified in the manual: freebsd-update(8).To bypass pager, you can redirect output to a file:
env PAGER=cat freebsd-update fetch
ENVIRONMENT
PAGER The pager program used to present various reports during the exe-
cution. (Default: "/usr/bin/less".)
PAGER can be set to "cat" when a non-interactive pager is desired.
On FreeBSD it's actually the same executable:Less is more.
root@molly:~ # ls -li /usr/bin/more /usr/bin/less
445455 -r-xr-xr-x 2 root wheel 198432 Apr 10 17:37 /usr/bin/less
445455 -r-xr-xr-x 2 root wheel 198432 Apr 10 17:37 /usr/bin/more
After suspending a job with Ctlr+Z you can have a look at what job you actually suspended. See for example the section on Jobs in tcsh(1) or FreeBSD : Job management with the command[...]
I did not get you! Ctrl+Z suspends it.
jobs
; or refer to the section on job control with your favourite shell. After you have suspended a job on your terminal, you can also have a look at ps -aux | grep <username>
to see what user <username> (=you) has actually running.Have done release upgrade many times previously, faced this output for the first time!