From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] remove the fat_cvf
Date: Wed, 5 Jun 2002 18:38:23 +0200 [thread overview]
Message-ID: <73BA70C46BF@vcnet.vc.cvut.cz> (raw)
On 6 Jun 02 at 0:31, OGAWA Hirofumi wrote:
> This patch is first stuff to remove fat_cvf. AFAIK, it seems the
> fat_cvf isn't used for a long time. And fat_cvf makes change of fatfs
> difficult.
>
> Is the fat_cvf needed? If it's not needed, I will submit the
> following patch at this weekend..
ftp://fb9nt.uni-duisburg.de/pub/linux/dmsdos/README reads:
--
PLEASE NOTE:
The DMSDOS project is dead. I no longer maintain it due to lack of time.
The latest supported kernel is 2.2.15 with dmsdos 0.9.2.1.
There will never be a kernel 2.4.x port. Dmsdos 0.9.2.3-pre2 was an
attempt to port the code, but it has failed. Don't use it.
--
and it is latest dmsdos related file I found (and 0.9.2.1 is latest
I used on 2.2.17), so I believe that it is safe to remove cvf code
from fatfs. Both Stacker and Doublespace supported FAT16 only, so
current usual 120GB disk would require 120 logical units with estimated
compression ratio 2:1. IMHO adding dmsdosfs into mtools is the best
solution for those who still need it.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-06-05 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 16:38 Petr Vandrovec [this message]
2002-06-06 13:08 ` [RFC] remove the fat_cvf OGAWA Hirofumi
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 15:31 OGAWA Hirofumi
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=73BA70C46BF@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.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