From: naota@elisp.net (Naohiro Aota)
To: kernelnewbies@lists.kernelnewbies.org
Subject: GSoC project idea: HFS Plus journal
Date: Mon, 21 Mar 2011 02:07:40 +0900 [thread overview]
Message-ID: <87r5a190v7.fsf@elisp.net> (raw)
In-Reply-To: <20110317155331.GA12018@kroah.com> (Greg KH's message of "Thu, 17 Mar 2011 08:53:31 -0700")
Greg KH <greg@kroah.com> writes:
> On Thu, Mar 17, 2011 at 06:57:27PM +0900, Naohiro Aota wrote:
>> Hi,
>>
>> I see some of you are talking about GSoC participation. I'm also
>> thinking of it.
>>
>> I have MacBookPro booting both MacOSX and Linux. Now Linux can write the
>> filesystem safely only when HFS Plus journal is off. My life would be
>> more better if Linux have complete HFS Plus filesystem read/write
>> support.
>>
>> So I'm thinking of implementing HFS Plus Journal support on Linux. I've
>> searched and found a technote about HFS Plus format describe its Journal
>> [1].
>>
>> How do you think about it?
>
> Looks like a nice self-contained, project proposal, good luck!
Thanks. I need someone to mentor me :) How can I find him/her? Maybe I
should post developing mailing list. But I don't find HFS+ developing
list :(
Regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110321/d4f0a3ed/attachment.bin
next prev parent reply other threads:[~2011-03-20 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 9:57 GSoC project idea: HFS Plus journal Naohiro Aota
2011-03-17 15:53 ` Greg KH
2011-03-20 17:07 ` Naohiro Aota [this message]
2011-03-20 18:47 ` Greg KH
2011-03-20 20:45 ` Greg Freemyer
2011-03-21 6:19 ` Rajat Sharma
2011-04-02 19:16 ` [RFC][GSoC] HFSPlus Journaling proposal Naohiro Aota
2011-04-02 19:16 ` Naohiro Aota
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=87r5a190v7.fsf@elisp.net \
--to=naota@elisp.net \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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.