somnec(1) [debian man page]

SOMNEC(1)						      General Commands Manual							 SOMNEC(1)

NAME

       somnec - Compute Sommerfield-Norton Ground Grids

SYNOPSIS

       somnec

DESCRIPTION

       somnec  is  a  program to generates grids used by the NEC2 program for the Sommerfeld-Norton approximation to realistic grounds.  It allows
       interactive user input of relative dielectric constant, ground conductivity, and frequency in MHz.  The output for use by nec2  is  written
       out  as	binary unformatted file.  The program .B nec2 reads this in, if the Sommerfield Norton Ground is specified in the nec2 input cards
       by the presence of a suitable suitable  Ground Parameters Card i.e. a GN card with IPERF set to 2 (coluns 3-5).	Hence  the  user  is  also
       prompted for a file name, and the grid arrays are written to the file.

OPTIONS

       Due  to	the  age of the program, it expects its input to be in the form of punched cards fed into a hopper.  It doesn't currently take any
       options, instead the name of the input and output files must be entered once the program has been run.

SEE ALSO

       nec(1)

       It is fully documented as part of the report Numerical Electromagnetics Code (NEC) -- Method of Moments", available as a  printed  publica-
       tion in three parts covering the theory of operation, the program code and the users' manual.

BUGS

       This  program  was  keyed  in  by  hand from a printed listing.	Thus it is possible that some extra bugs have been introduced. Unformatted
       binary files are often a fortran minefield, particuarly if transported between systems.

AUTHOR

       This manual page was written by	<alanb@chiark.greenend.org.uk>.  The original program was developed by G. J. Burke and	A.  J.	Poggio	of
       Laurence Livermore Laboratory.

																	 SOMNEC(1)

CSREQ(1)						    BSD General Commands Manual 						  CSREQ(1)

NAME

     csreq -- Expert tool for manipulating Code Signing Requirement data

SYNOPSIS

     csreq [-v] -r requirement-input -t
     csreq [-v] -r requirement-input -b outputfile

DESCRIPTION

     The csreq command manipulates Code Signing Requirement data.  It reads one requirement from a file or command arguments, converts it into
     internal form, checks it, and then optionally outputs it in a different form.

     The options are as follows:

     -b path
	     Requests that the requirement read be written in binary form to the path given.

     -r requirement-input
	     Specifies the input requirement. See "specifying requirements" below. This is exactly the same format as is accepted by the -r and -R
	     options of the codesign(1) command.

     -t      Requests that the requirement read be written as text to standard output.

     -v      Increases the verbosity of output. Multiple instances of -v produce increasing levels of commentary output.

     In the first synopsis form, csreq reads a Code Requirement and writes it to standard output as canonical source text.  Note that with text
     input, this actually compiles the requirement into internal form and then converts it back to text, giving you the system's view of the
     requirement code.

     In the second synopsis form, csreq reads a Code Requirement and writes its binary representation to a file. This is the same form produced by
     the SecRequirementCopyData API, and is readily acceptable as input to Code Signing verification APIs. It can also be used as input to subse-
     quent invocations of csreq by passing the filename to the -r option.

SPECIFYING REQUIREMENTS

     The requirement argument (-r) can be given in various forms. A plain text argument is taken to be a path to a file containing the require-
     ment. This program will accept both binary files containing properly compiled requirements code, and source files that are automatically com-
     piled for use.  An argument of "-" requests that the requirement(s) are read from standard input.	Again, standard input can contain either
     binary form or text.  Finally, an argument that begins with an equal sign "=" is taken as a literal requirements source text, and is compiled
     accordingly for use.

EXAMPLES

     To compile an explicit requirement program and write its binary form to file "output":
	   csreq -r="identifier com.foo.test" -b output.csreq

     To display the requirement program embedded at offset 1234 of file "foo":
	   tail -b 1234 foo | csreq -r- -t

FILES

DIAGNOSTICS

     The csreq program exits 0 on success or 1 on failure. Errors in arguments yield exit code 2.

SEE ALSO

     codesign(1)

HISTORY

     The csreq command first appeared in Mac OS 10.5.0 .

BSD
								   June 1, 2006 							       BSD