From: Pavel Machek <pavel@ucw.cz>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: minixfs bitmaps and associated lossage
Date: Sun, 7 May 2006 07:35:39 +0000 [thread overview]
Message-ID: <20060507073539.GA5765@ucw.cz> (raw)
In-Reply-To: <20060506220451.GQ27946@ftp.linux.org.uk>
Hi!
> Warning: text below is a mild example of software coproarchaeology,
> so if you are easily squicked by tangled mess of bugs and dumb lossage,
> well... you've been warned.
:-)
> So... What the hell can we do? Layouts (4) and (5) are clearly
> broken and _never_ worked - there's nothing that would manage to create
> such filesystem. So these are obvious candidates for switching - either
> to (2) (correct) or to (3) (broken, but at least match util-linux fsck.minix
> and mkfs.minix on such platforms). The question being, what do we do with
> (3) (big-endian metadata, little-endian bitmaps) and what do we do with
> Linux fsck.minix? Aside of repeating the mantra, that is ("All Software
> Sucks, All Hardware Sucks")...
Remove minix write support? Only writers care about bitmap layout,
right?
Pavel
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-05-08 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44560796.8010700@gmail.com>
[not found] ` <20060506162956.GO27946@ftp.linux.org.uk>
[not found] ` <20060506163737.GP27946@ftp.linux.org.uk>
2006-05-06 22:04 ` minixfs bitmaps and associated lossage Al Viro
2006-05-06 22:25 ` Matthew Wilcox
2006-05-06 22:26 ` Linus Torvalds
2006-05-06 23:10 ` Al Viro
2006-05-06 23:42 ` Linus Torvalds
2006-05-07 7:37 ` Al Viro
2006-05-07 7:35 ` Pavel Machek [this message]
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=20060507073539.GA5765@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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).