From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Job Bob <yzhang2004@yahoo.com>, reiserfs-list@namesys.com
Subject: Re: reiser4 for windows
Date: Sun, 16 Jan 2005 00:07:51 -0600 [thread overview]
Message-ID: <41EA04B7.3050606@slaphack.com> (raw)
In-Reply-To: <41E9D3DF.1060508@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
Or is compatibility not an issue?
|> All this leaves me with the distinct impression that it'd be cheaper to
|> buy some gigabit ethernet (or fibre) and a Linux CIFS/Samba fileserver
|> using reiser4. Steam and others refuse to install on network drives,
|> Windows probably will not boot off a network drive, but I imagine that
|> fixing these would be easier than porting a filesystem.
This was awhile ago, and I forget a lot of the context, but I'm
re-reading this and I agree with myself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQeoEtngHNmZLgCUhAQLEjA//QP63NbMvczSfz1YE+EZ/9WqwdE1Wtl/i
YbqSd2r/nZaCcluoIMO6CXN780m7lqSBBTEH05gaHkNuqqxIuupSvLG5YexuDltB
FQtz856AEp29+OtRz691Z+YYCzowJSI6OmHvS6PXviRlv1JBvi2q8e8d0mG+37sT
VhIS3xMOovbJsR7CaOJiJZTbzvE+nIG5iGzU0/gtMFyXOLq6oxN6GJ6yuwbr4dYr
s6uEy7BF/AivwARfTxqrgLeMQVd+kQ3YTV9ACLKuXz60+eO98TXtNVNM/FbnvIr/
Fj4S3yHFN78z02lIR8FKlm6ZaqlS8yXGCfL7aE3NHZWtqySFXdlReJeSKp4YokAo
oqYAFbXuJ0ZIACRYEAbyEpVsvdKwLUuahlVmM4xK6P+WuZUHIxbyeWXyXrfbZ2D/
3k10zIUP47DJM/WO70Fn2G4X/anowk+PRM0bRI6KSJOMH1KTFi9hrjb3NxqV9o9p
KoDl+QYQQpJg30fEHNSkY5lUEMjd2od7R3DgzfkVi2nA/fCqZufHirGLFjWTyrDe
fvTy/CCP4W4oTZR4CHULADQn5bL1BqBm7RJDkF48HBbGKbEyEelhKgxHITC8VUFv
DQ7vIOq7oZ7F59L78ZGLRIvNaZVCB0BITmYZWfCX3SjaFMjDAVxrP8FlyOMjSMyt
T5P7Lte1kz0=
=L++4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-16 6:07 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 [this message]
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
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=41EA04B7.3050606@slaphack.com \
--to=ninja@slaphack.com \
--cc=reiser@namesys.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.