All of lore.kernel.org
 help / color / mirror / Atom feed
From: Redeeman <redeeman@metanurb.dk>
To: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: reiser4 for windows
Date: Tue, 07 Dec 2004 09:29:22 +0100	[thread overview]
Message-ID: <1102408162.12503.25.camel@localhost> (raw)
In-Reply-To: <20041207060730.GA1344@zg.cz>

On Mon, 2004-12-06 at 22:07 -0800, Jiri Klouda wrote:
> > 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.
> 
> You might be onto something here. I am pretty sure my company would
> pay quite a lot for a working, fast and elegant implementation of 
> symbolic links on windows. Either as a new filesystem or as an addition 
> onto ntfs. We currently use one such addition and not very usable and
> uses a catalog of symlinks that can easily get corrupted.
> 
> Having reiser4 on Windows or even ext2, would be a huge thing.
a real implementation of ext2 for windows exists.. i had it once in
vmware.. but i cant remember the name
> 
> > 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.
> 
> Unfortunatelly even with very fast ethernet connections and network
> appliance with CIFS access, we still don't get the performance of a
> local filesystem. Plus, you don't want to really give write access 
> over network, that slows down anything when you get into hundreds of
> clients. And we really cannot pay for so many network applicances to
> make this scalable proposition.
> 
> I wish we could just drop Windows as a platform, but as long as there
> are customers, there will be need to support them as well... :(
> 
> -Jiri
> 
-- 
Redeeman <redeeman@metanurb.dk>


  reply	other threads:[~2004-12-07  8:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  6:07 reiser4 for windows Jiri Klouda
2004-12-07  8:29 ` Redeeman [this message]
2004-12-08  1:40   ` Spam
2004-12-08  4:38     ` David Masover
2004-12-08  7:50       ` Radovan Garabik
  -- strict thread matches above, loose matches on Subject: below --
2004-12-04 21:10 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
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

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=1102408162.12503.25.camel@localhost \
    --to=redeeman@metanurb.dk \
    --cc=reiserfs-list@namesys.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.