find entries but remind permission denied











up vote
-1
down vote

favorite












I attempt to find any entries containing "thunderbird" to delete them



me@algorithms:~$ sudo find / -iregex ".*thunderbird.*" | grep Permission
find: ‘/run/user/1000/gvfs’: Permission denied


but find do not have the permission to access ‘/run/user/1000/gvfs’.



I am noticed I have the unlimited privilege to manipulate under the administrator mode.



How could I do things freely without any reminder of `permission denied"










share|improve this question






















  • /run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
    – danzel
    Nov 28 at 0:48










  • could you please transmit the comment to answer. @danzel
    – avirate
    Nov 28 at 0:49















up vote
-1
down vote

favorite












I attempt to find any entries containing "thunderbird" to delete them



me@algorithms:~$ sudo find / -iregex ".*thunderbird.*" | grep Permission
find: ‘/run/user/1000/gvfs’: Permission denied


but find do not have the permission to access ‘/run/user/1000/gvfs’.



I am noticed I have the unlimited privilege to manipulate under the administrator mode.



How could I do things freely without any reminder of `permission denied"










share|improve this question






















  • /run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
    – danzel
    Nov 28 at 0:48










  • could you please transmit the comment to answer. @danzel
    – avirate
    Nov 28 at 0:49













up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I attempt to find any entries containing "thunderbird" to delete them



me@algorithms:~$ sudo find / -iregex ".*thunderbird.*" | grep Permission
find: ‘/run/user/1000/gvfs’: Permission denied


but find do not have the permission to access ‘/run/user/1000/gvfs’.



I am noticed I have the unlimited privilege to manipulate under the administrator mode.



How could I do things freely without any reminder of `permission denied"










share|improve this question













I attempt to find any entries containing "thunderbird" to delete them



me@algorithms:~$ sudo find / -iregex ".*thunderbird.*" | grep Permission
find: ‘/run/user/1000/gvfs’: Permission denied


but find do not have the permission to access ‘/run/user/1000/gvfs’.



I am noticed I have the unlimited privilege to manipulate under the administrator mode.



How could I do things freely without any reminder of `permission denied"







permissions find






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 at 0:36









avirate

1164




1164












  • /run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
    – danzel
    Nov 28 at 0:48










  • could you please transmit the comment to answer. @danzel
    – avirate
    Nov 28 at 0:49


















  • /run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
    – danzel
    Nov 28 at 0:48










  • could you please transmit the comment to answer. @danzel
    – avirate
    Nov 28 at 0:49
















/run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
– danzel
Nov 28 at 0:48




/run/user/1000 is not a persistent directory on your hard drive. It is a temporary file system (tmpfs) and will be deleted when you shut down your computer. You are not supposed to remove any files in it.
– danzel
Nov 28 at 0:48












could you please transmit the comment to answer. @danzel
– avirate
Nov 28 at 0:49




could you please transmit the comment to answer. @danzel
– avirate
Nov 28 at 0:49










1 Answer
1






active

oldest

votes

















up vote
0
down vote













/run/ is a "tmpfs" mount. It is a temporary file system location (tmpfs), and the contents will not persist after a reboot.



You can see this for yourself and confirm it is the case. From terminal, type the command mount. The output will show you the different storage devices and mount types with information about their mount points and underlying filesystem type.



# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1989412k,nr_inodes=497353,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404008k,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)


In the example above the first five mounts listed - sysfs, proc, udev, devpts, and tmpfs are specialized mounts that are not actually associated with a physical storage disk, but exist in non-persistent memory (ram) to facilitate the operating system and programs needs.



The sixth one listed, /dev/sda2 is an actual physical disk mount, mounted to the root mount point / with the filesystem type EXT4. This is a persistent mount and the contents will generally survive reboot as they are backed on non-volatile storage.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096660%2ffind-entries-but-remind-permission-denied%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    /run/ is a "tmpfs" mount. It is a temporary file system location (tmpfs), and the contents will not persist after a reboot.



    You can see this for yourself and confirm it is the case. From terminal, type the command mount. The output will show you the different storage devices and mount types with information about their mount points and underlying filesystem type.



    # mount
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    udev on /dev type devtmpfs (rw,nosuid,relatime,size=1989412k,nr_inodes=497353,mode=755)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404008k,mode=755)
    /dev/sda2 on / type ext4 (rw,relatime,data=ordered)


    In the example above the first five mounts listed - sysfs, proc, udev, devpts, and tmpfs are specialized mounts that are not actually associated with a physical storage disk, but exist in non-persistent memory (ram) to facilitate the operating system and programs needs.



    The sixth one listed, /dev/sda2 is an actual physical disk mount, mounted to the root mount point / with the filesystem type EXT4. This is a persistent mount and the contents will generally survive reboot as they are backed on non-volatile storage.






    share|improve this answer

























      up vote
      0
      down vote













      /run/ is a "tmpfs" mount. It is a temporary file system location (tmpfs), and the contents will not persist after a reboot.



      You can see this for yourself and confirm it is the case. From terminal, type the command mount. The output will show you the different storage devices and mount types with information about their mount points and underlying filesystem type.



      # mount
      sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
      udev on /dev type devtmpfs (rw,nosuid,relatime,size=1989412k,nr_inodes=497353,mode=755)
      devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404008k,mode=755)
      /dev/sda2 on / type ext4 (rw,relatime,data=ordered)


      In the example above the first five mounts listed - sysfs, proc, udev, devpts, and tmpfs are specialized mounts that are not actually associated with a physical storage disk, but exist in non-persistent memory (ram) to facilitate the operating system and programs needs.



      The sixth one listed, /dev/sda2 is an actual physical disk mount, mounted to the root mount point / with the filesystem type EXT4. This is a persistent mount and the contents will generally survive reboot as they are backed on non-volatile storage.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        /run/ is a "tmpfs" mount. It is a temporary file system location (tmpfs), and the contents will not persist after a reboot.



        You can see this for yourself and confirm it is the case. From terminal, type the command mount. The output will show you the different storage devices and mount types with information about their mount points and underlying filesystem type.



        # mount
        sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
        proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
        udev on /dev type devtmpfs (rw,nosuid,relatime,size=1989412k,nr_inodes=497353,mode=755)
        devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
        tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404008k,mode=755)
        /dev/sda2 on / type ext4 (rw,relatime,data=ordered)


        In the example above the first five mounts listed - sysfs, proc, udev, devpts, and tmpfs are specialized mounts that are not actually associated with a physical storage disk, but exist in non-persistent memory (ram) to facilitate the operating system and programs needs.



        The sixth one listed, /dev/sda2 is an actual physical disk mount, mounted to the root mount point / with the filesystem type EXT4. This is a persistent mount and the contents will generally survive reboot as they are backed on non-volatile storage.






        share|improve this answer












        /run/ is a "tmpfs" mount. It is a temporary file system location (tmpfs), and the contents will not persist after a reboot.



        You can see this for yourself and confirm it is the case. From terminal, type the command mount. The output will show you the different storage devices and mount types with information about their mount points and underlying filesystem type.



        # mount
        sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
        proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
        udev on /dev type devtmpfs (rw,nosuid,relatime,size=1989412k,nr_inodes=497353,mode=755)
        devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
        tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404008k,mode=755)
        /dev/sda2 on / type ext4 (rw,relatime,data=ordered)


        In the example above the first five mounts listed - sysfs, proc, udev, devpts, and tmpfs are specialized mounts that are not actually associated with a physical storage disk, but exist in non-persistent memory (ram) to facilitate the operating system and programs needs.



        The sixth one listed, /dev/sda2 is an actual physical disk mount, mounted to the root mount point / with the filesystem type EXT4. This is a persistent mount and the contents will generally survive reboot as they are backed on non-volatile storage.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 at 4:46









        user117197

        11




        11






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f1096660%2ffind-entries-but-remind-permission-denied%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

            How to send String Array data to Server using php in android

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Is anime1.com a legal site for watching anime?