Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Do you have a group with GUID 1000? All useradd is complaining about is that there doesn't seem to be such a group although you have specified it as default group in your configuration file.
No there is no group 1000. So 2 options, 1 remove the new group and user then create group 1000 or 2 leave as it is?
If I create group 1000 what to name it? If I leave it as it is I assume this will not affect the build
Ok I have checked the lfs book and it dosn't mention a group 1000, But it seems it would be a good idea to include it? As further packages relliy on it, But ok for future reference when creating the groups file, in lfs adding the group 1000 then would solve the prob, What should the group be named? or is group:x:1000 ok.
These 2 commands should create a group called messagebus with gid 18 and a user called messagebus with uid 18
I don't know why you see the error, but check if the group and user are present and have the correct id's. If so, you are done in regards to adding this specific user and group.
Do keep an eye out on this "group '1000' does not exist" error (you are probably going to create other users and group in due time).
I seem to remember it popping up when building ssh. On my 2nd build system I have put the user as group 1000 IS this a mistake!!! I dont think the error popped up when I installed ssh on that system
I seem to remember it popping up when building ssh. On my 2nd build system I have put the user as group 1000 IS this a mistake!!! I dont think the error popped up when I installed ssh on that system
I don't think that is is technically wrong but ssh, being a system user, is normally found in the lower regions of the uid count (Debian uses 107, BLFS uses 50 I use 108).
If this error showed up before you created the ssh user then ssh's uid of 1000 cannot be the cause. If this error showed up afterwards (or you do want to normalize the uid): You might try to change ssh's uid
Code:
usermod -u 50 sshd
and check afterwards if there are any leftover files with a uid of 1000 and change these as well
Code:
find / -uid 1000 -print
Hope this helps.
Last edited by druuna; 06-13-2011 at 02:05 PM.
Reason: typo
I have sshd as 50 0n my 1st system thats the 1 that pulled the error when installing ssh, and I have user as 1002 that was self generated when I added "me" as a user That is on my 1st build system.
The output of the find is home/martyn/ and all lower dirs. And /tools and /var/mail/help
I,m not to worried about it things work ok. just thought I would find correct way for group file,
1) create a group called users with gid 1000 groupadd -g 1000 users (users is commonly used as the default group).
2) if you already have a group called users, change the GROUP entry in /etc/default/useradd to reflect its gid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.