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.
Thread beginning with comment 514074
To view parent comment, click here.
To read all comments associated with this story, please click here.
ingraham
Member since:
2006-05-20

Well, if I'd realized how bad gconfig was I might have gone the menuconfig route, and I actually did try it at one point. Still, it OUGHT to work, so why not?

Reply Parent Score: 1

phoenix Member since:
2005-07-11

Was just about to post the same:

I decided to give up on CrunchBang


Really? You couldn't install a package to make "make gconfig" work, so you abandoned the entire OS? Really? Instead of just typing "make menuconfig" and carrying on with your day?

Aren't techies supposed to be lazy? ;) How is installing a completely new OS, learning a new package manager, yadda yadda easier than typing "make menuconfig" after "make gconfig" fails?

Reply Parent Score: 2

ingraham Member since:
2006-05-20

A ridiculous dependency loop is why I gave up on CrunchBang. Package managers are supposed to take care of this kind of thing automatically. The fact that I could have just not used those packages doesn't change the fact that CrunchBang was inherently broken. I don't want to take away from the difficulty of maintaining a distro, but when it fails so drastically out of the box, I don't see the point in sticking with it. There are so many options out there; why bother with something when it has such a glaring flaw?

Reply Parent Score: 2