That does raise the question: If there's no /usr/sbin/pkg,
how is one expected to install pkg initially?
Or does pkg itself uninstall /usr/sbin/pkg and related files
once pkg has been fully installed?
Or did reinstalling pkg mess up my system? :)
-WBE
That does raise the question: If there's no /usr/sbin/pkg,
how is one expected to install pkg initially?
Or does pkg itself uninstall /usr/sbin/pkg and related files
once pkg has been fully installed?
Or did reinstalling pkg mess up my system? :)
-WBE
That does raise the question: If there's no /usr/sbin/pkg,
how is one expected to install pkg initially?
Or does pkg itself uninstall /usr/sbin/pkg and related files
once pkg has been fully installed?
Or did reinstalling pkg mess up my system? :)
-WBE
If you do not have /usr/sbin/pkg (there should be one following an upgrade),^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
you can try:
/usr/local/sbin/pkg-static install -f pkg
I upgraded a system from 13.2 to 14.0.
Did you perform the minor update before the major upgrade?
As a normal part of a major release upgrade, I do pkg upgrade [-f]
after the second install reboot.
This time, however, I got:
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Unfortunately,
# pkg bootstrap -f
got
pkg: pkg(7) bootstrapper not found at /usr/sbin/pkg
(because, indeed, there is no /usr/sbin/pkg; it probably ought to be
/usr/local/sbin/pkg).
Reinstalling pkg itself with "pkg upgrade -f pkg" appears to have fixed
the [warning message] problem, "pkg bootstrap -f" not needed.
The issue if the combination ofshould be: ^^ is
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 43:18:38 |
Calls: | 8,141 |
Calls today: | 4 |
Files: | 13,085 |
Messages: | 5,857,853 |