Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #75998 > unrolled thread

Spotlight finds things that aren't there

Back to article view | Back to comp.sys.mac.system

Contents

  Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-05-28 10:19 -0700
    Re: Spotlight finds things that aren't there Alan Browne <alan.browne@freelunchvideotron.ca> - 2015-05-28 13:38 -0400
      Re: Spotlight finds things that aren't there D Finnigan <dog_cow@macgui.com> - 2015-05-28 17:46 +0000
        Re: Spotlight finds things that aren't there Alan Browne <alan.browne@freelunchvideotron.ca> - 2015-05-28 14:05 -0400
    Re: Spotlight finds things that aren't there D Finnigan <dog_cow@macgui.com> - 2015-05-28 17:37 +0000
    Re: Spotlight finds things that aren't there JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-05-28 13:43 -0400
      Re: Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-05-28 21:30 -0700
        Re: Spotlight finds things that aren't there Alan Baker <email@domain.com> - 2015-06-02 07:56 -0700
          Re: Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-06-02 10:52 -0700
            Re: Spotlight finds things that aren't there Alan Baker <email@domain.com> - 2015-06-02 13:38 -0700
              Re: Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-06-02 21:36 -0700
                Re: Spotlight finds things that aren't there JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-03 13:17 -0400
                  Re: Spotlight finds things that aren't there Alan Baker <email@domain.com> - 2015-06-03 10:28 -0700
                  Re: Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-06-03 21:49 -0700
    Re: Spotlight finds things that aren't there Barry Margolin <barmar@alum.mit.edu> - 2015-05-28 16:14 -0400
      Re: Spotlight finds things that aren't there JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-05-28 16:25 -0400
      Re: Spotlight finds things that aren't there isw <isw@witzend.com> - 2015-05-28 21:27 -0700
        Re: Spotlight finds things that aren't there -- solution, sort of isw <isw@witzend.com> - 2015-05-30 21:26 -0700
          Re: Spotlight finds things that aren't there -- solution, sort of JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-05-31 03:12 -0400
            Re: Spotlight finds things that aren't there -- solution, sort of isw <isw@witzend.com> - 2015-05-31 20:52 -0700
        Re: Spotlight finds things that aren't there -- Follow-on question isw <isw@witzend.com> - 2015-05-30 21:38 -0700
          Re: Spotlight finds things that aren't there -- Follow-on question Jim Gibson <JimSGibson@gmail.com> - 2015-05-31 22:25 -0700
            Re: Spotlight finds things that aren't there -- Follow-on question isw <isw@witzend.com> - 2015-06-01 09:34 -0700
              Re: Spotlight finds things that aren't there -- Follow-on question Martin Frost me at invalid stanford daht edu <nospam@stanford.edu.invalid> - 2015-06-01 19:08 -0700

Page 2 of 2 — ← Prev page 1 [2]

#76029 — Re: Spotlight finds things that aren't there -- Follow-on question

When I was trying to learn why Spotlight was "finding" all those JPG  
files, I discovered that not only the offending files, but a huge 
percentage of all the image files I have, have the "execute" bits set:

-rwxrwxrwx@

My guess is that the affected files are ones that originated in a 
digital camera (scanned images are not so afflicted), and that were 
never edited (using Photoshop, GIMP, or Preview, mostly).

Given that, I have a suspicion that the execute bits are being set as a 
result of the use of FAT- file systems on the memory cards that digital 
cameras use. Editing the image and saving clears them (I guess).

But however it happened, the question is: Do I Care?

And if it is something that should be fixed, what's an easy way to do 
that, over a pile of folders and a bigger pile of files?

Isaac

[toc] | [prev] | [next] | [standalone]

#76036 — Re: Spotlight finds things that aren't there -- Follow-on question

In article <isw-72B81D.21383130052015@news-roam.garlic.com>, isw
<isw@witzend.com> wrote:

> When I was trying to learn why Spotlight was "finding" all those JPG  
> files, I discovered that not only the offending files, but a huge 
> percentage of all the image files I have, have the "execute" bits set:
> 
> -rwxrwxrwx@
> 
> My guess is that the affected files are ones that originated in a 
> digital camera (scanned images are not so afflicted), and that were 
> never edited (using Photoshop, GIMP, or Preview, mostly).
> 
> Given that, I have a suspicion that the execute bits are being set as a 
> result of the use of FAT- file systems on the memory cards that digital 
> cameras use. Editing the image and saving clears them (I guess).
> 
> But however it happened, the question is: Do I Care?
> 
> And if it is something that should be fixed, what's an easy way to do 
> that, over a pile of folders and a bigger pile of files?

The easy way is to use command lines from within the Terminal
application. Check out the 'find' and 'chmod' commands:

  man find
  man chmod

Something like this (untested):

  find . -name \*.jpg -exec chmod -x {} \;

Test this on a single file in a single folder:

  cd myfolder
  find . -name mytest.jpg -exec chmod -x {} \:

and see if it does what you want. Then apply it to a whole folder using
the first version. Then all of your folders by executing it at the
top-level directory that is the parent of all of your folders and
files.

-- 
Jim Gibson

[toc] | [prev] | [next] | [standalone]

#76037 — Re: Spotlight finds things that aren't there -- Follow-on question

In article <310520152225584255%JimSGibson@gmail.com>,
 Jim Gibson <JimSGibson@gmail.com> wrote:

> In article <isw-72B81D.21383130052015@news-roam.garlic.com>, isw
> <isw@witzend.com> wrote:
> 
> > When I was trying to learn why Spotlight was "finding" all those JPG  
> > files, I discovered that not only the offending files, but a huge 
> > percentage of all the image files I have, have the "execute" bits set:
> > 
> > -rwxrwxrwx@
> > 
> > My guess is that the affected files are ones that originated in a 
> > digital camera (scanned images are not so afflicted), and that were 
> > never edited (using Photoshop, GIMP, or Preview, mostly).
> > 
> > Given that, I have a suspicion that the execute bits are being set as a 
> > result of the use of FAT- file systems on the memory cards that digital 
> > cameras use. Editing the image and saving clears them (I guess).
> > 
> > But however it happened, the question is: Do I Care?
> > 
> > And if it is something that should be fixed, what's an easy way to do 
> > that, over a pile of folders and a bigger pile of files?
> 
> The easy way is to use command lines from within the Terminal
> application. Check out the 'find' and 'chmod' commands:
> 
>   man find
>   man chmod
> 
> Something like this (untested):
> 
>   find . -name \*.jpg -exec chmod -x {} \;
> 
> Test this on a single file in a single folder:
> 
>   cd myfolder
>   find . -name mytest.jpg -exec chmod -x {} \:
> 
> and see if it does what you want. Then apply it to a whole folder using
> the first version. Then all of your folders by executing it at the
> top-level directory that is the parent of all of your folders and
> files.

Thanks. I generally subscribe to the "If it ain't broke, don't fix it", 
and also to the "Make sure you're actually fixing what is broken and not 
just putting a band-aid on it" philosophies of engineering, so before I 
do something to hundreds of files, I'd still like to know why those bits 
got set (on virtually every unedited digital camera file on my Mac), and 
if it matters whether those files think they are executables.

Isaac

[toc] | [prev] | [next] | [standalone]

#76045 — Re: Spotlight finds things that aren't there -- Follow-on question

isw <isw@witzend.com> writes:

> In article <310520152225584255%JimSGibson@gmail.com>,
>  Jim Gibson <JimSGibson@gmail.com> wrote:
> 
> > In article <isw-72B81D.21383130052015@news-roam.garlic.com>, isw
> > <isw@witzend.com> wrote:
> > 
> > > When I was trying to learn why Spotlight was "finding" all those JPG  
> > > files, I discovered that not only the offending files, but a huge 
> > > percentage of all the image files I have, have the "execute" bits set:
> > > 
> > > -rwxrwxrwx@
> > > 
> > > My guess is that the affected files are ones that originated in a 
> > > digital camera (scanned images are not so afflicted), and that were 
> > > never edited (using Photoshop, GIMP, or Preview, mostly).
> > > 
> > > Given that, I have a suspicion that the execute bits are being set as a 
> > > result of the use of FAT- file systems on the memory cards that digital 
> > > cameras use. Editing the image and saving clears them (I guess).
> > > 
> > > But however it happened, the question is: Do I Care?
> > > 
> > > And if it is something that should be fixed, what's an easy way to do 
> > > that, over a pile of folders and a bigger pile of files?
> > 
> > The easy way is to use command lines from within the Terminal
> > application. Check out the 'find' and 'chmod' commands:
> > 
> >   man find
> >   man chmod
> > 
> > Something like this (untested):
> > 
> >   find . -name \*.jpg -exec chmod -x {} \;
> > 
> > Test this on a single file in a single folder:
> > 
> >   cd myfolder
> >   find . -name mytest.jpg -exec chmod -x {} \:
> > 
> > and see if it does what you want. Then apply it to a whole folder using
> > the first version. Then all of your folders by executing it at the
> > top-level directory that is the parent of all of your folders and
> > files.
> 
> Thanks. I generally subscribe to the "If it ain't broke, don't fix it", 
> and also to the "Make sure you're actually fixing what is broken and not 
> just putting a band-aid on it" philosophies of engineering, so before I 
> do something to hundreds of files, I'd still like to know why those bits 
> got set (on virtually every unedited digital camera file on my Mac), and 
> if it matters whether those files think they are executables.
> 
> Isaac

It doesn't matter one bit (!) whether those files are marked as
executables.  (And for the record, those files can't think.)

Martin

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.sys.mac.system

csiph-web