The NVIDIA Driver is a software necessary for your NVIDIA Graphics GPU to function with better performance. It exchanges information between your Linux operating system, in this case Fedora 28 Linux, and the hardware in question, in this case the NVIDIA Graphics GPU.
In this guide you will learn how to install NVIDIA Drivers on Fedora 28 Linux. First, we will be disabling the default nouveau opensource NVIDIA Drivers and then install the official NVIDIA Driver by using the Linux terminal command.
With the use of modern Gnu/Linux distributions package managers, package dependencies are no more a problem per-se, but usually each distribution ships with a certain version of a program, and we want to install a new version we have to compile it, or rely on third party repositories. The same thing happens if the repositories of our favorite distribution doesn't contain a certain application we need. Also for an application distributor can be time-consuming having to provide different package formats for the same application.
Flatpak is a relatively new technology which aims at solving those kind of problems. Applications installed with Flatpack come pre-packaged with all their dependencies and run in their own sandboxed environment. In this tutorial we will see how to install and use flatpak on Fedora 28.
Two of the most popular and highest quality media programs available for Linux are not available through Fedora's default repositories. Of course, these are no other than Kodi and VLC, and they are available on Fedora through RPM Fusion.
Kodi, which was previously known as XBMC, has boomed in popularity as of late with both Linux and mainstream audiences.
VLC has been a long time favorite for anyone looking for a media player capable of playing content with just about any encoding or file extension.
Getting the Repositories
As with many multimedia things in Fedora, this is an instance of "RPM Fusion to the rescue." Utilizing the reliable and trusted RPM Fusion repository grants access to both Kodi and VLC as well as valuable multimedia codecs and libraries required to play many people's favorite content.
The best way to get the repositories is to use the series of commands provided by RPM Fusion.
Google Chrome is one of the fastest and most well liked browsers available. Despite its closed source, it has long been a favorite of Linux users. This is especially true because it integrates features traditionally locked behind other proprietary software, like Flash, which traditionally function poorly.
Distributions like Fedora which only ship free software don't include Chrome, but Google provides convenient repositories to major Linux distributions to make installing and managing Chrome on Linux easy.
Steam is easily the most popular PC gaming client, and with hundreds of titles available for Linux, it's not wonder why Linux gamers would want to install and use it. This is easier on some distributions than others, especially considering that Valve, the company behind Steam, officially targets Ubuntu and Debian.
Fedora users won't find Steam anywhere in the official Fedora repositories. This is mostly because of Fedora's strict free software policies. It is available through a reliable third-party repository, though, and it runs great when you get it set up.
Before You Install
Steam for Linux is 32bit only. That may feel like a hassle, but it really isn't. The only thing that you have to make sure of is that the 32bit version of your graphics driver is installed on your system.
If you are using any of the open source drivers, chances are, 32bit support is already installed and working. If you want to reinstall to be sure run whichever of the following fits your graphics card.
$ su -c 'dnf -y install xorg-x11-drv-intel mesa-libGL.i686 mesa-dri-drivers.i686'
Fedora 24 brings with it a number of technical improvements, software upgrades, and under the hood. It’s clear that the Fedora developers have been working closely with upstream sources to tightly integrate advances in everything from the kernel to GNOME, Systemd, NetworkManager, and GCC6 which have all been forged into a powerful core. However, that’s about where it ends.
When it comes to a being a full fledged desktop distribution, Fedora 24 falls a bit short, and that’s mostly due to the Fedora project’s limited repositories.
This article at is the logical continuation of our PXE article, because after reading this you will be able to network boot AND actually install the distribution of your choice. But there are other uses of creating your own repository. For example, bandwidth. If you manage a network and all the systems (or some) are running the same distribution, it's easier for you to just rsync in conjunction with a nearby mirror and serve updates yourself. Next, maybe you have some packages created by you that your distro won't accept in the main tree, but the users find them useful. Get a domain name, set up a webserver and there you go. We will not detail the setup of a webserver here, just basic installation tasks and the basic setup of a repository for Fedora or Debian systems. Hence you are expected to have the necessary hardware (the server and the necessary network equipment, depending on the situation) and some knowledge about Linux and webservers. So, let's start.
NOTE:This article was moved from our previous domain linuxcareer.com.
Creating a repository on Fedora systems
Installing the tools
Fedora has a tool called createrepo which simplifies the task at hand. So, all we need to install is that and httpd as the webserver:
# yum install createrepo httpd
Setting up the repositories
Now, after setting up your webserver, we will assume that the root directory is ar /var/www. We have to create the necessary directories in an organized matter (feel free to adjust to taste if necessary or just follow the official layout):
# cd /var/www/html
# mkdir -p fedora/15/x86_64/base
# mkdir fedora/15/x86_64/updates
You're already in the know regarding the C programming language. You got the taste of it and felt like you want to go further and write your own. Or maybe help the community and package that favorite software of yours for the distribution you like and use. Regardless of the situation, this part of the C development series will show you how to create packages for two of the most popular distributions, Debian and Fedora. If you read our articles so far and you have some solid knowledge of the command line, and you can say that you know your distro of choice, you're ready.
Before we go further...
Let's get some concepts and general ideas out of the way, just so we make sure we are on the same page. What we are about to outline here is available regardless of the project you decide to package (or contribute) for, be it Arch, NetBSD or OpenSolaris. The idea is: be careful. Check the code, whether it's yours or not, and make sure you remember that perhaps lots of people will use your code. You have a responsibility on your hands, and a pretty big one at that. If you doubt this, reverse places for a second: a package maintainer isn't careful when inspecting code and some sneaky, but grave bug makes his way installed on your computer. It's sneaky, as it only manifests itself on certain hardware and in certain situations, but it's grave enough to delete all the files resident inside your home folder. You happen to have that exact combination of hardware and mayhem ensues, as you forgot to write to DVD those pictures from your holiday. You get angry, your first reaction is to manifest negative feeling towards the operating system (or distribution) and so, following your decision to change distributions immediatley, that distro loses one user, all because one person's lack of attention and thoroughness.
Given Debian's excellent documentation, we won't be able to cover all the things one needs to become a developer. After all, this is not what we wanted. What we wanted is to show you basically how to get from a tarball to a .deb. Becoming a Debian developer takes lots of time and involves you helping out the community via IRC or mailing lists, reporting and helping fixing bugs, and so on, so that is not the object of our article. Have a look at the documentation the project provides for more insight. The Debian policy, New maintainer's guide and the Developer's reference are more than important for starting up, they must be like some kind of a book you sleep under the pillow with.
Your first stop should be, as outlined above, the policy, where you MUST acquaint yourself with the filesystem hierarchy, the archives, the fields in a control file and specific items to be remembered regarding diferent categories of software: binaries, libraries, source, games, documentation, ... Remember that a .deb file is nothing more than an archive, and it's made of two parts: the control part, with the control file and the install/ uninstall scripts, and the payload, where the files to be installed reside. It's not as hard as one would think it is. It's a very good idea that you download a .deb file, even better if it's packing some software you are familiar with, and start looking inside to see what's what. [HINT] - You can use the control file to create your own, as long as you're careful. As an example, let's take vim. deb files are nothing but ar(1) archives, so they can simply be unpacked by using the following linux command:
The intention of this config is to provide simple to follow steps on how to configure anonymous Internet browsing on Fedora Linux using privoxy and tor. Both services tor and privoxy are standalone services where tor provides anonymity using onion routing techniques and privoxy is a proxy server with content filtering and advertisement blocking.
Let's start by installation of both services:
# yum install privoxy tor
After the install start tor:
# service tor start
Redirecting to /bin/systemctl start tor.service
The following config will demonstrate how to install Adobe Flash player on Fedora Linux. The following linux commands are separated into two sections to show Adobe Flash player installation for 32-bit and 64-bit architectures.
Adobe Flash player installation on Fedora Linux 32-bit
Currently, the default python version on Fedora Linux is Python 2. Later Fedora Linux release 22 will ship with the Python 3 as a default version. In this config you will learn how to switch between python versions on Fedora Linux. Let's start by listing all Python versions available on your Fedora system: