Star Kernel Space: udev Rules, But Whose?
Linked by Thom Holwerda on Sat 23rd Aug 2008 15:31 UTC
Linux "Once upon a time, a Linux distribution would be installed with a /dev directory fully populated with device files. Most of them represented hardware which would never be present on the installed system, but they needed to be there just in case. Toward the end of this era, it was not uncommon to find systems with around 20,000 special files in /dev, and the number continued to grow. This scheme was unwieldy at best, and the growing number of hotpluggable devices (and devices in general) threatened to make the whole structure collapse under its own weight. Something, clearly, needed to be done." The solution came in the form of udev, and udev uses rules to determine how it should handle devices. This allows distributors to tweak how they want devices to be handled. "Or maybe not. Udev maintainer Kay Sievers has recently let it be known that he would like all distributors to be using the set of udev rules shipped with the program itself." ComputerWorld dives into the situation.
E-mail Print r 1   23 Comment(s) http://osne.ws/fld
Thread beginning with comment 327808
To view parent comment, click here.
To read all comments associated with this story, please click here.
Erunno
Member since:
2007-06-22

Very true. Qt4 itself uses GObject so Gtk+ and Qt can use the same common main loop and thus exchange information.


Qt 4 can be (optionally) pluged into the Glib main loop. It doesn't use GObject itself.

Reply Parent Bookmark Score: 2

SomeGuy Member since:
2006-03-20

It's optional, but the default is to use the GLib event loop in QT4/KDE4.

Reply Parent Bookmark Score: 2