public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Dylan Griffiths <dylang+kernel@thock.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: HFSPLus driver for Linux 2.6.
Date: Fri, 06 Feb 2004 14:15:26 +0100	[thread overview]
Message-ID: <jeptcsxsb5.fsf@sykes.suse.de> (raw)
In-Reply-To: <1076051611.885.25.camel@gaston> (Benjamin Herrenschmidt's message of "Fri, 06 Feb 2004 18:13:32 +1100")

Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> One thing we absolutely need too is a port of Apple's fsck for HFS+,
> currently, the driver will refuse to mount read/write a "dirty"
> HFS+ filesystem to avoid corruption, but that means we have to reboot
> MacOS to fsck it then... 

Not reboot, but boot. MOL is your friend. :-)

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-02-06 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <402304F0.1070008@thock.com>
     [not found] ` <20040205191527.4c7a488e.akpm@osdl.org>
2004-02-06  3:56   ` HFSPLus driver for Linux 2.6 Dylan Griffiths
2004-02-06  4:02     ` Andrew Morton
2004-02-06  5:03       ` Matthias Urlichs
2004-02-06  7:13       ` Benjamin Herrenschmidt
2004-02-06 13:15         ` Andreas Schwab [this message]
2004-02-06 19:09           ` Matthias Urlichs
2004-02-06 23:47         ` J.A. Magallon
2004-02-18 18:37   ` Updated HFSplus driver for 2.6.3 Dylan Griffiths

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=jeptcsxsb5.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=dylang+kernel@thock.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox