Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

Browsing through FTP help (i.e. ftp> ?), showed me a command name literal, description of which is

ftp> ? literal
literal         Send arbitrary ftp command

I tried to do some trial and error, and following is the terminal output. All returned 500 Unknown command.

ftp> literal check
500 Unknown command.
ftp> literal bye
500 Unknown command.
ftp> literal
Command line to send check
500 Unknown command.
ftp> literal
Command line to send ascii
500 Unknown command.

I would like to know more about this literal command and in what scenarios is it helpful?


Note: I am connecting a unix machine from windows 7 command prompt. And I see both literal and quote in ftp help.

share|improve this question
add comment

1 Answer

up vote 8 down vote accepted

FTP has quite a few commands. While the client maps some of these to a more userfriendly text interface.

For example, if you use ftp -v (depending on your ftp client, the one I use needs ftp -vd), you'll notice something like the following (---> shows what is sent to the server):

$ ftp -vd ftp.debian.org
Connected to ftp.debian.org.
220 ftp.debian.org FTP server
Name (ftp.debian.org:user): anonymous
---> USER anonymous
331 Please specify the password.
230 Login successful.
ftp> cd debian
---> CWD debian
250 Directory successfully changed.

That is, your convenient cd calls get mapped to CWD commands.

Some FTP clients allow you to send verbatim FTP commands to the server; in yours it is done with literal (my ftp uses quote):

ftp> quote CWD ..
---> CWD ..
250 Directory successfully changed.

Useful? Indeed, it allows you to interact with your FTP server in ways the client doesn't know about. Maybe your client doesn't implement SITE commands, then you could still use literal SITE [...] to have the server do what you want. Things like FXP can be done with any FTP client using handcrafted commands, too (albeit quite inconveniently). Also, for experimenting with FTP, it's more comfortable to have the login process handled by the FTP client and use literal commands afterwards (compared to using telnet/netcat only).

However, what the server understands obviously depends on your server:

ftp> quote foobar
---> foobar
500 Unknown command.
share|improve this answer
Thanks for the info. I see both literal and quote and both are working. So, isn't that redundant? –  mtk Jan 4 '13 at 10:08
Is it? You might get used to literal, but I might still prefer (and expect to find) quote... (this might be a rather weak argument) –  sr_ Jan 4 '13 at 10:14
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.