IFS是internal field separator的缩写，shell的特殊环境变量。ksh根据IFS存储的值，可以是空格、tab、换行符或者其他自定义符号，来解析输入和输出的变量值。

# The following code segment will only work in ksh,
# and it will fail in bash
IP=220.112.253.111
IFS="."
TMPIP=$(echo$IP)
IFS=" " # space
echo $TMPIP | read ip1 ip2 ip3 ip4 INVERT_IP=$ip4.$ip3.$ip2.$ip1 更详细的IFS的介绍参见下文：（原文地址：http://www.livefirelabs.com/unix_tip_trick_shell_script/oct_2003/10132003.htm  Another shell variable that you should become comfortable using is the IFS, or internal field separator, variable. The shell uses the value stored in IFS, which is the space, tab, and newline characters by default, to delimit words for the read and set commands, when parsing output from command substitution, and when performing variable substitution. IFS can be redefined to parse one or more lines of data whose fields are not delimited by the default white-space characters. Consider this sequence of variable assignments and for loops:$ line=learn:unix:at:livefire:labs$for i in$line> do> echo $i> donelearn:unix:at:livefire:labs$ OIFS=$IFS$ IFS=:$for i in$line> do> echo $i> donelearnunixatlivefirelabs$ The first command assigns the string “learn:unix:at:livefire:labs” to the variable named line.  You can see from the first for loop that the shell treats the entire string as a single field.  This is because the string does not contain a space, tab, or newline character.  After redefining IFS, the second for loop treats the string as four separated fields, each delimited by a colon.  Using a colon for IFS would be appropriate when parsing the fields in a record from /etc/passwd, the user account information file: livefire:x:100:1::/export/home/livefire:/bin/ksh Notice that the original value of IFS was stored in OIFS (“O” for original) prior to changing its value.  After you are finished using the new definition, it would be wise to return it to its original value to avoid unexpected side effects that may surface later on in your script.  TIP – The current value of IFS may be viewed using the following pipeline: $echo "$IFS" | od -b0000000 040 011 012 0120000004\$ The output of the echo command is piped into the octal dump command, giving you its octal equivalent.  You can then use an ASCII table to determine what characters are stored in the variable.  Hint: Ignore the first set of zeros and the second newline character (012), which was generated by echo.