fcs.mex

操作系统SunOS 4.1.3版本的源码

and cp's all necessary
sources (makefiles,
.L man?/$(FILES) ,
etc.) to 
.L $(CLONEDIR) .
This is to safeguard the original sources from rcp
flukes.
.br
.ne 8
.LP
Secondly,
.BS GRAY
.LS 2
% make \-f Printfile pinstall
.LE
.BE
.LP
.L $(CLONEDIR)
is recursively rcp'd onto
.L $(DESTHOST) .
This is a dangerous process (because of
the remote procedures), and you will
be warned accordingly.  
.L $(DESTHOST)
must be a
doctools host (that's why the pages cannot be made
on the release machine).
.LP
Since the above procedure was done remotely, it
is a good idea to check that all files do exist,
and have plausible contents.  A simple way to
verify this is
.BS GRAY
.LS 2
% cd man?
% ls | more
.LE
.BE
.LP
All work will now be done on 
.L $(DESTDIR) .
Any editing done to the files will be merged back
onto the release machine after printing.  In order
to run make on 
.L $(DESTDIR) ,
the SunPro version of make
must be in
.L /usr/bin ,
and
.L default.mk
must exist in
.L $(DESTDIR) ,
or in
.L /usr/include/make
on 
.L $(DESTDIR) .
.LP
A significant amount of work has been done on the
pages, and now that they are on the doctools host, the pages are
no longer under the security of SCCS.  So, to protect
our changes, a backup tape should be made at this point.
.LP
The last check must be done on the doctools host.
.BS GRAY
.LS 2
% make checknr
.LE
.BE
.UH S "BUILDING PRINTED PAGES"
.LP
Now, the final steps of building the printed pages.
.BS GRAY
.LS 2
% make man
.LE
.BE
.LP
Will produce
.L ?.man
in 
.L $(DESTDIR)
as well as
.L man? .
.L ?.man
is one concatenated file containing
all pages for that directory.
.BS GRAY
.LS 2
% make PS
.LE
.BE
.LP
This command depends on
.L "make man" ,
so the
previous command is an optional step.  Using
.L ?.man ,
.L "make PS"
creates the postscript
files for each section,
.L ?.PS ,
and the other necessary printed files,
.L cover.PS ,
.L pag.PS ,
and
.L index.PS .
.br
.ne 8
.LP
The PS files can then be printed individually, using
.BS GRAY
.LS 2
% psprint pag.PS
% psprint ?.PS
.LE
.BE
.LP
Print the pagination first, and read it thoroughly.  The
most obvious (and easiest to overlook) mistakes could be
caught at this point, saving a lot of time and frustration.
Check pagination for:
.RS
.IP \(bu
pages that are in the wrong section (mostly section 3? pages)
.IP \(bu
pages that are out of alphabetical order
.IP \(bu
missing pages, or pages that appear too short
.RE
.LP
If there is a problem with a particular section
it is not necessary to remake the entire
document.  By fudging the slushfile, you can make
only a specified PS file.
.BS GRAY
.LS 2
% mv slushfile slushfile.old
% vi slushfile

	\fIinsert the starting page number for this section
	as the first line of the slushfile and exit\fP

% make ?.PS
.LE
.BE
.LP
Note:  If remaking that section will affect the
pagination, or index,  then you MUST run:
.BS GRAY
.LS 2
% make clean
.LE
.BE
.LP
This will move all the files generated by
make (?.PS and ?.man) so that they do not
appear up to date.  
.LP
and
.BS GRAY
.LS 2
% make PS
.LE
.BE
.LP
Just because you have remade the document does
not mean you have to reprint any sections, only
pages affected by the problem need
to be reprinted.  Mainly, the document must be
remade for slushfile purposes.
.UH S "PRINTING"
.LP
Before you begin printing, change the printer
cartridge (and have an extra cartridge on hand).
.LP
You can begin printing a PS file as soon as make goes
on to the next section.  To print:
.BS GRAY
.LS 2
% psprint ?.PS
.LE
.BE
.LP
When checking the pagination against the printed
pages, look for the following:
.RS
.IP \(bu
make sure the name and page numbers match
.IP \(bu
scan page for errors (point size, fonts
that aren't turned off, overprints or
run-off lines)
.IP \(bu
pages that contain more than one NAME line
.IP \(bu
spots or smudges on pages, these should be
whited out where possible, in extreme cases
the page could be reprinted as a patch
.RE
.LP
Once the pagination is complete, and double
checked, insert pink sheets to indicate where tabs
should be inserted.  Turn in manual and
pagination to production, saving a photocopy of the
pagination for your records.  Tell Production how many
immediate copies will be needed.  Immediate copies will not
come from the printer, they are photocopies of 
the manual as it was turned in. 
.UH S "CHECKING BLUELINES"
.LP
Remain available until the manual has been sent to the
printer.  Check with production periodically until
bluelines are in.  Proofread bluelines immediately,
request a 48 hour turn around from production.
.LP
When checking bluelines remember that this is not
the time to make edits, we have to pay for each
change we make (excepting printer errors we
catch).  Always keep a cost/benefit ratio in
mind.
.LP
Check bluelines for:
.RS
.IP \(bu 4
overprints
.IP \(bu 4
copy printed off edge of page
.IP \(bu 4
blank pages
.IP \(bu
spots, smudges, and streaks
.IP \(bu 4
printer marks
.IP \(bu 4
incorrectly ordered pages and sections
.IP \(bu 4
bad page breaks
.IP \(bu 4
any other glaring, horrendous errors
.RE
.UH S "CLEAN UP"
.LP
After the manual is turned in you can begin the
cleaning up process.
.UH S "On doctools host"
.LP
As a precaution, a final tape should be made at this time.
This tape should be saved
.I at
.I least
until the next release.
.LP
.L $(DESTDIR)
and all of its contents should remain fully
intact until bluelines have been sent back to the printer,
and a final review copy has been approved.  The final review copy
will be printed in ink, unlike the bluelines.
.LP
As mentioned earlier, any pages that have been changed
since the cloning process must be merged back onto the
release machine.
.BS GRAY
.LS 2
% make mergeback
.LE
.BE
.LP
will generate eight lists,
.L /tmp/man?.mergeback ,
containing all files that have been changed
in each directory on 
.L $(DESTDIR) .
This list should be rcp'd onto the
release machine.  We are now finished with 
.L $(DESTDIR) .
.UH S "On release machine"
.LP
The files listed in the file
.L mergeback
need to be rcp'd from 
.L $(DESTHOST) ,
and checked into SCCS.
This can be done easily using the following script.
.BS GRAY
.LS 2
% foreach i ( man[1-8] )
? cd $i
? sccs edit -s `cat /tmp/$i.mergeback`
? rsh abraxas "cd /usr/tmp/man/$i ; \e
?   rcp `cat /tmp/$i.mergeback` argon:/usr/src/man/$i"
? sccs delget -s -y"merge back from printed versions" \e
?   `cat /tmp/$i.mergeback`
? cd ..
? end
%
.LE
.BE
.LP
While all make-generated files in the current directory
will be removed by 'clean', those in subdirectories will not.
These files must be removed by hand, verifying that each
file should actually be removed.
.LP
To clean up the man pages directories, type:
.BS GRAY
.LS 2
% cd /usr/src/man
% make clean
.LE
.BE
.LP
While all make-generated files in the current directory
will be removed by 'clean', those in subdirectories will not.
These files must be removed by hand, verifying that each
file should actually be removed.
.LP
We are now finished our work on the pages and directories,
to prepare for the next build, type:
.BS GRAY
.LS 2
% make
.LE
.BE
.LP
This will do an
.L "sccs get"
on all the files necessary to
install the on-line man pages, leaving a current version
of all pages available.
.UH S "TEST CATMAN"
.LP
To make using the 
.L man
command easier, and generate cross-references,
users will run 
.L catman
soon after installing SunOS.  We must make
sure that the man pages will not break when they do this.
.LP
Since we just want to test this command, not actually create its output,
we do not need to nroff entire files, the first line of each file is
sufficient.  Bob has created a "dummy" nroff
version that handles this for us, 
.L /usr/krypton/rdh/Nroff .
By moving this file to
.L nroff
somewhere in 
.L $(PATH) 
.I before
.L /bin/nroff ,
.L catman
will use this version, and be non the wiser.
.LP
WARNING:  Do not forget to move
.L nroff
back to
.L Nroff !
.br
.ne 8
.LP
Run
.L catman :
.BS GRAY
.LS 2
% cd /usr/src/man
% catman

	\fIoutput from catman\fR

.LE
.BE
.LP
.L catman
creates a corresponding cat directory for each existing
man directory, the nroff output files are placed
in these directories.  For
.L .so
files, cat places
a link in the directory to the nroffed version of
the source file. 
.LP
Error messages will appear in the 
.L catman
output.
They indicate a bad
.L .so
reference, or a
non-existent file.  These files must be
investigated.  First, check for their existence
in the appropriate
.L man
directory.  Then check the
.L cat
directory.  Possible errors include:
.RS
.IP \(bu 4
The
.L \&.so
file has embedded spaces in the source
file
.IP \(bu 4
The current version of a file must be extracted
from SCCS, use
.L sccs get
.I filename .
.IP \(bu 4
The
.L \&.so
references a non-existent file, or
misspells filename.
.RE
.LP
After fixing these errors, run
.L catman
again to verify the fix and make certain that
new errors were not introduced.  Once
.L catman
has run successfully, remove the
.L cat
directories and the
.L nroff ed
files.
.LP
Remember to move
.L nroff
back to
.L Nroff !
.UH S "The \&\fLwhatis\fP Database"
.LP
.L catman
also builds the
.L whatis
database for
.L "man -k" '' ``
and
.L apropos .
If the 
.SM NAME
line of a man page is garbled, this will often show up in the
first few lines of the database (an
.SM ASCII
file).  Be sure to edit the man pages that contain the errors,
and run
.L "catman -w" '. `
again to verify your corrections.
.NS NOTE
Any high priority bugs that come in while the
pages are at the printers, can be fixed in the
source (the on-line pages), and a note inserted in
the RTF to mention the discrepancy between the
printed and on-line pages.  High priority means
bugs that are reported by engineers as must fix.
.NE