From: Hans Reiser <reiser@namesys.com>
To: Mark Piper <mwp@cs.cmu.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: ReiserFS IFSD for Windows
Date: Fri, 13 May 2005 11:14:32 -0700 [thread overview]
Message-ID: <4284EE88.2020309@namesys.com> (raw)
In-Reply-To: <42838B75.1000605@cs.cmu.edu>
Mark Piper wrote:
> This summer, I will be starting a 3.5-month project to create an
> Installable File System Driver (IFSD) to read ReiserFS under Microsoft
> Windows, similar to ext2fsd. (The project is a practicum to complete
> my degree in software engineering from Carnegie Mellon.)
I would prefer that you not do it. Namesys believes that people who use
proprietary operating systems should pay to use reiserfs.
I can suggest quite a few other tasks that would make a more impressive
practicum (copy on write links, various other new and needed plugins).
>
> I have three questions:
>
> * Is anyone out there interested in using the tool as it is developed?
>
> * Is anyone out there interested in mentoring the development of the
> tool? (This basically consists of answering specific technical
> questions when they arise.)
>
> * Other than compliance to the GPL, are there any other liscensing
> factors I should be aware of?
>
> For anyone interested, my initial plan is to port the read-only
> ReiserFS 3 code from the GRUB bootloader, and turn it into an IFSD
> using the same techniques as in ext2fsd -- although I'd love to hear
> other ideas, and opinions of whether the project might be feasible
> with ReiserFS 4.
>
> Thanks,
> Mark Piper
>
>
>
>
>
next prev parent reply other threads:[~2005-05-13 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 16:59 ReiserFS IFSD for Windows Mark Piper
2005-05-12 17:15 ` Bedros Hanounik
2005-05-12 21:37 ` Christian Iversen
2005-05-13 18:14 ` Hans Reiser [this message]
2005-05-14 0:57 ` David Masover
2005-05-16 18:10 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2005-07-10 21:06 Leif W
2005-07-12 2:17 ` Hans Reiser
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=4284EE88.2020309@namesys.com \
--to=reiser@namesys.com \
--cc=mwp@cs.cmu.edu \
--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.