Switching to Linux: A Comprehensive Guide on Drivers, Software Management, and System Transfer

0
17
Asked By CuriousCat94 On

I'm planning to dive into Linux full time after working with low-level system components in Windows for a while. I've previously dabbled with various Linux distributions like Debian, Ubuntu, Kali, and Fedora, and now I'm keen on using Arch because I love its modularity and build-it-yourself philosophy. However, I have a few questions that I hope you all can help clear up:

1. Regarding drivers: Do I need to install them on Linux? I've seen that most are included in the kernel by default, but I've also heard it's recommended to install things like Nvidia drivers directly from their packages. Is the reason for this that only open-source drivers are included in the kernel?

2. How does program installation and uninstallation work compared to Windows? I've read that uninstalling a package on Linux removes all related data, whereas Windows often leaves behind residual files. If I use a package manager to install and then uninstall a program, will it get rid of every file related to that software?

3. What's the process for transferring an installation to another computer? Is it advisable? With Windows, this is typically tricky due to motherboard-specific drivers, but since drivers are generally included in the kernel, will this even be a problem as long as the kernel is updated? Any advice on best practices would be greatly appreciated!

1 Answer

Answered By TechGuru89 On

1. Yes, only open-source drivers come bundled with the kernel. If a driver can't meet coding standards or hasn't been integrated yet—like some wireless drivers—those will need to be provided either by your distribution in a separate package or installed manually.

2. This really depends on your package manager. For example, with 'apt', it usually keeps configuration files in /etc during uninstallation unless you use the `--purge` option. However, anything in your home directory won't be removed automatically.

3. Transferring the installation itself can be tricky if you're dealing with proprietary drivers that need specific versions. UEFI firmware might also require a new boot entry when switching hardware, and tools like efibootmgr or boot-repair might be necessary.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.