John Snow writes:
> On 12/17/2015 01:15 PM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 12/17/2015 03:30 AM, Markus Armbruster wrote:
John Snow writes:
> This allows us to distinguish between the current disk type and the
> current drive type. The drive is what's
On 12/17/2015 01:15 PM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 12/17/2015 03:30 AM, Markus Armbruster wrote:
>>> John Snow writes:
>>>
This allows us to distinguish between the current disk type and the
current drive type. The drive is what's reported to CMOS, the disk
John Snow writes:
> On 12/17/2015 03:30 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> This allows us to distinguish between the current disk type and the
>>> current drive type. The drive is what's reported to CMOS, the disk is
>>> whatever the pick_geometry function suspects has bee
On 12/17/2015 03:30 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> This allows us to distinguish between the current disk type and the
>> current drive type. The drive is what's reported to CMOS, the disk is
>> whatever the pick_geometry function suspects has been inserted.
>>
>> The dri
John Snow writes:
> This allows us to distinguish between the current disk type and the
> current drive type. The drive is what's reported to CMOS, the disk is
> whatever the pick_geometry function suspects has been inserted.
>
> The drive field maintains the exact same meaning as it did previous
This allows us to distinguish between the current disk type and the
current drive type. The drive is what's reported to CMOS, the disk is
whatever the pick_geometry function suspects has been inserted.
The drive field maintains the exact same meaning as it did previously,
however pick_geometry/fd_
