I need to install old kernel into Kali (Debian like) distro. I need to run program which requires older kernel.
I downloaded kernel but the installation gives me too many errors. I was reading similar topics and watch the videos, but so far I am not successful.
I do not have experience with kernels. Is there .deb package for kernels or any other easier way to do it?
Can I use such old kernel for this distribution?
Thank you
The 2.4.33 kernel is pretty old. According to Debian's packaging files installing that old a kernel doesn't seem to be doable in wheezy. Attempting to install and run an old kernel outside the packaging system is not going to to work. All the "modern" libraries and applications will be broken when running the 2.4 kernel, as will the program (you need more than just a kernel for your program). If it were me, I'd set up a virtualization environment like VirtualBox or something similar and pick an old distro like CentOS 3.9 or an older Debian release (sarge or later). If that's not an option, you could always try and port the program to a more recent kernel.
Related
I have a raspberry on Raspbian and a vm on Kali linux.
My question is simple :
Kali is based on Debian.
Kali last kernel is 4.19 but Debian last kernel is about 4.9.
So, can I add debian sources.list to my Kali and upgrade my kernel to Debian 4.9 ?
I tried and it seems to work.
Is the upgrade of kernel possible only with distributions that have the same packet manager (yum, apt...) ?
Thanks !
Proc
Yes, since as you noted both are based on the Debian distro. Sticking with the same distro and package manager is the safest route. While many distros offer interoperability options (e.g. Alien) the conventional wisdom is summed up rather well here:
Because different distribution families use different packaging systems (Debian: *.deb / CentOS: *.rpm / openSUSE: *.rpm built specially for openSUSE), a package intended for one distribution will not be compatible with another distribution. However, most distributions are likely to fall into one of the three distribution families covered by the LFCS certification.
From https://www.tecmint.com/linux-package-management/
Also, a handy super-reference for distros and packaging: Distrowatch
I'm trying to replace centos 6.6 system with centos 7.2, but my kernel module for centos 6.6(kernel 2.6.32) dose not work on centos 7.2(kernel 3.10.0).
There is no source code and I am just a server engineer, not a programmer.
Could you please help me... is there any good solution?
For example, kernel module converter 2.6.32 => 3.10.0, or some hacks to force loading old kernel module...
You can, depending on the kernels.
You can also force load it. But if you force load it your system might crash, depending on how you do it.
I tried that with mint 17 and mint 18.
I am running CentOS 6.5 on top of Linux kernel 2.6.32-358.6.1.el6.x86_64
I got a warning from my vserver hoster that I need to upgrade to a Linux kernel > 3.15-rc5 because there is a security breach that would allow my server to be taken over.
I did a yumupgrade, but it wouldn't upgrade the kernel to a higher version than 2.6.32-358.6.1.el6.x86_64.
Currently I am confused about how to go on.
Could anybody tell me what is going on and how he would act in my position?
Thank you!
That kernel is a development kernel and will likely require you compile from source to install it. Upgrading from kernel 2.6 to 3.1n will likely break a bunch of packages also. The upgrade path for 3.1n in CentOS would be to upgrade to CentOS7 and then compile that kernel yourself.
CentOS backports security fixes and I certainly haven't heard anything about any security bug, and we manage like 150 centos servers. I would ask your host to specify what the security bug is and which patch applied in the 3.15-rc5 kernel fixes it. Who's the host?
I'm using CentOS 6.5 and have no problem using the ElRepo Long term kernel (currently 3.10.x).
See http://elrepo.org/tiki/kernel-lt
Upgrading was just a case of
yum --enablerepo=elrepo-kernel install kernel-lt
and rebooting.
I have been working with Linux kernel, compiling and inserting modules, in my custom kernels. Previously I had Ubuntu where I had been working with my custom kernel and all the commands for compiling and installing kernel worked like a charm once I had installed all the required libraries.
Now I have switched over to Fedora 20, here I want to install my custom kernel and for that I downloaded all possible kernel tools, namely, Kernel Development Kernel Tools these are group installs and other libraries that I downloaded were ia32 libraries (as I am working on 64-bit OS), kernel-devel package. Still I am not able to work with make-kpkg command. It says bash: make-kpkg: command not found....
I googled out and did everything I could.
Can anyone get me out of this trouble?
make-kpkg is a Debian kernel packaging tool. It does not exist on RHEL family distributions, such as Fedora.
Please refer to the Fedora documentation page "Building a custom kernel" for the correct procedure. (I have not reproduced it here as it is rather long, and I'm not sure how far you may have gotten.)
The make-kpkg tool is part of the 'kernel-package' package on Debian systems. It is a Debian tool to produce debian package files. Ubuntu is based on Debian and has this tool. However, Fedora uses a different system to manage packages. So, make-kpkg would not be available on Fedora.
Can I install an older version of gcc/g++ (4.1.3) on the latest Ubuntu (which comes with 4.4.3) and use it to compile a .so which should run on CentOS? The binary compiled with the Ubuntu version of gcc fails to load on CentOS because of missing imports (GLIB_2_11, ...). I need C++ (including exceptions), so I can't just statically link against glibc, which I already tried.
Can I install the older gcc without removing the newer one? How do I go about the libs required by the older gcc?
I'm currently developing code in CentOS, but it's such a pain to use. I really want to move to an Ubuntu desktop.
g++-4.1 is available for Ubuntu; just run apt-get install g++-4.1 then run g++-4.1 instead of g++. However, simply using an older compiler may not fix all of your library issues.
Like Joachim Sauer said, your best bet is to do your development on Ubuntu then do the final compilation on CentOS.
Even though you're using C++, static linking should still be an option. (However, you're much better off compiling on CentOS and using dynamic linking.)
Edit: A virtual machine is the most straightforward way to build on CentOS, but if you want to avoid the memory and CPU overhead of running a VM and don't care about differences between Ubuntu's and CentOS's kernel, then you can create a subdirectory containing a CentOS or Fedora filesystem and chroot do that to do your builds. This blog posting has details.