public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: handling the "uucp" group
Date: Thu, 8 Feb 2018 15:24:14 -0500	[thread overview]
Message-ID: <CAJ0EP43gmJNkkpin=ijFqJx5A=kWf3nKTD-F2C9ZWcoL8xDZgg@mail.gmail.com> (raw)
In-Reply-To: <20180208190306.GA31846@whubbs1.gaikai.biz>

On Thu, Feb 8, 2018 at 2:03 PM, William Hubbs <williamh@gentoo.org> wrote:
> Hi all,
>
> I have noticed that in the latest versions of udev we are  patching the
> default upstream rules to  accomodate our "uucp"  group.
>
> I don't think it is a good idea to patch default rules, so, I want to
> bring up possible fixes.
>
> First, baselayout has had the "dialout" group since 2015, so the
> longterm fix imo is to possibly use that instead of the uucp group. What
> would it take to make that happen, or are we stuck with the uucp group
> forever?

I think a news item targeting current eudev/udev/systemd users
announcing the change would suffice. Basically, the change means that
modem/serial devices will be owned by the "dialout" group instead of
"uucp", so people will need to update their group membership settings
if they rely on that.

> Also, I think if we are stuck with the uucp group we should write a rule
> of our own instead of patching the default rules.

If we keep the uucp group, I would prefer to continue patching the
udev rule. This makes it very simple to notice if/when upstream makes
changes to it.

Whatever you do, please keep the systemd and eudev teams in the loop
-- this affects more than just sys-fs/udev.


  reply	other threads:[~2018-02-08 20:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 19:03 [gentoo-dev] rfc: handling the "uucp" group William Hubbs
2018-02-08 20:24 ` Mike Gilbert [this message]
2018-02-08 20:32 ` Ulrich Mueller
2018-02-08 22:55   ` R0b0t1
2018-02-09  6:13     ` Ulrich Mueller

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='CAJ0EP43gmJNkkpin=ijFqJx5A=kWf3nKTD-F2C9ZWcoL8xDZgg@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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