Tag Info

Hot answers tagged

3

Sizes given from that command (which is really overcomplicated: you could just use du -ahd 1 ~/ | sort -hr ; notice that this command includes /home itself in the list) are printed in a "Human readable" form, and they are approximated. Run these commands and you'll see that the sum of the sizes in Bytes of all the files/folders inside /home will match the ...


2

The log file gets bigger and bigger as it keeps appending to itself some recurring problem. First, identify the log file in the directory .cache that is growing in size using baobab (Disk Usage Analyzer), then open the log file using gedit and try to identify what is causing the problem. In my case it was one of the Startup Applications that was looking for ...


2

Using the df command to keep track of the disk space, and the lsblk command to keep track of the mounted drives, the script below, run in the background, will log changes in the free space of all mounted drives. It creates a log file: ~/disklog where it writes changes to (in k). If you run it in the terminal, it will output the result simultaneously. The ...


2

You can try this bash script: #!/bin/bash all_files=( $(dpkg -L "$1") ) for file in "${all_files[@]}"; do [ -f "$file" ] && du -h "$file" done Pass the name of the package as first argument e.g. bash script.sh nano. dpkg -L package will list all the files installed by package, we have saved the list as an array. It will include the parent ...


2

I think that the limitation will be the write BW of your disks. Anyway, it is important too to choose the right blocksize: ⌂89% [romano:~/tmp] % time dd if=/dev/zero of=test1.tmp count=2M 2097152+0 records in 2097152+0 records out 1073741824 bytes (1,1 GB) copied, 12,6078 s, 85,2 MB/s dd if=/dev/zero of=test1.tmp count=2M 0,37s user 3,18s system 27% cpu ...


2

What you have is a free fall sensor, (accelerometer) whether it is failing, or giving erroneous data, I'm not sure. I recomend you black list the free fall sensor, and depending on how critical your hard disk drive space is, delete or clear the syslog file as well. sudo > /var/adm/sylog I am suspicious that there is another issue as well, that logs ...


1

Could not resist expanding a bit, completely based on heemayl's concept, to make a script with two options: Only output the (total) size of an installed package (but without its dependencies, since dependencies are practically always shared, so which package should have it on its "account"?) an example: $ check_size gimp 6644.1K or: ...


1

open a terminal and at the command prompt type du -sk * | sort -n This will give you a list of the biggest files or folders in size order, with the largest at the bottom. If a folder is particularly large, cd into it and repeat the process.


1

Texmaker is a particular case. Whomever packaged it, correctly assumed it will be used to create and compile LaTeX documents, and thus marked TexLive as a recommended dependency. TexLive is a bit of a monster, the complete package suite is over 1 Gb; Texmaker marks the most common modules, that should cover most users needs. You can instruct apt to install ...



Only top voted, non community-wiki answers of a minimum length are eligible