|
Lines 501-515
Link Here
|
| 501 |
|
501 |
|
| 502 |
<!-- Sorry folks, but I disagree here. I believe it is worded fine. If anything, drop everything after "perform" and change "updates" to "FreeBSD Updates" and link that to the handbook --> |
502 |
<!-- Sorry folks, but I disagree here. I believe it is worded fine. If anything, drop everything after "perform" and change "updates" to "FreeBSD Updates" and link that to the handbook --> |
| 503 |
|
503 |
|
| 504 |
<note> |
504 |
<important> |
| 505 |
<para>In order for &fbus.ap; to work properly, updates |
505 |
<para>In order for &fbus.ap; to work properly, updates |
| 506 |
for both the <emphasis>current</emphasis> release and the |
506 |
for both the <emphasis>current</emphasis> release and the |
| 507 |
release <emphasis>one wants to upgrade to</emphasis> need to be |
507 |
release <emphasis>one wants to upgrade to</emphasis> need to be |
| 508 |
built. This is necessary for determining the differences of |
508 |
built. This is necessary for determining the differences of |
| 509 |
files between releases. For example, when upgrading a &os; |
509 |
files between releases. For example, when upgrading a &os; |
| 510 |
system from version 7.1 to 7.2, updates will need to be built |
510 |
system from 7.1-RELEASE to 7.2-RELEASE, updates will need to be |
| 511 |
for 7.1-RELEASE as well as for 7.2-RELEASE.</para> |
511 |
built and uploaded to your distribution server for both versions. |
| 512 |
</note> |
512 |
</para> |
|
|
513 |
</important> |
| 513 |
|
514 |
|
| 514 |
<para>For reference, the entire run of <ulink |
515 |
<para>For reference, the entire run of <ulink |
| 515 |
url="init.txt"><filename>init.sh</filename></ulink> is |
516 |
url="init.txt"><filename>init.sh</filename></ulink> is |