Hi, > ... > Looking at useradd.c at least four filenames should be changed; > passwd, shadow, group and sgroup. > > The password db abstraction does allow easy changing of the file > names, but home directory, skel directory, mail spool and probably > more should also be changed, so maybe it makes sense to simply have > useradd call chroot() according to an option early on in main()? > This will definitely not work on cross targets? I think, there is not a real workaround for post-installes that need to run on the target plattform, according to my experience. I always emerged such packages on the target itself, leading sometimes to very high compilation times.
The cleanest way would be an execute stack that gets created/extended while cross building and processed when the target starts the next time, but this would mean a really huge work amount to implement in ebuilds and the system itself. Cheers, Daniel
