The disk-manager question is irrelevant, no one uses disk managers anymore.
Noted by: scottl Approved by: bcr (mentor)
This commit is contained in:
parent
6b085fa242
commit
07522c1d64
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40112
1 changed files with 0 additions and 27 deletions
|
|
@ -1475,33 +1475,6 @@
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
||||||
<qandaentry>
|
|
||||||
<question id="disk-manager">
|
|
||||||
<para>Is &os; compatible with any disk managers?</para>
|
|
||||||
</question>
|
|
||||||
|
|
||||||
<answer>
|
|
||||||
<para>&os; recognizes the <application>Ontrack Disk
|
|
||||||
Manager</application> and makes allowances for it. Other disk
|
|
||||||
managers are not supported.</para>
|
|
||||||
|
|
||||||
<para>If you just want to use the disk with &os; you do not
|
|
||||||
need a disk manager. Just configure the disk for as much
|
|
||||||
space as the BIOS can deal with (usually
|
|
||||||
504 megabytes), and &os; should figure out how much
|
|
||||||
space you really have. If you are using an old disk with an
|
|
||||||
MFM controller, you may need to explicitly tell &os; how
|
|
||||||
many cylinders to use.</para>
|
|
||||||
|
|
||||||
<para>If you want to use the disk with &os; and another
|
|
||||||
operating system, you may be able to do without a disk
|
|
||||||
manager: just make sure the &os; boot partition and the
|
|
||||||
slice for the other operating system are in the first 1024
|
|
||||||
cylinders. If you are reasonably careful, a
|
|
||||||
20 megabyte boot partition should be plenty.</para>
|
|
||||||
</answer>
|
|
||||||
</qandaentry>
|
|
||||||
|
|
||||||
<qandaentry>
|
<qandaentry>
|
||||||
<question id="missing-os">
|
<question id="missing-os">
|
||||||
<para>When I boot &os; for the first time after install I get
|
<para>When I boot &os; for the first time after install I get
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue