Messages in this thread | | | Date | Mon, 01 Sep 2008 13:30:55 +0200 | From | qxc@gmx ... | Subject | Re: udev and inotify |
| |
OK, thx!
-------- Original-Nachricht -------- > Datum: Mon, 1 Sep 2008 13:28:16 +0200 > Von: Matthias Schniedermeyer <ms@citd.de> > An: qxc@gmx.de > CC: linux-kernel@vger.kernel.org > Betreff: Re: udev and inotify
> On 01.09.2008 11:32, qxc@gmx.de wrote: > > Hi, > > > > after I have tried it in different webboards and also in different > mailing lists from vger.kernel.org without success I afraid I have to ask my > question here (guessing that it is definitely the wrong mailing list): > > > > I have compiled a special kernel without inotify and dnotify because the > target system is very static and doesn't needs them (but kernel size is > important on that system). > > > > Unfortunately now I get an error message from udev that inotify is > missing and therefore udev can't check if its cofiguration files change (what > never will happen on that system). > > > > So my question is: how do I get rid of that error message? Can I set a > udev option somewhere that turns it off? It is verty irritating for users > because it displays an error that is no error... > > After locking into the source. > udevd.c, main-function. > Just look for the "inotify_init". It's the if/else if/else after that > > The error-message doesn't depend on any further conditions. > If you want to get rid of it, you have to patch it out, getting rid of > the else if and else should to the trick. > > > > > > Bis denn > > -- > Real Programmers consider "what you see is what you get" to be just as > bad a concept in Text Editors as it is in women. No, the Real Programmer > wants a "you asked for it, you got it" text editor -- complicated, > cryptic, powerful, unforgiving, dangerous.
-- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |