I'll mark this as solved!
]]>We just copy the uuid related line from the pacnew files to the old files and we are set. Right???? (and reboot of course)
]]>The fifth field doesn't matter, it just stores some comments and maybe a display name. see 'man 5 passwd' for more details.
Thanks - forgot the 5...
]]>However, there was one difference regarding uuidd which I wasn't sure about:
uuidd:x:68:68:uuidd:/:/sbin/nologin
uuidd:x:995:995::/:/sbin/nologin
I'm not worried about the different uid/gid but I'm not sure whether I should add the second occurrence of "uuidd".
]]>Thanks for the heads-up.
I wonder though if it wouldn't be 'safe' to do the number change anyway as, at least as far as I understand it, the different IDs will pop up sooner or later with a new filesystem package update and this 'different IDs what should I do?' discussion would pop up again (especially if those who keep the numbers forget why they actually kept them in the future).
]]>TL;DR: if you change the uuidd uid/gid or not does not matter, either way is fine.
This is what happened:
The uuidd user/group was being created on install by the util-linux package. Since the uuidd user/group does not actually own any persistent files we did not hard-code a uid/gid as it did not matter.
However, it turns out that the uuidd user/group not existing before util-linux was installed caused some issues on fresh installs, so to work around that we added them to the gid/uid's we hardcode in the filesystem package. This required us to pick specific gid/uid numbers, which is why they are likely to differ from what you already have on your system.
You can just leave the numbers alone if you already have the user/group. If you decide to change them to the new numbers that's fine too, just remember to do a reboot so that /run/uuidd is recreated with with the correct owner/group.
Sorry for the inconvenience,
Tom
]]>[bill@Jeremiah ~]$ sudo find / -uid 68
[sudo] password for bill:
find: `/proc/758/task/758/fd/5': No such file or directory
find: `/proc/758/task/758/fdinfo/5': No such file or directory
find: `/proc/758/fd/5': No such file or directory
find: `/proc/758/fdinfo/5': No such file or directory
find: `/run/user/1000/gvfs': Permission denied
Where 998 returns:
[bill@Jeremiah ~]$ sudo find / -uid 998
find: `/proc/761/task/761/fd/5': No such file or directory
find: `/proc/761/task/761/fdinfo/5': No such file or directory
find: `/proc/761/fd/5': No such file or directory
find: `/proc/761/fdinfo/5': No such file or directory
/run/uuidd
find: `/run/user/1000/gvfs': Permission denied
So, I'm assuming that lines beginning with "find: `" are not actually results but instead output messages from the find command..
]]>- .gvfs file in my user's home
- several /proc folders related to tasks (with different IDs depending on running -uid or -gid) that are nonetheless reported to be a non-existent files/folders.
@headkase
As far as understand it you get nothing because the new group/user id does not own anything, yet, on your system. The problem would if there are still files related to the old id which would be kind of 'orphans' if you ask me.
]]>Edit:
And to confirm it I did:
sudo find / -uid 68
which returned nothing. So when I initially set the new user number, 68, and rebooted that time it did not make a persistent change in the file-system.
]]>@headcase - Google is your friend.
Thank you, I did:
find / -user uuidd
And not including permission error folders all that was returned was:
/run/uuidd
Which is an empty folder. I did change the uuidd user back to the user ID it was previously and rebooted before I did "find."
I believe "/run" is all handled at run-time so it should not matter if the user ID for uuidd was different?
]]>Dammit, I went and changed the uuidd from 998 to 68. Is there any way I can tell what files it may have owned? Should I change it back?
Look for the "-uid" and "-gid" options in find to find the files which are owned by a specific numeric id. e.g.
find / -uid 998
find / -gid 998