List readonly files












2














I need to list or show or query for the files in a folder (well, technically, on a USB drive, but I can navigate to it in Finder/Terminal) that are marked readonly.



All the Google-fu in the world just reveals solutions to change permissions but I don't need to do that.



My Dashcam marks videos/images readonly to save them when I press the button on it, but they're still in a folder with a few hundred MOV files, and I need a simple way to filter down to the ones I am looking for.






terminal finder permission







share|improve this question









New contributor




Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    2














    I need to list or show or query for the files in a folder (well, technically, on a USB drive, but I can navigate to it in Finder/Terminal) that are marked readonly.



    All the Google-fu in the world just reveals solutions to change permissions but I don't need to do that.



    My Dashcam marks videos/images readonly to save them when I press the button on it, but they're still in a folder with a few hundred MOV files, and I need a simple way to filter down to the ones I am looking for.






    terminal finder permission







    share|improve this question









    New contributor




    Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      2












      2








      2







      I need to list or show or query for the files in a folder (well, technically, on a USB drive, but I can navigate to it in Finder/Terminal) that are marked readonly.



      All the Google-fu in the world just reveals solutions to change permissions but I don't need to do that.



      My Dashcam marks videos/images readonly to save them when I press the button on it, but they're still in a folder with a few hundred MOV files, and I need a simple way to filter down to the ones I am looking for.






      terminal finder permission







      share|improve this question









      New contributor




      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I need to list or show or query for the files in a folder (well, technically, on a USB drive, but I can navigate to it in Finder/Terminal) that are marked readonly.



      All the Google-fu in the world just reveals solutions to change permissions but I don't need to do that.



      My Dashcam marks videos/images readonly to save them when I press the button on it, but they're still in a folder with a few hundred MOV files, and I need a simple way to filter down to the ones I am looking for.






      terminal finder permission




      terminal finder permission






      share|improve this question









      New contributor




      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 1 hour ago









      Nimesh Neema

      14.6k43871




      14.6k43871






      New contributor




      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 hours ago









      Steven Evers

      1111




      1111




      New contributor




      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Steven Evers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          2 Answers
          2






          active

          oldest

          votes


















          1














          List the files and grep for the read-only pattern:



          ls -l | grep '^-r--'



          ^ symbol indicates start the line.



          We are filtering only files here by mentioning ^-, after that looking only for read permission files by specifying r--. If you want to filter read & executable permission files, you can use r-x.



          If you want just the filename, you can use below command



          ls -l | grep '^-r--' | awk 'NF>1{print $NF}'



          Printing the file name using above command works, only if you don't have spaces in file name.






          share|improve this answer










          New contributor




          BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















          • Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
            – Yoric
            1 hour ago





















          0














          One way is to make use of the -w option in bash to check if the file is writable or not.



          Go into the directory you want to check your files, then enter:



          for RO in $(find . -type f);do [ -r "$RO" ] && [ ! -w "$RO" ] && echo $RO;done



          (credit to www.unix.com)






          share|improve this answer










          New contributor




          Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "118"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });






            Steven Evers is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f347110%2flist-readonly-files%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            List the files and grep for the read-only pattern:



            ls -l | grep '^-r--'



            ^ symbol indicates start the line.



            We are filtering only files here by mentioning ^-, after that looking only for read permission files by specifying r--. If you want to filter read & executable permission files, you can use r-x.



            If you want just the filename, you can use below command



            ls -l | grep '^-r--' | awk 'NF>1{print $NF}'



            Printing the file name using above command works, only if you don't have spaces in file name.






            share|improve this answer










            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
              – Yoric
              1 hour ago


















            1














            List the files and grep for the read-only pattern:



            ls -l | grep '^-r--'



            ^ symbol indicates start the line.



            We are filtering only files here by mentioning ^-, after that looking only for read permission files by specifying r--. If you want to filter read & executable permission files, you can use r-x.



            If you want just the filename, you can use below command



            ls -l | grep '^-r--' | awk 'NF>1{print $NF}'



            Printing the file name using above command works, only if you don't have spaces in file name.






            share|improve this answer










            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
              – Yoric
              1 hour ago
















            1












            1








            1






            List the files and grep for the read-only pattern:



            ls -l | grep '^-r--'



            ^ symbol indicates start the line.



            We are filtering only files here by mentioning ^-, after that looking only for read permission files by specifying r--. If you want to filter read & executable permission files, you can use r-x.



            If you want just the filename, you can use below command



            ls -l | grep '^-r--' | awk 'NF>1{print $NF}'



            Printing the file name using above command works, only if you don't have spaces in file name.






            share|improve this answer










            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            List the files and grep for the read-only pattern:



            ls -l | grep '^-r--'



            ^ symbol indicates start the line.



            We are filtering only files here by mentioning ^-, after that looking only for read permission files by specifying r--. If you want to filter read & executable permission files, you can use r-x.



            If you want just the filename, you can use below command



            ls -l | grep '^-r--' | awk 'NF>1{print $NF}'



            Printing the file name using above command works, only if you don't have spaces in file name.







            share|improve this answer










            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            share|improve this answer



            share|improve this answer








            edited 3 mins ago





















            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            answered 2 hours ago









            BarathVutukuri

            1112




            1112




            New contributor




            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





            New contributor





            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            BarathVutukuri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.












            • Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
              – Yoric
              1 hour ago




















            • Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
              – Yoric
              1 hour ago


















            Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
            – Yoric
            1 hour ago






            Grepping the ls -l is a smart way to do it, but beware that your files might start with -rw-r--r-- with root as the owner, and such files won't be listed, even though they aren't writeable for the user.
            – Yoric
            1 hour ago















            0














            One way is to make use of the -w option in bash to check if the file is writable or not.



            Go into the directory you want to check your files, then enter:



            for RO in $(find . -type f);do [ -r "$RO" ] && [ ! -w "$RO" ] && echo $RO;done



            (credit to www.unix.com)






            share|improve this answer










            New contributor




            Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              One way is to make use of the -w option in bash to check if the file is writable or not.



              Go into the directory you want to check your files, then enter:



              for RO in $(find . -type f);do [ -r "$RO" ] && [ ! -w "$RO" ] && echo $RO;done



              (credit to www.unix.com)






              share|improve this answer










              New contributor




              Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                One way is to make use of the -w option in bash to check if the file is writable or not.



                Go into the directory you want to check your files, then enter:



                for RO in $(find . -type f);do [ -r "$RO" ] && [ ! -w "$RO" ] && echo $RO;done



                (credit to www.unix.com)






                share|improve this answer










                New contributor




                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                One way is to make use of the -w option in bash to check if the file is writable or not.



                Go into the directory you want to check your files, then enter:



                for RO in $(find . -type f);do [ -r "$RO" ] && [ ! -w "$RO" ] && echo $RO;done



                (credit to www.unix.com)







                share|improve this answer










                New contributor




                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer








                edited 1 hour ago





















                New contributor




                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 1 hour ago









                Yoric

                2014




                2014




                New contributor




                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Yoric is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                    Steven Evers is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    Steven Evers is a new contributor. Be nice, and check out our Code of Conduct.













                    Steven Evers is a new contributor. Be nice, and check out our Code of Conduct.












                    Steven Evers is a new contributor. Be nice, and check out our Code of Conduct.
















                    Thanks for contributing an answer to Ask Different!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid …



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid …



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f347110%2flist-readonly-files%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    -

                    Popular posts from this blog

                    Bundesstraße 106

                    Image
                    Dieser Artikel beschreibt die Bundesstraße 106 in Deutschland. Zur gleichnamigen Straße in Österreich siehe Mölltal Straße. Vorlage:Infobox hochrangige Straße/Wartung/DE-B Bundesstraße 106 in Deutschland Karte Basisdaten Betreiber: Deutschland  Bundesrepublik Deutschland Straßenbeginn: Wismar ( 53° 54′  N , 11° 24′  O 53.900536 11.396875 ) Straßenende: Schwerin ( 53° 36′  N , 11° 24′  O 53.592785 11.404892 ) Gesamtlänge: 40,7 km Bundesland: Mecklenburg-Vorpommern Ausbauzustand: zweistreifig [1] Bundesstraße 106 in Schwerin (Umgehungsstraße) Straßenverlauf Land Mecklenburg-Vorpommern Landkreis Nordwestmecklenburg Ortsumgehung Wismar Wallensteingraben über   Dorf Mecklenburg Wallensteingraben Groß Stieten Bad Kleinen OT Niendorf Bahnstrecke Lübeck–Bad Kleinen Zickhusen Lübstorf Klein Trebbow OT Kirch Stück ...
                    Read more

                    Verónica Boquete

                    Image
                    Verónica Boquete im Trikot der Nationalmannschaft (2013) Personalia Name Verónica Boquete Giadans Geburtstag 9. April 1987 Geburtsort Santiago de Compostela, Spanien Größe 159 cm Position Mittelfeld / Sturm Juniorinnen Jahre Station 2001–2005 Xuventú Aguiño Frauen Jahre Station Spiele (Tore) 1 2005–2008 Prainsa Zaragoza 83 (40) 2008–2010 Espanyol Barcelona 53 (30) 2010 Buffalo Flash 9 0 (9) 2010 Chicago Red Stars 3 0 (1) 2010–2011 Espanyol Barcelona 26 (41) 2011 Philadelphia Independence 13 0 (5) 2011 Energija Woronesch 5 0 (1) 2012–2014 Tyresö FF 39 (14) 2014 Portland Thorns FC 15 0 (4) 2014–2015 1. FFC Frankfurt 23 0 (7) 2015–2016 FC Bayern München 9 0 (0) 2016–2018 Paris Saint-Germain 31 0 (8) 2018 Peking BG Phoenix 2019– Utah Royals FC 0 0 (0) Nationalmannschaft Jahre Auswahl ...
                    Read more

                    Ida-Boy-Ed-Garten

                    Image
                    Die Lage des Ida-Boy-Ed-Gartens, rot markiert Der Ida-Boy-Ed-Garten Der Ida-Boy-Ed-Garten, Blick von der Wakenitzmauer durch das Tor in der Stadtmauer Der Ida-Boy-Ed-Garten ist eine Straße der Lübecker Altstadt. Inhaltsverzeichnis 1 Lage 2 Geschichte 3 Literatur 4 Weblinks Lage | Der etwa 90 Meter lange Ida-Boy-Ed-Garten befindet sich an der nördlichen Spitze der Altstadtinsel, vor dem Burgtor. Die in einem Bogen durch eine Grünanlage hangaufwärts führende Straße verbindet die Wakenitzmauer mit der Burgtorbrücke. Geschichte | Der heutige Ida-Boy-Ed-Garten wurde ursprünglich als Verlängerung der Wakenitzmauer angelegt. 1903 wurde in den erhaltenen Teil der mittelalterlichen Stadtmauer, an dem die Wakenitzmauer bei der Einmündung der Kaiserstraße begann, ein Tor mit einem großen Bogen für die Durchführung der Straße und zwei kleineren seitlichen Öffnungen für Fußgänger gebrochen, um für die neu errichteten Wohnhäuser in diesem Bereich ...
                    Read more