How to force chmod 777 on readonly usb - usb

This happens often where i cannot write to my flasdrive, then I must format the thing.
I do not know why this happens either, can it be prevented?
How can I force chmod 777 on the drive so I can copy files to it?
any help and advise please?
thanks

well try it as:
chmod -rf 777
or if this doesn't work try:
sudo chmod -rf 777
Edit:
on some Unix distributions it you can do it as:
chmod -f 777
sudo chmod -f 777

If you have a mac, open Finder and go to the file. Then right click and select Get Info. Next, UNCHECK the box that says LOCKED (you may need to click on the padlock and enter your password first). Once that's done, you can chmod at will.

Related

Can't execute command chmod 0777 * -R in CentOS 7

I am trying to execute command chmod 0777 * -R, but the chmod: changing permissions of ‘70-persistent-net.rules’: Operation not permitted error appears. How to solve this problem?
Thanks for answer!
It is not a good idea to change the rights in /etc/udev
everything there should remains to root account and the message the system provides you an insight about it.
In my case, i try to execute sudo chmod 0777 * -R and it work fine

Avoiding "/mnt/" while calling sudo chown -R in "Ubuntu on Windows"

I'm using Ubuntu on Windows.
I want to take ownership all of the files and folders in the current user profile.
To do that, I call
sudo chown -R USERNAME /
It works, but it also tries to chown all files in folders under "/mnt/".
This means it tries to work on all my Windows folders as well.
I don't want that.
How could I process only the files and folder in the user profile?
Thank you!

Apache File permissions issue in Ubuntu

I'm trying to use Apache to access a file on my Documents folder.
I tried the following:
sudo chown -R www-data:www-data /home/$USER/public_html
sudo adduser $USER www-data
sudo chmod -R 775 /home/$USER/public_html
As suggested by this post:
https://askubuntu.com/questions/26848/permissions-issue-how-can-apache-access-files-in-my-home-directory
Although this works, now I cannot edit or the files directly as the user (without using sudo), despite being a member of the www-data group. The only solution that seemed to work is using chmod -R 777 (which I rather not do).
Turns out all I had to do is restart the OS and it was sorted!

Path for logs is not writable

When I'm running codecept run on the first try after bootstrap, I'm running into this error,
[Codeception\Exception\Configuration]
Path for logs is not writable. Please, set appropriate access mode for log path.
Thanks!
I had the same problem, but chmod 777 _log resulted in no such file or directory.
Use: chmod 777 -R tests/_log
For me, _log file was already there but I was still getting the same error.
My problem was solved when I used SUDO with my execution command.
I created _log folder inside the folder, "/tests" and gave it a write access,
chmod 777 _log

Impossible write into the AJXP_DATA_PATH folder ajaxplorer

I uploaded ajaxplorer "pydio-core-5.0.4.zip" to my server and after I extracted files into a folder in the server i request the folder to starting install but i get this message :
"Impossible write into the AJXP_DATA_PATH folder: Make sure to grant write access to this folder for your webserver!"
i made the folder : /data permissions to 777 and it did not make change ..
any solve ?
I'v got the same problem few hours ago.
The problem:
You put full permissions (777) to the data folder, but subfolders don't get it.
The solution:
sudo chmod -R 777 data
sudo chmod -R 777 data
or
sudo mkdir -m 777 your_pydio_path/data/tmp/sessions
I know this is old, but I was having the same issue with pydio-core-6.0.8. Also, I'm going to preface this by saying that I am a php noob. But I was able to resolve my issue without a chmod 777 command. Instead, I made the nginx user the owner of the data directory.
chown -R nginx /path/to/pydio-core-6.0.8/data
And then made sure that php-fpm was running as the nginx user with the two php-fpm.conf settings
listen.owner = nginx
user = nginx
After restarting php-fpm, I was able to load the pydio page which went into the startup wizard.
This command is so easy! But it's dangerous!
Go to /var/www/pydio for apache2 or /usr/share/nginx/html/pydio for nginx and try:
chmod ugo+x data
It's more protected!