[Linux-decnet-commit] CVS: dnprogs/dncopy dncopy.1,1.11,1.12

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/linux-decnet/dnprogs/dncopy
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv18814/dncopy

Modified Files:
	dncopy.1 
Log Message:
fixed some lintian warnings

Index: dncopy.1
===================================================================
RCS file: /cvsroot/linux-decnet/dnprogs/dncopy/dncopy.1,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -r1.11 -r1.12
*** dncopy.1	4 Oct 2008 11:20:33 -0000	1.11
--- dncopy.1	6 Jul 2010 00:32:15 -0000	1.12
***************
*** 57,68 ****
  The environment DNCOPY_OPTIONS may be used to provide a default set of
  options for copying files. If (for example) you wanted to normally send
! files as blocks rather than records you could set DNCOPY_OPTIONS="-mblock".
  Then, to send a file as records you would need to type
! .B dncopy -mrecord myfile.txt vmsbox::
  instead.
  .br
  Options in DNCOPY_OPTIONS may be overridden by options typed on the
  command-line except where there is no negating option available (see
! .B -k -d -i
  ). If you put these options in DNCOPY_OPTIONS then to remove them you will
  have to override the whole environment variable eg:
--- 57,68 ----
  The environment DNCOPY_OPTIONS may be used to provide a default set of
  options for copying files. If (for example) you wanted to normally send
! files as blocks rather than records you could set DNCOPY_OPTIONS="\-mblock".
  Then, to send a file as records you would need to type
! .B dncopy \-mrecord myfile.txt vmsbox::
  instead.
  .br
  Options in DNCOPY_OPTIONS may be overridden by options typed on the
  command-line except where there is no negating option available (see
! .B \-k \-d \-i
  ). If you put these options in DNCOPY_OPTIONS then to remove them you will
  have to override the whole environment variable eg:
***************
*** 78,83 ****
  .TP
  .I "\-v"
! Verbose operation. The more -v options are present the more verbose dncopy
! will become. One -v is roughly equivalent to the /LOG qualifier on the DCL
  copy command. More than one is really just useful for debugging.
  .TP
--- 78,83 ----
  .TP
  .I "\-v"
! Verbose operation. The more \-v options are present the more verbose dncopy
! will become. One \-v is roughly equivalent to the /LOG qualifier on the DCL
  copy command. More than one is really just useful for debugging.
  .TP
***************
*** 99,103 ****
  Keep version numbers on files copied from VMS systems. By default dncopy will
  strip the version number from files because they have no meaning in Linux.
! if you specify -k on the command line then the VMS file will be created with
  exactly the same name as it had on the VMS system. To access these files under
  Linux you will need to enclose them in quotes. eg less "vmsfile.txt;1".
--- 99,103 ----
  Keep version numbers on files copied from VMS systems. By default dncopy will
  strip the version number from files because they have no meaning in Linux.
! if you specify \-k on the command line then the VMS file will be created with
  exactly the same name as it had on the VMS system. To access these files under
  Linux you will need to enclose them in quotes. eg less "vmsfile.txt;1".
***************
*** 111,118 ****
  .B block
  is used for sending binary files to the VMS system. Note that if you
! use -mblock to pull files from VMS you may not be able to make sense of
  the file on Linux because dncopy will also pull all the VMS internal
  structuring of the file as well as the data. Unless you really know what
! you are doing -mblock is only really useful for sending files.
  .TP
  .I "\-a {none|ftn|cr|prn}"
--- 111,118 ----
  .B block
  is used for sending binary files to the VMS system. Note that if you
! use \-mblock to pull files from VMS you may not be able to make sense of
  the file on Linux because dncopy will also pull all the VMS internal
  structuring of the file as well as the data. Unless you really know what
! you are doing \-mblock is only really useful for sending files.
  .TP
  .I "\-a {none|ftn|cr|prn}"
***************
*** 137,141 ****
  Set the block size for transfers. The default is high enough for all record
  structured files. if you are sending a file with
! .B -mblock
  then you should use this to set the block size of the file to be created at
  the VMS end. When sending block files the default changes to 512 as this is
--- 137,141 ----
  Set the block size for transfers. The default is high enough for all record
  structured files. if you are sending a file with
! .B \-mblock
  then you should use this to set the block size of the file to be created at
  the VMS end. When sending block files the default changes to 512 as this is
***************
*** 159,163 ****
  Delete the file when it is closed. This is only really useful in conjunction
  with 
! .I -P.
  .TP
  .I "\-T connect timeout"
--- 159,163 ----
  Delete the file when it is closed. This is only really useful in conjunction
  with 
! .I \-P.
  .TP
  .I "\-T connect timeout"
***************
*** 185,189 ****
  bash or ksh:
  .br
! $ DNCOPY_OPTIONS="-mblock -anone -b1024" ; export DNCOPY_OPTIONS
  .br

--- 185,189 ----
  bash or ksh:
  .br
! $ DNCOPY_OPTIONS="\-mblock \-anone \-b1024" ; export DNCOPY_OPTIONS
  .br

***************
*** 191,195 ****
  csh or tcsh:
  .br
! $ setenv DNCOPY_OPTIONS "-mblock -anone -b1024"
  .br

--- 191,195 ----
  csh or tcsh:
  .br
! $ setenv DNCOPY_OPTIONS "\-mblock \-anone \-b1024"
  .br

***************
*** 197,201 ****
  makes dncopy send files as 1024 byte blocks with no carriage control. You can
  override these options by specifying replacements on the command-line as usual.
! Be aware that some options have no converse (eg -i -k -d -v) so if you put
  these in DNCOPY_OPTIONS you cannot disable them without deassigning the
  variable.
--- 197,201 ----
  makes dncopy send files as 1024 byte blocks with no carriage control. You can
  override these options by specifying replacements on the command-line as usual.
! Be aware that some options have no converse (eg \-i \-k \-d \-v) so if you put
  these in DNCOPY_OPTIONS you cannot disable them without deassigning the
  variable.
***************
*** 223,227 ****
  .br
  .PP
!     dncopy -mblock test.exe 'tramp"christine pjc123"::[.BIN]'
  .br

--- 223,227 ----
  .br
  .PP
!     dncopy \-mblock test.exe 'tramp"christine pjc123"::[.BIN]'
  .br

***************
*** 231,235 ****
  .br
  .PP
!     dncopy secret.dat  marsha:: -p (s:, o:rwed, g:re, w:)'
  .br
  .br
--- 231,235 ----
  .br
  .PP
!     dncopy secret.dat  marsha:: \-p (s:, o:rwed, g:re, w:)'
  .br
  .br
***************
*** 239,243 ****
  .br
  .PP
!     dtype 'trisha"christine -"::login.com'
  .br
      You will then be prompted for a password
--- 239,243 ----
  .br
  .PP
!     dtype 'trisha"christine \-"::login.com'
  .br
      You will then be prompted for a password
***************
*** 247,253 ****
  For fetching files the defaults should serve for most purposes. Most VMS files
  are record orientated and
! .B -mrecord
  is the default transfer mode. It is rare you will need to fetch files using
! .B -mblock
  because you will get all the record control information downloaded too and
  that probably isn't any use to you.
--- 247,253 ----
  For fetching files the defaults should serve for most purposes. Most VMS files
  are record orientated and
! .B \-mrecord
  is the default transfer mode. It is rare you will need to fetch files using
! .B \-mblock
  because you will get all the record control information downloaded too and
  that probably isn't any use to you.
***************
*** 266,277 ****
  Carriage control can also be specified if you want to be that picky.

! Binary files may often need to be sent -mblock to be useful at the VMS end,
  You will probably want to specify a block size with the
! .B -b
  option. The default is 512 which is fairly useful but if you are sending
  (say) a saveset 8192 or 32256 may be required. Trial-and-error may
  be the only way in some cases unless you know the file contents very well.
  If you really don't know what to do, just send it
! .B -mblock
  and use the set file/attr command to massage it on the VMS end until you are
  happy with it. (If you are using VMS earlier than 6.1 then you will need
--- 266,277 ----
  Carriage control can also be specified if you want to be that picky.

! Binary files may often need to be sent \-mblock to be useful at the VMS end,
  You will probably want to specify a block size with the
! .B \-b
  option. The default is 512 which is fairly useful but if you are sending
  (say) a saveset 8192 or 32256 may be required. Trial-and-error may
  be the only way in some cases unless you know the file contents very well.
  If you really don't know what to do, just send it
! .B \-mblock
  and use the set file/attr command to massage it on the VMS end until you are
  happy with it. (If you are using VMS earlier than 6.1 then you will need