From: Hans Reiser <reiser@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: Job Bob <yzhang2004@yahoo.com>, reiserfs-list@namesys.com
Subject: Re: reiser4 for windows
Date: Tue, 18 Jan 2005 09:03:39 -0800 [thread overview]
Message-ID: <41ED416B.8040202@namesys.com> (raw)
In-Reply-To: <41EC99E4.2050708@slaphack.com>
David Masover wrote:
>
>
> Hans Reiser wrote:
> | David Masover wrote:
> |
> |> Hans Reiser wrote:
> |> [...]
> |> |
> |> |>
> |> |> To start with, ntfs read access is still case insensitive, last I
> |> |> checked. How deep does that go?
> |> |
> |> |
> |> | In reiser4, it is just a directory plugin.
> |>
> |> Nono -- how do you give Windows, which is case insensitive, access to a
> |> case-sensitive filesystem? For instance, how do you get a
> Windows-based
> |> backup program to back up a reiser4 partition from a Linux
> installation,
> |> if it has filenames that are identical except for case?
> |
> |
> | This problem is insoluble. Either make reiser4 case insensitive and use
> | it that way or educate the windows programs or live with bugs. I see no
> | alternative. Do you?
>
> Mangling. Or case-sensitivity (forget who said that NTFS has that). Or
> force case-insensitive FSes only. I think all three would work in
> different situations, and I don't think it would be too difficult to add
> all three.
Ok, so it is soluble.
>
> Just for clarification -- mangling is how VFAT is backwards-compatible
> with DOS, for example. myreallylongfile.doc becomes MYREAL~1.DOC when
> viewed from DOS, so that while VFAT should really be read with Windows
> 95 or better (Linux), it can still be accessed in Dos.
>
> This loses information (if a DOS program backs up and restores
> MYREAL~1.DOC, you lose the long (myreallylongfile.doc) name.) But
> sometimes there's no alternative, and if you mangle it (instead of just
> chopping off the end of the filename) you avoid collisions -- that is,
> if you have:
>
> myreallylongfile.doc
> myreallife.doc
>
> then they become
>
> MYREAL~1.DOC
> MYREAL~2.DOC
>
>
>
> Only question is, where to set which of these to choose (mangle or case
> sensitivity)? Maybe it could be per-directory, most likely per-mount.
> But I have no idea how Windows passes mount options ... I don't think it
> has any mount options at all.
>
well, all this assumes we have resources to spare from debugging reiser4
for linux.....;-)
next prev parent reply other threads:[~2005-01-18 17:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 21:10 reiser4 for windows Job Bob
2004-12-05 1:57 ` Hans Reiser
2004-12-05 4:00 ` Hans Reiser
2004-12-05 4:54 ` David Masover
2004-12-07 8:28 ` Redeeman
2004-12-08 0:51 ` Philip Miller
2005-01-26 19:27 ` Marcus Furlong
2005-01-16 2:39 ` Hans Reiser
2005-01-16 6:07 ` David Masover
2005-01-17 16:46 ` Hans Reiser
2005-01-17 17:12 ` Christian Iversen
2005-01-18 16:37 ` Hans Reiser
2005-02-01 8:52 ` mjt
2005-02-01 9:59 ` Christian Iversen
2005-02-02 1:18 ` David Masover
2005-02-02 8:02 ` Christian Iversen
2005-01-18 5:08 ` David Masover
2005-01-18 17:03 ` Hans Reiser [this message]
2004-12-05 8:14 ` Dr. Giovanni A. Orlando
2004-12-05 7:37 ` David Masover
2004-12-06 2:31 ` Jonathan Briggs
2004-12-06 4:17 ` Tierra
2004-12-06 14:55 ` Dr. Giovanni A. Orlando
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 6:07 Jiri Klouda
2004-12-07 8:29 ` Redeeman
2004-12-08 1:40 ` Spam
2004-12-08 4:38 ` David Masover
2004-12-08 7:50 ` Radovan Garabik
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=41ED416B.8040202@namesys.com \
--to=reiser@namesys.com \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=yzhang2004@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.