All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Schindler" <uwe@thetaphi.de>
To: 'Bob Tracy' <rct@gherkin.frus.com>
Cc: debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org,
	mattst88@gmail.com, mcree@orcon.net.nz
Subject: RE: recent udev upgrade failure on alpha
Date: Mon, 15 Aug 2011 19:09:04 +0200	[thread overview]
Message-ID: <007701cc5b6e$092c7360$1b855a20$@thetaphi.de> (raw)
In-Reply-To: <00cd01cc4306$6269fe00$273dfa00$@thetaphi.de>

Today, my alpha installed Debian libc6.1-2.13-11, I will try to revert udev
to the original and remove the package hold here.

I will tell if it works!

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de


> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@thetaphi.de]
> Sent: Friday, July 15, 2011 5:47 PM
> To: 'Bob Tracy'
> Cc: debian-alpha@lists.debian.org; linux-alpha@vger.kernel.org;
> mattst88@gmail.com; mcree@orcon.net.nz
> Subject: RE: recent udev upgrade failure on alpha
> 
> Hi Bob,
> 
> > > (...)
> > > I tried then to upgrade the package "udev" (was on hold, to prevent
> > > me from making system unbootable), with the hope that the inotify is
> > > working with this debian kernel. Unfortunately that's not the case,
> > > UDEV complains about missing inotify.
> > >
> > > So is the patch below already included in some kernel images
> > > available? Or does somebody have a recent udev version as .deb
> > packages?
> >
> > I still have (and am using) my modified "udev" package
> > (udev_166-1_alpha.deb: includes the patch you quoted in your original
> > message).  I can send it your way if you wish.  In truth, the only
> > thing
> you
> > need is "/sbin/udevd" from that package to be operational, and I can
> > send you just that piece if you prefer.  Just let me know.
> 
> A patch for udev would be the best (do you have it available as a patch),
then I
> can build a custom udev whenever an update occurs. Do you have it
> somewhere on the web/dropbox whatever? But /sbin/udev is also a good
> choice for now. Maybe send both as attachment to my private mail. THANKS!
> 
> >From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614099 it seems
> >that
> this is fixed in glibc 2.13-1, unfortunately on debian-ports is only
2.11.2-13. So
> we have to wait until buildds are working :( Maybe I try to compile the
libc
> package (hours of waiting included...)
> 
> > The underlying problem isn't anything missing in the kernel (at least
> > when built from the mainline kernel.org source): inotify_init1() is
> > definitely
> there.
> > The problem is the userspace call to inotify_init1() in the current
> > Alpha version of libc6.1 is a stub function.  I elected to rebuild the
"udev"
> package
> > with a valid workaround rather than risk modifying and having to debug
> "libc"
> > :-).
> 
> I was confused about the whole discussion, thanks for making it clear.
> 
> Uwe
> 
> 
> --
> To UNSUBSCRIBE, email to debian-alpha-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
> Archive:
> http://lists.debian.org/00cd01cc4306$6269fe00$273dfa00$@thetaphi.de


  reply	other threads:[~2011-08-15 17:09 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
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 [this message]
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='007701cc5b6e$092c7360$1b855a20$@thetaphi.de' \
    --to=uwe@thetaphi.de \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcree@orcon.net.nz \
    --cc=rct@gherkin.frus.com \
    /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.