How to disable automount for external devices in openSUSE 13.2?Automount not disabling in Ubuntu 12.04 or...

Cross-referencing enumerate item

How would one country purchase another?

Irish Snap: Variant Rules

How to prevent cutting edges on my TV, HDMI-connected?

Is it safe to remove the bottom chords of a series of garage roof trusses?

Prove your innocence

What is this symbol: semicircles facing eachother

Compelling story with the world as a villain

Cultural before-and-afters

Notepad++ - How to find multiple values on the same line in any permutation

If the first law of thermodynamics ensures conservation of energy, why does it allow systems to lose energy?

Rule based coloured background for labeling in QGIS

LeetCode: Pascal's Triangle C#

Which household object drew this pattern?

Are modern clipless shoes and pedals that much better than toe clips and straps?

Are there any elected officials in the U.S. who are not legislators, judges, or constitutional officers?

Why does The Ancient One think differently about Doctor Strange in Endgame than the film Doctor Strange?

What to say to a student who has failed?

Fancy String Replace

I have a player who yells

Was there ever a treaty between 2 entities with significantly different translations to the detriment of one party?

How to use "Du hast/ Du hattest'?

What is wrong about this application of Kirchhoffs Current Law?

Did the British navy fail to take into account the ballistics correction due to Coriolis force during WW1 Falkland Islands battle?



How to disable automount for external devices in openSUSE 13.2?


Automount not disabling in Ubuntu 12.04 or 13.04How to Disable AutoMount of External DrivesGet password login for opensuse 13.2?Can't start mysql server on OpenSUSE 13.2How to create wifi hotspot in opensuse 13.2Make opensuse 13.2 accept remote logging?opensuse 13.2 installationKDE graphics broken in OpenSuse 13.2OpenSuse 13.2 mysql-workbench refuses to startHow to install lsb_release in opensuse 13.2?Setting disk ownership when Nemo mounts a hot-plugged USB block-device?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







6















Previously I used openSUSE 11.4 and I had an old manual mount. Despite, I copied all config files (I think) I noticed that unknown to /etc/fstab devices are automounted (know I defined as noauto). But since this is big difference in openSUSE 13.2 distro versions I am not so surprised.



So how to do this in openSUSE 13.2? I would like to mount the device manually by mount, and unmount also manually by umount. No other way, no smart timeout on inactivity or anything like that.



I would like to disable that feature at system level, nothing per desktop (for the record I use KDE 3.5, not a joke), so I could be 100% sure this problem will not appear again when working in pure console or another desktop.



Related issue provided by don-crissti: Automount not disabling in Ubuntu 12.04 or 13.04



Update



# more /etc/udev/rules.d/85-no-automount.rules
SUBSYSTEM=="usb", ENV{UDISKS_AUTO}="0"



  • kernel-desktop-devel-3.16.6-2.1.x86_64

  • udev-210-25.5.4.x86_64

  • udisks2-2.1.3-2.1.5.x86_64










share|improve this question



























  • @don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

    – greenoldman
    Dec 21 '14 at 9:03











  • @don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

    – greenoldman
    Dec 21 '14 at 15:23


















6















Previously I used openSUSE 11.4 and I had an old manual mount. Despite, I copied all config files (I think) I noticed that unknown to /etc/fstab devices are automounted (know I defined as noauto). But since this is big difference in openSUSE 13.2 distro versions I am not so surprised.



So how to do this in openSUSE 13.2? I would like to mount the device manually by mount, and unmount also manually by umount. No other way, no smart timeout on inactivity or anything like that.



I would like to disable that feature at system level, nothing per desktop (for the record I use KDE 3.5, not a joke), so I could be 100% sure this problem will not appear again when working in pure console or another desktop.



Related issue provided by don-crissti: Automount not disabling in Ubuntu 12.04 or 13.04



Update



# more /etc/udev/rules.d/85-no-automount.rules
SUBSYSTEM=="usb", ENV{UDISKS_AUTO}="0"



  • kernel-desktop-devel-3.16.6-2.1.x86_64

  • udev-210-25.5.4.x86_64

  • udisks2-2.1.3-2.1.5.x86_64










share|improve this question



























  • @don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

    – greenoldman
    Dec 21 '14 at 9:03











  • @don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

    – greenoldman
    Dec 21 '14 at 15:23














6












6








6


1






Previously I used openSUSE 11.4 and I had an old manual mount. Despite, I copied all config files (I think) I noticed that unknown to /etc/fstab devices are automounted (know I defined as noauto). But since this is big difference in openSUSE 13.2 distro versions I am not so surprised.



So how to do this in openSUSE 13.2? I would like to mount the device manually by mount, and unmount also manually by umount. No other way, no smart timeout on inactivity or anything like that.



I would like to disable that feature at system level, nothing per desktop (for the record I use KDE 3.5, not a joke), so I could be 100% sure this problem will not appear again when working in pure console or another desktop.



Related issue provided by don-crissti: Automount not disabling in Ubuntu 12.04 or 13.04



Update



# more /etc/udev/rules.d/85-no-automount.rules
SUBSYSTEM=="usb", ENV{UDISKS_AUTO}="0"



  • kernel-desktop-devel-3.16.6-2.1.x86_64

  • udev-210-25.5.4.x86_64

  • udisks2-2.1.3-2.1.5.x86_64










share|improve this question
















Previously I used openSUSE 11.4 and I had an old manual mount. Despite, I copied all config files (I think) I noticed that unknown to /etc/fstab devices are automounted (know I defined as noauto). But since this is big difference in openSUSE 13.2 distro versions I am not so surprised.



So how to do this in openSUSE 13.2? I would like to mount the device manually by mount, and unmount also manually by umount. No other way, no smart timeout on inactivity or anything like that.



I would like to disable that feature at system level, nothing per desktop (for the record I use KDE 3.5, not a joke), so I could be 100% sure this problem will not appear again when working in pure console or another desktop.



Related issue provided by don-crissti: Automount not disabling in Ubuntu 12.04 or 13.04



Update



# more /etc/udev/rules.d/85-no-automount.rules
SUBSYSTEM=="usb", ENV{UDISKS_AUTO}="0"



  • kernel-desktop-devel-3.16.6-2.1.x86_64

  • udev-210-25.5.4.x86_64

  • udisks2-2.1.3-2.1.5.x86_64







opensuse automounting






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:37









Community

1




1










asked Nov 29 '14 at 10:10









greenoldmangreenoldman

2,63310 gold badges43 silver badges59 bronze badges




2,63310 gold badges43 silver badges59 bronze badges
















  • @don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

    – greenoldman
    Dec 21 '14 at 9:03











  • @don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

    – greenoldman
    Dec 21 '14 at 15:23



















  • @don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

    – greenoldman
    Dec 21 '14 at 9:03











  • @don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

    – greenoldman
    Dec 21 '14 at 15:23

















@don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

– greenoldman
Dec 21 '14 at 9:03





@don_crissti, thank you, I tried just fixing the typo (it was in original post you linked), and I tried your version, with both pendrive is still automounted.

– greenoldman
Dec 21 '14 at 9:03













@don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

– greenoldman
Dec 21 '14 at 15:23





@don_crissti, I am grateful nevertheless for your help. Maybe OS has some bug or issue which requires other handling.

– greenoldman
Dec 21 '14 at 15:23










3 Answers
3






active

oldest

votes


















7















The automounting you see on a modern Linux distribution like OpenSUSE or Fedora is implemented by the udisks2 service.



Thus, you can disable that feature on system level via stopping that service, e.g.:



# systemctl stop udisks2.service


To verify that it is stopped:



# systemctl status udisks2


Of course, this change isn't permanent.



The udisks2 service isn't even enabled, by default and thus isn't autostarted during boot. Instead, it is activated via Dbus (e.g. when the first user starts a desktop session).



Thus, if you really hate udisks2:



$ systemctl mask udisks2


This will block all starts, including manual ones.



Motiviation



Why would one want to disable automounting via the fine disks2 disk manager?



There are several good reasons, e.g.




  • work around a udisks2 automount bug1

  • do forensics work on some USB drives

  • rescue data from a corrupted FS on a USB device (where the automount would lead to more destruction)



1. e.g. on Fedora 25, when connecting 2 USB devices that are a Btrfs RAID-1 mirror, the mirror is automounted unter /run/media/juser/mirror alright - BUT it also mounted a second time under /run/media/juser/mirror1 when unlocking the screen ... while the first mount is still live ...






share|improve this answer



































    0















    # /etc/udev/rules.d/99-noautomount.rules
    ENV{UDISKS_PRESENTATION_HIDE}="1"
    ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
    ENV{UDISKS_AUTOMOUNT_HINT}="never"
    ENV{UDISKS_SYSTEM_INTERNAL}="1"
    ENV{UDISKS_IGNORE}="1"
    ENV{UDISKS_AUTO}="0"


    Edit:



    https://www.systutorials.com/docs/linux/man/7-udisks/ :



    UDISKS_PRESENTATION_HIDE
    If set to 1 this is a hint to presentation level software that the device should not be shown to the user.

    UDISKS_PRESENTATION_NOPOLICY
    If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device).

    UDISKS_AUTOMOUNT_HINT
    A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it.

    UDISKS_SYSTEM_INTERNAL
    If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount).


    https://www.systutorials.com/docs/linux/man/8-udisks/ :



    UDISKS_IGNORE
    If set, this overrides the value of the HintIgnore property.

    UDISKS_AUTO
    If set, this overrides the value of the HintAuto property.





    share|improve this answer










    New contributor



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

















    • 2





      Can you also explain why that works?

      – RalfFriedl
      2 days ago











    • I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

      – Atila Romero
      16 hours ago



















    -1















    simple reason is. The permitions on udisk2 are wrong if you mount usb vfat.
    And the documentation how to modify that is lo level.



    Using: raspberry 3, VERSION="9 (stretch)"



    I tried to use small SVN repo on USB Flash drive. I always got the problem that apache (www-data) could not access the repo. Because the permitions are always set only for user pi (pi:pi). I did not find where i chan change this.



    Now autoload is disabled and i mount the drive myself. Then the permitions are ok. (root:users)






    share|improve this answer























    • 2





      The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

      – Scott
      Nov 24 '18 at 19:15














    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f170549%2fhow-to-disable-automount-for-external-devices-in-opensuse-13-2%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    7















    The automounting you see on a modern Linux distribution like OpenSUSE or Fedora is implemented by the udisks2 service.



    Thus, you can disable that feature on system level via stopping that service, e.g.:



    # systemctl stop udisks2.service


    To verify that it is stopped:



    # systemctl status udisks2


    Of course, this change isn't permanent.



    The udisks2 service isn't even enabled, by default and thus isn't autostarted during boot. Instead, it is activated via Dbus (e.g. when the first user starts a desktop session).



    Thus, if you really hate udisks2:



    $ systemctl mask udisks2


    This will block all starts, including manual ones.



    Motiviation



    Why would one want to disable automounting via the fine disks2 disk manager?



    There are several good reasons, e.g.




    • work around a udisks2 automount bug1

    • do forensics work on some USB drives

    • rescue data from a corrupted FS on a USB device (where the automount would lead to more destruction)



    1. e.g. on Fedora 25, when connecting 2 USB devices that are a Btrfs RAID-1 mirror, the mirror is automounted unter /run/media/juser/mirror alright - BUT it also mounted a second time under /run/media/juser/mirror1 when unlocking the screen ... while the first mount is still live ...






    share|improve this answer
































      7















      The automounting you see on a modern Linux distribution like OpenSUSE or Fedora is implemented by the udisks2 service.



      Thus, you can disable that feature on system level via stopping that service, e.g.:



      # systemctl stop udisks2.service


      To verify that it is stopped:



      # systemctl status udisks2


      Of course, this change isn't permanent.



      The udisks2 service isn't even enabled, by default and thus isn't autostarted during boot. Instead, it is activated via Dbus (e.g. when the first user starts a desktop session).



      Thus, if you really hate udisks2:



      $ systemctl mask udisks2


      This will block all starts, including manual ones.



      Motiviation



      Why would one want to disable automounting via the fine disks2 disk manager?



      There are several good reasons, e.g.




      • work around a udisks2 automount bug1

      • do forensics work on some USB drives

      • rescue data from a corrupted FS on a USB device (where the automount would lead to more destruction)



      1. e.g. on Fedora 25, when connecting 2 USB devices that are a Btrfs RAID-1 mirror, the mirror is automounted unter /run/media/juser/mirror alright - BUT it also mounted a second time under /run/media/juser/mirror1 when unlocking the screen ... while the first mount is still live ...






      share|improve this answer






























        7














        7










        7









        The automounting you see on a modern Linux distribution like OpenSUSE or Fedora is implemented by the udisks2 service.



        Thus, you can disable that feature on system level via stopping that service, e.g.:



        # systemctl stop udisks2.service


        To verify that it is stopped:



        # systemctl status udisks2


        Of course, this change isn't permanent.



        The udisks2 service isn't even enabled, by default and thus isn't autostarted during boot. Instead, it is activated via Dbus (e.g. when the first user starts a desktop session).



        Thus, if you really hate udisks2:



        $ systemctl mask udisks2


        This will block all starts, including manual ones.



        Motiviation



        Why would one want to disable automounting via the fine disks2 disk manager?



        There are several good reasons, e.g.




        • work around a udisks2 automount bug1

        • do forensics work on some USB drives

        • rescue data from a corrupted FS on a USB device (where the automount would lead to more destruction)



        1. e.g. on Fedora 25, when connecting 2 USB devices that are a Btrfs RAID-1 mirror, the mirror is automounted unter /run/media/juser/mirror alright - BUT it also mounted a second time under /run/media/juser/mirror1 when unlocking the screen ... while the first mount is still live ...






        share|improve this answer















        The automounting you see on a modern Linux distribution like OpenSUSE or Fedora is implemented by the udisks2 service.



        Thus, you can disable that feature on system level via stopping that service, e.g.:



        # systemctl stop udisks2.service


        To verify that it is stopped:



        # systemctl status udisks2


        Of course, this change isn't permanent.



        The udisks2 service isn't even enabled, by default and thus isn't autostarted during boot. Instead, it is activated via Dbus (e.g. when the first user starts a desktop session).



        Thus, if you really hate udisks2:



        $ systemctl mask udisks2


        This will block all starts, including manual ones.



        Motiviation



        Why would one want to disable automounting via the fine disks2 disk manager?



        There are several good reasons, e.g.




        • work around a udisks2 automount bug1

        • do forensics work on some USB drives

        • rescue data from a corrupted FS on a USB device (where the automount would lead to more destruction)



        1. e.g. on Fedora 25, when connecting 2 USB devices that are a Btrfs RAID-1 mirror, the mirror is automounted unter /run/media/juser/mirror alright - BUT it also mounted a second time under /run/media/juser/mirror1 when unlocking the screen ... while the first mount is still live ...







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jul 3 '17 at 20:35

























        answered Jul 3 '17 at 20:30









        maxschlepzigmaxschlepzig

        36.1k35 gold badges149 silver badges221 bronze badges




        36.1k35 gold badges149 silver badges221 bronze badges




























            0















            # /etc/udev/rules.d/99-noautomount.rules
            ENV{UDISKS_PRESENTATION_HIDE}="1"
            ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
            ENV{UDISKS_AUTOMOUNT_HINT}="never"
            ENV{UDISKS_SYSTEM_INTERNAL}="1"
            ENV{UDISKS_IGNORE}="1"
            ENV{UDISKS_AUTO}="0"


            Edit:



            https://www.systutorials.com/docs/linux/man/7-udisks/ :



            UDISKS_PRESENTATION_HIDE
            If set to 1 this is a hint to presentation level software that the device should not be shown to the user.

            UDISKS_PRESENTATION_NOPOLICY
            If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device).

            UDISKS_AUTOMOUNT_HINT
            A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it.

            UDISKS_SYSTEM_INTERNAL
            If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount).


            https://www.systutorials.com/docs/linux/man/8-udisks/ :



            UDISKS_IGNORE
            If set, this overrides the value of the HintIgnore property.

            UDISKS_AUTO
            If set, this overrides the value of the HintAuto property.





            share|improve this answer










            New contributor



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

















            • 2





              Can you also explain why that works?

              – RalfFriedl
              2 days ago











            • I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

              – Atila Romero
              16 hours ago
















            0















            # /etc/udev/rules.d/99-noautomount.rules
            ENV{UDISKS_PRESENTATION_HIDE}="1"
            ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
            ENV{UDISKS_AUTOMOUNT_HINT}="never"
            ENV{UDISKS_SYSTEM_INTERNAL}="1"
            ENV{UDISKS_IGNORE}="1"
            ENV{UDISKS_AUTO}="0"


            Edit:



            https://www.systutorials.com/docs/linux/man/7-udisks/ :



            UDISKS_PRESENTATION_HIDE
            If set to 1 this is a hint to presentation level software that the device should not be shown to the user.

            UDISKS_PRESENTATION_NOPOLICY
            If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device).

            UDISKS_AUTOMOUNT_HINT
            A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it.

            UDISKS_SYSTEM_INTERNAL
            If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount).


            https://www.systutorials.com/docs/linux/man/8-udisks/ :



            UDISKS_IGNORE
            If set, this overrides the value of the HintIgnore property.

            UDISKS_AUTO
            If set, this overrides the value of the HintAuto property.





            share|improve this answer










            New contributor



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

















            • 2





              Can you also explain why that works?

              – RalfFriedl
              2 days ago











            • I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

              – Atila Romero
              16 hours ago














            0














            0










            0









            # /etc/udev/rules.d/99-noautomount.rules
            ENV{UDISKS_PRESENTATION_HIDE}="1"
            ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
            ENV{UDISKS_AUTOMOUNT_HINT}="never"
            ENV{UDISKS_SYSTEM_INTERNAL}="1"
            ENV{UDISKS_IGNORE}="1"
            ENV{UDISKS_AUTO}="0"


            Edit:



            https://www.systutorials.com/docs/linux/man/7-udisks/ :



            UDISKS_PRESENTATION_HIDE
            If set to 1 this is a hint to presentation level software that the device should not be shown to the user.

            UDISKS_PRESENTATION_NOPOLICY
            If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device).

            UDISKS_AUTOMOUNT_HINT
            A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it.

            UDISKS_SYSTEM_INTERNAL
            If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount).


            https://www.systutorials.com/docs/linux/man/8-udisks/ :



            UDISKS_IGNORE
            If set, this overrides the value of the HintIgnore property.

            UDISKS_AUTO
            If set, this overrides the value of the HintAuto property.





            share|improve this answer










            New contributor



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









            # /etc/udev/rules.d/99-noautomount.rules
            ENV{UDISKS_PRESENTATION_HIDE}="1"
            ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
            ENV{UDISKS_AUTOMOUNT_HINT}="never"
            ENV{UDISKS_SYSTEM_INTERNAL}="1"
            ENV{UDISKS_IGNORE}="1"
            ENV{UDISKS_AUTO}="0"


            Edit:



            https://www.systutorials.com/docs/linux/man/7-udisks/ :



            UDISKS_PRESENTATION_HIDE
            If set to 1 this is a hint to presentation level software that the device should not be shown to the user.

            UDISKS_PRESENTATION_NOPOLICY
            If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device).

            UDISKS_AUTOMOUNT_HINT
            A variable to influence whether a device should be automounted. Possible values include "always" (to hint that a device should always be automounted) and "never" (to hint that a device should never be automounted). Note that this is only a hint - the auto-mounter might not honor it.

            UDISKS_SYSTEM_INTERNAL
            If set, this will override the usual bus type based detection of whether a device is considered "system internal". "0" means "removable" (i. e. eligible for automounting, and normal users can mount), any other value means "system internal" (i. e. no automounting, and only administrators can mount).


            https://www.systutorials.com/docs/linux/man/8-udisks/ :



            UDISKS_IGNORE
            If set, this overrides the value of the HintIgnore property.

            UDISKS_AUTO
            If set, this overrides the value of the HintAuto property.






            share|improve this answer










            New contributor



            Atila Romero 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 16 hours ago





















            New contributor



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








            answered 2 days ago









            Atila RomeroAtila Romero

            12 bronze badges




            12 bronze badges




            New contributor



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




            New contributor




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













            • 2





              Can you also explain why that works?

              – RalfFriedl
              2 days ago











            • I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

              – Atila Romero
              16 hours ago














            • 2





              Can you also explain why that works?

              – RalfFriedl
              2 days ago











            • I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

              – Atila Romero
              16 hours ago








            2




            2





            Can you also explain why that works?

            – RalfFriedl
            2 days ago





            Can you also explain why that works?

            – RalfFriedl
            2 days ago













            I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

            – Atila Romero
            16 hours ago





            I edited the answer to include some man page descriptions. The UDISKS_PRESENTATION_HIDE and UDISKS_IGNORE may be irrelevant.

            – Atila Romero
            16 hours ago











            -1















            simple reason is. The permitions on udisk2 are wrong if you mount usb vfat.
            And the documentation how to modify that is lo level.



            Using: raspberry 3, VERSION="9 (stretch)"



            I tried to use small SVN repo on USB Flash drive. I always got the problem that apache (www-data) could not access the repo. Because the permitions are always set only for user pi (pi:pi). I did not find where i chan change this.



            Now autoload is disabled and i mount the drive myself. Then the permitions are ok. (root:users)






            share|improve this answer























            • 2





              The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Nov 24 '18 at 19:15
















            -1















            simple reason is. The permitions on udisk2 are wrong if you mount usb vfat.
            And the documentation how to modify that is lo level.



            Using: raspberry 3, VERSION="9 (stretch)"



            I tried to use small SVN repo on USB Flash drive. I always got the problem that apache (www-data) could not access the repo. Because the permitions are always set only for user pi (pi:pi). I did not find where i chan change this.



            Now autoload is disabled and i mount the drive myself. Then the permitions are ok. (root:users)






            share|improve this answer























            • 2





              The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Nov 24 '18 at 19:15














            -1














            -1










            -1









            simple reason is. The permitions on udisk2 are wrong if you mount usb vfat.
            And the documentation how to modify that is lo level.



            Using: raspberry 3, VERSION="9 (stretch)"



            I tried to use small SVN repo on USB Flash drive. I always got the problem that apache (www-data) could not access the repo. Because the permitions are always set only for user pi (pi:pi). I did not find where i chan change this.



            Now autoload is disabled and i mount the drive myself. Then the permitions are ok. (root:users)






            share|improve this answer















            simple reason is. The permitions on udisk2 are wrong if you mount usb vfat.
            And the documentation how to modify that is lo level.



            Using: raspberry 3, VERSION="9 (stretch)"



            I tried to use small SVN repo on USB Flash drive. I always got the problem that apache (www-data) could not access the repo. Because the permitions are always set only for user pi (pi:pi). I did not find where i chan change this.



            Now autoload is disabled and i mount the drive myself. Then the permitions are ok. (root:users)







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 25 '18 at 14:35

























            answered Nov 24 '18 at 16:41









            Arnold BraunArnold Braun

            11 bronze badge




            11 bronze badge











            • 2





              The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Nov 24 '18 at 19:15














            • 2





              The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Nov 24 '18 at 19:15








            2




            2





            The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

            – Scott
            Nov 24 '18 at 19:15





            The problem is that the system is automatically mounting a device that the OP doesn't want to be automatically mounted — and you say it's a permissions issue?  Can you provide a reference to support that claim, or even an argument as to how it makes sense? Please do not respond in comments; edit your answer to make it clearer and more complete.

            – Scott
            Nov 24 '18 at 19:15


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f170549%2fhow-to-disable-automount-for-external-devices-in-opensuse-13-2%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

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...