Hi Donald.
Actually, in this case, I think you do need to maintain the data in 2 places. Here is the reason why:
In Windows, your data is accessed through a file path that looks like this: "\\NAS1\arcgisdata".
But your Linux Server will never be able to make sense of a file path like that.
Linux must see the share as: "/array0/dist/docs/arcgisdata".
The software looks at these paths explicitly.
Therefore, when you try to publish from ArcMap with "'Same as publisher folder path'", it will not work.
You will need to copy the data to the Linux machine and tell the Server (during the publish process) to translate the path as it is seen from Windows to a Path that Linux will understand.
Alternatively, you can package the data with the Service and not have to worry about it. But still, you will end up with 2 versions of the data either way: one version on Windows, one version on Linux.
Does this make sense?