Yeah, that's not completely trivial, that's why I don't say you: "OK,
I'll fix that in two hours for the next release". I'm not sure I'll have
the time to try implementing this for Lucid.
perl is not very hard to understand when you have priori knowledge of C
or another similar language. You'd nee
I have had a look into /usr/share/system-tools-
backends-2.0/scripts/Users/Users.pm. Unfortunatly I am not at all
familliar with perl.
If it is currently reading in settings from /etc/adduser.conf it should
work with a linked profile as well, what you mean is probably reading in
other installed pr
Do you think you could try to implement the support for adduser profiles
in the system-tools-backends? I'm currently reworking the D-Bus
protocol, so it would be the time to make these changes if we want. They
are written in perl.
--
users-admin profiles default to force [GU]ID, home dir, shell a
I have actually produced a patch to adduser now, as far as I could.
Since it is my first one I'd appreciate any feedback. Its in LP: #489136
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
adduser
https://bugs.launchpad.net/bugs/488913
You received this bug notific
Alternativly adduser.conf can be shipped as a symlink to a
adduser.conf.dist (distribution) profile.
This allows to switch the symlink to an admin provided profile, so that
it will be used as a adduser default, without having to touch the .dist
profile.
--
users-admin profiles default to force [
Oh, I just realized that adduser supports user profiles, maybe even
since its first version.
System wide profiles can be provided as adduser.conf. and the profile
is selected with:
# adduser --conf adduser.conf.
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
ad
