Mac Developer Library Developer


This manual page is for Mac OS X version 10.9

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

SHAR(1)                   BSD General Commands Manual                  SHAR(1)

     shar -- create a shell archive of files

     shar file ...

     shar writes an sh(1) shell script to the standard output which will recreate the file hierarchy speci-fied specified
     fied by the command line operands.  Directories will be recreated and must be specified before the
     files they contain (the find(1) utility does this correctly).

     shar is normally used for distributing files by ftp(1) or mail(1).

     compress(1), mail(1), tar(1), uuencode(1)

     shar makes no provisions for special types of files or files containing magic characters.

     To create a shell archive of the program ls(1) and mail it to Rick:

           cd ls
           shar `find . -print` |  mail -s "ls source" rick

     To recreate the program directory:

           mkdir ls
           cd ls
           <delete header lines and examine mailed archive>
           sh archive

     The shar command appears in 4.4BSD.

     It is easy to insert trojan horses into shar files.  It is strongly recommended that all shell archive
     files be examined before running them through sh(1).  Archives produced using this implementation of
     shar may be easily examined with the command:

           egrep -v '^[X#]' shar.file

4.4BSD                           June 6, 1993                           4.4BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.