| Summary: | If no passwd/group files exist in sysroot, users/groups are picked up from /etc | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Peter Kjellerstedt <peter.kjellerstedt> |
| Component: | core | Assignee: | Saul Wold <sgw> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | liezhi.yang, meta.mr.watcher, meta.watcher, Qi.Chen, seebs, tomw |
| Version: | 1.5 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Peter Kjellerstedt
2013-11-29 16:55:10 UTC
How about making such recipe dependent on base-passwd? //Chen Qi Do you use the useradd.bbclass to modify the user or group files? It has a dependency on base-passwd as Chen Qi suggests. How are you modifing the group file? Well, for recipes that need to add users and/or groups in addition to what base-passwd provides, useradd.bbclass is appropriate. However, I am talking about recipes that only use the users and groups provided by base-passwd. In Poky, there are only two recipes that depend on base-passwd: sysvinit and shadow-sysroot. Any other recipe that installs files (and that should be just about every single recipe) relies on the fact that the users and groups in /etc are similar enough to the ones provided by bass-passwd, most notably that root exists. That said, this may be more of a theoretical problem as the likelihood of having a host system without a user called "root" is pretty slim... It would make sense to change that behavior in pseudo, I would be inclined to have pseudo use a small built-in passwd/group set instead of the host system's in that case. Not sure what more info I am expected to provide... |