-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble recreating symlinks for ROM folders #116
Comments
I am not sure I understand exactly the problem. Do you mean the folder have permissions that differ from expected? This should have been repaired as you rerun the playbook for MiSTer.
Could you please clarify if all other symlinks created correctly for MiSTer? |
And disregard - after running it 4 times earlier today with no success, I just reran it again and the following symlinks regenerated: Not sure why it didn't work earlier today and just worked now... but its resolved Feel free to mark as closed unless you think there is something to learn from this except some weird user error on why they didn't regenerate when I ran the script earlier today.... of note the only thing I noticed that was different this time vs. the three times earlier today, was that this time when I opened the retronas TUI I got a message saying retronas had been updated required me to hit enter to confirm (I don't remember the exact message) before taking me to the TUI |
sorry i had no chance to come back around to this yet, the message you saw said you could now run we have made no changes that space I am aware of so it is certainly odd, i will close thise for now and we can revisit if have more reports of the same. thanks for the follow up |
Due to the way i copied over my rom folders I ended up with the symlinks for roms/nintentdo/famicom_disk and roms/nintendo/nes having the wrong ownership and permissions. I deleted the symlinks (confirming that the direcotires they pointed to are still there) and reran the Samba for MISTer script in the TUI but the symlinks did not get re-created.
Any idea how to correct this?
The text was updated successfully, but these errors were encountered: