You are not logged in.
I've been wondering for a while, how do you guys keep your system clean? When my system was exactly how I wanted it, I went on trying other applications et cetera. This brought all sorts of packages and dependencies with it, for which I accurately kept a list so I could uninstall all off them and thus, keep my system clean. (Don't get me wrong, I know off the -Rns switch, but I'd still like to check for all dependencies.)
So, how do you do this? Off course there's pacman -Rs $(pacman -Qtdq) and cleaning your cache afterwards. But what other tricks do you have, except for those and the manual-dependency list?
Last edited by Unia (2011-07-16 17:28:19)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
I always make system images right after a fresh install, then it's no problem to experiment at will and break the system routinely because it's only about a 3 or 4 minute restoration process to bring the system back to its pristine condition.
Edit: forgot to add that any upgrades that I like call for a new imaging process.
Last edited by ozar (2011-07-16 17:39:36)
oz
Offline
If I get that right, that's more like a backup than keeping things clean and uncluttered. It sounds interesting though, I gotta look into that. Any hints for me? ![]()
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
The easiest way to do that is to have 2 Arch installs: one for the system you want, and another for experimenting.
Personally, If I want to change something as major as a DE then I would fully reinstall, even if I can switch without reinstalling, it makes things easier.
Currently, on my laptop I have Arch LXDE 32bit (Main install) and Arch KDE 64bit (Looking pretty good, I might switch to it as main system someday)
Last edited by Dastingo (2011-07-16 19:44:23)
Offline
I use "pacgraph -c" to find what takes up space and then "pacman -Rss" whatever junk pacgraph turns up. Occasionally I'll use "pacgraph-tk" to find apps with crazy deps, then rebuild from ABS without the deps.
To free up space in $home, Ncdu is handy.
Last edited by keenerd (2011-07-16 20:24:24)
Offline
pacgraph was indeed a great tip! I really like it!
And to the topic: before knowing "pacgraph" I just used "pacman -Qdt" to find orphans (and mostly deleted them) and filelight to find big directories.
Last edited by matse (2011-07-16 21:46:01)
Offline
Great tip, pacgraph! What exactly does Ncdu do, what you can't do with a file manager? (check for leftover config files?)
Last edited by Unia (2011-07-16 21:48:20)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
@Unia it broswe directories but with disk usage info and sort this by space taken.
it is usefull to check what is taking too much space
O' rly ? Ya rly Oo
Offline
ncdu is my favorite tool to check folder sizes. It basically does a "du" on a target folder and allows you to browse the folders sorted by filesize. It's similar to treesize, gt5 and... what was that in Ubuntu that was called... I forgot what it was called :-D
Offline
ncdu is my favorite tool to check folder sizes. It basically does a "du" on a target folder and allows you to browse the folders sorted by filesize. It's similar to treesize, gt5 and... what was that in Ubuntu that was called... I forgot what it was called :-D
wiki to the rescue https://wiki.archlinux.org/index.php/Co … y_Programs !
Offline
You may also want to keep an eye on files not owned by any packages:
Offline
Another tool is in the pipeline: http://mailman.archlinux.org/pipermail/ … 13926.html
Offline
This is basically why I wrote pacsync:
https://bbs.archlinux.org/viewtopic.php?id=109028
With that, I can install packages wildly without fear, then when I want my system back to normal, just run pacsync. If I haven't tweaked my config to include the new packages I want, all the crap I installed gets removed. It's not a perfect solution, but it's certainly nice to have. It solves a few other problems too.
Offline
hose all the dust out of the case every 3 months. clean the keyboard and monitors weekly.
Hofstadter's Law:
It always takes longer than you expect, even when you take into account Hofstadter's Law.
Offline
I just clean my cache and unneeded dependencies after I try a ton of new stuff I don't want to keep. Aside from that, I guess I'm just satisfied with a single set of applications most of the time, so I don't commonly clutter up my system.
Offline
You may want to try pacruft.
Offline
You may want to try pacruft.
It looks good, but it also lists packages that I think aren't safe to remove, even though you haven't used them quite a while. For example, it listed grub :\
Still gotta look into pacsync, it looks promising but also time consuming..
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
I usually run these two commands:
pacman -Scc
pacman -Rs $(pacman -Qqtd) - although every once in a while this tries to remove things I use...
Bleachbit is a pretty good GUI app too.
Last edited by Mr_ED-horsey (2011-08-21 21:04:20)
Desktop: Fedora 21 Mate + Compiz [x86_64] on 2 TiB HDD / Windows 7 Professional [x86_64] on 500 GiB HDD
Laptop: Arch Linux + Openbox [i686] 120 GiB SSD on Acer c720 Chromebook
Offline
This is a great script. To enhance it, having two columns as the output the first would be the file and the 2nd would be the corresponding filesize sorted in decending order would be great! Anyone with bash skills up to it?
+1 for bleachbit by the way.
# bleachbit --delete system.cache system.localizations system.trash system.tmpLast edited by graysky (2011-08-21 21:12:41)
Offline
anonymous_user wrote:This is a great script. To enhance it, having two columns as the output the first would be the file and the 2nd would be the corresponding filesize sorted in decending order would be great! Anyone with bash skills up to it?
Replace the last line of the script with:
comm -23 "$fs" "$db" | xargs stat -c "%n %s" | sort -rn -k 2This will misbehave if any unpackaged files have spaces in their names. In that case, you might just want to reverse the size and name fields, like this:
comm -23 "$fs" "$db" | xargs stat -c "%s %n" | sort -rnI find that version's output much easier to read in any case.
I didn't put this in the wiki page as I think it's of limited utility.
Offline
Bleachbit looks and is great! Another tool for my standard set up ![]()
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
After I install stuff for tests I query the installed packages by date and remove what I don't want (easiest way I found to go back to my stable system. I just need to have an idea of what I started installing for the tests.)
yaourt -Q --date
Offline
^ Sorting by date.. clever! Also, I just set up pacsync and gotta say, it is amazing! Just what I was looking for actually!
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
I use baobab (Gnome's Disk Usage Analizer)
But also thanks for the pacgraph (I was using some bash scripts instead of that)
Using baobab or du with some fstab directory bind is usefull:
/usr /arch/usr auto bind 0 0
/var /arch/var auto bind 0 0
/opt /arch/opt auto bind 0 0
/lib /arch/lib auto bind 0 0
/home /arch/home auto bind 0 0
/root /arch/root auto bind 0 0
And you just write "sudo baobab /arch" (or du /arch ...), and it doesn't count your personal data on mounted drives.
Last edited by ilius (2012-03-12 13:39:14)
Offline
I always remove anything I dont need with -Rsnc and the same with pacman -Rsnc $(pacman -Qdqt)
The easiest way to do that is to have 2 Arch installs: one for the system you want, and another for experimenting.
Personally, If I want to change something as major as a DE then I would fully reinstall, even if I can switch without reinstalling, it makes things easier.
Also I would strongly agree/suggest [with] this.
Offline