I posted about this but I think I asked the wrong question.

I have a USB mass storage device whose format is a bit weird, but it used to mount when plugged in and now it doesn't. I can't reformat it because it wouldn't work if I did (it's actually a remote control).

I think it is because of new UDEV rules.

The device id is Vendor 06e7 Product 8015. (8020 on USA devices - I have a European and a USA version and they behave exactly the same.)

Is there a UDEV rule that I can add that would allow it to automount when plugged in?

Just to say that it does mount on MX-Linux 18.3, but no longer does on MX19 beta. Similarly it mounts on antiX 17.4 but no longer on antiX19 beta. It hasn't mounted on PCLinuxOS or Fedora for a year or so, but did in the past. I think this is due to changes in UDEV (MX and antiX are less cutting-edge, lagging a little behind Debian Stable).

The full readouts from dmesg when plugged into MX18 and PCLOS/MX19 show how it reacts to different versions of UDEV. These are in the previous thread, with the wrong question, I believe.
https://www.linuxquestions.org/quest...ts-4175660817/

You can write udev rules to do any kind of actions that you like. There are many good guides to writing them.

How do you know it is changes in udev that are causing this ? That is only your hypothesis. What you need to do is find the exact rule that is triggered in both cases. You need to use udevadm test info and similar commands.

https://superuser.com/questions/6771...dev-rule-fired

1 members found this post helpful.

Should be reasonably straight-forward on non-systemd systems like that. Might pay to run udevmonitor on both to see what (if any) differences are.
If you can put a label on the filesystem, might enhance your chances too.

1 members found this post helpful.

Thanks, both of you!

tofino_surfer: I've been to that superuser link and tried a few of the things there. I'll post again when I get the stuff together.

syg00: Interestingly, one of the things I tried showed a UUID label in MX18 but not in MX19. Could that be crucial to the whole issue?

Anyway I have to keep booting back and forth between MX18 and MX19 and saving outputs, so it will take me a while to get it sorted out to post here.

I've found that, in two different distros, when you plug in one of these remotes to usb, as well as the usual mass storage device, a "shortcut" is automatically created which is the same for both distros and both remotes.

/dev/disk/by-id/usb-UEI_Remotes_UEI_Mass_Storage_000000000001-0:0-part1

So all I need to do is to add two new commands on the XFCE drop-down menu for Remote Master:

sudo mount -t vfat /dev/disk/by-id/usb-UEI_Remotes_UEI_Mass_Storage_000000000001-0:0-part1 /home/myusername/Documents/remote/REMOTE/ -o uid=1000,gid=1000,utf8,dmask=027,fmask=137

sudo umount /dev/disk/by-id/usb-UEI_Remotes_UEI_Mass_Storage_000000000001-0:0-part1

And in the Remote Master program itself, set the destination as follows:

Remote > Interface > JPS... > Other > /home/myusername/Documents/remote/REMOTE/settings.bin

Once set up, it's one extra click after I plug in the remote, and one when I disconnect it. I can live with that.