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: Sat, 15 Jan 2005 18:39:27 -0800 [thread overview]
Message-ID: <41E9D3DF.1060508@namesys.com> (raw)
In-Reply-To: <41B29491.20405@slaphack.com>
David Masover wrote:
>
> Hans Reiser wrote:
> | I should add that reiser4 for windows would be proprietary. If they
> | can pay MS, they can pay me, and I see no reason to do free work for MS.
>
> Don't think too highly of the Cygwin project, do you? Oh, and it's
> almost impossible to get a laptop without paying MS, directly or
> indirectly. No
windows
> reiser4 for laptops, then.
>
> Also, is it a given that reiser4 for windows would work without help
> from MS? I've just never seen a third-party filesystem driver for
> windows. You'd think that at least one other filesystem, one of the
> Linux/BSD/etc ones, would have done this, if it was feasable.
I don't know, honestly.
>
> 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.
> How many programs would be broken if
> it was changed? How much point would there be if one could not access a
> unix-created reiser4 partition, or if unix reiser4.2 had to be case
> insensitive? And let's not go into the file-as-directory stuff -- it's
> hard enough on unix.
>
> 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.
>
next prev parent reply other threads:[~2005-01-16 2:39 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 [this message]
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
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=41E9D3DF.1060508@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.