https://library.morph.zone/index.php?title=F.A.Q.&feed=atom&action=historyF.A.Q. - Revision history2024-03-28T17:46:23ZRevision history for this page on the wikiMediaWiki 1.30.0https://library.morph.zone/index.php?title=F.A.Q.&diff=245&oldid=prevGuruman: Reintroduced italic, and updated a bit the content of the first answer to reflect support of minis requiring again the small partition2009-12-07T16:45:08Z<p>Reintroduced italic, and updated a bit the content of the first answer to reflect support of minis requiring again the small partition</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr style="vertical-align: top;" lang="en">
<td colspan="2" style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: white; color:black; text-align: center;">Revision as of 16:45, 7 December 2009</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small FFS partition for the boot.img file, and one larger, bootable, possibly SFS, partition for system files. You said only one is necessary.''</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small <ins class="diffchange diffchange-inline">''</ins>FFS<ins class="diffchange diffchange-inline">'' </ins>partition for the <ins class="diffchange diffchange-inline">''</ins>boot.img<ins class="diffchange diffchange-inline">'' </ins>file, and one larger, bootable, possibly <ins class="diffchange diffchange-inline">''</ins>SFS<ins class="diffchange diffchange-inline">''</ins>, partition for system files. You said only one is necessary.''</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only FFS partitions. So the boot.img was put in a FFS partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a SFS partition, due to its higher reliability. New versions of the HAL/OF can read SFS partitions, and PFS partitions as well, so you can put everything on a single reliable partition.  </div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only <ins class="diffchange diffchange-inline">''</ins>FFS<ins class="diffchange diffchange-inline">'' </ins>partitions. So the <ins class="diffchange diffchange-inline">''</ins>boot.img<ins class="diffchange diffchange-inline">'' </ins>was put in a <ins class="diffchange diffchange-inline">''</ins>FFS<ins class="diffchange diffchange-inline">'' </ins>partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a <ins class="diffchange diffchange-inline">''</ins>SFS<ins class="diffchange diffchange-inline">'' </ins>partition, due to its higher reliability. New versions of the HAL/OF can read <ins class="diffchange diffchange-inline">''</ins>SFS<ins class="diffchange diffchange-inline">'' </ins>partitions, and <ins class="diffchange diffchange-inline">''</ins>PFS<ins class="diffchange diffchange-inline">'' </ins>partitions as well, so you can put everything on a single reliable partition<ins class="diffchange diffchange-inline">. A notable exception is the installation of MorphOS on a supported Apple Mac machine. The Open Firmware of these machines only supports booting from ''HFS'' or ''HFS+'' partitions, therefore the creation of a very small partition for the ''boot.img'' file is again mandatory, as explained in the [[Dual-boot MorphOS and MacOS X on a Mac Mini G4]] guide</ins>.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>''You said that Quark and other low-level software are compressed in the boot.img file. Compressed?''</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>''You said that <ins class="diffchange diffchange-inline">''</ins>Quark<ins class="diffchange diffchange-inline">'' </ins>and other low-level software are compressed in the <ins class="diffchange diffchange-inline">''</ins>boot.img<ins class="diffchange diffchange-inline">'' </ins>file. Compressed?''</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The boot.img file is a gzip archive, the real image file (e.g. bootpegasos2rom.img) is inside and is extracted and run by the HAL/OF.</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The <ins class="diffchange diffchange-inline">''</ins>boot.img<ins class="diffchange diffchange-inline">'' </ins>file is a gzip archive, the real image file (e.g. <ins class="diffchange diffchange-inline">''</ins>bootpegasos2rom.img<ins class="diffchange diffchange-inline">''</ins>) is inside and is extracted and run by the HAL/OF.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>''You said that in earlier versions of this article that Quark supports memory protection and virtual memory, but it seems these features are not active.''</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>''You said that in earlier versions of this article that <ins class="diffchange diffchange-inline">''</ins>Quark<ins class="diffchange diffchange-inline">'' </ins>supports memory protection and virtual memory, but it seems these features are not active.''</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Memory protection did not exist in the AmigaOS, and is not implemented within the ABox of MorphOS for compatibility reasons (almost all the legacy applications would not be able to run correctly with memory protection). On the other hand, memory protection is usable within the QBox and might be available for future applications especially designed for QBox in case a migration of hardware drivers from ABox to QBox will take place. Virtual memory was implemented in the beginning of MorphOS development, but its upgrade is currently halted, due to very low priority. In fact, the maximal RAM requirements of MorphOS and native/legacy programs are very small in comparison with the usual RAM sizes currently available.</div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Memory protection did not exist in the AmigaOS, and is not implemented within the <ins class="diffchange diffchange-inline">''</ins>ABox<ins class="diffchange diffchange-inline">'' </ins>of MorphOS for compatibility reasons (almost all the legacy applications would not be able to run correctly with memory protection). On the other hand, memory protection is usable within the <ins class="diffchange diffchange-inline">''</ins>QBox<ins class="diffchange diffchange-inline">'' </ins>and might be available for future applications especially designed for QBox in case a migration of hardware drivers from <ins class="diffchange diffchange-inline">''</ins>ABox<ins class="diffchange diffchange-inline">'' </ins>to <ins class="diffchange diffchange-inline">''</ins>QBox<ins class="diffchange diffchange-inline">'' </ins>will take place. Virtual memory was implemented in the beginning of MorphOS development, but its upgrade is currently halted, due to very low priority. In fact, the maximal RAM requirements of MorphOS and native/legacy programs are very small in comparison with the usual RAM sizes currently available.</div></td></tr>
</table>Gurumanhttps://library.morph.zone/index.php?title=F.A.Q.&diff=18&oldid=prevASiegel: Created page with '''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small FFS partition for the boot.img file, and one larger, bootabl…'2009-11-29T10:34:07Z<p>Created page with '''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small FFS partition for the boot.img file, and one larger, bootabl…'</p>
<p><b>New page</b></p><div>''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small FFS partition for the boot.img file, and one larger, bootable, possibly SFS, partition for system files. You said only one is necessary.''<br />
<br />
This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only FFS partitions. So the boot.img was put in a FFS partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a SFS partition, due to its higher reliability. New versions of the HAL/OF can read SFS partitions, and PFS partitions as well, so you can put everything on a single reliable partition. <br />
<br />
<br />
''You said that Quark and other low-level software are compressed in the boot.img file. Compressed?''<br />
<br />
The boot.img file is a gzip archive, the real image file (e.g. bootpegasos2rom.img) is inside and is extracted and run by the HAL/OF.<br />
<br />
<br />
''You said that in earlier versions of this article that Quark supports memory protection and virtual memory, but it seems these features are not active.''<br />
<br />
Memory protection did not exist in the AmigaOS, and is not implemented within the ABox of MorphOS for compatibility reasons (almost all the legacy applications would not be able to run correctly with memory protection). On the other hand, memory protection is usable within the QBox and might be available for future applications especially designed for QBox in case a migration of hardware drivers from ABox to QBox will take place. Virtual memory was implemented in the beginning of MorphOS development, but its upgrade is currently halted, due to very low priority. In fact, the maximal RAM requirements of MorphOS and native/legacy programs are very small in comparison with the usual RAM sizes currently available.</div>ASiegel