Sending Files by E-mail
Often, we have files we wish to send colleagues and friends by e-mail. Depending on the type of file you wish to send, there is a Linux command to make the process easy for you.
The shell archive file command shar is very useful for combining plaintext files into one file, which can then be sent by e-mail. shar writes shell commands for unpacking the output file inside the file itself, as well as code to verify the content using an MD5 checksum. It is much easier to use than the archive command tar, whose complexities can trip up even an expert. All you have to do to run shar is type:
shar input_filenames > filename.shar
It will take all the input files and write them to the output file, embedding the unpacking commands as it goes. The extension conventionally used with shar output files is .shar. To unpack the file, you don't need to know the embedded commands or retrieve them from the file yourself. Instead, use the command sh. The first argument to uuencode is the input file name; the second is the name to put in the output file header. We will use the same name for both. Type:
sh filename.sharThe sh command will do the work for you by reading the file, extracting the commands and executing them to unpack the archive.
It is permissible to use wild cards in naming your shar input files, so you can easily pack all the files in one or more directories. Just remember, the files must all be plaintext—no binaries.
The purpose of the shar command is quite similar to that of tar. However, the command and its format are much easier to remember, and since the output is plaintext instead of binary, it does not need to be encoded to send it as e-mail.
Non-plaintext files such as binaries and graphics must be encoded before e-mailing them. First, pack and compress your files using tar, which outputs a binary file. We won't go into tar in detail here, since it has been discussed before: see “Tar and Taper for Linux” by Yusuf Nagree, Linux Journal, February 1996 (http://www.linuxjournal.com/lj-issues/issue22/1216.html). A simple command to pack and compress all the files in the current directory would look like this:
tar -cvzf tar_files.tgz *
Now, the tar file can be encoded using the command uuencode by typing:
uuencode tar_file.tgz tar_file.tgz > mail_fileThe output file can now be put into e-mail and sent off into the ether.
The recipient can save the e-mail (perhaps as mail.save) and decode the file easily—no need to even remove mail headers. Simply use the command uudecode by typing:
uudecode mail.save
uudecode will do just what its name says: decode the mail file, leaving a file called tar_file.tgz in the current directory. To unpack the tar file, type:
tar -xvzf tar_file.tgzA single graphics file can be encoded and decoded in the same way, skipping the tar step since an archive file is not needed.

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- The Secret Password Is...
- New Products
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




3 hours 25 min ago
5 hours 16 min ago
10 hours 30 min ago
13 hours 41 min ago
15 hours 57 min ago
16 hours 25 min ago
17 hours 23 min ago
18 hours 52 min ago
20 hours 1 min ago
20 hours 47 min ago