I am using a linux machine hosted via Amazon's EC2. Today, I moved all of the contents over to a larger hard drive. I use Coda as my text editor.
Problem: I can not view the contents of many of the directories inside my new data drive via Coda. I can view all of the contents in these directories via Terminal.
Things I have tried:
- Checked to make sure permissions were set for said directories, sub-directories, and their contents. These are all set to 775
- I moved the files to another directory via terminal and then moved them back to their original folder. This allowed me to view the files and directories that I moved, but none of their sub-directories or files within these sub-directories.
- Refreshed all folders, quit out of Coda, deleted the site connection, and re-created it. This did not change anything.
Any ideas of what is going on?
Weird.... I had changed all permission to 775 at once, but some of the directories were still set to 755, so I had to change these manually.
Related
I was recently cleaning up my %USERPROFILE% folder, this included deleting the documents and pictures folders from the OneDrive folder, changing some registry entries, etc.
However, Now when I go to my userprofile folder via the pinned link in Quick Access I do not see my Documents folder, but when I got to the userprofile folder through C:\Users\user it is there. If I type C:\Users\Username\Documents in search, I also reach the right folder.
The problem persists after refreshes of file explorer and after restarts.
Image of folder through quick access shortcut
Image of folder through manual navigation
Image of registry keys I edited
I was able to fix the problem by deleting some other registry values pointing to (the non-existent) %USERPROFILE%/OneDrive in:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders
I was trying to install matlab on my linux (mint) computer, using some of the .iso files. I was trying to mount one of them using the command
mount R2017a_glnxa64_dvd1.iso /home/.../Documents/
which seems to have mounted the .iso file into my Documents directory and replaced everything there. When I try and open up the Documents directory, it just contains the contents of the .iso file and none of the files which I know were in there previously.
If I go to, say libre office, and click 'open recent file', any of my recent files which were in my documents now don't exist. This is quite worrying as I have a lot of work in there which isn't backed up.
I don't really know anything about what mount does. Will it have permanently deleted all the files from my Documents directory? I can 'unmount' the Documents directory now, but am worried it might be a bad idea and permanently delete the stuff that used to be there. Can anyone help me try and recover my Documents directory?
thanks
I wanna to freeze a folder in red hat so nobody (even root) can not add file into the folder or change files that exist in the folder already, i tried to make folder read only but this does not work and root user can add files normally as before, please somebody help me to solving this problem.
Create a filesystem in a file (eg: an iso file) containing the files you want in the directory then use a loopback mount to mount it read only onto the directory.
Anybody who tries to modify the filesystem normally (including root) will get a "read-only filesystem" error.
No. By design, in Linux, root ignores existing permissions on all entities. However, what you can do is encrypt files so that they can't be read and can't be modified by those who don't know the key. You can't prevent new files from being added, but with both encryption and decryption keys private, you can easily verify if any file is valid.
This also means you can't have either key on your computer!
I'm looking for a way to store all my applications files within a single folder. However, when someone clicks on the folder I want the application inside the folder to open up as opposed to open the folder itself. I want to keep all dependancies and files inside this folder at all times.
I'm doing this because I'm going to be deploying a couple applications on a common framework and want to ensure that they are together and independent of the distribution have all requirements.
Folders are directories, and directories are distinct from files. There's no way to redirect a directory to an executable file. However, you can make a hidden directory (begin name with ".") and use an executable file to provide access to that directory. The directory will then not appear in window manager folders, just the application. However, window managers will not misrepresent the executable file as a directory.
I've got a Perforce server set up, and installed the P4V client. I've created a new depot and a new workspace. Per the documentation, I've mapped the workspace to the depot. So far so good.
I now have a .SQL script that was created by an external application that I wish to check in for the first time. I copied the file into my workspace and can see the file in the client's workspace tree window. Yet when I attempt to mark the file for add, I get a "file(s) not opened on this client" error. I've tried editing a changelist to include the file, but the changelist editor does not "see" the file.
I've read through the documentation (PDF files), but I just do not see what I'm missing. I've worked with other RCS software in a commercial setting, but this is my first stab at trying to set up and administer and RCS system up for personal use.
I think your problem is likely to be with the mappings. This is a reasonably common issue.
Taking your details
Workspace root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666
File dir under root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files
View mappings:
//tunnel/... //wtansill_localhost_1666/tunnel/...
//tunnel/* //wtansill_localhost_1666/tunnel/*
With the details above, the line
//tunnel/... //wtansill_localhost_1666/tunnel/...
means that you need to place the files you wish to add into the root of your workspace plus the directory tunnel eg.
C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel
rather than
C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files
where you seem to have put them. A way around this is
Create the tunnel folder in the correct place (and any subfolders)
Remove the final folder from your workspace mapping so
//tunnel/... //wtansill_localhost_1666/tunnel/...
becomes
//tunnel/... //wtansill_localhost_1666/...
this would mean anything under
C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files
would be mapped to //tunnel/tunnel_files which is I think what you want.
Hope this helps.
Are you sure your filespec includes the directory you have added your file in?
Perhaps you could post your ClientSpec, and the directory in which your file is located?
Workspace root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666
File dir under root: C:\Documents and Settings\wtansill\Perforce\wtansill_localhost_1666\tunnel_files
View mappings:
//tunnel/... //wtansill_localhost_1666/tunnel/...
//tunnel/* //wtansill_localhost_1666/tunnel/*
It's sort of a moot point though. The above workspace was the default set up by Perforce when I installed it. I deleted that workspace and created a new one using the P4V client, retraced my original steps, and now, lo, it works! Go figure.