From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Disk data layout (was: /dev/drum)
Date: Fri, 27 Apr 2018 14:37:15 -0400 [thread overview]
Message-ID: <CAC20D2MjhYpP6dc-5dyWiZ-w+dFLK1iP=wzYd=FSzkTD8Pd4Pw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VQzxh5i3PViGW+RgHgAN1DVJsr21cc_oEPT1zE9ThZa9A@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Fri, Apr 27, 2018 at 2:16 PM, Paul Winalski <paul.winalski at gmail.com>
wrote:
> On 4/27/18, Dave Horsfall <dave at horsfall.org> wrote:
> > On Wed, 25 Apr 2018, Paul Winalski wrote:
> >
> >> Bin number was zero except on the IBM 2321 data cell drive. CKD drives
> >> supported a variable number of records on each track, hence the term
> >> "record" rather than "sector".
> >
> > Would that have been the infamous chicken-plucker?[*] Wherein if things
> > went OK, then they were OK, but if things went wrong...
>
> That's the one. I'd always heard "noodle picker", though. From the
> outside it looked like a drum in the shape of a multi-sided polygon.
> Each bin held a number of wide pieces of multitrack magnetic tape. To
> seek to your data, the drum rotated under a head that pulled the
> appropriate tape out of the bin and wrapped it on rotating drum. From
> there reading and writing was much like any other drum device. It's
> as if someone asked Rube Goldberg to design a disk drive.
Accept that it will like tape in the head contacted the media.
Question for Debbie S --- my memory is you folks had one up the hill at
LBL. I think that's where I saw it in action.
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180427/226ab860/attachment.html>
next prev parent reply other threads:[~2018-04-27 18:37 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 15:02 [TUHS] /dev/drum Tim Bradshaw
2018-04-20 15:58 ` Clem Cole
2018-04-20 16:00 ` David Collantes
2018-04-20 16:12 ` Dan Cross
2018-04-20 16:21 ` Clem Cole
2018-04-20 16:33 ` Warner Losh
2018-04-20 19:17 ` Ron Natalie
2018-04-20 20:23 ` Clem Cole
2018-04-20 22:10 ` Dave Horsfall
2018-04-22 17:01 ` Lars Brinkhoff
2018-04-22 17:37 ` Clem Cole
2018-04-22 19:14 ` Bakul Shah
2018-04-22 20:58 ` Mutiny
2018-04-22 22:37 ` Clem cole
2018-04-22 21:51 ` Dave Horsfall
2018-04-25 1:27 ` Dan Stromberg
2018-04-25 12:18 ` Ronald Natalie
2018-04-25 13:39 ` Tim Bradshaw
2018-04-25 14:02 ` arnold
2018-04-25 14:59 ` tfb
2018-04-25 14:33 ` Ian Zimmerman
2018-04-25 14:46 ` Larry McVoy
2018-04-25 15:03 ` ron minnich
2018-04-25 20:29 ` Paul Winalski
2018-04-25 20:45 ` Larry McVoy
2018-04-25 21:14 ` Lawrence Stewart
2018-04-25 21:30 ` ron minnich
2018-04-25 23:01 ` Bakul Shah
2018-04-23 16:42 ` Tim Bradshaw
2018-04-23 17:30 ` Ron Natalie
2018-04-23 17:51 ` Clem Cole
2018-04-23 18:30 ` Ron Natalie
2018-04-25 14:02 ` Tom Ivar Helbekkmo
2018-04-25 14:38 ` Clem Cole
2018-04-23 20:47 ` Grant Taylor
2018-04-23 21:06 ` Clem Cole
2018-04-23 21:14 ` Dan Mick
2018-04-23 21:27 ` Clem Cole
2018-04-24 3:28 ` [TUHS] 3330s, 3340s, Winchesters... (was: /dev/drum) Greg 'groggy' Lehey
2018-04-24 11:43 ` Paul Winalski
2018-04-24 13:13 ` Clem Cole
2018-04-25 0:52 ` Greg 'groggy' Lehey
2018-04-25 20:54 ` Paul Winalski
2018-04-23 22:07 ` [TUHS] /dev/drum Tim Bradshaw
2018-04-23 22:15 ` Warner Losh
2018-04-23 23:30 ` Grant Taylor
2018-04-24 9:37 ` Michael Kjörling
2018-04-24 9:57 ` Dave Horsfall
2018-04-24 13:01 ` Nemo
2018-04-24 13:03 ` Arthur Krewat
2018-04-25 1:31 ` [TUHS] Disk data layout (was: /dev/drum) Greg 'groggy' Lehey
2018-04-25 6:43 ` Hellwig Geisse
2018-04-25 21:17 ` Paul Winalski
2018-04-25 21:55 ` Bakul Shah
2018-04-27 15:47 ` Dave Horsfall
2018-04-27 18:16 ` Paul Winalski
2018-04-27 18:37 ` Clem Cole [this message]
2018-04-23 23:45 ` [TUHS] /dev/drum Arthur Krewat
2018-04-24 8:05 ` tfb
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='CAC20D2MjhYpP6dc-5dyWiZ-w+dFLK1iP=wzYd=FSzkTD8Pd4Pw@mail.gmail.com' \
--to=clemc@ccc.com \
/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).