A system admin FAQ for *some* Perforce admin/usage...

[JeffBowlesjeff.bowles at weblogic.com]

My system admins here are pretty good, and set up a number of
basic things on every new engineer's machine - including a P4
client for them.

They recently asked if we could spend a couple of hours with them,
going over basic P4 usage and the specific kinds of P4 support
information they'd probably need for basic stuff.

We'll probably construct an FAQ for them, in addition to spending
a couple of hours going over basic stuff, so that they have it in
electronic form for reference at the wee hours of the night. (Anything
to avoid the 3 AM phone call.) I put together a tentative list of
questions to answer for them, and they added a couple at the
end of the list. Here's my list, so far.

*** I'm not asking this mailing list for answers to these questions! ***
*** Instead, I'm asking if there are other questions to answer that  ***
*** a person doing basic system admin might wanna know.              ***

1. What's a client? What's a client spec? How do I tell what this client spec 
     does and doesn't do? 
2. How do you add/delete files? Can you retrieve a deleted file? How? 
3. How does Perforce deal with CR/LF issues? Can this be overridden? 
4. How do I tell what some else's client spec looks like? How do I change the 
     e-mail address for a user is, if it's not the same as their P4 user
name? 
5. Should we store binaries in Perforce? Why, or why not? 
6. If the machine on which the Perforce depot dies, what do we do? If it
runs out of space on the depot      filesystem, what do we do? 
7. What is/How do I do a p4 revert?
8. What is/How do I do an integration?

If you have other questions that your local admins would probably want
to have included in an FAQ, let me know. I'll forward the resultant FAQ
to you, if you like.

- -Jeff Bowles