Connecting to Linux
The course is part of this learning path
In this course, you will learn how to install a Linux system and connect to it, whether that be on Mac or Windows. You'll also learn how to install Linux from scratch. This course is part of the Linux Administration Bootcamp learning path, designed to get you up and running with Linux.
- Understand what a Linux distribution is, what the most common Linux distributions are, and how to choose the right one for you
- Learn how to install VirtualBox on Windows and Mac
- Learn how to install Linux using an image for VirtualBox
- Understand common issues that may arise with VirtualBox and how to deal with them
- Learn how to install CentOS from scratch
- Learn how to connect to a Linux system
- Anyone with little to no knowledge of Linux who wants to learn more about the operating system
- Professionals who want to learn about Linux to enhance their career prospects
This is a beginner-level course so there are no prerequisites, but an interest in Linux and programming knowledge in general would be beneficial.
The external resources for this course can be found here:
I wanna go over some common issues that might arise when working with VirtualBox. The first issue I wanna talk about is antivirus software. Some windows antivirus software, such as Avira, AVG, and others, had been known to interfere with the operation of VirtualBox. I've listed some errors on your screen here that can be associated with this type of issue.
If you get such an error when starting a virtual machine, try disabling your antivirus software and rebooting your system. Here's a screenshot of one such error. Again, the workaround for this is to simply disable the antivirus software or switch to another antivirus software that doesn't interfere with VirtualBox. If you happen to have a Mac, you could use it for your coursework as most of the issues we'll be talking about here are windows related in some way.
If you see an error in your virtual machine window that says something along the lines of, This kernel requires an x86-64 CPU but only detected an i686 CPU, then you need to enable the virtualization options in your BIOS, this means making sure that you have VT-x for Intel processors, and AMD-v for AMD processors enabled. This varies from manufacturer to manufacturer, so you might have to look up the documentation for your specific computer.
Another thing that can cause the, This kernel requires an x86-64 CPU message, can be that you've selected a 32-bit processor in VirtualBox itself. In this case, the error message really isn't talking about your physical processor but the virtual processor that it sees. Go into the settings of the virtual machine you're having an issue with and make sure you've selected a 64-bit version for whatever Linux distribution you're using. For example, if you're using CentOs, select Red Hat 64-bit because CentOs really is Red Hat just without the branding. If you're using Ubuntu, make sure you select Ubuntu 64-bit, et cetera.
Finally, I wanna leave you with one last troubleshooting step, which is to simply reboot your physical computer and try again. There's a chance that something is not functioning properly that isn't immediately obvious to us when it comes to troubleshooting our local systems, this is a relatively quick and harmless thing to try.
Jason is the founder of the Linux Training Academy as well as the author of "Linux for Beginners" and "Command Line Kung Fu." He has over 20 years of professional Linux experience, having worked for industry leaders such as Hewlett-Packard, Xerox, UPS, FireEye, and Amazon.com. Nothing gives him more satisfaction than knowing he has helped thousands of IT professionals level up their careers through his many books and courses.