Have worked with Fat32 all along? Can anyone clarify? So makes me wonder if that was the issue all along, and this could
What's going on here? Can anyone suggest a clean way to configure this so that Windows can also write on this drive? Is it the format that's the issue? NTFS perhaps better? Thanks in advance Now I have also started exploring the notation with FOUR numbers, not three, but when I do something like chmod 7775 or whatever (while being verbose with -v) I see that each action fails with "Operation not permitted failed to change mode. I have also tried adding lines in the smb.conf file directly such as: create mask = 770 However, the ls -l command still shows that root is the only user that can write. The command finishes successfully (silently). I ran the chmod command: chmod -R 777 (or other variations here but always starting with a 7) /media/WD-External. When I type: ls -l /media/WD-External the permissions are only set for "root". I can copy FROM it and drag and drop on my Win10 desktop etc. I can add as a mapped drive with an assigned letter as well etc. I can successfully connect to this drive from a networked Windows 10 computer. dev/sdb2 /media/WD-External vfat defaults 0 2 I have also added it to the fstab file so that it mounts automatically at boot via the line: I want to explore the possibility of being able to read it from a networked Mac as well. I connected a 1 Terrabyte WD external hard drive and mounted it successfully under /media/WD-External.
I have tried a dozen things and more, but nothing works.Ĭonverted a very old T43 Thinkpad to a home server by installing Ubuntu 16.04 (it seemed to be the only version I could get with 32-bit support if anyone knows how to get latest with 32-bit please shout). I am compelled to add a new thread as a million people have some other variant of my problem but I cannot seem to find help in their threads.