Subj : Re: NFS File Area Issue To : deon From : paulie420 Date : Wed Mar 24 2021 09:25:44 de> pa> Thanks for any help; we should be able to use these types of mounts f de> pa> file areas, right? de> de> I dont really understand the error might be helpeful to get the actual de> error - but to answer your question - yes. de> ...лоеп me> Yes, you can use NFS mounts for your file areas, I have a bunch on me> mine. Also you can use symlinks and bind mounts too. As long as the FS me> can be seen from the normal navigation and mystic has read/write access me> to the areas, it should be all gravy. me> MeaTLoTioN Thanks for replying deon.. also, I posted mL's response and I feel pretty stupid. So yea, thats it - it must be the permissions. Derp. mL has recently seen some of my knowledge with Linux; I know a lot, and then.. I know so little. Even I should have known this... I didn't give ANY access consideration to the NFS drive. So thats most likely where Mystic is failing. My BBS is on user 'pi'... and my NAS is on a user 'paulie420'. Lol, the /ROMs folder is listed 'paulie420 : users'. And I suppose I'm gonna need a whole lesson on permissions - which I can do mostly on my own time, but... On my local BBS box I know how to use chown and chmod to make sure Mystic has access to things it needs. But on this NFS mount, is it going to be that I need to add the BBS box credentials to that 'users' group? Again, I can learn how to doso on my own time, but... in what way do I give the BBS box access to the remote NAS /ROMs folder? |07p|15AULIE|1142|07o |08......... --- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32) * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129) .