El 17/03/13 20:08, Basil Chupin escribió:

Thanks for this bit of information.

I didn't know that. But is this something which has only happened now because of the change of where the device(s) are mounted or has this always been this way (ie /run/media/.....) being a "copy" of the mounting point?

/var/run is a symlink to /run... which is provided as stop-gap backward compatibility kludge. some applications and standards expect /var/run to exist. /run is the official new location, yet some apps still have not been updated to reflect this fact. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin said the following on 03/17/2013 07:08 PM:

On 17/03/13 16:44, Andrey Borzenkov wrote:

...

� Sun, 17 Mar 2013 16:16:18 +1100 Basil Chupin �����:

...

In another thread I mentioned that when I switch on my external 2TB USB WD HDD, Dolphin accesses it and displays its contents to me; but then when I go to use mc (Midnight Commander) this device is no longer mounted in /media as it has been in past many years but now is found in /var/run/media/<username>/<devicename> [in this case the volume name is WD].

Quite by accident a few minutes ago ('cause I am having another hassle, to be describe later) I discovered that the device is ALSO mounted in 'run/media/<username>/<device>'.

/run and /var/run refer to exactly the same filesystem. You can consider them aliases.

Thanks for this bit of information.

I didn't know that. But is this something which has only happened now because of the change of where the device(s) are mounted or has this always been this way (ie /run/media/.....) being a "copy" of the mounting point?

Methinks they are the same inode by different names: $ ls -lid /var/run /run 2370 drwxr-xr-x 24 root root 760 Mar 17 17:51 /run 2370 drwxr-xr-x 24 root root 760 Mar 17 17:51 /var/run And a tmpfs at that! See man (5) tmpfiles.d man (8) systemd-tmpfiles The mount point depending on which desktop manager you use seems like lunacy to me; at the very least it should be a system configuration parameter. At worst something in udev or udisks rules .. Oh, wait ..... -- This is not a novel to be tossed aside lightly. It should be thrown with great force. -- Dorothy Parker -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez said the following on 03/17/2013 08:48 PM:

El 17/03/13 21:25, Anton Aylward escribió:

...

The mount point depending on which desktop manager you use seems like lunacy to me.

It does not depend on the desktop, but on what udisks version (1 or 2) you are running...

Good game, good game. I have BOTH on my system. It seems which one is used, as if the difference between /media and /run/media (hard coded into it!) is a ball-buster thanks to the ability to symlink) depends on which desktop I use. What was that saying about 'a difference that makes no difference ....' Symlinking may destroy the tree nature of the FS but its the sysadmin's friend :-) -- "You learn more from geting your butt kicked than from getting it kissed". -- Tom Hank. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Sorry to reopen older thread... Dne Ne 17. března 2013 22:05:58, Anton Aylward napsal(a):

Cristian Rodríguez said the following on 03/17/2013 08:48 PM:

...

El 17/03/13 21:25, Anton Aylward escribió:

...

The mount point depending on which desktop manager you use seems like lunacy to me.

It does not depend on the desktop, but on what udisks version (1 or 2) you are running...

So where does the org.freedesktop "database" live?

I don't mean the polkit stuff, that just "access control" http://udisks.freedesktop.org/docs/latest/udisks-polkit-actions.html I mean the stuff mentioned in

http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.File system.html#gdbus-property-org-freedesktop-UDisks2-Filesystem.MountPoints

such as

http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.File system.html#gdbus-property-org-freedesktop-UDisks2-Filesystem.MountPoints

Which you see in action but using the command 'udisksctl monitor' and inserting the USB drive

As far as I can see there is n database, that this is all hypothetical with those strings, including all the 'org.freedesktop ones, hard coded.

Which makes me wonder what's the point.

According to https://bugzilla.novell.com/show_bug.cgi?id=809837 this is a bug, which should be already fixed. I have openSUSE 12.3 (upgraded from 12.2) with KDE 4.10.1, but I still see removable media in /var/run/username/medainame and not in /media as I was used to for quite a long time... $ rpm -qa | grep udisk udisks-1.0.4-11.1.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 What do I do wrong? How to get medias back to /media? I didn't do any changes to udisk rules. Have a nice day, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

Dne Ne 31. března 2013 09:44:00 jste napsal(a):

"Vojtěch Zeisek" wrote:

...

Dne Ne 17. března 2013 22:05:58, Anton Aylward napsal(a):

...

Cristian Rodríguez said the following on 03/17/2013 08:48 PM:

...

El 17/03/13 21:25, Anton Aylward escribió:

...

The mount point depending on which desktop manager you use seems

like

...

...

...

lunacy to me.

It does not depend on the desktop, but on what udisks version (1 or

2)

...

...

you are running...

So where does the org.freedesktop "database" live?

I don't mean the polkit stuff, that just "access control" http://udisks.freedesktop.org/docs/latest/udisks-polkit-actions.html I mean the stuff mentioned in

http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.Fil e

system.html#gdbus-property-org-freedesktop-UDisks2-Filesystem.MountPoints

...

such as

http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.Fil e

system.html#gdbus-property-org-freedesktop-UDisks2-Filesystem.MountPoints

...

Which you see in action but using the command 'udisksctl monitor' and inserting the USB drive

As far as I can see there is n database, that this is all

hypothetical

...

with those strings, including all the 'org.freedesktop ones, hard

coded.

...

Which makes me wonder what's the point.

According to https://bugzilla.novell.com/show_bug.cgi?id=809837 this is a bug, which should be already fixed. I have openSUSE 12.3 (upgraded from 12.2) with KDE 4.10.1, but I still see removable media in /var/run/username/medainame and not in /media as I was used to for quite a long time... $ rpm -qa | grep udisk udisks-1.0.4-11.1.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 What do I do wrong? How to get medias back to /media? I didn't do any changes to udisk rules. Have a nice day, Vojtěch

The bugzilla says you have to both get the update and edit the rules. You say you didn't edit the rules and you wonder why it doesn't work?

Greg

I'm sorry for my blindness and poor knowledge of udev rules, but from the discussion in Bugzilla I don't see where should I put what. Yes, to /etc/udev/rules.d/, but what next? Unless it needs some custom actions like manual edits of udev rules, I don't consider the bug as fixed... All the best, Vojtěch PS: Greg, sorry for PM first, I didn't check correct reply to address... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

Patrick Shanahan said the following on 03/31/2013 05:31 PM:

I created:

/etc/udev/rules.d/99-correct-media-mount-point.rules including:

** INCLUDING ** ???? So what else was in there? Might it be critical? I hate it when you phrase things like that and leave us hanging ... Oh, and is one of Linda's "need to reboot" cases? -- "Education must precede motivation." Jim Rohn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Sun, 31 Mar 2013 19:02:25 -0400 Patrick Shanahan пишет:

* Anton Aylward [03-31-13 17:51]:

...

Patrick Shanahan said the following on 03/31/2013 05:31 PM:

...

I created:

/etc/udev/rules.d/99-correct-media-mount-point.rules including:

** INCLUDING ** ????

So what else was in there? Might it be critical?

I hate it when you phrase things like that and leave us hanging ...

Ah, "including" one liner :^), ie: that's all folks!

##> cat /etc/udev/rules.d/99-correct-media-mount-point.rules ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

...

Oh, and is one of Linda's "need to reboot" cases?

I didn't reboot and the mount moved from previously /run/media/paka/<device-name> to /media/<device-name> on the *same* boot, ie: no reboot was necessary.

no guarantees, ymmv

if you want to be sure it is picked up udevadm control --reload -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [05-27-13 19:35]:

On Sunday, 2013-03-31 at 19:02 -0400, Patrick Shanahan wrote:

...

Ah, "including" one liner :^), ie: that's all folks!

##> cat /etc/udev/rules.d/99-correct-media-mount-point.rules ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

...

Oh, and is one of Linda's "need to reboot" cases?

I didn't reboot and the mount moved from previously /run/media/paka/<device-name> to /media/<device-name> on the *same* boot, ie: no reboot was necessary.

no guarantees, ymmv

Can you verify something on your side, please?

I'm using that on a virtual test machine (12.3), and doing that I noticed that /media is not a tmpfs.

Is this normal?

It is not tmpfs on my system.

In my current 12.1 it is a tmpfs:

Telcontar:~ # mount | grep media tmpfs on /media type tmpfs (rw,nosuid,nodev,relatime,mode=755) Telcontar:~ #

But not in 12.3:

eleanor3:~ # mount | grep media eleanor3:~ #

Now I don't know if this happens on all 12.3 systems, or if it is a side effect of applying this rule... :-?

I cannot say, but I have a vbox of 13.1/factory which "/media" is not tmpfs....

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 28 May 2013 03:41:47 +0200 (CEST) "Carlos E. R." wrote: ...

Now I wonder... where are these tmpfs defined? Not in fstab.

Try this: http://www.freedesktop.org/software/systemd/man/tmpfiles.d.html http://www.freedesktop.org/software/systemd/man/systemd-tmpfiles.html -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-05-28 04:16, Cristian Rodr￭guez wrote:

El 27/05/13 21:56, Rajko escribi￳:

...

On Tue, 28 May 2013 03:41:47 +0200 (CEST) "Carlos E. R." <> wrote: ...

...

Now I wonder... where are these tmpfs defined? Not in fstab.

Try this: http://www.freedesktop.org/software/systemd/man/tmpfiles.d.html http://www.freedesktop.org/software/systemd/man/systemd-tmpfiles.html

...

Those have nothing to do with tmpfs mounts.

Ok, then where is it done? Because the files mentioned in those man pages do exist in 12.3: eleanor3:~ # ls /etc/tmpfiles.d/*.conf /run/tmpfiles.d/*.conf \ /usr/lib/tmpfiles.d/*.conf ls: cannot access /run/tmpfiles.d/*.conf: No such file or directory /etc/tmpfiles.d/remove-systemd-private.conf /usr/lib/tmpfiles.d/legacy.conf /usr/lib/tmpfiles.d/nscd.conf /usr/lib/tmpfiles.d/parallel-printer.conf /usr/lib/tmpfiles.d/screen.conf /usr/lib/tmpfiles.d/systemd.conf /usr/lib/tmpfiles.d/tmp.conf /usr/lib/tmpfiles.d/x11.conf eleanor3:~ # And they do contain definitions to create some tmpfs, like the one used to mount devices: eleanor3:~ # grep "run/user" /etc/tmpfiles.d/*.conf \ /run/tmpfiles.d /*.conf /usr/lib/tmpfiles.d/*.conf grep: /run/tmpfiles.d/*.conf: No such file or directory /usr/lib/tmpfiles.d/systemd.conf:d /run/user 0755 root root ~10d eleanor3:~ # :-? - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGkFzMACgkQIvFNjefEBxoThQCfd1zE1yqG3HiprNGi2kVk6rzq RYYAnjJbGMtJzP4DWrf0tdW+EEwFu9JZ =m/nL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-05-28 04:41, Cristian Rodríguez wrote:

El 27/05/13 22:32, Carlos E. R. escribió:

...

And they do contain definitions to create some tmpfs, like the one used to mount devices:

No, they contain definitions to create directories that may or may not be in tmpfs ..

systemd-tmpfiles does not have the capability of creating mount points.

No, that's not what we are talking about. The mount points in /media are created already, in /media, not in 'run/media/<username>/<device>', as we want. The problem is that in 12.1 /media was a tmpfs, and in 12.3 it is not. Why? Is this an intentional change, or is it a slip and should we create "/media" ourselves as a tmpfs (and how), and create a bugreport about it? - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGkHsoACgkQIvFNjefEBxrsvwCaA86v419bytbbTOWdC7gjDMna KcQAn0XowMrZz8DMcHvlaivxkN/yI/pG =Gh/T -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tuesday 28 May 2013, Andrey Borzenkov wrote:

В Tue, 28 May 2013 05:04:42 +0200

"Carlos E. R." пишет:

...

The problem is that in 12.1 /media was a tmpfs, and in 12.3 it is not. Why?

Is this an intentional change, or is it a slip and should we create "/media" ourselves as a tmpfs (and how), and create a bugreport about it?

commit 231931ffba1bca9d8759bbd6f797e56f8c6971fa Author: Lennart Poettering Date: Tue Mar 27 17:04:22 2012 +0200

units: don't mount tmpfs on /media anymore

udisks2 doesn't use /media anymore, instead mounts removable media in a user-private directory beneath /run. /media is hence mostly obsolete and hence it makes little sense to continue to mount a tmpfs to it.

And how can we auto-mount removable medias now so that they are visible for all users, using persistent mount point names (independent of a user's name)?

Distributions should consider dropping the mount point entirely since nothing uses it anymore.

cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

"Carlos E. R." wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2013-05-28 06:18, Andrey Borzenkov wrote:

...

В Tue, 28 May 2013 05:04:42 +0200 "Carlos E. R." <> пишет:

...

The problem is that in 12.1 /media was a tmpfs, and in 12.3 it is not. Why?

...

Is this an intentional change, or is it a slip and should we create "/media" ourselves as a tmpfs (and how), and create a bugreport about it?

commit 231931ffba1bca9d8759bbd6f797e56f8c6971fa Author: Lennart Poettering Date: Tue Mar 27 17:04:22 2012 +0200

units: don't mount tmpfs on /media anymore

udisks2 doesn't use /media anymore, instead mounts removable media in a user-private directory beneath /run. /media is hence mostly obsolete and hence it makes little sense to continue to mount a tmpfs to it.

Distributions should consider dropping the mount point entirely since nothing uses it anymore.

So, it is intentional.

However, it is wrong, because: if we create:

/etc/udev/rules.d/99-correct-media-mount-point.rules

with this content:

ENV{ID_FS_USAGE}=="filesystem|other|crypto", \ ENV{UDISKS_FILESYSTEM_SHARED}="1"

(one line, mail wraps)

and run

udevadm control --reload

then media is again mounted in /media. I understand that this works after a patch, so we need to reconsider that "/media" removal, and how to create it again as a tmpfs.

Interesting, sounds like a couple of bugzilla's should be opened: one for 2.3 and one for factory. I say 2 since I suspect each will need a different fix. The patch you refer to is actually a back port from current udisks2 upstream as I recall, so Lennart's patch should be reverted upstream as well. Then the patch reversion should flow into factory automatically. I don't have a theory as to what should happen in 12.3. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 16:01 +0200, Carlos E. R. wrote:

On 2013-05-28 15:38, Greg Freemyer wrote:

...

Interesting, sounds like a couple of bugzilla's should be opened: one for 2.3 and one for factory. I say 2 since I suspect each will need a different fix.

I can write the 12.3 one. I don't have a factory system installed at the moment.

Against what component, I wonder? Systemd?

There is no systemd component. I'll use "Basesystem". Done: Bug 821989 - About the /media directory in 12.3 - tmpfs or not? - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGkv3QACgkQtTMYHG2NR9Ud7gCffRzeRAk3mQ/aHxCZx6JTkyXs iKAAnRxi8QQc1CWaNf6fmwRf+/Z+CWIN =1cUk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 19:07 +0400, Andrey Borzenkov wrote:

В Tue, 28 May 2013 16:01:50 +0200 "Carlos E. R." <> пишет:

...

Dunno... I would be happy if they simply tell me where to configure it myself.

What's wrong with /etc/fstab?

That 12.1 did not do it that way? :-) It is created in /etc/init.d/boot.localfs: if test -d /media && ! mountpoint -q /media; then mount -n -t tmpfs -o mode=0755,nodev,nosuid tmpfs /media fi - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGky88ACgkQtTMYHG2NR9Xi1wCfYW0iZWXJfSVQSl6EVrYJStex PSMAnRSJXYG30TTn1D6gOKeHsBGgJHyc =pkoX -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: On Tuesday, 2013-05-28 at 19:50 +0400, Andrey Borzenkov wrote:

В Tue, 28 May 2013 17:22:55 +0200 (CEST) "Carlos E. R." <> пишет:

...

-----BEGIN PGP SIGNED MESSAGE-----

(there is something in your signature that confuses Alpine, it says the signature is wrong. However, Thunderbird says it is OK. Could be the extra line with garbage after the pgp block.)

...

...

What's wrong with /etc/fstab?

That 12.1 did not do it that way? :-)

And what's wrong with /etc/fstab in 12.3?

That none of the existing tmpfs in 12.3 is not done there? :-) - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk1dIACgkQtTMYHG2NR9WKRQCcCa+Lxrkp0diGAJGyqkMeVj1B u24AnjN6PxuBgalR2+fkrmf/Rv6kUbi1 =Nw41 -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 13:12 -0400, Cristian Rodríguez wrote:

El 28/05/13 11:22, Carlos E. R. escribió:

...

On Tuesday, 2013-05-28 at 19:07 +0400, Andrey Borzenkov wrote:

...

В Tue, 28 May 2013 16:01:50 +0200 "Carlos E. R." <> пишет:

...

...

Dunno... I would be happy if they simply tell me where to configure it myself.

What's wrong with /etc/fstab?

That 12.1 did not do it that way? :-)

It is created in /etc/init.d/boot.localfs:

if test -d /media && ! mountpoint -q /media; then mount -n -t tmpfs -o mode=0755,nodev,nosuid tmpfs /media fi

boot.localfs is only used by sysvinit.

I know that. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk5ksACgkQtTMYHG2NR9XzTgCgh670uSqY5CkXHIbAf86u8SHz f6QAn1l3u/X23gxdMesSJDRGVNtpjLl8 =GyE7 -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 12:48 -0400, Greg Freemyer wrote:

On Tue, May 28, 2013 at 11:07 AM, Andrey Borzenkov <> wrote:

...

В Tue, 28 May 2013 16:01:50 +0200 "Carlos E. R." <> пишет:

...

...

The patch you refer to is actually a back port from current udisks2 upstream as I recall, so Lennart's patch should be reverted upstream as well.

Then the patch reversion should flow into factory automatically.

I don't have a theory as to what should happen in 12.3.

Dunno... I would be happy if they simply tell me where to configure it myself.

What's wrong with /etc/fstab?

Doesn't it require a line per unique thumbdrive / external USB drive?

If a person has dozens / hundreds of those, then he has to maintain hundreds of /etc/fstab lines.

And if he buys a new one, he has to edit /etc/fstab each time?

You are not reading the thread correctly. Andrey is suggesting that I create /media as a tmpfs in fstab, he is not talking of mounting external media via fstab - nor am I. However, it is possible to do what you suggest: just label all the devices with the same name, and mount by label. As long as you don't need two of them, it works. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk4skACgkQtTMYHG2NR9UpbgCggllDtG0WGW+JtZjvpOPUDgNL 2XEAnib41ax1JrDg77TXy6fGC/qAJIJT =7uHT -----END PGP SIGNATURE-----

El 28/05/13 09:06, Carlos E. R. escribió:

So, it is intentional.

However, it is wrong, because: if we create:

/etc/udev/rules.d/99-correct-media-mount-point.rules

with this content:

ENV{ID_FS_USAGE}=="filesystem|other|crypto", \ ENV{UDISKS_FILESYSTEM_SHARED}="1"

(one line, mail wraps)

then media is again mounted in /media. I understand that this works after a patch, so we need to reconsider that "/media" removal, and how to create it again as a tmpfs.

No, adding custom udev rules to modify default behavior means you are on your own. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 19:12 +0200, Istvan Gabor wrote:

Hello:

I confess I have no idea what udisks2 is, and the latest version of openSUSE I have is 12.1. I also use 11.2 on other machines. My goal is to be able to use my SUSE computer in the same way as I used it in the last ten years . Changes like these seems for me arbitrary and unnecessary. In 12.1 /media is a tmpfs. That means I can not create my floppy directory in it like in previous versions.

You were assumed never to create your mountpoints in /media, you should leave that directory alone. For manual mounting you were assumed to use /mnt instead.

Then I read here that in newer versions removable media is not mounted in media but some other /run/? directories. Why is that good? Who prefers to navigate to some ../../../../ directory instead of /media? And as I understand correctly the media mounted by user A can't be read by user B. On a desktop. Why? That is if I mount a CD and switch user, that user can not read the CD? Do we really want this nonsense?

Yes, that's right. On some setups, you want to keep media private; on some they need it shared. There is no easy to find switch to change that behaviour. At least, there is support for using /media by some devs, while some other devs (Cristian) want to punish us users for some unknown sins, perhaps, and decide what is best for us.

I start to think that it would be more benefit for linux if those developers of todays did not do programing.

:-} - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk56QACgkQtTMYHG2NR9UokgCfXBf5PKyswjNQ8jEs4AxFOnju ekcAn0TH6r5PE36f9p/Kd/7TkD2KvYEq =wDhF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----Original Message----- From: Carlos E. R. To: oS-en Subject: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Tue, 28 May 2013 05:04:42 +0200 ..... The mount points in /media are created already, in /media, not in 'run/media/<username>/<device>', as we want. -----Original Message----- Just wondering: which "..../<username>/...." If user_A, user_B, user_C, user_D are currently logged in, and you insert a mem-stick, cd or dvd where does that appear, and to whom is it reachable? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----Original Message----- From: DenverD To: opensuse@opensuse.org Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Tue, 28 May 2013 14:07:09 +0200 On 05/28/2013 01:37 PM, Hans Witvliet wrote:

Just wondering: which "..../<username>/...."

If user_A, user_B, user_C, user_D are currently logged in, and you insert a mem-stick, cd or dvd where does that appear, and to whom is it reachable?

should we assume (in your question) that each of those users have their own terminal (or X server? or own SSH/VNC session), their own monitor/keyboard/USB/ and CD/DVD drive when "you" (i should assume user_A?) inserts a mem-stick into "your" USB? or was each of those users previously logged into an active session, but not active when user_D inserted a mem-stick? or what? dd -----Original Message----- On the machine that i was working this afternoon, there were over hundred others logged in remotely, with nomachine's NX. How would you differentiate bewteen remote/local users? Even if you could, wasn't there a project involving machines with multiple displays and ditto keyboards & mices..... In that case there are all local users! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----Original Message----- From: Carlos E. R. To: OS-en Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Tue, 28 May 2013 19:54:17 +0200 (CEST) On Tuesday, 2013-05-28 at 19:49 +0200, Hans Witvliet wrote:

On the machine that i was working this afternoon, there were over hundred others logged in remotely, with nomachine's NX. How would you differentiate bewteen remote/local users?

Yes, the system knows who is local and who is not. Automonting has to be only for local users, it makes no sense for remote users. Check the output of "who", for instance.

Even if you could, wasn't there a project involving machines with multiple displays and ditto keyboards & mices..... In that case there are all local users!

In this case, yes. -----Original Message----- No, automount should not be restricted for locals only. But with regards to locally mounted media, would this problem not be avoided to make (some) user member of a media-group, and make any media available to that group? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

В Tue, 28 May 2013 19:49:04 +0200 Hans Witvliet пишет:

...

On 05/28/2013 01:37 PM, Hans Witvliet wrote:

...

Just wondering: which "..../<username>/...."

If user_A, user_B, user_C, user_D are currently logged in, and you insert a mem-stick, cd or dvd where does that appear, and to whom is it reachable?

...

On the machine that i was working this afternoon, there were over hundred others logged in remotely, with nomachine's NX. How would you differentiate bewteen remote/local users?

Local users are users logged in using locally attached devices. VGA adapter and keyboard are local devices, SSH session is not.

...

Even if you could, wasn't there a project involving machines with multiple displays and ditto keyboards & mices..... In that case there are all local users!

Current model is - devices are combined in "seats", so users working on one seat do not have access to device connected to another seat. "Seat" could consist of monitor, keyboard/mouse and USB hub in this keyboard. So USB stick plugged in USB port on keyboard belongs to user that is logged in using this keyboard.

Hmm, if that (i.e. including the USB hub in the "seat") actually works, it would be pretty cool! -- Per Jessen, Zürich (12.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-05-28 13:37, Hans Witvliet wrote:

From: Carlos E. R. <>

...

The mount points in /media are created already, in /media, not in 'run/media/<username>/<device>', as we want.

Just wondering: which "..../<username>/...."

If user_A, user_B, user_C, user_D are currently logged in, and you insert a mem-stick, cd or dvd where does that appear, and to whom is it reachable?

To the one that is seated in front of the computer and keyboard, using the active local session. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGkqp0ACgkQIvFNjefEBxq5EwCggfbpBcUFL+vJI3+rbROdfDE4 lesAoMrkd3BGbqIm8rk/uhKxXeCpQkI2 =UKwk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 15:23 +0200, Per Jessen wrote:

Carlos E. R. wrote:

...

To the one that is seated in front of the computer and keyboard, using the active local session.

There might even be more of those - ref the multi-seat discussion from a few days ago.

Oh - I didn't notice that thread. Or I forgot. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGkuyIACgkQtTMYHG2NR9XHZACgl2xkTDc4iUlDVgaWL0TFu0vY asUAn2MUiwgPQaInB2/TvZZA3gygEMUW =xqsv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 16:15 +0200, Ruediger Meier wrote:

On Tuesday 28 May 2013, Per Jessen wrote:

...

There might even be more of those - ref the multi-seat discussion from a few days ago.

Yes, I have setups with 2 monitors, 2 keyboards, 2 mouses ... 2 active users sitting in front of the machine. And there are also machines where I want to allow ssh users to access the automounts. For example the last machine in our office which still has a DVD drive.

Auto-mounting user-dependent does not make sense in my case.

Not even automounting! :-) You need manual mounting, because the mounted filesystem has to be assigned to someone... You need control of the group permissions. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGkwS8ACgkQtTMYHG2NR9V3TQCeOCIY6ZIe99GB/alQPMSf9qGi 9VQAoIIw4rHBL+4wDtPbuCxB5pKe+Jvk =0wYB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 11:15 -0400, Greg Freemyer wrote:

"Carlos E. R." <> wrote:

...

You need manual mounting, because the mounted filesystem has to be assigned to someone... You need control of the group permissions.

Why doesn't the shared auto-mounting feature work for that? That's the newly available configurable feature rolled out to 12.3 as a bugzilla fix and will be available day 1 in 3.1 (via a manual config file edit only I assume).

Dunno about that feature. :-? - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk2qUACgkQtTMYHG2NR9Um6wCferBWWBV8xNb6YPBpiIGsNAsd DOAAoITTNqi90F0N9TUEEoE7j8JBmY+T =3tQk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-05-28 at 12:43 -0400, Greg Freemyer wrote:

On Tue, May 28, 2013 at 12:26 PM, Carlos E. R. <> wrote:

That means when a thumbdrive, etc. is physically plugged in it gets mounted in /media as a shared resource, not per-user. Anyone with multiple physical heads would probably want to get the latest udisk2 update (via a normal zypper update or zypper patch) and then create the config entry as described above. I don't think there is any need for a manual mount.

I'm using that feature since about a month ago - but you miss the point, the permissions: eleanor3:~ # l /media total 40 drwxr-xr-x 3 root root 4096 May 28 18:51 ./ drwxr-xr-x 24 root root 4096 May 1 02:43 ../ drwx------ 16 cer users 16384 Jan 1 1970 KINGSTON/ eleanor3:~ # Only the user in the seat can access it, it is not a "shared resource". That's the problem that Ruediger has - check the thread. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGk4esACgkQtTMYHG2NR9UPxQCgmLpGwjyj1sBf/5lyg9KjpRXc VzcAmwbGaNZU2W49vVXOnXnMTto7Jhqf =G4Qk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Tue, 28 May 2013 21:25:29 +0400 Andrey Borzenkov пишет:

В Tue, 28 May 2013 18:57:15 +0200 (CEST) "Carlos E. R." пишет:

...

On Tuesday, 2013-05-28 at 12:43 -0400, Greg Freemyer wrote:

...

On Tue, May 28, 2013 at 12:26 PM, Carlos E. R. <> wrote:

...

That means when a thumbdrive, etc. is physically plugged in it gets mounted in /media as a shared resource, not per-user. Anyone with multiple physical heads would probably want to get the latest udisk2 update (via a normal zypper update or zypper patch) and then create the config entry as described above. I don't think there is any need for a manual mount.

I'm using that feature since about a month ago - but you miss the point, the permissions:

eleanor3:~ # l /media total 40 drwxr-xr-x 3 root root 4096 May 28 18:51 ./ drwxr-xr-x 24 root root 4096 May 1 02:43 ../ drwx------ 16 cer users 16384 Jan 1 1970 KINGSTON/ eleanor3:~ #

Only the user in the seat can access it, it is not a "shared resource". That's the problem that Ruediger has - check the thread.

In the current (where "current" means several years old at least) framework this is out of scope of system administration. Filesystem is mounted using whatever options *client* supplies. Where "client" usually means some agent started as part of your favorite desktop environment.

So if shared access is needed, either desktop environment has to offer interface to configure mount options (to set gid=xxx or umask=xxx or whatever) or - preferably - file system that supports access control under Linux is to be used.

As an illustration. bor@opensuse:~/src/udisks> tail -1 /proc/mounts /dev/sdb /var/run/media/bor/A48F-A29B vfat rw,nosuid,nodev,relatime,uid=501,gid=501,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0 bor@opensuse:~> udisksctl unmount -b /dev/sdb Unmounted /dev/sdb. bor@opensuse:~> udisksctl mount -b /dev/sdb -o dmask=000 Mounted /dev/sdb at /run/media/bor/A48F-A29B. bor@opensuse:~/src/udisks> tail -1 /proc/mounts /dev/sdb /var/run/media/bor/A48F-A29B vfat rw,nosuid,nodev,relatime,uid=501,gid=501,fmask=0022,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0 bor@opensuse:~/src/udisks> ll /run/media/bor итого 32 drwxrwxrwx 3 bor bor 16384 янв 1 1970 A48F-A29B The real problem is - how to change mount options. I spent almost an hour trying to find it for GNOME3 with no avail. I still do not know. It seems that the only way is to check out full GNOME sources and use grep ... -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlGlqaEACgkQR6LMutpd94zB2wCfXt7/kPTmXHups9cTHmtTHH1h yQYAnRDkPVadDBOVj+59L8nv83BBDeMd =Gw81 -----END PGP SIGNATURE----- N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠О╝·к⌡╠йБmЙ)z{.╠Й+│:╒{Zrшaz▄'z╥╕j)h╔ИЛ╨г╬ё ч╝┼^·к╛z┼Ю

On 5/29/2013 11:49 AM, Andrey Borzenkov wrote:

Final answer is - GNOME3 does not provide any way to customize mount options. Even with obscure and undocumented dconf invocation ... it simply does not pass mount options to udisks2.

Since Gnome 3 doesn't provide it, you must be wrong for wanting it. All hail Gnome 3. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----Original Message----- From: Brian K. White To: opensuse@opensuse.org Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Wed, 29 May 2013 12:01:08 -0400 On 5/29/2013 11:49 AM, Andrey Borzenkov wrote:

Final answer is - GNOME3 does not provide any way to customize mount options. Even with obscure and undocumented dconf invocation ... it simply does not pass mount options to udisks2.

Since Gnome 3 doesn't provide it, you must be wrong for wanting it. All hail Gnome 3. -----Original Message----- But ..... perhaps somebody finds "another" obscure desktop environment which does provide that info. So there might still be hope! (for some, at least ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 5/30/2013 3:38 PM, Ken Schneider - openSUSE wrote:

On 05/30/2013 03:34 PM, Hans Witvliet pecked at the keyboard and wrote:

...

-----Original Message----- From: Brian K. White To: opensuse@opensuse.org Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Wed, 29 May 2013 12:01:08 -0400

On 5/29/2013 11:49 AM, Andrey Borzenkov wrote:

...

Final answer is - GNOME3 does not provide any way to customize mount options. Even with obscure and undocumented dconf invocation ... it simply does not pass mount options to udisks2.

Since Gnome 3 doesn't provide it, you must be wrong for wanting it. All hail Gnome 3.

-----Original Message-----

But ..... perhaps somebody finds "another" obscure desktop environment which does provide that info.

So there might still be hope! (for some, at least ;-)

Perhaps it is not Gnome3's job to provide that ability but instead it is the job of Yast to do so.

Not Gnome's job to mount things? Blaspheme! Next you'll be saying maybe init shouldn't also be cron and xinetd and syslog and udev and that system management should be implemented in human-readable, run-time/emergency editable, run-time/emergency debuggable, infinitely flexible, future-proof shell scripts, that have already been written even! Or that it's not the boot loaders job to try to activate fancy graphics cards before the user has been given any option to say "no that will break the serial console please don't do that" and that the graphics are not more important than robust access to booting! Or that maybe dbus isn't the most efficient thing to have init depend on! -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----Original Message----- From: Brian K. White To: opensuse@opensuse.org Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Thu, 30 May 2013 16:06:45 -0400 On 5/30/2013 3:38 PM, Ken Schneider - openSUSE wrote:

On 05/30/2013 03:34 PM, Hans Witvliet pecked at the keyboard and wrote:

...

-----Original Message----- From: Brian K. White To: opensuse@opensuse.org Subject: Re: [opensuse] Why is not /media a tmpfs any more in 12.3? [Was: What is it with this behaviour in 12.3?] Date: Wed, 29 May 2013 12:01:08 -0400

On 5/29/2013 11:49 AM, Andrey Borzenkov wrote:

...

Final answer is - GNOME3 does not provide any way to customize mount options. Even with obscure and undocumented dconf invocation ... it simply does not pass mount options to udisks2.

Since Gnome 3 doesn't provide it, you must be wrong for wanting it. All hail Gnome 3.

-----Original Message-----

But ..... perhaps somebody finds "another" obscure desktop environment which does provide that info.

So there might still be hope! (for some, at least ;-)

Perhaps it is not Gnome3's job to provide that ability but instead it is the job of Yast to do so.

Not Gnome's job to mount things? Blaspheme! -----Original Message----- <grin> Of course it is Gnome job to do such things! Even when you don't use GNOME ;-) Lets just imagine: In a distant universe far, far away, there might be a lonely soul who is only using the CLI: No KDER, sfce, lxde, E17 or even "X". It would still be gnome's responsibility tp indicate where mount things? Ok, serilously. I don't think it is wise to have YaST invoked each time a new media is detected. </grin> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dne Ne 31. března 2013 17:31:56, Patrick Shanahan napsal(a):

* Vojtěch Zeisek [03-31-13 17:25]:

...

I'm sorry for my blindness and poor knowledge of udev rules, but from the discussion in Bugzilla I don't see where should I put what. Yes, to /etc/udev/rules.d/, but what next? Unless it needs some custom actions like manual edits of udev rules, I don't consider the bug as fixed...

For me with:

17:29 Crash: ~ # rpm -qa *udisk* udisks-1.0.4-11.1.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 udisks-glue-1.3.1-86.1.1.x86_64

I created:

/etc/udev/rules.d/99-correct-media-mount-point.rules including: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

that's a one liner

and it works-for-me :^)

gud luk,

It works fine, thank You. Such result I call fiexd bug. ;-) Have a nice day, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

* Carl Hartung [04-01-13 05:54]:

On Sun, 31 Mar 2013 17:31:56, Patrick Shanahan wrote: <snipped>

...

...

17:29 Crash: ~ # rpm -qa *udisk* udisks-1.0.4-11.1.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 udisks-glue-1.3.1-86.1.1.x86_64 <snipped>

I'm running 12.3 x86_64/KDE fully updated and have only the 'udisks2' flavor of the above packages installed. Do you know what package(s) pulled in 'udisks' and 'udisks-glue' and if it is necessary for this modification that they be installed?

I have Tumbleweed which is currently at 12.3. The udisks/udisks-glue packages were undoubtedly "left-over" after the change to udisks2. 08:46 Crash: ~ # rpm -qa --last *udisk* udisks2-2.0.0-5.4.1.x86_64 Wed Mar 27 13:54:14 2013 libudisks2-0-2.0.0-5.4.1.x86_64 Wed Mar 27 13:52:33 2013 udisks-glue-1.3.1-86.1.1.x86_64 Wed Mar 13 15:29:28 2013 udisks-1.0.4-11.1.1.x86_64 Wed Mar 13 15:24:44 2013 08:47 Crash: ~ # rpm -q --whatrequires udisks udisks-glue no package requires udisks no package requires udisks-glue I have cc'd Greg KH for his attention as Tumbleweed is normally discussed in -factory. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 17 Mar 2013 14:53:48 +0100 Per Jessen wrote:

Basil Chupin wrote:

...

In another thread I mentioned that when I switch on my external 2TB USB WD HDD, Dolphin accesses it and displays its contents to me; but then when I go to use mc (Midnight Commander) this device is no longer mounted in /media as it has been in past many years but now is found in /var/run/media/<username>/<devicename> [in this case the volume name is WD].

Quite by accident a few minutes ago ('cause I am having another hassle, to be describe later) I discovered that the device is ALSO mounted in 'run/media/<username>/<device>'.

(How many times is such a device 'mounted' and where else may I find it?)

'df' will tell you.

According to https://forums.opensuse.org/english/get-technical-help-here/hardware/484495-... this is a regression; see bug report: https://bugzilla.novell.com/show_bug.cgi?id=809837 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org