rsync: [generator] link /slackware/slackware-10.2/slackware/l/install-packages" => slackware-10.0/extra/ham/install-packages failed: No space left on device (28)
rsync: [generator] link /slackware/slackware-10.2/slackware/l/install-packages" => slackware-10.0/extra/ham/install-packages failed: No space left on device (28)
Just a reminder that rsync may report this error "No space left on device (28)" even when it's true, meaning your array/partition has lots of space left and assuming df -ishows lots of inodes.
This can often happen on various file/fuse based distributed filesystems like gluster, es........
When is it time to leave your VPS/VDS Cloud Hosting Provider?
When Is It Time to Leave Your VPS, VDS, and Dedicated Server Provider?
Choosing the right hosting solution—be it Virtu........
How to install and configure haproxy on Linux Ubuntu Debian
haproxy is one of the best known and widely used Open Source load balancers out there and a strong competitor to nginx.
haproxy is used by many large sites per Wikipedia:
HAProxy is used by a number of high-profile websites including GoDaddy, GitHub,........
How To Create OpenVPN Server for Secure Remote Corporate Access in Linux Debian/Mint/Ubuntu with client public key authentication
Why choose OpenVPN instead of a firewall appliance?
OpenVPN can be a reliable and easy replacement for traditional hardware or just be an additional tool that your company uses so that the firewall can focus on its job rather than acting as a VPNappliance at the same time.
When comparing OpenVPN with traditional firewal........
Virtualbox vbox not starting
If you've just installed VBox and it is not starting or working, the most common problem is usually that you don't have your kernel source installed, which means there is no kernel driver for vbox so it can't work.
You may get an error that says "Kernel driver not installed" in your Virtualbox.
So the first thing you should do is install your kernel source by running this:
sudo apt-get install linux-headers-`uname -r`........
eth0 changed to eth1 or eth2 and the solution to fix it
If you move your hard drive(s) around to other computers/servers, you'll find that your eth0 keeps getting higher, the first time it will become eth1 and then eth2 etc and even higher if your server has dual or quad NICs. The reason is that udevd basically assigns eth0 tot he first NIC it finds and remembers it, if it encounters a NIC with a differentMAC, it assigns it one higher (eg. eth1).
See the example below, I have eth2 now so how doI fix it?........