Line 2: |
Line 2: |
| The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE, 8.0-BETA[1234], or 8.0-RC[123] can upgrade as follows: | | The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE, 8.0-BETA[1234], or 8.0-RC[123] can upgrade as follows: |
| <pre> | | <pre> |
− | freebsd-update upgrade -r 8.0-RELEASE | + | freebsd-update upgrade -r 11.0-RELEASE |
| </pre> | | </pre> |
| During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. | | During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. |
Line 16: |
Line 16: |
| freebsd-update install | | freebsd-update install |
| </pre> | | </pre> |
− | At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See:
| |
| | | |
− | http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html
| + | Finally, reboot into 11.0-RELEASE: |
− | | |
− | for more details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:
| |
− | <pre>
| |
− | freebsd-update install
| |
− | </pre>
| |
− | Finally, reboot into 8.0-RELEASE: | |
| <pre> | | <pre> |
| shutdown -r now | | shutdown -r now |
Line 62: |
Line 55: |
| | | |
| Reboot. | | Reboot. |
| + | |
| + | Tuning Make Info: |
| + | Remark: If you have a Multi CORE CPU System you often read Tuning Tips on setting "-j5" after the make Option! Don't use it on Production Systems it can break the Build Process cause the Maintainer / Developers of the Pakets SET the correct Settings for successful and clean builds!! Often Users asked me why the "build world" breaks or the "port build" breaks! |
| + | |
| + | Make Process runs safe on normal Mode, cause it prevent the build processes from blocking access each other or on Library Files!!! Give the System to compile clean and safe.. |
| | | |
| ---- | | ---- |