Was wondering if anyone that’s using Lucid has a good solution to the various filesystem permissions issues that seem to crop up between macOS and Rocky.
I often find that folders/files created on macOS need to be chmod’d in Lucid in order to see them in Flame. I’m mounting lucid in Rocky via a system.d service at launch and do have the --fuse-allow-other flag in my daemon command but that doesn’t seem to resolve the issues.
Trying to work on some solutions with Lucid support, but I thought I’d reach out here in case anyone has been down this road. Other than wielding my potentially dangerous chmod -R 777 sword I have very little knowledge regarding sysadmin stuff. So thanks in advance for any thoughts/advice,
I’d hate to take up any more of your time outside of our chats, so if this is something that might be more easily handled next time we talk I can hold off on trying to solve it until then.
As for your questions, who is setting/owning these process where?
I am “admin” for Mac, Rocky and Lucid. That word is in quotes because I clearly don’t deserve that title, but I’m the one trying to make it all happen
Everything works the second you create permissions on project folder roots, create some groups, assign those permissions to groups and throw so users in those groups.
The only snafu is mixing SSO and Lucid standard users. Otherwise it’s pretty solid.
Yup, that all sounds like what I probably need to do. Unfortunately a side effect of being an “artist” turned “artist/sysadmin” is that I was always working in a walled off garden and just opened everything up (umask 0 baby!, chmod 777 it all) and was never taught/learned the proper ins/outs of user/group/permissions management. Instead of fixing the issues, I just band-aided them so they worked.
But now that I’m really trying to get on board with a proper cloud based, shared, connected workflow, I gotta tear things down and just do it the “right” way.
{starts frantically googling the “right” way to do it}