Linked by James Ingraham on Thu 12th Apr 2012 22:36 UTC
Linux I don't actually have a reason for trying to build a Linux kernel with the CONFIG_PREEMPT_RT patch set. There's no way I can even measure the impact of it. Still, I felt like having a "real-time" Linux box, and set out to make one. Little did I know how difficult it would be to even get started.
Permalink for comment 514370
To read all comments associated with this story, please click here.
RE[2]: Lack of Slack
by wigry on Mon 16th Apr 2012 15:32 UTC in reply to "RE: Lack of Slack"
Member since:

Sorry about that very important missed detail that author wasn't Thom this time ;) Sorry again!

Still I would urge you to continue the guest of RT kernels and perhaps recommend to try out a little hands-on linux where you have to make things working yourself. This way you learn what is important and what is not, You learn linux in general, not just that particular distro. After getting a bit customed with tinkering and all the command-line stuff suggest to start trying out to compile your custom kernels from scratch - beginning from clean config that is. After couple trial and errors you learn what parts of the kernel configs are important to you and which are not. For example, if you leave V4L part out of your kernel then it probably still continues to boot, but if you choose IDE controller on SATA system then you will be greeted with Kernel panic on next boot. If you haven't configured the boot loader with previous working kernel available, then that means reinstall ;) Or if you are wizard enough, boot with some live CD, mount your partition, copy the working kernel with modules over there, configure boot loader and hope for the best. Linux is fun, if you have the time. Also you will learn A LOT.

Good luck and will be waiting for your RT kernel article still with all the comparisons, where it is better and where it is worse.

Reply Parent Score: 1