Kernel panic on Linux is hard to identify and troubleshoot. Finding a root cause of a kernel panic often requires reproducing a situation that occurs rarely and collecting data that is difficult to gather. As the name implies, the Linux kernel gets into a situation where it doesn’t know what to do next. When this happens, the kernel gives as much information as it can about what caused the problem, depending on what caused the panic.

If your laptop/PC/virtual machine running Linux is booting straight to BIOS, it might indicate there’s something wrong with your boot partition (/boot). In this post I’m going to learn you a thing or two about fixing said /boot partition and recovering a broken Linux system.

I’d like to dedicate this post to my dear friend – C.P. – who once said: ”How the f!!k do you setup FTP on this stupid OS”. His words game me inspiration, an idea for the best post this blog will ever be a home of: How to setup an SFTP server in the fastest, easiest and just secure enough to be acceptable.

For the past month, I was using cable connection in my office. The reason being – I couldn’t connect to wi-fi! I never really bothered solving that problem, because I hardly ever had to work without an ethernet cable nearby. This unfortunately has changed today and I had to finally do some NetworkManager troubleshooting.

The story how Linux failed me or how I failed to understand Linux. When I first started using VMware View, I instantly decided to use it on my Linux laptop. Everything went fine without any issues up until I had to connect to Horizon Server with no VMware Blast support (RDP only).