Hi John, But that's also the nice thing about open source software; everything is wide open, and you always have the choice to use or not use something. If the docs are poor, but for some reason you like the software, why not help with its documentation? Of course, some of us do not have sufficient time... ----- Original Message ----- From: "John" <valhalla@computerdatasafe.com.au> To: <blinux-list@redhat.com> Sent: Sunday, August 18, 2002 6:52 PM Subject: Re: Secure FTP > On Sunday 18 August 2002 20:20, John J. Boyer wrote: > > John, > > Thanks. That's the way documentation should be written. > > John > > thanks for the kind comment. > > Really, we need two kinds of documentation: > Tutorials that tell you how to perform common tasks > and > Reference documents that give you all the gory details to help with the > uncommon problems. > > Tutorials are hopeless when you want to see the switches for the scp command, > or to check on one of them in particular. > > A problem with Open Source software is that there is no dictum from On High to > rule that, "It must be done this way." > > > > -- > > > Cheers > John. > > Please, no off-list mail. You will fall foul of my spam treatment. > Join the "Linux Support by Small Businesses" list at > http://mail.computerdatasafe.com.au/mailman/listinfo/lssb > > > > > _______________________________________________ > > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list