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'm somewhat skeptical of the tuned-kernel movement, so I didn't install it expecting to make my OS "fly" or anything. It just happened that recently there had been some weird kernel error messages ("perf samples too long"), and, related to that or not, the OS would become sluggish with lots of read-or-write activity (on my old HDD that must be really slow, to add to sluggishness). Apparently you can sort of solve it in a sysctl-like way, printing a "0" to some file/parameter,...
# -------------------------------------------------------------------------- #
# General information
# -------------------------------------------------------------------------- #
The chapter that deals with setting up the kernel (Linux-x.y.x) is too limited in my opinion. I do realise that my extension is out-of-scope for the LFS developers, but I do think that many will benefit from it, especially if you want to tinker with kernels and their settings.
...
Well.. when you write your own kernel module, in the devel stage, chances for bringin down the kernel (panic.. ah sick) are huge.
Oops (pet name for kernel panic) mostly spits lots of martian traces that include stack addresses, registers and its value, EIP, etc.
To know the culprit line that caused panic, decode the address to line as follows:
EIP wud luk like...
WARNING: before downloading any of these binary kernels you should know that there is NO WARRANTY, you are using them AT YOUR OWN RISK!!!
If you are paranoid: yes, I am untrusted source of binary packages, these kernels should only be used for testing purposes, you are adviced not to enable networking for qemu at all.
It is better that you fetch the config and build it yourself using cross-toolkit in your distro.
These binary kernels were tested in Gentoo Linux x86_64...
I've made this post as a reminder, to link to it from forum.
Probably, if you were linked here, you had troubles when someone gained root at your system.
The problem I'm writing this post about is kernel/software cracking.
Many people had troubles with crackers who gained root at their servers or desktops. Some of users had all permissions and privileges set up correctly but still got kernel BOF'ed and rooted.
For instance, let us take most exploitable vulnerability,...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
