Download Folders Remove
Kimberlee Caballero
We have multiple svn repo to move to even more git repositories, this implies some repository folder merges and splits.During the process I need to remove a set of root folders and I'd like to remove those to the whole history.
I tried to use the BFG --delete-folders and it works fine for one single folder but I did not find a way to delete multiple folders. Is it even possible ? or shall I loop to call BFG as many times as I have folders to remove ?
You can delete specific files or photos on Microsoft OneDrive, or you can delete entire folders and all the items in them. If you need to, you might be able to restore deleted files from the OneDrive recycle bin.
To remove items from your Recent view, select the files or folders you want to remove by pointing to each item and clicking the circle check box that appears. On the bar at the top of the page, select Remove.
Is there a way to remove all the files and folders associated with package when I remove a package?
Meaning specific folders which are created for it and the config files created at various locations.
lilbenden is it safe to remove files listed by pacman -Ql ? Wouldnt it be good to prompt the user if he wants the system to be cleaned when he is removing the package? I mean config files in Home directory makes sense but why leave files in the file system?
NO! pacman -Ql lists all installed files!
The link provides a script to determine which files are NOT in that list. Files that are not in the pacman -Ql list can only be created by the user, or through .install files or configs etc. Sometimes there's leftovers from a unsucceeded install, or removal. Also there are a lot of fonts listed (ms-fonts) cause they can only be used following certain rules.
It is never safe to simply remove files listed by the script, but some files are easily recognizable so you can decide to remove or keep them.
If you're in doubt about some files post your list (from that script) up here.
Yes I am still wondering if someone can explain to why it is a necessity to leave junk behind, I mean keep the configs in the home folder, if it is done in the system folders then atleast there should be an option to get rid of it.
Maybe i dont know something which the experts know
Thanks for the script, I will post my list here.
It's actually not really pacman's fault most of the time. The files are created after installation, or in a separated .install script. If packages and packagers keep to the standards there shouldn't be any leftovers, even in those special cases you can use .remove script for that, runned by pacman -R... also be sure you don't make any mistakes.
Sometimes packages are broken do tue whatever reason. In this case you can force a reinstall after which you can remove it completely...
Anyway you can do a reading through some of the topics I collected in the feature request. You'll find some more answers there.
After you have done this. You can have a look at the sanity of your system (according to junk files).
Run the script provided above. It will look for packages in all specified folders that are not in the list of files belonging to installed packages. Choose which folders you want to include in this search. Well check the options of the script...
Then you have an overview of files that might be useless. Hopefully this list isn't too big. It shouldn't be. As I said before, if you remember any pacman crashes or wrong installs/removals, there are some files expected. Else it should only be a list of some fonts, some java stuff and maybe more (don't remember)... but those files aren't useless. They are not created in a standard way, so pacman is unable to list them, that's all. Reasons for this I told you earlier.
Now I'm curious how big your list is going to be... so if you're done show it to us. I don't garantee I can be of any help. Soon I'll be on vacation too... but there are others which will be willing to help you determine whether files are sane or junky...
Go on now!
I made the list have shorter, you posted it double. You posted owned but not found too. This means you didn't include certain folders you should have included. Can you provide which folders you included? Or did you use the defaults?
Here is what I found till now:
All .pacsave and .pacnew files can be removed. These are backups of important config files pacman makes during installation/removal. If you are sure you don't need those anymore it's safe to remove them.
There are a lot of shared-mime-info (broken?) files. Check if they are owned with pacman -Qo. If they aren't you should force a reinstall of the package with pacman -Sf shared-mime-info. I could be wrong but it seems that package is broken.
Further I found files belonging to:
virtualbox
bluetooth
You should check those...
This folder is a huge one too:
/etc/ssl/certs ???????
I couldn't find where it belonged too. Some ssl application... I don't know, so try to find out by yourself.
The answer on how to remove files on that list easily (in stead of one by one) would be: grep and sed. Try to make yourself familiar with those (also called regular expressions) and command line linux becomes a lot more fun.
If you delete an item inadvertently, Box does not immediately remove it. Instead it remains in your trash for 30 days, during which time you can recover it. (Administrators of Business and Enterprise accounts can shorten or lengthen this 30-day period.)
However one thing I cannot yet seem to get it to do is to remove original directories. The --remove-source-files flag does just that, removes the source files, but not also source directories. I wish there were a --remove-source-directories flag as well, but there's not.
We obviously need to keep our data on our file servers, but we want to make new groups to hold the permissions. Right now we have single users assigned to folders through NTFS permissions all over the place and its a total nightmare.
Any one know of any scripts or tools that could help delete old SID's of deleted users from folders, remove permissions of current single users without going into each folder individually, etc etc? Feel free to ask questions, I know this is pretty open-ended.
You probably can just turn Inheritance on for some root folders, put a group in there, let it propagate throughout the file server. This should remove the explicit user permissions that have been granted. Once that cruft is gone you can make your groups in folder roots or subfolders as needed.
an example you have folder call share reset all other subfolder permissions to same as share on share remove all unnecessary users and only give domain admins permissions and all the subfolders files inside will have same perms
If you want to do a complete redo, I would robocopy the file and folder structure over with the /create switch, set all of the permissions on the folders as you want them using groups, and then robocopy the data over. They will then inherit the new permissions.
If you are starting fresh with file permissions, then I would start at the top most folder where you want to recreate those permissions, go to advanced security settings, set full control for administrators, remove any other unnecessary permissions, then click the option to "Replace all child object permission entries with inheritable permission entries from this object", and then click ok. This will remove all permissions on all subfolders and give you a clean slate. Once in a while, you'll run into some folders where the administrator was denied access or removed from the permission list. In this case, you would want to repeat the process, but this time, Change the owner to the administrator, and then click the option to "Replace owner on subcontainers and objects".
The folders in question can neither be subscribed to nor unsubscribed from, because there are no checkboxes next to them. As you can see by the attached screenshot, I only have the stock folders subscribed. Do you mean that I should temporarily unsubscribe even from them?
Folders are a way to organize conversations into a common view. In other words, a folder is a custom view of conversations that already exist in one of your other top-level folders. This article will help you create your first folder.
Folders are created via rule-based Workflows, which allows you to define folder conditions to suit your needs. These folders are displayed in your inbox's sidebar and can be quickly accessed by your team.
Folders are helpful when needing to group conversations based on specific criteria. For example, you might want to group conversations based on the conversation topic, or group conversations based on how long the customer has been waiting for a reply. There are a variety of workflow conditions that can be used to define your folders.
Keep your workflow folders as strictly defined as possible.
Workflow Folders that copy thousands of conversations can lead to poor performance, such as incorrect folder counts or folders that are slow to refresh. If you've given it a bit of time and the numbers still seem off, get in touch.