From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Strange udev error
Date: Sat, 30 Jul 2016 14:06:04 +0200 [thread overview]
Message-ID: <579C982C.2060809@mlbassoc.com> (raw)
In-Reply-To: <579C70FC.3040204@mlbassoc.com>
On 2016-07-30 11:18, Gary Thomas wrote:
> I just got this udev error - anyone know what to make of it?
> udevd[149]: no sender credentials received, message ignored
>
> Note: I'm running Poky/Yocto master (039f47ad) and I don't
> recall ever seeing this before and I only saw it on one target
> built from these sources, others didn't report it.
>
> Any pointers graciously accepted
>
BTW, I think this may be related to a cranky USB->ethernet
adapter I have, so if that's it, just let me know and I'll
move on...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2016-07-30 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 9:18 Strange udev error Gary Thomas
2016-07-30 12:06 ` Gary Thomas [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=579C982C.2060809@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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