Ed Greshko:
>> I guess you did "dnf info openvswitch" and
"dnf info libhugetlbf"?
>>
>> I'm guessing those are what resulted in the reservation of the
>> ID's.
Jon LaBadie:
> What? Just asking for information as an ordinary user might
> cause a change to system files? Doesn't seem likely.
Ed Greshko:
You are right. My response was poorly worded.
The first line was a referenced to the question "I don't know what
hugetlbfs is, nor openvswitch"
I originally misread your post as meaning to suggest I'd done a
dnf install openvswitch
dnf install libhugetlbf
As in I'd installed them myself, and caused the issue. Hence my
subsequent reply about it being a default install, with just a few
extras (which didn't include those packages).
But, yes, before posting that I didn't know what they were, I had read
the package info, and it didn't particularly leave me any wiser.
$ dnf info openvswitch
Description: Open vSwitch provides standard network bridging functions
and support for the OpenFlow protocol for remote per-flow control of
traffic.
Doesn't really tell me if that's some feature of networking that I
might be making use of without knowing about it.
$ dnf info libhugetlbfs (with the missing "s" on the end of it)
Description : libhugetlbfs is a library which provides easy access to
huge pages of memory. It is a wrapper for the hugetlbfs file system.
Applications can use huge pages to fulfill malloc() requests without
being recompiled by using LD_PRELOAD. Alternatively, applications can
be linked against libhugetlbfs without source modifications to load BSS
or BSS, data, and text segments into large pages.
Likewise, I can't tell, from that, whether it's a feature that my OS is
making use of at the moment, or might be at some time.
The second was to confirm that those packages were the ones that
consumed the GID which was wanted.
Between your posts, and poking around with dnf and rpm queries, I
seemed to cleared up the problem with setting the computer on fire.