public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel: 'udevd'-messages after Core 145 update
Date: Sun, 07 Jun 2020 14:38:12 +0100	[thread overview]
Message-ID: <ED063EA2-EB56-46DC-97BB-3D566C66068C@ipfire.org> (raw)
In-Reply-To: <436a6fb3-f102-fbe5-1ad3-963c801195a0@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

Hi,

Those have always been there, and we should add the groups simply to avoid the noise.

Would you like to submit a patch?

LFS should have some more details about their individual configurations.

-Michael

> On 7 Jun 2020, at 13:28, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> after updating - yesterday - to Core 145 I just noticed some new kernel
> messages today (in the middle of working):
> 
> ...
> 14:06:04 kernel: <27>udevd[502]: specified group 'input' unknown
> 14:06:04 kernel: <27>udevd[502]: specified group 'render' unknown
> 14:06:04 kernel: <27>udevd[502]: specified group 'kvm' unknown
> ...
> 
> Besides of this, the update was installed without any error messages -
> no reboot required.
> 
> The machine runs unobtrusively (Deepl translation!) - no visible problems.
> 
> Hardware is a Duo Box, running Core 145 / x86_64.
> 
> Only me - or can somone confirm?
> 
> Best,
> Matthias


      reply	other threads:[~2020-06-07 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 12:28 Matthias Fischer
2020-06-07 13:38 ` Michael Tremer [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=ED063EA2-EB56-46DC-97BB-3D566C66068C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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