From: Tomasz Torcz <zdzichu@irc.pl>
To: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: inotify - i dont get a inotify device
Date: Wed, 20 Jul 2005 13:40:01 +0200 [thread overview]
Message-ID: <20050720114001.GB10223@irc.pl> (raw)
In-Reply-To: <1121858078.17798.2.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Wed, Jul 20, 2005 at 01:14:38PM +0200, Kasper Sandberg wrote:
> hello.. i have a small problem with inotify in kernel 2.6.13-rc3-git4 -
> i do not get the inotify device, i know i build it in,
> gzcat /proc/config.gz | grep -i inotify confirms it, and i have a very
> new udev, where inotify is in the rules file, i tried udevstart but it
> did not create me the inotify device..
> anyone that can help? perhaps a fix is known?
Inotify got converted to using syscall. There is no longer a device
node. You can check the details of using inotify here:
http://rlove.org/log/2005071401.html
--
Tomasz Torcz "God, root, what's the difference?"
zdzichu@irc.-nie.spam-.pl "God is more forgiving."
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
prev parent reply other threads:[~2005-07-20 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 11:14 inotify - i dont get a inotify device Kasper Sandberg
2005-07-20 11:40 ` Tomasz Torcz [this message]
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=20050720114001.GB10223@irc.pl \
--to=zdzichu@irc.pl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.