The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] H.J. Lu Bootable Root & Base System disks
Date: Tue, 21 Jul 2020 00:15:47 -0400	[thread overview]
Message-ID: <20200721041547.GH388817@mit.edu> (raw)
In-Reply-To: <e52c9f7b-f065-f555-13c4-34c004628194@spamtrap.tnetconsulting.net>

Sorry for not responding on this thread earlier; I've been pretty
swamped lately.

Xiafs was introduced at about the same time of ext2; Wikipedia states that

   "Initially, Xiafs was more stable than ext2, but being a fairly
   minimalistic modification of the MINIX file system, it was not very
   well suited for future extension."

The first part wasn't quite accurate.  It turns out that xiafs had the
same bug as ext2, but ext2 had the necessary sanity checking so that
it actually issued a warning when the bug was triggered, where xiafs
just silently corrupted the file system.

The real issue was that xiafs was mostly a one-person show (namely
Frank Xia) and he suffered blowback when he tried to rename xiafs to
linuxfs, which was interpreted by many as a marketing effort --- about
as tone-deaf as Stallman trying to jawbone people to rename "Linux" to
"LiGNUx" ten years later.

And xiafs was technically worse compared to ext2, and ext2 had a
larger number of developers.  So xiafs never really stood much of a
chance.

Also, by that point, very few people were actually using HJ's
boot/root disks.  Most developers had moved on to the MCC distribution
by that time, since it was more comprehensive, and it was easier to
bootstrap a working development system.

So to be honest, I had never noticed that HJ was trying to use xiafs
in his boot/root disks.

Cheers,

					- Ted

  reply	other threads:[~2020-07-21  4:22 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  4:17 Grant Taylor via TUHS
2020-07-17  1:40 ` John Gilmore
2020-07-17  1:59   ` Larry McVoy
2020-07-17  3:35     ` Larry McVoy
2020-07-17  5:18       ` Random832
2020-07-17 13:12         ` Ron Pool
2020-07-17 23:50         ` Grant Taylor via TUHS
2020-07-21  4:15           ` tytso [this message]
2020-07-21 17:49             ` Grant Taylor via TUHS
2020-07-17  5:23       ` Petr Titěra
2020-07-17  5:41         ` Grant Taylor via TUHS
2020-07-17  6:04           ` Petr Titěra
2020-07-17 15:12             ` Grant Taylor via TUHS
2020-07-17 17:19               ` Larry McVoy
2020-07-17 17:42                 ` [TUHS] Linux on TUHS [was: H.J. Lu Bootable Root & Base System disks] salewski
2020-07-17 17:47                   ` Sergio Pedraja
2020-07-17 17:26               ` [TUHS] H.J. Lu Bootable Root & Base System disks Warner Losh
2020-07-17 17:50                 ` Adam Thornton
2020-07-17 20:16                 ` Petr Titěra
2020-07-17 21:48                 ` A. P. Garcia
2020-07-17 19:46               ` Harald Arnesen
2020-07-17  5:24       ` Adam Thornton
2020-07-17  5:30 ` Grant Taylor via TUHS
2020-07-17 20:37   ` Petr Titěra
2020-07-17 18:16 ` Grant Taylor via TUHS
2021-05-18  1:33 ` Jason Stevens
2021-05-21  9:46   ` Sean Dwyer via TUHS
2021-05-26  1:12     ` Jason Stevens
2021-05-26  1:34       ` Gregg Levine
2021-05-26  2:53         ` Jason Stevens
2021-05-26  6:06       ` Lars Brinkhoff
2021-05-26  7:03         ` Jason Stevens
2021-05-26  7:37           ` Lars Brinkhoff
2021-05-26  7:45             ` Jason Stevens
2021-05-26  7:51               ` arnold
2021-05-26  7:56               ` Lars Brinkhoff
2021-05-26 14:58                 ` Clem Cole
2021-05-26 18:12                   ` Jason Stevens
2021-05-26 23:29                     ` Chris Torek
2021-05-26 14:06               ` Al Kossow
2021-05-26 14:25                 ` Larry McVoy
2021-05-26 14:57               ` Clem Cole
2020-07-17 18:08 Norman Wilson
2020-07-17 18:14 ` John Cowan
2020-07-17 18:19 ` Larry McVoy

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=20200721041547.GH388817@mit.edu \
    --to=tytso@mit.edu \
    --cc=gtaylor@tnetconsulting.net \
    --cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).