i want to ask , i have installing DRBD binary package for CentOS on RHEL v5, there is 2 files.
1. drbd83-8.3.13-2.el5.centos.x86_64.rpm
2. kmod-drbd83-8.3.13-1.el5.centos.x86_64.rpm
first i execute drbd83-8.3.13-2.el5.centos.x86_64.rpm file with rpm -i <filename>, and then i execute kmod-drbd83-8.3.13-1.el5.centos.x86_64.rpm file with same command, but the second operation give output below :
error: Failed dependencies:
kernel(rhel5_lib_u6) = aab649531cab69cbeff5665f2aef9e0dba844b20 is needed by kmod-drbd83-8.3.13-1.el5.centos.x86_64
so what i must to do ??
i know, it required dependencies file named is aab649531cab69cbeff5665f2aef9e0dba844b20, but i do know what is aab649531cab69cbeff5665f2aef9e0dba844b20 ??
The error says that the kernel DRBD module (driver) you install is not built for the kernel version you have. The kernel version can be seen using
rpm -qa | grep kernel
Ensure that you have updated your Centos system (using 'yum update') and that you have the last relevant kmod-drbd.
On the Centos packages repository I can see that there is a newer drbd-kmod version than yours
Related
I got a binary kernel module provided by 3rd party, which expects version magic 5.4.0-81-generic SMP mod_unload modversions aarch64 of the kernel. It means that I need to grab the exact source tree to build the kernel for using the .ko, on my own customized SoC platform.
Now I have serveral questions for this task:
5.4.0-81-generic: 5.4.0 seems refer to the official kernel version 5.4; what is 81? Is this a patch level (or abi number)?
Can I obtain the exact source tree by patching the official kernel version 5.4? If so, where can I find the corresponding patch file for patch level 81?
I can do apt install linux-source-5.4.0, but there is no patch level on the linux-source pkg name. However, to install the headers, there are patch level on the pkg name, e.g. apt install linux-header-5.4.0-81? Why the difference?
Thanks!
Ubuntu collects its own patched sources into a source package which you can download.
The version number includes a build version; the upstream sources (the Linux kernel) does not have an Ubuntu build, but each released build has a specific version with a number after the dash and you want exactly the right one.
apt-get install linux-headers-$(uname -r)
If you want the full sources,
apt source linux-generic
though in practice you want to read the instruction it prints and download the sources from Github.
Perhaps see also https://ubuntu.com/kernel and https://linuxhint.com/install-linux-kernel-ubuntu/
I have to manage an Ethernet traffic card (my Linux target board(mips32)) having net-snmp 5.5 installed on it.
I want to upgrade it to latest net-snmp 5.7.3 and have successfully compiled net-snmp.
After that I had changed the all the libnetsnmp* library files, MIB text files and snmpd and snmptrapd daemons...but it gives errors like failed to open shared library ....can not find libnesnmp.so.20 files Why it is throwing this error even though I have updated net-snmp library files.
I am confused that what files of 5.5 has to be replaced by the 5.7.3, in order to upgrade my net-snmp package.
Also please guide me the steps to install a Fresh net-snmp package on any Linux board.
The net-snmp suite comes in 3 distinct Linux packages.
net-snmp (the snmpd agent and snmptrapd daemons, documentation, etc)
net-snmp-utils (various utilities e.g. for interrogating SNMP agents,
sending traps, etc )
net-snmp-libs (runtime libraries)
Have a look at https://stackoverflow.com/a/32093525/449347 to a more detailed listing of files in each.
Make sure you have updated ALL that you have installed.
EDIT ...
Paraphrasing http://www.betweendots.com/topic/45-install-the-latest-version-of-net-snmp/
When you have a CentOS box and type "yum install net-snmp", you'll get
version 5.5. If for some reason you want the latest version (5.7 at
the time of writing), then here's what you have to do:
yum remove net-snmp net-snmp-utils
Install dependencies: yum install perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker
Unpack and install net-snmp:
tar zvxf net-snmp-*.tar.gz
cd net-snmp-*
./configure
make
make install
Create an snmpd.conf and put it in /usr/local/share/snmp.
But follow above link for more info!
I have an rpm compiled in centos 5.x which requires libnetsnmp.so.10 and other shared objects. I want to create an rpm of it which is to be run on centos 6.x but it fails to install as on installation it says :
error: Failed dependencies:
libnetsnmp.so.10()(64bit) is needed and so on...
But Centos 6.x contains libnetsnmp.so.20
So I created symbolic links of libnetsnmp.so.10 of libnetsnmp.so.20.
But problem is still the same.
So can you please help me to resolve this problem?
If recompiling for Centos 6 isn't an option, you can try two things, first, install the correct libnetsnmp in the Centos 6 server. If that's not an option, you can add the following to your RPM spec file:
Autoreq: no
This will cause it not to scan your binary for dependencies (such as dynamically linked libraries), and automatically build that into the RPM.
Of course, if that version of libnetsnmp is ACTUALLY required, your just hosing yourself down the road, but likely newer versions will work just fine.
How to run a object TCL script in a LINUX environment? I am working with tcl 8.4. When i am trying to run a below code,
package require Itcl
class Tree {
variable parent ""
}
I am getting error "package undefined".
Is it possible to run a object TCl with out a package?
How to check whether the package is installed are not?
can any one help me. Any comments are accepted.
You need to install the Itcl package onto your system. As you don't say what variety of linux this is we shall guess that it is debian based. apt-cache search itcl shows itcl3 and itcl3-dev so it is likely that installing these packages will make this available.
On Debian based systems dpkg --list packagename shows if it is installed or not. For instance on my Ubuntu system:
$ dpkg --list tcl
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-========================================================================
ii tcl 8.5.0-2 The Tool Command Language (default version) - run-time files
If you are using some other Linux variety you may need to find the package management utilities for that system or get the sources for Itcl and build it yourself.
I installed Fedora 19 x86_64 on My vmware workstation. When I try to install the third party software. it give me a message "can't find kernel source files".
I checked that the kernel version is 3.9.5-301.fc19.x86_64 via uname -r.
but I found the kernel source version is higher than the current running kernel version.
there are two symblic links in /lib/modules/3.9.5-301.fc19.x86_64 folder. they are
build -> /usr/src/kernels/3.9.5-301.fc19.x86_64
source -> build
They are broken, because there is no folder /usr/src/kernels/3.9.5-301.fc19.x86_64 in my system.
Can anyone tell me why this situation happens. and how to install correct kernel source in my Fedora.
Big thanks.
Any reason to not run the latest kernel? You might benefit from updating everything first.
# yum update
Doubt you actually need the entire kernel source. Have you installed kernel-devel?
# yum install kernel-devel
If you need more, next install kernel headers.
# yum install kernel-headers
If you do update the running kernel, reboot into that kernel before installing the 3rd party software.
You can check here what is the currently most stable kernel available (and download associated RPMs if you requiere):
https://admin.fedoraproject.org/updates/kernel
The same happened to me on my Fedora 19 box and my kernel version was: 3.14.4-100.fc19.x86_64 so VirtualBox was looking for the source here:
/usr/src/kernels/3.14.4-100.fc19.x86_64
I checked my /usr/src/kernels dir which and found that it was empty. Then I downloaded the kernel src from the net which was named:
kernel-3.14.4-100.fc19.**src**.rpm
and extracted to /usr/src/kernels/ and run:
/etc/init.d/vboxdrv setup
Which returned:
Stopping VirtualBox kernel modules [ OK ]
Recompiling VirtualBox kernel modules [ OK ]
Starting VirtualBox kernel modules [ OK ]
Was working great!