All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: Michael Cree <mcree@orcon.net.nz>
Cc: debian-alpha@lists.debian.org, mattst88@gmail.com,
	linux-alpha@vger.kernel.org
Subject: Re: recent udev upgrade failure on alpha
Date: Thu, 24 Feb 2011 04:25:47 -0600	[thread overview]
Message-ID: <20110224102547.GA29330@gherkin.frus.com> (raw)
In-Reply-To: <4D662AD3.5000700@orcon.net.nz>

On Thu, Feb 24, 2011 at 10:54:27PM +1300, Michael Cree wrote:
> Oops, sorry, I should've sent a message to the list to warn people of this!

Not your job to protect us from ourselves :-).  Besides...  What better
way to see who's still actively (in some sense) involved in the Alpha
community, eh?

> As you have identified the problem is that the syscall inotify_init1() 
> is not implemented in the Debian supplied kernel.  It did not make it 
> into the kernel until version 2.6.33. I did submit a bug report and a 
> patch to update the kernel to the Debian bugzilla but I was too late and 
> the Squeeze freeze beat me to it and it didn't get included.

Actually, I've been running "sid" for a long time...  The risk of a
broken system has always been there, but needless to say I've been
lucky.  Besides, that's the only way to get current packages on the
Alpha from Debian these days.  That's a roundabout way of saying I'm
running late enough kernels (both Debian-supplied and built from
kernel.org source) that inotify_init1() was definitely present in the
running kernel when I did the upgrade.  As you point out later in your
reply, libc6.1 hasn't caught up on Alpha: I noticed the stubbed-out
function.

As I type this, I'm back up and running with a patched udev_166-1.  It
was easier and faster to patch/build "udev" than do a libc6.1 build.
When the smoke cleared, I simply copied in the new version of
"/sbin/udevd" and was finally able to configure the installed package
(as well as the other 49-or-so packages).  That's more excitement than I
wanted this evening: local time is now 0424 and I've been up since 0700
yesterday :-(.

-- 
------------------------------------------------------------------------
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
------------------------------------------------------------------------

      reply	other threads:[~2011-02-24 10:25 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
2011-08-15 17:28           ` Uwe Schindler
2011-02-24  9:54 ` Michael Cree
2011-02-24 10:25   ` Bob Tracy [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=20110224102547.GA29330@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 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.