Writing colons to USB mounted NTFS partitions

[aria]

Hello,
Last Kubuntu distribution to write colons to external drives NTFS formatted was 18.04. I am now with 24.04, in my view the best Kubuntu since 18.04. And I have huge libraries with movies and transcoded music, which files contain colons. If I want to copy them to another NTFS formatted external drive, errors will occur as now NTFS-3G is set (according to NTFS-3G manual) to "windows_names" and it won't write colons anymore. My question is:

• How could I permanently change this setting, to Posix writing, so to write colons too? And do this for all NTFS drives, not only for chosen ones (according to their UUID). I've read something about "acl" (in the same NTFS-3G manual), but don't know how to set it. Could somebody help me with the codes?

PS: The solution here won't work anymore, and besides was UUID specific: https://forums.linuxmint.com/viewtop...66721#p1866721 , and the other I've learned some time ago:

sudo ntfs-3g /dev/sdb1 /media/userspace​

also doesn't work anymore. Previously was a one shot (not permanent) solution.

Thanks.

PS2: I haven't use Windows since 2010, and will never use it again, so writing colons to NTFS drives doesn't bother me at all, on the contrary, it simplifies my life and makes it better

[aria]

Looked in the ntfs-3g manual and believe the code to make it write colons permanently, could be:
ntfs-3g -o acl /dev/sdb /media/userspace
But not sure if preceded by sudo, and also if volume should be rather sdb1, then running the code again for sdb2 and sdb3... And not sure either if a ntfs volume should be plugged in to a USB port when running this code.
Coding for me is German (10+ years and only ja, nein, guten Morgen, Tag, Nacht)... And don't want to mess the system.
Could somebody confirm, or correct the code I need to make ntfs-3g write colons, and to do this permanently?
Thanks.

[oshunluvr]

I seems unlikely you will get an answer to your primary question here. I believe very few use NTFS at all and if they do, using colons has a high likelihood of not being a priority.

Generally, anything at the file system level will require sudo, Not using sudo wouldn't break anything, just generate an error regarding lack of root access.

As far volume (actually "device") name, since you are acting on a file system not a piece of hardware, the correct target would be the device containing the target file system. So if you want to make this change to the file system residing on /dev/sdb1, then that's your target. Targeting /dev/sdb will fail because there is no file system there, only a header and partition table.

As far as other file systems; regardless of the type of connection (USB or not) entering the above command correctly will not and could not effect anything other than the targeted file system.

If you are concerned about the effect of using this command, the best way to know for sure is to simply test it on a sacrificial (empty) file system. Use a freshly formatted partition or USB drive and test it. You might put a couple files on it before running the command to see what effect, if any, it has on existing files. Then you should have the confidence to proceed or know for sure that you shouldn't. After the test is over, simply re-format to restore a normal file system.

[aria]

Good advises and ideas on how to test the code without risks! Will try this soon, and will post results here.
Thanks!

PS: Code
sudo ntfs-3g -o acl /dev/sdb1 /media/userspace
did nothing: Posix ACLs were enabled by default, so the issue is not with ACL. Still searching.
Sorry for the confusion in my last post above (#2), where I wrote sdb1, sdb2, sdb3, while I should write sdb1, sdc1, sdd1 (different USB keys or hard drives, not different volumes on the same key or hard drive).

[aria]

Tested 3 recommended methods, in different versions: with ntfs or ntfs-3g, with different options (-t and/or -o rw), and with different mounting points (/home/userspace or /mnt/newfolder), and with reboot for the method writing to fstab. All in vain: couldn't write colons to an external ntfs drive. These methods worked in 20.04, thus I wonder if the issue is not with the version of the ntfs-3g installed in 24.04. Will search for data and will write a new post on how to install an older version of ntfs, and to set it not to upgrade (backports or something like this).
Thanks.