In the past, I had already some implementation for that, where
enewuser()/enewgroup() in case of not being root (uid zero) used some
'root.sh' file, containing real commands for the target-userland to be
executed by real-root, as well as easy-to-parse comments containing the
arguments of previous enewuser/enewgroup calls.
What was missing there: to empty the file once it was executed by
real-root user, because i had no need yet to really add the users as i
did not need to start some daemons installed from prefix-portage yet.
But i needed this temporary "passwd-database" to have egetent()
recognize not-yet-physically-executed enewuser() calls in addition to
In the attached 'eutils.eclass' look for access to file
'var/spool/emerge/doasroot' and calls to edoasroot().
PS: I'm happy to be back again to prefix-portage, currently trying to
get some portage-alt-prefix packages to fly on x86-redhat-linux.
On Tue, 2006-06-13 at 11:00 +0200, Grobian wrote: > On 12-06-2006 15:20:56 -0600, m h wrote:
> > Folks-
> > Has anyone thought out user management in a prefix setting. An
> > example being apache or mysql which usually run as their own users.
> > Is this the plan for prefix too?
> The last ideas for OSX were to have some propagation tools from prefix
> to host OS. This is a bit scary, but would mean useradd actions just
> get forwarded. This requires root privileges of course. The portage
> people seem to work on something to keep the administration of users
> added by Portage, and keep that administration synchronised with the
> real password backend. This initiative is very nice for prefix of
> course, as it would probably allow us to just plug on that
> administration... Sorry, I have no pointers...
> Fabian Groffen
> Gentoo for Mac OS X Project
Michael Haubenwallner SALOMON Automation GmbH
Forschung & Entwicklung A-8114 Friesach bei Graz
No HTML/MIME please, see http://expita.com/nomime.html
email@example.com mailing list