If you are happy with experimenting a bit, I suggest to proceed as follows. Disclaimer: I don't have a dual boot machine, I kicked Windows off my Laptop years ago.
Install texlive under windows and test it. Then boot into Linux and start the installation of texlive. Cancel the installation process after some minutes. Now, you have a TDS compliant structure, but the content is missing. EDIT: Delete all files and folders inside /texlive/2014/texmf-dist/tex/latex and /texlive/2014/texmf-dist/doc (not in your Windows folder, I'm speaking only of the Linux side!).
Then make two links:
- link from .../texlive/2014/texmf-dist/tex/latex to C:/texlive/2014/texmf-dist/tex/latex
- link from .../texlive/2014/texmf-dist/doc to C:/texlive/2014/texmf-dist/doc
I don't know whether a hard link or a symbolic link, but as Linux has this link feature, I'd check this possibility. Maybe here are some geeks who know exactly how to set a link from a Linux folder to a NTFS folder somewhere else.
Why only those two links? Because the LaTeX packages and the documents make the lions share of the texlive.
OK. Then restart the installation under Linux. I hope that tlmgr will accept the link to your windows installation and then try to install every single package and documentation, but notices they are already there.
Recently I transferred all doc and latex files to another computer and that part (start installation, abort, transfer, restart) worked. But I have no experience with linking into a windows installation.
Of course, you have to install the linux packages for writing into ntfs. And maybe you ruin your texlive installation on windows, if the installer tries something unexpected. But if you make a backup of it, why not giving it a whirl.
Best Answer
You do not need to switch your antivirus off. Just click on the "more info" and it will ask you if you want to "run anyway".
Some code is very well recognised, or is signed with a certificate that is recognized by Microsoft. There are different types of code signing certificates - some more expensive. The cheaper ones may take some time for a new software build to be recognised as widely enough used to be considered safe.