pwilson wrote:Forgive me, but the QNAP design makes perfect sense. They are mounted as "shares" so they can be mounted/dismounted at will. You can always setup an "ISOs" share, and then create symlinks to point to each individual ISO share as you desire from there. This would give you the "logical" layout you want, without breaking anything.
(I too am a Linux user. I've been running Linux since 1991).
If you insist on doing this manually, simply add your mount commands to your NAS's "autorun.sh" file. (I definitely do not recommend doing this), and then manually create "shares" to point to these folders. It would be far safer to use the symlinks via a dummy "ISOs" share to provide the logical structure you are looking for.
All your "shares", including ISO Shares, get mounted at /share under QNAP's design.
Remember that creating a ISO share is a two step process, these steps are done automatically by the Firmware.
It mounts the ISO file to a folder (via a Loop device)
It shares the newly mounted ISO folder out via AFS, SMB/CIFS, and NFS so all your client devices can access it.
I won't help with an "autorun.sh" file for this purpose, but I am willing to help you create an "ISOs" dummy share, with symlinks to the real ones. If you want to pursue this idea, simply create the ISO shares using the Firmware, and explain the logical structure you are looking for:
Perhaps you want a logical structure such as:
/share/ISOs/Ubuntu
/share/ISOs/Redhat
/share/ISOs/Win8
/share/ISOs/Win7Sp3
I need more information in order to be able to help.
You're right. It defines shares so it's completely correct.
Yes, that's exactly the structure I want. It's for my PXE environment. It would be nice if they added a GUI for "mount ISO to mountpoint function".
Thank you for your offer but I can set that up myself.
I will make a script that will recursively search a folder and mount all ISO files that it can find on a specified path in separate mountpoints.
The name of the mountpoint will be the name of the ISO file.
Or maybe it will load settings from a text file beside the ISO file that tells the script what the mountpoint should be named and mount it there.
pwilson wrote:Forgive me, but the QNAP design makes perfect sense. They are mounted as "shares" so they can be mounted/dismounted at will. You can always setup an "ISOs" share, and then create symlinks to point to each individual ISO share as you desire from there. This would give you the "logical" layout you want, without breaking anything.
(I too am a Linux user. I've been running Linux since 1991).
If you insist on doing this manually, simply add your mount commands to your NAS's "autorun.sh" file. (I definitely do not recommend doing this), and then manually create "shares" to point to these folders. It would be far safer to use the symlinks via a dummy "ISOs" share to provide the logical structure you are looking for.
All your "shares", including ISO Shares, get mounted at /share under QNAP's design.
Remember that creating a ISO share is a two step process, these steps are done automatically by the Firmware.
It mounts the ISO file to a folder (via a Loop device)
It shares the newly mounted ISO folder out via AFS, SMB/CIFS, and NFS so all your client devices can access it.
I won't help with an "autorun.sh" file for this purpose, but I am willing to help you create an "ISOs" dummy share, with symlinks to the real ones. If you want to pursue this idea, simply create the ISO shares using the Firmware, and explain the logical structure you are looking for:
Perhaps you want a logical structure such as:
/share/ISOs/Ubuntu
/share/ISOs/Redhat
/share/ISOs/Win8
/share/ISOs/Win7Sp3
I need more information in order to be able to help.
You're right. It defines shares so it's completely correct.
Yes, that's exactly the structure I want. It's for my PXE environment. It would be nice if they added a GUI for "mount ISO to mountpoint function".
Thank you for your offer but I can set that up myself.
I will make a script that will recursively search a folder and mount all ISO files that it can find on a specified path in separate mountpoints.
The name of the mountpoint will be the name of the ISO file.
Or maybe it will load settings from a text file beside the ISO file that tells the script what the mountpoint should be named and mount it there.
Ah. I suspected as much. I chose to rip apart all the ISO's and store the files on the NAS. This means I only needed to mount them once. I've been using my NAS as a PXE Service ever since QTS 3.6.1. it works really well here.
