From: Dee Sharpe <demetrioussharpe@netscape.net>
To: grub-devel@gnu.org,
"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: AFS and BFS removed. Unacceptable license.
Date: Thu, 03 Nov 2011 14:06:34 -0500 [thread overview]
Message-ID: <4EB2E63A.4030106@netscape.net> (raw)
In-Reply-To: <4EAC1DCA.4040809@gmail.com>
On 10/29/2011 10:37 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 29.10.2011 17:22, Dee Sharpe wrote:
>> Ok, so I'd assume that the AFS driver needs to be rewritten. Is it absolutely mandatory that copyright be assigned to the FSF?
>>
> They need to be rewritten. Assignment can be discussed. I've already
> done a part of BFS (using "practical file system design" book as a
> reference) and since AFS is similar it can use same file with some
> defines. So it should
> Actually if you want to help what I need the most is the way of mkfs and
> write to AFS (or as a variant something which already generates AFS with
> files on it like xorriso can do for iso9660) for automated testing purposes.
> It has to run on my testing system (Debian GNU/Linux)
Ok, I will see what I can find. I'm sure that this stuff is in the repo,
it's just a matter of me finding where it's located.
--
Dee Sharpe
The difference between what IS done
& what COULD be done is relational to
what you ARE doing& what you COULD be doing!
next prev parent reply other threads:[~2011-11-03 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 9:37 AFS and BFS removed. Unacceptable license Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-29 15:22 ` Dee Sharpe
2011-10-29 15:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-03 19:06 ` Dee Sharpe [this message]
2011-10-30 15:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4EB2E63A.4030106@netscape.net \
--to=demetrioussharpe@netscape.net \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.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.