Am Montag, 31. März 2008 schrieb Reese Schreiber:
> Hi Oliver and Jeffrey,
>
> If you are burning a UDF disc using our content creation we should
> already be suppressing the files you mention below. If you don't
> think this is happening please file a bug. Please note the
> suppression will only automatically happen if the content is being
> created by the UDF content creation provided by the DiscRecording
> framework. Judging from your wording below I think you are
> formatting your media with a UDF file system though, in this case no
> automatic suppression is going to occur. If this is the case, how are
> you formatting your optical media and how are you laying down a UDF
> file system (what version of UDF are you using). The "no_log" file
> for disabling .fseventsd is not a hack and is by design. Feel free to
> file a bug if you believe it should be done differently. I believe
> spotlight also offers a method to disable indexing (rather than just
> disabling spotlight in its entirety). I will need to look
> into .Trashes though, for a less hackish way to disable it.
Hello Reese,
I'm doing a "newfs_udf -r 2.50 /dev/disk1" where disk1 is my BD device
containing a BD-RE (rewritable Blu-Ray disc) and use Finder and command line
tools to copy, remove and replace files on the disc.
Spotlight and fseventsd work immediately on the disc after (auto) mounting
which is imho bad practice and I also don't want to write files to discs to
disable OS specific services. This behavior should be disabled by default for
optical and flash devices.
You are right, you can disable the indexer alone but this would render
Spotlight quite useless.
thanks for your answer and looking into this,
O.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/filesystem-dev/email@hidden
This email sent to email@hidden
