286
edits
Changes
Jump to navigation
Jump to search
mLine 26:
Line 26: − + − + − + Line 46:
Line 46: − + Line 56:
Line 56: − + − +
no edit summary
These concerns have led to the following recommended sequence. Note that the detailed sequence for particular updates may require additional steps, but this core process should remain unchanged for some time:
These concerns have led to the following recommended sequence. Note that the detailed sequence for particular updates may require additional steps, but this core process should remain unchanged for some time:
<pre>
<pre>
make buildworld
make -s buildworld
</pre>
</pre>
This first compiles the new compiler and a few related tools, then uses the new compiler to compile the rest of the new world. The result ends up in /usr/obj.
This first compiles the new compiler and a few related tools, then uses the new compiler to compile the rest of the new world. The result ends up in /usr/obj.
<pre>
<pre>
make buildkernel
make -s buildkernel KERNCONF=CUSTOM
</pre>
</pre>
Unlike the older approach, using config(8) and make(1), this uses the new compiler residing in /usr/obj. This protects you against compiler-kernel mismatches.
Unlike the older approach, using config(8) and make(1), this uses the new compiler residing in /usr/obj. This protects you against compiler-kernel mismatches.
<pre>
<pre>
make installkernel
make -s installkernel
</pre>
</pre>
Place the new kernel and kernel modules onto the disk, making it possible to boot with the newly updated kernel.
Place the new kernel and kernel modules onto the disk, making it possible to boot with the newly updated kernel.
This does some initial configuration file updates in preparation for the new world. For instance it may add new user groups to the system, or new user names to the password database. This is often necessary when new groups or special system-user accounts have been added since the last update, so that the installworld step will be able to use the newly installed system user or system group names without problems.
This does some initial configuration file updates in preparation for the new world. For instance it may add new user groups to the system, or new user names to the password database. This is often necessary when new groups or special system-user accounts have been added since the last update, so that the installworld step will be able to use the newly installed system user or system group names without problems.
<pre>
<pre>
make installworld
make -s installworld
</pre>
</pre>
Copies the world from /usr/obj. You now have a new kernel and new world on disk.
Copies the world from /usr/obj. You now have a new kernel and new world on disk.
Reboot.
Reboot.
Tuning Make Info:
'''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!
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..
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..