File permissions problem | Bitcointalksearch.org

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: successcouncil on December 10, 2020, 02:58:32 PM

Is it safe to just change the permissions on the bitcoin and armory directory to 666?

It would most probably fix your problem but isn't recommended.

Quote from: successcouncil on December 10, 2020, 02:58:32 PM

Or is there a way to change the owner of the file on the Mac so the Ubuntu user can set it to what ever it needs to be? And what should it be?

Are you only accessing these files/folders from your ubuntu machine from now on?
If so, you are free to change the owner to your current ubuntu owner:

Code:

sudo chown -R USER FOLDER

Replace USER with your user and FOLDER with the folder containing all other folders and files.

HCP

legendary

Activity: 2086

Merit: 4361

Given that Mac uses a similar file system to Linux, you should find that using commands in Ubuntu like sudo, chown ("change ownership"), chgrp ("change group") and chmod (modify file permissions) should help you fix the file ownership and permissions issues.

You should just need to change the ownership to the Ubuntu user which should fix the write permissions.

There should be plenty of online tutorials explaining how the various commands work, to save lengthy explanations here Wink

successcouncil

newbie

Activity: 46

Merit: 0

So I bit the bullet and gave up on Armory working on Mac. I bought my ubuntu machine. Found the external drive. (The one I used to use on Mac.)

but could not Write to the bitcoin directory and I am sure the Armory directory when I get to it. I still have access to the Mac.

Is it safe to just change the permissions on the bitcoin and armory directory to 666?

Or is there a way to change the owner of the file on the Mac so the Ubuntu user can set it to what ever it needs to be? And what should it be?

Should I just buy another harddrive and copy the blockchain across

What is quickest for a tech struggler like me?

Thanks in advance.

Topic: File permissions problem (Read 107 times)