| 1 |
On Thu, Feb 8, 2018 at 2:03 PM, William Hubbs <williamh@g.o> wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> I have noticed that in the latest versions of udev we are patching the |
| 5 |
> default upstream rules to accomodate our "uucp" group. |
| 6 |
> |
| 7 |
> I don't think it is a good idea to patch default rules, so, I want to |
| 8 |
> bring up possible fixes. |
| 9 |
> |
| 10 |
> First, baselayout has had the "dialout" group since 2015, so the |
| 11 |
> longterm fix imo is to possibly use that instead of the uucp group. What |
| 12 |
> would it take to make that happen, or are we stuck with the uucp group |
| 13 |
> forever? |
| 14 |
|
| 15 |
I think a news item targeting current eudev/udev/systemd users |
| 16 |
announcing the change would suffice. Basically, the change means that |
| 17 |
modem/serial devices will be owned by the "dialout" group instead of |
| 18 |
"uucp", so people will need to update their group membership settings |
| 19 |
if they rely on that. |
| 20 |
|
| 21 |
> Also, I think if we are stuck with the uucp group we should write a rule |
| 22 |
> of our own instead of patching the default rules. |
| 23 |
|
| 24 |
If we keep the uucp group, I would prefer to continue patching the |
| 25 |
udev rule. This makes it very simple to notice if/when upstream makes |
| 26 |
changes to it. |
| 27 |
|
| 28 |
Whatever you do, please keep the systemd and eudev teams in the loop |
| 29 |
-- this affects more than just sys-fs/udev. |
Archives