From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] Unix v6 File System information
Date: Sun, 21 Feb 2016 09:21:30 -0600 [thread overview]
Message-ID: <3EEAC13B-2B79-46F4-A45F-89EA56651E74@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1602220021100.79948@aneurin.horsfall.org>
A technical description would be appreciated although the manpage looks like a good start as does Lions. I hadn't gotten to chapter 20 yet, should have known he would cover the topic.
Sent from my iPhone
> On Feb 21, 2016, at 7:34 AM, Dave Horsfall <dave at horsfall.org> wrote:
>
>> On Sun, 21 Feb 2016, Noel Chiappa wrote:
>>
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/man/man5/fs.5
>
> Yeah, but I was unsure whether the OP wanted a technical description, or
> one in plain English :-) I'm still prepared to do the latter, once I can
> find a spare hour.
>
> Somewhere, deep within Minnie's bowels, there might be a paper that I
> wrote upon implementing a "bad block" system (specifically directed at the
> RK-05, but generally applicable to any device); it involved the hitherto-
> unused inode "0", to which were chained the bad blocks (added by hand).
>
> The trick was that normal FS utilities would ignore it...
>
> Someone at the time (Kevin Hill?) pointed out that inode "-1" could also
> be used, but I wasn't prepared to go that far :-)
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-02-21 15:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 11:44 Noel Chiappa
2016-02-21 13:34 ` Dave Horsfall
2016-02-21 15:21 ` Will Senn [this message]
2016-02-21 17:21 ` John Cowan
2016-02-22 1:58 ` Dave Horsfall
2016-02-22 2:32 ` Lyndon Nerenberg
2016-02-22 12:30 ` Tony Finch
2016-02-21 15:36 ` Will Senn
2016-02-21 20:24 ` Warren Toomey
2016-02-21 17:31 ` Random832
2016-02-21 17:36 ` ron
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 1:54 Norman Wilson
2016-02-22 3:02 ` Larry McVoy
2016-02-21 21:51 Noel Chiappa
2016-02-21 18:27 Noel Chiappa
2016-02-21 18:59 ` Clem Cole
2016-02-21 19:31 ` arnold
2016-02-21 20:45 ` Will Senn
2016-02-21 21:06 ` Clem Cole
2016-02-21 21:05 ` Will Senn
2016-02-21 21:21 ` Clem Cole
2016-02-22 2:20 ` Warren Toomey
[not found] ` <2D41A491-40CD-41DB-B3BA-0ACBD831E2C7@gmail.com>
2016-02-22 7:27 ` Warren Toomey
2016-02-21 17:50 Noel Chiappa
2016-02-21 18:36 ` Random832
2016-02-22 13:10 ` ron
2016-02-21 9:45 Will Senn
2016-02-21 10:01 ` Dave Horsfall
2016-03-04 19:10 ` Jacob Ritorto
2016-03-10 8:51 ` Dave Horsfall
2016-03-10 9:31 ` SPC
2016-02-21 10:27 ` arnold
2016-02-21 12:29 ` Dave Horsfall
2016-02-21 13:54 ` arnold
2016-02-21 14:40 ` Clement T. Cole
2016-03-04 9:27 ` Dave Horsfall
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=3EEAC13B-2B79-46F4-A45F-89EA56651E74@gmail.com \
--to=will.senn@gmail.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).