From: Bob Tracy <rct@gherkin.frus.com>
To: debian-alpha@lists.debian.org
Cc: linux-alpha@vger.kernel.org, mattst88@gmail.com, mcree@orcon.net.nz
Subject: Re: recent udev upgrade failure on alpha
Date: Thu, 24 Feb 2011 01:51:49 -0600 [thread overview]
Message-ID: <20110224075149.GA28779@gherkin.frus.com> (raw)
In-Reply-To: <20110224070203.GA28419@gherkin.frus.com>
On Thu, Feb 24, 2011 at 01:02:03AM -0600, Bob Tracy wrote:
> Running "dpkg --configure udev" gives me the following:
>
> udevd[pid]: inotify_init failed: Function not implemented
> udevd[pid]: error initializing inotify
>
> and the post-installation script fails.
>
> So... What's missing or unimplemented on Alpha? Prior versions of
> "udev" worked just fine.
Found it. inotify_init1() is a stub function on Alpha. A heated
discussion *somewhere* produced a udev patch that *may* work:
--- a/udev/udev-watch.c
+++ b/udev/udev-watch.c
@@ -38,8 +38,10 @@ static int inotify_fd = -1;
*/
int udev_watch_init(struct udev *udev)
{
- inotify_fd = inotify_init1(IN_CLOEXEC);
- if (inotify_fd < 0)
+ inotify_fd = inotify_init();
+ if (inotify_fd >= 0)
+ util_set_fd_cloexec(inotify_fd);
+ else
err(udev, "inotify_init failed: %m\n");
return inotify_fd;
}
(Formatting of the above is probably bogus due to conversion from a
formatted html presentation, but the gist of the fix should be apparent).
Time to retrieve the source package and rebuild it...
--
------------------------------------------------------------------------
Bob Tracy | "Every normal man must be tempted at times to spit
rct@frus.com | upon his hands, hoist the black flag, and begin
| slitting throats." -- H.L. Mencken
------------------------------------------------------------------------
next prev parent reply other threads:[~2011-02-24 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 7:02 recent udev upgrade failure on alpha Bob Tracy
2011-02-24 7:51 ` Bob Tracy [this message]
2011-02-24 10:09 ` Uwe Schindler
2011-02-24 15:11 ` Matt Turner
2011-02-24 18:55 ` Uwe Schindler
[not found] ` <008101cbd454$02036770$060a3650$@thetaphi.de>
[not found] ` <005301cc1555$58f92c30$0aeb8490$@thetaphi.de>
[not found] ` <20110518145605.GJ3539@smp.if.uj.edu.pl>
2011-05-18 15:28 ` Uwe Schindler
2011-05-18 18:37 ` Bob Tracy
2011-07-15 14:04 ` Uwe Schindler
2011-07-15 15:17 ` Bob Tracy
2011-07-15 15:46 ` Uwe Schindler
2011-08-15 17:09 ` Uwe Schindler
2011-08-15 17:28 ` Uwe Schindler
2011-02-24 9:54 ` Michael Cree
2011-02-24 10:25 ` Bob Tracy
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=20110224075149.GA28779@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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