thank you Seth,
I have no problems with the script executed at the UDEV event (if this is the meaning you attribute to the term <UDEV script>).
I've already done this script that works, if run from a terminal.
If by the term <UDEV script> you mean something different, please tell me.
The problem is that this script is not executed as a result of the UDEV event.
- - - - - -
But maybe there is still something not clear for me that I can ask you:
The HD (USB) that I am using, is divided into three partitions (in order to keep the saved data separate):
= - = - = - = - = - =
the blkid command give this output ...:
/ dev / sdc1: LABEL = "PRTZm_sys-admin" UUID = "1A5CEE7149E4BA81" TYPE = "ntfs" PARTUUID = "0007fd62-01"
/ dev / sdc2: LABEL = "PRTZm_data-common" UUID = "7FB1E3D91206DE1C" TYPE = "ntfs" PARTUUID = "0007fd62-02"
/ dev / sdc3: LABEL = "PRTZm_programming" UUID = "0A69FDE9688969D9" TYPE = "ntfs" PARTUUID = "0007fd62-03"
= - = - = - = - = - =
so far, till now, I tried to reveal the montage of the HD without taking into the account of partitions into which the USB HD is divided ..
But since the blkid command does not reveal its own UUID I am now thinking that this could be the problem.
IN CONCLUSION, since the USB is divided into partitions, ... will the UDEV event reveal the presence of the entire HD (as the sole unit), or will it instead reveal the presence of the three individual different partitions?
Still I would ask .... : this is a good syntax ? ENV{ID_FS_UUID}=="1A5CEE7149E4BA81"
and still also, :-) ....
what I have to use the UUID number, or instead the PARTUUID number ?
thank you very much
Angelo