On 3/12/20 3:20 AM, Pierre Labastie via blfs-support wrote:
Le 12/03/2020 à 08:26, Teresa Williams via blfs-support a écrit :
Noticed this today:
LFS, section 6.6 creates user nobody, UID=99, and group nobody, GID=99.
But in BLFS, elogind during the meson configuration stage looks for both UID
and GID of 65534, and comments that the configuration is non-standard, with
possible problems (sorry, I've lost the exact message).
I don't think it is serious - the build continues fine - but I'm not sure since
I have other problems with this build.
I guess it is not the source of your problems, since I have this too, and
everything runs OK. The exact messages are:
------
meson.build:900: WARNING:
The local user with the configured user name "nobody" of the nobody user does
not have UID 65534 (it has 99).
Your build will result in an user table setup that is incompatible with the
local system.
meson.build:919: WARNING:
The local group with the configured group name "nobody" of the nobody group
does not have UID 65534 (it has 99).
Your build will result in an group table setup that is incompatible with the
local system.
-------
But then, it seems happy with:
-------
nobody user name: nobody
nobody group name: nobody
-------
Right. See
http://www.linuxfromscratch.org/blfs/view/stable/postlfs/users.html Sed
the line at the bottom.
The reason for 65524 is that when UIDs were 16-bits that value was
interpreted as -2. That was the value that nfs used if the user
'nobody' was missing.
The warning is bogus. No user program should care what the numerical
value of a gid is.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
