[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| slackbook:basic_networking_utilities [2012/09/17 02:39 (UTC)] – [mutt] Added original text and formatting mfillpot | slackbook:basic_networking_utilities [2012/09/17 02:49 (UTC)] (current) – [Sources] updated the author list mfillpot | ||
|---|---|---|---|
| Line 490: | Line 490: | ||
| ==== mailx ==== | ==== mailx ==== | ||
| - | So those are great and everything, but what if you just want a mail client that isn't menu-driven? | + | So those are great and everything, but what if you just want a mail |
| + | client that isn't menu-driven? | ||
| + | **//mailx//** is here to save you. | ||
| - | mailx is based on the Berkeley Mail application, | ||
| - | mailx reads mail from your computer' | + | **//mailx//** is based on the Berkeley Mail |
| + | application, | ||
| + | appearing as early as Version 1 of AT& | ||
| + | used either interactively or non-interactively. | ||
| + | |||
| + | |||
| + | **// | ||
| + | mail spool and displays the usual combination of sender, subject, | ||
| + | status, and size in a list, leaving the user at an interactive | ||
| + | prompt. In fact, it might look familiar to you if you bothered | ||
| + | checking your mail immediately after installing Slackware and read | ||
| + | Pat Volkerding' | ||
| < | < | ||
| + | |||
| darkstar:~# mailx | darkstar:~# mailx | ||
| - | Heirloom mailx version 12.4 7/ | + | Heirloom mailx version 12.4 7/ |
| "/ | "/ | ||
| - | >N 1 To root Thu Mar 10 23:33 | + | >N1 To rootThu |
| - | N 2 To root Thu Mar 10 23:35 321/15417 Welcome to Linux (Slackware 14.0)! | + | N2 To rootThu |
| ?; | ?; | ||
| </ | </ | ||
| - | To read a message, enter the number of the message at the prompt. This displays the message using more, so use the **RETURN** key to view the next page. Once the end of the message has been reached, press **q** to return to the list view, or **RETURN** to continue to the next message. | ||
| - | To see a list of available commands, enter **?** at the mail prompt; using the commands provided, you can view the headers of mail in the spool, reply, delete, save, and many other common email tasks. | + | To read a message, enter the number of the message at the |
| + | prompt. This displays the message using | ||
| + | **// | ||
| + | key to view the next page. Once the end of the message has been | ||
| + | reached, press < | ||
| + | < | ||
| + | |||
| + | |||
| + | To see a list of available commands, enter < | ||
| + | **//mail//** prompt; using the commands provided, | ||
| + | you can view the headers of mail in the spool, reply, delete, save, | ||
| + | and many other common email tasks. | ||
| + | |||
| + | |||
| + | **// | ||
| + | scripting. For all of the options available for | ||
| + | **// | ||
| + | send an email to someone requires only the command itself and the | ||
| + | destination address. | ||
| - | mailx is most powerful when used in scripting. For all of the options available for mailx, view its man page. A simple way to send an email to someone requires only the command itself and the destination address. | ||
| < | < | ||
| - | | + | |
| + | darkstar: | ||
| </ | </ | ||
| - | After the command has been issued, an interactive prompt appears for a subject line, the message body, and the end character (a single period on an otherwise empty line). | ||
| - | mailx can be used entirely without human intervention, | + | After the command has been issued, an interactive prompt appears for |
| + | a subject line, the message body, and the end character (a single | ||
| + | period on an otherwise empty line). | ||
| + | |||
| + | |||
| + | **//mailx//** can be used entirely without human | ||
| + | intervention, | ||
| + | attribute you can define in the interactive shell for | ||
| + | **//mailx//** can also be defined while scripting | ||
| + | it or using it as one non-interactive command. | ||
| < | < | ||
| - | | + | |
| + | darkstar:~$ mailx -n -s "Test message" | ||
| </ | </ | ||
| - | In this example, the contents of the file message.txt would be sent as the message body to the specified recipient. No interaction from the user is required. | ||
| - | Within one's own computer (localhost) or one's own network, sending email in this manner is entirely possible. But over the internet a few more steps are usually required along the way. Of course, most notably there is usually an smtp server handling the delivery of your email. This, too, can be specified as part of your mail command: | + | In this example, the contents of the file |
| + | '' | ||
| + | to the specified recipient. No interaction from the user is required. | ||
| + | |||
| + | |||
| + | Within one's own computer (localhost) or one's own network, sending | ||
| + | email in this manner is entirely possible. But over the internet a | ||
| + | few more steps are usually required along the way. Of course, most | ||
| + | notably there is usually an smtp server handling the delivery of your | ||
| + | email. This, too, can be specified as part of your | ||
| + | **//mail//** command: | ||
| < | < | ||
| - | | + | |
| - | from=" | + | darkstar: |
| - | smtp=relay.example.com mail -n -s "Test message" | + | from=" |
| + | smtp=relay.example.com mail -n -s "Test message" | ||
| </ | </ | ||
| - | In this case, the MAILRC variable is set to /dev/null in order to override any system defaults, and the smtp server as well as the //FROM:// line are defined. The rest of the command is the same as using mailx internally within one's own computer or network. | ||
| - | Over all, mailx is usually viewed as a mail client with the bare-minimum features; this is largely true, but when you need to be able to script sending notification emails or important update messages, it quickly becomes a lot more valuable than a fully interactive application like pine or mutt. | + | In this case, the //MAILRC// variable |
| + | /dev/null in order to override any system defaults, and the | ||
| + | smtp server as well as the //FROM:// line are | ||
| + | defined. The rest of the command is the same as using | ||
| + | **// | ||
| + | computer | ||
| + | Over all, **// | ||
| + | mail client with the bare-minimum features; this is largely true, | ||
| + | but when you need to be able to script sending notification emails | ||
| + | or important update messages, it quickly becomes a lot more valuable | ||
| + | than a fully interactive application like | ||
| + | **// | ||
| ===== FTP Clients ===== | ===== FTP Clients ===== | ||
| - | Lots of data is stored on FTP servers the world over. In fact, Slackware Linux was first publically offered via FTP and continues to be distributed in this fashion today. Most open source software can be downloaded in source code or binary form via FTP, so knowing how to retrieve this information is a handy skill. | + | Lots of data is stored on FTP servers the world over. In fact, |
| + | Slackware Linux was first publically offered via FTP and continues to | ||
| + | be distributed in this fashion today. Most open source software can be | ||
| + | downloaded in source code or binary form via FTP, so knowing how to | ||
| + | retrieve this information is a handy skill. | ||
| ==== ftp ==== | ==== ftp ==== | ||
| - | The simplest FTP client included with Slackware is named simply, ftp(1) and is a reliable if somewhat simple means of sending and retrieving data. ftp connects to an FTP server, asks for your username and password, and then allows you to put or get data to and from that server. ftp has fallen out of favor with more experienced users do to a lack of features, but remains a handy tool, and much of the documentation you see online will refer you to it. | + | The simplest FTP client included with Slackware is named simply, |
| + | **//ftp//**(1) and is a reliable if somewhat simple | ||
| + | means of sending and retrieving data. **//ftp//** | ||
| + | connects to an FTP server, asks for your username and password, and | ||
| + | then allows you to put or get data to and from that server. | ||
| + | **//ftp//** has fallen out of favor with more | ||
| + | experienced users do to a lack of features, but remains a handy tool, | ||
| + | and much of the documentation you see online will refer you to it. | ||
| + | |||
| + | |||
| + | Once an FTP session has been initialized, | ||
| + | somewhat like a shell.From here you can change and list directories | ||
| + | using the //" | ||
| + | may issue the //" | ||
| + | command to retrieve data from the server. If you're connecting to a | ||
| + | public FTP server, you'll want to use the //" | ||
| + | simply enter your e-mail address (or a fake one) for the password. | ||
| - | Once an FTP session has been initialized, | ||
| < | < | ||
| Line 570: | Line 651: | ||
| ==== ncftp ==== | ==== ncftp ==== | ||
| - | ncftp(1) (pronounced nick-f-t-p), | + | **//ncftp//**(1) (pronounced nick-f-t-p), |
| + | feature rich successor to **//ftp//**, supporting | ||
| + | tab completion and recursive retrieval. It automatically connects to a | ||
| + | server as the anonymous user, unless you specify a different username | ||
| + | on the commandline with the //-u// argument. The primary | ||
| + | advantage over **//ftp//** is the ability to send | ||
| + | and retrieve multiple files at once with the //" | ||
| + | commands. If you pass the //-R// argument to either of them, | ||
| + | they will recursively put or get data from directories. | ||
| < | < | ||
| darkstar:~# ncftp ftp.osuosl.org | darkstar:~# ncftp ftp.osuosl.org | ||
| - | Logging in... | + | Logging in... |
| Login successful. | Login successful. | ||
| - | Logged in to ftp.osuosl.org. | + | Logged in to ftp.osuosl.org. |
| ncftp / > cd pub/ | ncftp / > cd pub/ | ||
| Directory successfully changed. | Directory successfully changed. | ||
| ncftp ...ware/ | ncftp ...ware/ | ||
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| - | isolinux/ | + | isolinux/ |
| ncftp ...ware/ | ncftp ...ware/ | ||
| </ | </ | ||
| - | |||
| ==== lftp ==== | ==== lftp ==== | ||
| - | The last client we're going to look at is lftp(1). Like ncftp, it supports tab completion and recursive activity, but has a more friendly license. Rather than user " | + | The last client we're going to look at is |
| + | **//lftp//**(1).Like | ||
| + | **//ncftp//**, it supports tab completion and | ||
| + | recursive activity, but has a more friendly license.Rather than user | ||
| + | //" | ||
| + | //" | ||
| + | I'll have to refer you to the man page and the built-in | ||
| + | for complete details. | ||
| < | < | ||
| darkstar:~# lftp ftp.osuosl.org | darkstar:~# lftp ftp.osuosl.org | ||
| lftp ftp.osuosl.org: | lftp ftp.osuosl.org: | ||
| - | cd ok, cwd=/ | + | cd ok, cwd=/ |
| lftp ftp.osuosl.org:/ | lftp ftp.osuosl.org:/ | ||
| - | Total: 2 directories, | + | Total: 2 directories, |
| New: 16 files, 1 symlink | New: 16 files, 1 symlink | ||
| 14636789 bytes transferred in 20 seconds (703.7K/s) | 14636789 bytes transferred in 20 seconds (703.7K/s) | ||
| lftp ftp.osuosl.org:/ | lftp ftp.osuosl.org:/ | ||
| </ | </ | ||
| - | |||
| ===== rsync ===== | ===== rsync ===== | ||
| - | Ready to see something cool? Have you ever found yourself needing just a handful of files from a large directory, but you're not entirely sure which files you already have and which ones you need? You can download the entire directory again, but that's duplicating a lot of work. You can pick and chose, manually check everything, but that's very tedious. Perhaps you've downloaded a large file such as an ISO, but something went wrong with the download? It doesn' | + | Ready to see something cool? Have you ever found yourself needing just |
| + | a handful of files from a large directory, but you're not entirely sure | ||
| + | which files you already have and which ones you need? You can download | ||
| + | the entire directory again, but that's duplicating a lot of work. You | ||
| + | can pick and chose, manually check everything, but that's very tedious. | ||
| + | Perhaps you've downloaded a large file such as an ISO, but something | ||
| + | went wrong with the download? It doesn' | ||
| + | have to pull down the entire file again if only a few bits have been | ||
| + | corrupted.Enter | ||
| + | versatile copying tool for local and remote files. | ||
| + | |||
| + | |||
| + | **// | ||
| + | effective techniques to determine what needs to be changed. By checking | ||
| + | file size and time stamps, it can determine if two files are different. | ||
| + | If something has changed, it can determine what bytes are different, | ||
| + | and simply download that handfull of data rather than an entire file. | ||
| + | It is truly a marvel of modern technology. | ||
| - | rsync uses a handful of simple, but very effective techniques to determine what needs to be changed. By checking file size and time stamps, it can determine if two files are different. If something has changed, it can determine what bytes are different, and simply download that handfull of data rather than an entire file. It is truly a marvel of modern technology. | ||
| - | In its simplist form, rsync connects to an rsync protocol server and downloads a list of files and directories, | + | In its simplist form, **//rsync//** connects to an |
| + | rsync protocol server and downloads a list of files and directories, | ||
| + | along with their sizes, timestamps, and other information. It then | ||
| + | compares this to the local files (if any) to determine what it needs to | ||
| + | transfer. Only files that are different will be synced.Additionally, | ||
| + | it breaks up large files into smaller chunks and compares those chunks | ||
| + | using a quick and simple hash function. Any chunks that match are not | ||
| + | transferred, | ||
| + | dramatically reduced.**//rsync//** also supports | ||
| + | compression, | ||
| + | many other options. For a complete list, you'll need to refer to the | ||
| + | man page, but I've included a small table of some of the more common | ||
| + | options. | ||
| **Table 16.1. rsync Arguments** | **Table 16.1. rsync Arguments** | ||
| Line 626: | Line 750: | ||
| |-z |Compress - handy for slow network connections| | |-z |Compress - handy for slow network connections| | ||
| - | Due to the power and versatility of rsync, it can be invoked in a number of ways. The following two examples connect to an rsync protocol server to retrieve some information and to another server via ssh to encrypt the transmission. | + | Due to the power and versatility of **//rsync//**, |
| + | it can be invoked in a number of ways.The following two examples | ||
| + | connect to an rsync protocol server to retrieve some information and to | ||
| + | another server via ssh to encrypt the transmission. | ||
| < | < | ||
| Line 633: | Line 761: | ||
| darkstar:~# rsync -e ssh ftp.slackware.com:/ | darkstar:~# rsync -e ssh ftp.slackware.com:/ | ||
| </ | </ | ||
| - | |||
| ====== Chapter Navigation ====== | ====== Chapter Navigation ====== | ||
| Line 642: | Line 769: | ||
| ====== Sources ====== | ====== Sources ====== | ||
| <!-- If you copy information from another source, then specify that source --> | <!-- If you copy information from another source, then specify that source --> | ||
| - | * Original source: [[http:// | + | * Original source: [[http:// |
| <!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
| - | < | + | |
| <!-- * Contrbutions by [[wiki: | <!-- * Contrbutions by [[wiki: | ||
