From: "jdow" <jdow@earthlink.net>
To: <linux-kernel@vger.kernel.org>
Subject: Amiga partition reading patch
Date: Tue, 24 Aug 2004 04:37:39 -0700 [thread overview]
Message-ID: <00f301c489ce$c2cd01a0$1225a8c0@kittycat> (raw)
This is a patch known good against Mandrake 2.6.3-7mdk. I suspect it will
apply to later versions equally well since the file affected appears to
be unchanged as late as 2.6.9-rc1.
I have a large archive of files stored on Amiga volumes. Many of these
volumes are on Fujitsu magneto-optical disks with 2k sector size. The
existing partitioning code cannot properly read them since it appears
the OS automatically deblocks the large sectors into logical 512 byte
sectors, something AmigaDOS never did. I arranged the partitioning code
to handle this situation.
Second I have some rather strange test case disks, including my largest
storage partition, that have somewhat unusual partition values. As such
I needed additional information in addition to the first and last block
number information. AmigaDOS reserves N blocks, with N greater than or
equal to 1 and less than the size of the partition, for some boot time
information and signatures. I have some partitions that use other than
the usual value of 2.
There is one more "fix" that could be put in if someone needs it. Another
value in the "Rigid Disk Blocks" description of a partition is a "PreAlloc"
value. It defines a number of blocks at the end of the disk that are not
considered to be a real part of the partition. This was "important" in
the days of 20 meg and 40 meg hard disks. It is hardly important and not
used on modern drives without special user intervention.
This partitioning information is known correct. I wrote the low level
portion of the hard disk partitioning code for AmigaDOS 3.5 and 3.9. I
am also responsible for one of the more frequently used partitioning
tools, RDPrepX, before that.
Please consider adding this to the build tree as a completeness item.
Thank you.
{^_^} Joanne Dow, jdow@earthlink.net
(I tried submitting this to Roland a couple times now and
nothing happened so I am submitting it to the list.)
next reply other threads:[~2004-08-24 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 11:37 jdow [this message]
2004-08-24 12:18 ` Thomas Richter
2004-08-24 13:50 ` Gene Heskett
2004-08-24 20:58 ` jdow
2004-08-24 16:41 ` Geert Uytterhoeven
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='00f301c489ce$c2cd01a0$1225a8c0@kittycat' \
--to=jdow@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®