# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm # dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm
EPEL stand for Extra Packages for Enterprise Linux.
EPEL repository is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux,
including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Enterprise Linux(OEL).
Extra Packages for Enterprise Linux (EPEL) - (See http://fedoraproject.org/wiki/EPEL) provides rebuilds of Fedora packages for EL6 and EL7. Packages should not replace base, although there have been issues around point releases in the past. You can install EPEL by running yum --enablerepo=extras install epel-release. The epel-release package is included in the CentOS Extras repository that is enabled by default. Support available on Freenode in #epel, on mailing lists, and its issue tracker. If you are willing to help test EPEL updates before they are pushed to stable, you can enable the epel-testing repository on your development/testing servers. Enabling epel-testing on production systems is not a good idea.
Remi repository is a yum repository maintained by a French dude – Remi Collet. This post describe the basic steps to prepare and install the additional
CentOS packages with EPEL and Remi Repository into CentOS 6.
Remi Repository - (See http://rpms.remirepo.net/) Remi Collet maintains a large collection of RPMS, including latest versions of PHP etc.
He's also got an FAQ at http://blog.remirepo.net/pages/English-FAQ .
Note that this is a collection of repos, and using the -safe series will ensure that nothing from the base CentOS Linux distro is overwritten or replaced.
However, be aware that this repo does not play nicely with other third party repos - for example,
Remi's packages contain Obsoletes: lines for packages from both IUS and Webtatic repos and thus will automatically replace them with the .remi version.
This may not be the desired behaviour and you should be careful with enabling this repo for that reason.
About 'enabled' and 'disabled' repository configuration files
Please read man 5 yum.conf, particularly the discussion of enabled=0 versus enabled=1 . A line containing one of these options is recommended for each repository in each .conf file in the /etc/yum.repos.d/ directory. This allows the administrator to more clearly specify whether a repository is or is not used for packages. After any edits of these files, in order to clear any cached information, and to make sure the changes are immediately recognized, as root run:
# yum clean all
After modifying the repository file with new entries, proceed and clear the DNF / YUM cache as shown.
# dnf clean all OR # yum clean all
To confirm that the system will get packages from the locally defined repositories, run the command:
# dnf repolist OR # yum repolist
To map a network drive, type the following command:
net use DRIVE: PATH
DRIVE is the drive letter you want to use and PATH is the full UNC path to the share.
So, for example, if we wanted to map drive letter K to the share \\PC-name\files, we’d use the following command:
net use K: \\PC-name\files
By default, mapped drives are not persistent. If we map drives using the commands we’ve talked about so far, the mapped drives would disappear when you restarted your computer. If you’d rather those mapped drives stick around, you can make them persistent by using the
/persistent switch. The switch works as a toggle:
- /persistent:Yes: Makes the connection you’re currently creating persistent. Future connections you make using the command during the same session are also persistent (you don’t need to keep using the switch) until you use the
/persistent:Noswitch to turn it off.
- /persistent:No: Turns off the persistency toggle. Future connections you make are not persistent until you turn the toggle back on.
So, essentially, you could type something like the following command:
net use s: \\tower\movies /user:HTG CrazyFourHorseMen /persistent:Yes
And the drive map would be persistent. All future mapping you create (even if you don’t use the
/persistent:Yes switch) will also be persistent until you turn it off using the
If you ever need to delete a mapped network drive, all you have to do is specify the drive letter and add the /delete switch. For example, the following command would delete the drive mapping we assigned to drive S:
net use s: /delete
You can also use the asterisk as a wildcard should you ever want to delete all your mapped drives in one go:
net use * /delete
How to Install Remote Desktop - Xrdp Server on CentOS 8
Installing Desktop Environment
dnf groupinstall "Server with GUI"
dnf install epel-release
dnf install xrdp
systemctl enable xrdp --now
You can verify that Xrdp is running by typing:
netstat -antup | grep xrdp
systemctl status xrdp
firewall-cmd --permanent --add-port=3389/tcp firewall-cmd --reload
chcon --type=bin_t /usr/sbin/xrdp chcon --type=bin_t /usr/sbin/xrdp-sesman
Problem with yum update
[root@b1s tmp]# yum update
Extra Packages for Enterprise Linux Modular 8 - x86_64 148 kB/s | 117 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 2.6 MB/s | 8.0 MB 00:03
created by dnf config-manager from file:///root/= 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'root_':
- Curl error (37): Couldn't read a file:// file for file:///root/=/repodata/repomd.xml [Couldn't open file /root/=/repodata/repomd.xml]
Błąd: Failed to download metadata for repo 'root_': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Open folder /etc/yum.repos.d
delete epel repository - files with new date