Hi *, On Sat, Feb 19, 2005 at 06:38:43PM -0500, Daniel Carrera wrote: > [...] > 1) I used exactly the same documentation that there is now.
Too bad, you 1, I 0 :-) > 2) Documentation is not a replacement for simplicity. But how can the documentation be any simpler than it is now, explaining and mentioning each single step? > Take my example of > complex analysis. If I give you my book on complex analysis you'll have > all the documentation you need to answer the problem I posed. Does that > mean it's not difficult anymore? There is no book on complex analysis that explains every single step. But comparisons always suck, that's right. I would agree with you if the documentation still would be the same as "in the old days". Were basically the instruction was: "create a key, attach it to an issue" ;-) > > My experience is that the only problem is that people try to connect > > using the tunnel before their key is uploaded to the server causing the > > attemt to connect to fail (and any action tried after that failed > > connection). > > I had trouble figuring out what the heck a tunnel is, Do you really have to know what a tunnel is? You don't have to know what ssh stands for, do you? > I had trouble > figuring out what a key is, see above. You don't have to know to set up your system. > I had trouble figuring out how to generate a > key (the documentation is ridiculously ambiguous on that point), Are you talking about the same document? what is ambiguous with the instruction 'enter "ssh-keygen -d"' the instructions even tell you that you are asked for a passphrase and that you have to type your passphrase twice to avoid spelling mistakes. > I had > trouble figuring out how to establish the tunnel once my key was uploaded, Again, are you really talking about the same document? 'At the prompt, enter "ssh -2 -x -L 2401:localhost:2401 [EMAIL PROTECTED]" The server should ask you for your passphrase. Enter it. If the passphrase is entered wrongly, the server will immediately ask for your password. This request indicates a failure. You should try again, and hope for better luck' How can one have trouble following this instructions? You even can use cut'n'paste.. > I had trouble figuring out how to use a tunnel once it was established. I'm almost confident that you're not talking about the same document. * The screen does not show a prompt. It may, at most, say something. That's how it should be. The tunnel has been established. You are now ready to begin using CVS. * You can, at this point, minimize the terminal, but do not close it or enter Ctrl-C (^C). Doing so will kill the terminal tunnel. You do nothing with the tunnel other than establishing it (or killing it after you're done) A little down you find: "Step 4. What to do after you have established a tunnel Okay, you've come this far. If you've done everything right, you will have a tunnel on your desktop to the server housing the CVS repository. [...]" > In other words: Every single step of the process felt like hitting a brick > wall. Again: I don't thing you're talking about the same document. > I did offer to write the instructions at the time. Of course, my offer > went ignored, like they always are. Have a look again at http://www.openoffice.org/scdocs/ddSSHGuide.html and see whether you're really talking about the same instructions. ciao Christian -- NP: Donots - Friends (FuXXXX) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
