@mad_ady, thanks
@engineer14, the link you provide is some good background, it's that discussion combined with the need to modify the linksheet script to handle menusheets as well that resulted in this tutorial,
my recommendation though would be to leave linksheets as it is, and not disable it with the user-script
afterall if linksheets is disabled how will MSHEETDIR work
some more details about the script that may be interesting
linksheet script is actually called S67msheet it scans for moviesheets and then links them to a directory /msheets
this directory /msheets then get's unionfs 'd with /osd
this results in the a file like Batman_sheet.jpg appearing is /osd as Batman (and yes it's still a jpg, even though it's not named as one)
this file along with some edits that have been done to the .xml's located in /osd causes the image to be displayed on screen
the linksheet script also does one other thing, it handles MSHEETDIR, when MSHEETDIR is set the script will mount -o bind the directory to /msheets which is unionfs 'd with /osd, no scanning required but linksheets must be ON to have the script run,
this is also why, MSHEETDIR will work on fat32 and I suspect NTFS or other format types, there are no format restrictions on a mount -o bind command
so providing that there are no other sheets on the system once MSHEETDIR is mounted and then union 'd linksheet script will exit, my current set up the light only blinks maybe 2 or 3 times and then stops
however if MSHEETDIR is set and duplicate or other sheets are on the system linksheets will continue to scan and create links, this is where the problems are found with drive formats, linksheets ends up attempting to create symlinks on a drive who's format does not support it, this is what causes corruption of MSHEETDIR, if fact this causes corruption on some file systems while others it results in the file being completely removed/deleted
KAD