From: Szabolcs Szakacsits <szaka@ntfs-3g.org>
To: openembedded-devel@openembedded.org
Subject: Re: union fs
Date: Tue, 15 Apr 2008 21:48:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20080415T212907-239@post.gmane.org> (raw)
In-Reply-To: 4804CA41.7050800@dls.net
Mike (mwester <mwester <at> dls.net> writes:
>
> According to the official docs, due to limitations of the fuse driver
> for 2.4 kernels, ntfs-3g on such old kernels is prone to data loss.
> This is a fuse problem, but effectively if you value your NTFS
> partition's consistency, it means that ntfs-3g on such old kernels
> should be read-only.
>
> On 2.6, ntfs-3g works wonderfully on all the devices in read and write
> modes, and is the driver I recommend for NTFS support on the SlugOS
> (ARM) distro.
>
> Sorry for not being more clear.
I see, thank you for the explanation. I think we should have better documented
this ntfs-3g issue, sorry about it.
Everything is as safe with the 2.4 kernels as with the 2.6 ones if after umount
one makes sure that the ntfs-3g process is terminated before a device is
detached or the box is powered down. This can be ensured automatic e.g. by a
few shell commands.
Regards, Szaka
--
NTFS-3G: http://ntfs-3g.org
next prev parent reply other threads:[~2008-04-15 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 12:12 union fs RvP
2008-04-14 16:49 ` Mike (mwester)
2008-04-15 8:36 ` Szabolcs Szakacsits
2008-04-15 10:58 ` Package_arch for x86 architectures Stelios Koroneos
2008-04-15 15:31 ` union fs Mike (mwester)
2008-04-15 21:48 ` Szabolcs Szakacsits [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 20:24 RvP
2008-04-14 20:55 ` Mike (mwester)
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=loom.20080415T212907-239@post.gmane.org \
--to=szaka@ntfs-3g.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.