[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 revisionLast revisionBoth sides next revision | ||
slackbook:basic_networking_utilities [2012/09/17 02:43 (UTC)] – [FTP Clients] Added original text and formatting mfillpot | slackbook:basic_networking_utilities [2012/09/17 02:49 (UTC)] – [rsync] Added original text and formatting mfillpot | ||
---|---|---|---|
Line 609: | Line 609: | ||
==== 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 636: | 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 692: | 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 699: | Line 761: | ||
darkstar:~# rsync -e ssh ftp.slackware.com:/ | darkstar:~# rsync -e ssh ftp.slackware.com:/ | ||
</ | </ | ||
- | |||
====== Chapter Navigation ====== | ====== Chapter Navigation ====== | ||