qemu-img can convert many formats.
Here is an example of how to convert different images to different formats for QEMU-KVM
The example above converts a raw windows2019.img file from QEMU to a Virtualbox .vdi
qemu-img convert -f raw -Ovdi windows2019.img windows2019.vdi
-f raw = this means the format of the source image (instead of raw it could be vdi, vmdi, qcow2 etc..)........
Downloading and compiling from source to get the latest version of Asterisk is really simple with this guide.
apt install gcc make g++ libedit-dev uuid-dev libjansson-dev apt install libxml2-dev sqlite3 libsqlite3-dev
tar -zxvf asterisk-16-current.tar.gz
If you get this error change y........
A very handy feature of ImageMagick's convert command is that it can convert PDF's to other image formats like jpg but did you know you can even manually select a range or specific pages from the PDF?
Here is an example of converting a range of pages from a PDF in this case pages 25 to 36:
convert -density 300 "vSphere 6.5-1.pdf[25-36]" vsphere.jpg
Here is an example of converti........
The example below converts youvm.img into a vdi.
The -O vdi specifies the new format will be vdi but you can use any other valid formats/vice versa.
qemu-img convert yourvm.img -O vdi yourvm.vdi
This is very handy for those who need to switch between virtualization technologies.........
This is a great way to use your ftp server space, for example on your web hosting account (althoughI believe many hosts don't allow storage like this), but if you have a VPS/Dedicated Server etc.., this would be perfect. Imagine how easy it is to work with an ftp account that you can just mount as a normal partition or directory in Linux, it would be great for backups etc..
curlftpfs - mount a ftp host as a local directory
I successfully created a single RAID 1 partition which includes /boot inside it and my root directory through the Debian installer. It said GRUB installed successfully but when I try booting the OS it seems GRUB can't read anything.
When trying to boot from GRUB
GRUB Loading stage 1.5.
GRUB loading, please wait...
I get "Error 2" when trying to boot Debian. I also notice from a LiveCD that........
The folder I was trying to archive is about 72GB, but much like rsync at about 17GB it chokes because of the filesize. What's with so many common and essential Linux tools having such limitations? I guess it is likely that the authors never wrote their code with the idea that files would be so large but it's still very annoying. It's important to stay on top of these limitations on production servers because I didn't realize what happened until I checked the file with "........
I decided on using yum to help me decide even though I normaly use proftpd I decided to see what else I could find.
yum search ftp
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* rpmforge: ftp-stud.fht-esslingen.de
* base: mirrors.netdna.com
* updates: updates.interworx.info
* addons: yum.singlehop.com
* extras: mirrors.netdna.com