linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy G <randyg@tdl.com>
To: linux-hotplug@vger.kernel.org
Subject: Kernel 2.6.26-2-686 won't boot: udev error
Date: Thu, 30 Apr 2009 17:50:51 +0000	[thread overview]
Message-ID: <1241113851.8612.4.camel@localhost> (raw)

Kernel 2.6.26-2-686 won't boot. Last messge displayed is:
udevd[400]: GOTO 'libsane_rules_end' has no matching label in:
'/etc/udev/rules.d/z60_iscan.rules'

Kernel 2.6.26-1-686  displays same error but continues.

I have removed/purged the iscan packages. The file "z60_iscan.rules" is
no longer present on the system.

Why is udev still looking for, reporting on, or using a file that isn't
present.

Debian "testing"

Thank You,
-  

Randy G

<<randyg@tdl.com>>


                Don't take life too seriously...
                        You'll never get out alive.

                                --Bugs Bunny--




             reply	other threads:[~2009-04-30 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 17:50 Randy G [this message]
2009-04-30 17:54 ` Kernel 2.6.26-2-686 won't boot: udev error Marco d'Itri

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=1241113851.8612.4.camel@localhost \
    --to=randyg@tdl.com \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).