public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: qxc@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev and inotify
Date: Mon, 1 Sep 2008 13:28:16 +0200	[thread overview]
Message-ID: <20080901112816.GA27059@citd.de> (raw)
In-Reply-To: <20080901093201.105550@gmx.net>

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.


  reply	other threads:[~2008-09-01 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1753064AbYIAJYb/20080901092431Z+302@vger.kernel.org>
2008-09-01  9:32 ` udev and inotify qxc
2008-09-01 11:28   ` Matthias Schniedermeyer [this message]
2008-09-01 11:30     ` qxc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080901112816.GA27059@citd.de \
    --to=ms@citd.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qxc@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox