From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in disk/format
Date: Sat, 25 May 2002 23:01:10 -0700 [thread overview]
Message-ID: <200205260601.g4Q61AtV093336@ducky.net> (raw)
In-Reply-To: <124619951e4fdbe0e6a2ba1dde590b2e@plan9.bell-labs.com>
>> By the way, in your attempt to reproduce this problem did you use
>> a system with a SCSI disk? Note that the behavior of opendisk()
>
>No, just a zeroed file appropriately sized.
>I don't think format actually cares about
>the geometry. I don't have any SCSI disks handy.
Format *does* care about the geometry. If it puts the wrong values
into the boot sector, the boot sector /386/pbs won't work, because
the function BIOSread needs to know the geometry in order to convert
linear offsets to the C/H/S addressing used in Int 10 BIOS calls.
(I use /386/pbslba on my SCSI disk to avoid this problem.)
>> is different for IDE vs. SCSI disks, particularly how it guesses
>> the disk geometry. In the past I submitted a bugfix to disk.c that
>> would greatly increase the likelihood of SCSI geometry being correctly
>> guessed, and I see my patch was ignored...
>
>More likely just missed. Where is this patch?
https://lists.cse.psu.edu/archives/9fans/2000-October/008039.html
Two messages later (in .../008042.html) you replied with "Thanks for the fix".
Therefore I stand by "was ignored" or perhaps even "was brutally discarded" :-)
next prev parent reply other threads:[~2002-05-26 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 5:27 rsc
2002-05-26 6:01 ` Mike Haertel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 17:49 rsc
2002-05-27 8:32 nigel
2002-05-26 22:13 rsc
2002-05-27 6:31 ` Michael Baldwin
2002-05-26 6:19 rsc
2002-05-26 20:40 ` Mike Haertel
2002-05-26 5:22 Geoff Collyer
2002-05-26 4:13 rsc
2002-05-26 5:11 ` Mike Haertel
2002-05-26 3:01 Mike Haertel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200205260601.g4Q61AtV093336@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).