Hi Jacqueline,
The notes you sent below are some of the most helpful notes anyone has ever sent to me. I'm very psyched that you sent this again, cuz I lost my copy. I still have a printed copy that I use. Your notes are part of what inspired the SSH FAQ set.
I couldn't clip them... they'll be good for the archives.
:)
Thank you! Diane
Jacqueline McNally wrote: [...]
-------- Original Message -------- Hello Diane
I pop in now and again to the [authors] list and spotted something I may be able to assist you with.
When I started out, at Louis' suggestion, I looked up all these, with varying levels of success: http://www.openoffice.org/docs/ddSSHGuide.html http://www.openoffice.org/docs/ddCVS.html http://website.openoffice.org/support/en/howtos/1-v1a.html http://website.openoffice.org/support/en/howtos/1.html http://www.nbcs.rutgers.edu/ssh/putty.php3
Now, that I have history recorded in my bash shell, I don't have to worry about them that much.
The tricky part is knowing the directory structure of the project that you are working on. Hopefully if I show you the one for marketing, you will be able to figure out the one for documentation. I think you should safely be able to s/marketing/documentation. Also, the examples below are assuming your OOo username is mackmoon.
I work with two terminal windows or shells.
The first to establish the tunnel:
ssh -2 -x -L 2401:localhost:2401 [EMAIL PROTECTED]
I am then prompted for my ssh passphrase. Successfully entered, I minimise this shell. Note: If I mistype the passphrase it will prompt for the ssh passphrase two more times, before giving up. The first time (ever) you do this, it will ask for a password, in which case you exit out, and start over.
In the second shell, I use to login into CVS and actually do some work:
To login: cvs -d:pserver:[EMAIL PROTECTED]:/cvs login Then prompted for OOo password associated with OOo username mackmoon.
To checkout (or startover) from the cvs repository: cvs -d:pserver:[EMAIL PROTECTED]:/cvs checkout marketing Note: You have to do this the first time.
If you don't want to checkout or startover the whole project, you can update a particular file, this is assuming you have checked out initially: cvs -d:pserver:[EMAIL PROTECTED]:/cvs checkout marketing/www/index.html Where the filename=index.html and is located in the www directory of the marketing project.
To commit changes to a file in the repository having tweaked on your own disk: cvs -d:pserver:[EMAIL PROTECTED]:/cvs commit -m "comment" marketing/www/filename
Note 1: If you do not include a comment, you will be prompted for one. Note 2: Directory structure is project name/www/project files for most projects.
To add a new file is a two step process. cvs -d:pserver:[EMAIL PROTECTED]:/cvs add marketing/www/filename cvs -d:pserver:[EMAIL PROTECTED]:/cvs commit -m "comment" marketing/www/filename
The only gotcha is sometimes the directory paths don't appear to work. The way around this is simply to go to the particular directory where the file is located on your hard disk and remove any references to the directory in the cvs command. For example, if you are committing a file called todo.html, use cd to move to the directory that contains todo.html, then: cvs -d:pserver:[EMAIL PROTECTED]:/cvs commit -m "comment" todo.html
I have not attempted to use any GUI for CVS as I find that most of the work is done locally except for the few commands above that are contained in my bash history.
Hope this helps.
Regards Jacqueline
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
