Here is an extract of the questions I (Michael Boman,
michael.boman@securecirt.com) had with the Dpsyco author (mostly
in Swedish, so pardon me for bad translation). I would guess this is a
start of an FAQ...

Maintainer note: I did some spellchecking as Michael Boman asked me to.

--

Q: How stable is dpsyco.. how long has it been around?

A: I wrote it this summer but the concept have been around (on my systems)
   since something like a year ago.

   The stability... Well it is quite stable but also a bit dangerous. I
   think most bugs are in the debian bug-database.

--

Q: What do you mean Dpsyco is a bit dangerous?

A: When user information is removed/deleted or for some other reason
   no longer exists the user will be disabled, and the users file will
   be moved out of the way. This effects all users with UID/GID (User
   ID / Group ID) between 500-999. If there is no user information about
   these users they will be disabled. This is what I mean with dangerous.

--

Q: Is there any documentation that explains how dpsyco is working?

A: The only documentation yet is the source code and the documentation
   in /usr/share/doc/dpcyso*/. All contributions are welcome.

--

Q: Can Dpsyco replace NIS?

A: Yes and no, it depends on what you are going to use NIS..

   Dpsyco can:
    * Add users
    * Remove users
    * Change name and password for users
    * Can configure samba to a degree
    * Make sure the user get "good" permissions on his home directory
      (including samba profile and email) if UID/GID is changed.
    * The idea is to change/create debian packets with system information
      and push it out to a cluser of computers

   Problems:
    * There is no check what UID/GID the user gets
    * Information is only updated if the packets updates (if you are
      not using rsync or similar)

   Conclusion:
    * This works good for administration accounts or accounts where there
      is no need for NFS shared files (or similar) that depends on
      UID/GID is the same across systems
    * Passwords are hard to change, as you have to manually paste the
      encrypted password in a special file. I have not had the time/energy
      to write such a script yet...

--

Q: If the users will be created in the same order on all servers, will
   they get the same UID/GID?

A: If all packages (that contains user information) installs in the same
   order on all computers they *should* get the same UID/GID

--

Q: Is there any problems rebuilding Dpsyco on a Potato (2.2 / Stable)
   machine [Dpsyco only exists in woody/sid at the moment]?

A: No, I run Dpsyco on several Potato installations without problems.

--

Q: How does the communication between machines work?

A: Simple: there is none. User information gets packaged and then it's
   up to you (as the administrator) to copy the package to all the
   machines and install it.

--

Q: I have several groups of users, and I don't want to let all of them
   have access to all servers. Can Dpsyco do this?

A: I recommend you to create several packages for this. Dpsyco can handle
   same user in several packages without problems.

--

Q: This FAQ has several spelling errors, who do I shout at?

A: Well, I rather have a email sent to me at michael.boman@securecirt.com
   with a diff file.

--

Q: I read this and now my system doesn't work anymore

A: Well, sorry. Please restore from your latest backup (you do that
   backups, right?). This FAQ is provided "AS IS" an does not offer any
   kind of warranty.



