Do you have a PDF that was too large after merging using convert / ImageMagick? Use gs or ghostscript as below, specify the output file and also the input file. In the example below the output file is "outputfile-resized.pdf" and the input file is "original-pdf.pdf". Change the input file to the name of your pdf gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/prepress -dNOPAUSE -dQUIET -dBATCH -sOutputFile=outputfile........

Do you hate how Centos 7 defaults to allocating most of your valuable space to /home even though it is a production server? Here is a quick guide on how to take back that space live, while online (of course make sure you have backups just in case something goes wrong!): First we will reduce our home dir by 100G: lvreduce -L -100G /dev/mapper/centos-home WARNING: Reducing active and open logical volume to ........

lvreduce -L -100G /dev/mapper/centos-home Do you really want to reduce centos/home? [y/n]: y Size of logical volume centos/home changed from ........

The Correct Way To Resize In Place qemu-img resize kvmuserwindows2008dcetest.img +1G Image resized. Below is a common mistake that some users make they are trying to specify a new image name but it can be resized in place (just make sure the VMis NOT running and you've backed up the data in case something goes wrong). qemu-img resize kvmuser453111.img kvmuser453111-larger.img +5G New i........

I've never seen this before in all of my years. Ihave some very old CDs and DVDs 12-15 years old that seem not to work in this BD-R/DVD-R/CD-R Asus drive. The discs are fine actually and ironically they even work fine on a normal LG USB based BD-R drive! Here are the errors in Linux: [2914936.884924] attempt to access beyond end of device [2914936.884927] loop1: rw=0, want=730424, limit=688384 [2914954.556873] attempt to........

lvextend -L +10G /dev/kvmvm/w2k8r2evalstandard Extending logical volume w2k8r2evalstandard to 20.00 GiB Logical volume w2k8r2evalstandard successfully resized The above adds 10GB to the logical volume. Of course you must resize the filesystem using other tools to take advantage of the space.........

The best way I could figure out is to use another guest of some sort to do this, while assigning the disk that needs to be resized to the same guest. So say we have /dev/xvda as the guests drive and we've booted it up. We also have /dev/xvdb (this is going to be the image/disk to be resized). In this case it's based on an ext3/4 image. Run e2fsck on it to ensure there are no filesystem errors. e2fsck /dev/xvdb........