CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I believe I should select this package... kernel-3.10.0-862.2.3.el7.centos.plus.src.rpmMay 10, 2018
...but I have a few questions.
I also clicked the "Click Here to Find Similar Threads" button on LQ and had 5 results. Read them. This from 273 https://www.linuxquestions.org/quest...os-4175481114/
is similar to the LQ post I mentioned above, and references the same link as kdingo.
Questions
Is this the correct package?
Who's procedure should I follow? "megajason"; "kdingo"; or "273"?
Or, is there a simpler way this these procedures were first compiled?
Thanks in advance for any assistance you can provide.
Received the error. Note: Unable to copy & paste the full error message received. Instead, had to screen shot. See attached for partial error.
Searched LQ for "kernel-devel", "failed", "virtualbox", "centos"; returned 4 hits, including kdingo's However, this post is from 2008. I went to their suggested link and drilled down to <snip>
I believe I should select this package...kernel-3.10.0-862.2.3.el7.centos.plus.src.rpmMay 10, 2018...but I have a few questions.
Questions
Is this the correct package?
Who's procedure should I follow? "megajason"; "kdingo"; or "273"?
Or, is there a simpler way this these procedures were first compiled?
You're getting the error because the online repo you're after isn't available. This is probably due to the fact you're using RHEL, and are trying to use the CentOS repositories; this is evidenced by the top of your error that says "This system is not registered with an entitlement server. You can use subscription-manager to register", which is an RHEL error/information message: https://access.redhat.com/solutions/253273
To address the list:
Honestly, the answer is "maybe", since you're running RHEL and are trying to install CentOS packages. While they *TYPICALLY* are the same, they may not be, depending on your build. The RHEL install image may have a different kernel on it than the more up-to-date CentOS.
The megajason instructions are the most concise, and are accurate.
Nothing simpler.
As said in your other thread, you're using RHEL without paying; the 'entitlement' message says this. This means you DO NOT have access to the online resources. As suggested by Chrism01 here (point #2): https://www.linuxquestions.org/quest...0/#post5876061
But fresh installs are easier. Your path forward remains:
Pay for RHEL and run the megajason how-to
Load CentOS and run the megajason how-to
While you *CAN* hunt, peck, and install RPM packages one at a time, compile things from source, and do all sorts of different things, for a 'newbie' they won't be easy. A fresh install of CentOS will take about 30 minutes and you're done, as will registering your system with RHEL. Or spend hours and have a flaky system with packages that may (or may not) work together.
Two different issues/projects. This one is CentOS via VBox on PC Only CentOS was installed; no other software that I am aware of; therefore, the VBoxGA should be correct.
CentOS doesn't have entitlement servers; that's RHEL and/or another piece of commercial software on that box that isn't registered. I have three CentOS boxes spinning now, and none of them have ever given me that message, nor is it even part of the CentOS docs.
Quote:
Here is the VBox window with CentOS version and error messages (first 3 thumbnails) when running this command.
Code:
# yum install kernel-devel
Attempted VBoxGA install through mounted iso on CentOS VM desktop (last 2 thumbnails).
Right; because your system cannot receive updates, and you can't install the kernel-devel package, which is needed. Until you do that and satisfy that dependency, you will (very obviously), NOT be able to proceed. The 401/Unauthorized message hints at a proxy server issue. But again, you say nothing about your environment or what's between you and the Internet, so we can't tell you anything about how to configure a proxy for yum to use. You can turn off the entitlement message by paying for the software that's on the box, as was suggested many times previously.
dkms is no longer required by Virtualbox, and deprecated as of Virtualbox 5
Therefore, I decided to skip the rest of megajason's suggestions, as I had only performed the prework to installing VBox_GA, and return to CentOS and to install from the mounted iso (see first 2 thumbnails).
The Files "VBox_GAs_5.2.14" is ready message was not displayed prior.
After the install completed, the mouse worked immediately.
However, I was unable to copy and paste, or move files between CentOS and my Win8.1 desktop until I rebooted.
As can be seen from the previous thumbnails, I am running CentOS 7 within VBox 5.3.14r... This is on a Win81 PC.
Yes, we saw the cat command of the release file. Aside from the fact that it's a plain text file that's easy to edit/change (not saying you did....), the "entitlement server" message remains, and has two possibilities: RHEL or commercial-software installed, as stated. Either one (or both) is true.
As the above is for RHEL and not CentOS, I ran this to determine my kernel-devel version
Code:
# uname -r
3.10.0-862.6.3.el7.x86_64
and than ran this
Code:
# yum install kernel-devel-3.10.0-862.6.3.el7.x86_64
Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos,
: subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Loading mirror speeds from cached hostfile
* base: mirrors.cat.pdx.edu
* extras: mirror.es.its.nyu.edu
* updates: mirror.es.its.nyu.edu
base | 3.6 kB 00:00
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package kernel-devel.x86_64 0:3.10.0-862.6.3.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
kernel-devel x86_64 3.10.0-862.6.3.el7 updates 16 M
Transaction Summary
================================================================================
Install 1 Package
Total download size: 16 M
Installed size: 37 M
Is this ok [y/d/N]: y
Downloading packages:
kernel-devel-3.10.0-862.6.3.el7.x86_64.rpm | 16 MB 00:02
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : kernel-devel-3.10.0-862.6.3.el7.x86_64 1/1
Verifying : kernel-devel-3.10.0-862.6.3.el7.x86_64 1/1
Installed:
kernel-devel.x86_64 0:3.10.0-862.6.3.el7
Complete!
[root@jjc-tj0keu ~]#
As megajason continues with the CLI, he uses a command
Code:
yum install dkms
according to Habitual this has been deprecated in VBox 5
DKMS won't hurt either way, so following that step is optional.
Quote:
Therefore, I decided to skip the rest of megajason's suggestions, as I had only performed the prework to installing VBox_GA, and return to CentOS and to install from the mounted iso (see first 2 thumbnails). The Files "VBox_GAs_5.2.14" is ready message was not displayed prior. After the install completed, the mouse worked immediately. However, I was unable to copy and paste, or move files between CentOS and my Win8.1 desktop until I rebooted.
And how did the 401/unauthorized message go away??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Error Install VirtualBox Guest Additions.iso "Failed...Trying other mirror" - CentOS 7.5.1804/VBoxGuestAdditions.iso 5.2.14.123301/Win8.1
