From: David Weinehall <tao@acc.umu.se>
To: "Carl D. Speare" <carlds@attglobal.net>
Cc: Quim K Holland <qkholland@my-deja.com>, linux-kernel@vger.kernel.org
Subject: Re: need to suggest a good FS:
Date: Fri, 23 Feb 2001 18:34:23 +0100 [thread overview]
Message-ID: <20010223183423.N5465@khan.acc.umu.se> (raw)
In-Reply-To: <20010223143235.E5465@khan.acc.umu.se> <Pine.BSF.4.33.0102231216030.4359-100000@topgun.unixexchange.com>
In-Reply-To: <Pine.BSF.4.33.0102231216030.4359-100000@topgun.unixexchange.com>; from carlds@attglobal.net on Fri, Feb 23, 2001 at 12:20:34PM -0500
On Fri, Feb 23, 2001 at 12:20:34PM -0500, Carl D. Speare wrote:
> Actually there isn't. Hmmm, sounds like I'll have some hacking to do...
>
> But I have to ask if this is something that would actually be desirable.
> Given how rare it is, does the Linux community actually want to have YAFS
> (yet another file system) added to the list, especially for an even more
> rare OS like OpenServer 5.0.x? Maybe now that Caldera is involved more
> with SCO, it might be something that happens in a few months anyway...
Make a read-only version; this will make transition from HTFS to
{ext2fs, reiserfs, xfs, jfs, ...} easy. Read-only also has the property
that it won't cause on-disk corruption; at worst, you get in-memory
corruption...
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-02-23 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 1:27 Quim K Holland
2001-02-23 3:35 ` Carl D. Speare
2001-02-23 13:32 ` David Weinehall
2001-02-23 17:20 ` Carl D. Speare
2001-02-23 17:34 ` David Weinehall [this message]
2001-02-23 17:49 ` Carl D. Speare
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 0:05 root
2001-02-23 0:57 ` Wakko Warner
2001-02-23 1:16 ` David Weinehall
2001-02-23 2:15 ` Mike A. Harris
2001-02-23 13:34 ` David Weinehall
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=20010223183423.N5465@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=carlds@attglobal.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qkholland@my-deja.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
all inboxes | Powered by JetHome®