1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�28.�Unicode/Charsets</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="integrate-ms-networks.html" title="Chapter�27.�Integrating MS Windows Networks with Samba"><link rel="next" href="Backup.html" title="Chapter�29.�Backup Techniques"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�28.�Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="Backup.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter�28.�Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><span class="contrib">Japanese character support</span><div class="affiliation"><div class="address"><p><tt class="email"><<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="unicode.html#id2607888">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2607926">What Are Charsets and Unicode?</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2607997">Samba and Charsets</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2608091">Conversion from Old Names</a></span></dt><dt><span class="sect1"><a href="unicode.html#id2608116">Japanese Charsets</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2608179">Basic Parameter Setting</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2608622">Individual Implementations</a></span></dt><dt><span class="sect2"><a href="unicode.html#id2608759">Migration from Samba-2.2 Series</a></span></dt></dl></dd><dt><span class="sect1"><a href="unicode.html#id2608901">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="unicode.html#id2608907">CP850.so Can't Be Found</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607888"></a>Features and Benefits</h2></div></div></div><p> 2Every industry eventually matures. One of the great areas of maturation is in 3the focus that has been given over the past decade to make it possible for anyone 4anywhere to use a computer. It has not always been that way, in fact, not so long 5ago it was common for software to be written for exclusive use in the country of 6origin. 7</p><p> 8Of all the effort that has been brought to bear on providing native 9language support for all computer users, the efforts of the 10<a href="http://www.openi18n.org/" target="_top">Openi18n organization</a> 11is deserving of special mention. 12</p><p> 13Samba-2.x supported a single locale through a mechanism called 14<span class="emphasis"><em>codepages</em></span>. Samba-3 is destined to become a truly trans-global 15file and printer-sharing platform. 16</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607926"></a>What Are Charsets and Unicode?</h2></div></div></div><p> 17Computers communicate in numbers. In texts, each number will be 18translated to a corresponding letter. The meaning that will be assigned 19to a certain number depends on the <span class="emphasis"><em>character set (charset) 20</em></span> that is used. 21</p><p> 22A charset can be seen as a table that is used to translate numbers to 23letters. Not all computers use the same charset (there are charsets 24with German umlauts, Japanese characters, and so on). The American Standard Code 25for Information Interchange (ASCII) encoding system has been the normative character 26encoding scheme used by computers to date. This employs a charset that contains 27256 characters. Using this mode of encoding each character takes exactly one byte. 28</p><p> 29There are also charsets that support extended characters, but those need at least 30twice as much storage space as does ASCII encoding. Such charsets can contain 31<span><b class="command">256 * 256 = 65536</b></span> characters, which is more than all possible 32characters one could think of. They are called multi-byte charsets because they use 33more then one byte to store one character. 34</p><p> 35One standardized multi-byte charset encoding scheme is known as 36<a href="http://www.unicode.org/" target="_top">unicode</a>. A big advantage of using a 37multi-byte charset is that you only need one. There is no need to make sure two 38computers use the same charset when they are communicating. 39</p><p>Old Windows clients use single-byte charsets, named 40<i class="parameter"><tt>codepages</tt></i>, by Microsoft. However, there is no support for 41negotiating the charset to be used in the SMB/CIFS protocol. Thus, you 42have to make sure you are using the same charset when talking to an older client. 43Newer clients (Windows NT, 200x, XP) talk unicode over the wire. 44</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607997"></a>Samba and Charsets</h2></div></div></div><p> 45As of Samba-3, Samba can (and will) talk unicode over the wire. Internally, 46Samba knows of three kinds of character sets: 47</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2608014"></a>unix charset</span></dt><dd><p> 48 This is the charset used internally by your operating system. 49 The default is <tt class="constant">UTF-8</tt>, which is fine for most 50 systems, which covers all characters in all languages. The default 51 in previous Samba releases was to save filenames in the encoding of the 52 clients, for example cp850 for western european countries. 53 </p></dd><dt><span class="term"><a class="indexterm" name="id2608040"></a>display charset</span></dt><dd><p>This is the charset Samba will use to print messages 54 on your screen. It should generally be the same as the <i class="parameter"><tt>unix charset</tt></i>. 55 </p></dd><dt><span class="term"><a class="indexterm" name="id2608065"></a>dos charset</span></dt><dd><p>This is the charset Samba uses when communicating with 56 DOS and Windows 9x/Me clients. It will talk unicode to all newer clients. 57 The default depends on the charsets you have installed on your system. 58 Run <span><b class="command">testparm -v | grep "dos charset"</b></span> to see 59 what the default is on your system. 60 </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608091"></a>Conversion from Old Names</h2></div></div></div><p>Because previous Samba versions did not do any charset conversion, 61characters in filenames are usually not correct in the UNIX charset but only 62for the local charset used by the DOS/Windows clients.</p><p>Bjoern Jacke has written a utility named <a href="http://j3e.de/linux/convmv/" target="_top">convmv</a> 63that can convert whole directory structures to different charsets with one single command. 64</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608116"></a>Japanese Charsets</h2></div></div></div><p> 65Setting up Japanese charsets is quite difficult. This is mainly because: 66</p><div class="itemizedlist"><ul type="disc"><li><p>The Windows character set is extended from the original legacy Japanese 67 standard (JIS X 0208) and is not standardized. This means that the strictly 68 standardized implementation cannot support the full Windows character set. 69 </p></li><li><p> Mainly for historical reasons, there are several encoding methods in 70 Japanese, which are not fully compatible with each other. There are 71 two major encoding methods. One is the Shift_JIS series, it is used in Windows 72 and some UNIX's. The other is the EUC-JP series, used in most UNIX's 73 and Linux. Moreover, Samba previously also offered several unique encoding 74 methods, named CAP and HEX, to keep interoperability with CAP/NetAtalk and 75 UNIX's which can't use Japanese filenames. Some implementations of the 76 EUC-JP series can't support the full Windows character set. 77 </p></li><li><p>There are some code conversion tables between Unicode and legacy 78 Japanese character sets. One is compatible with Windows, another one 79 is based on the reference of the Unicode consortium and others are 80 a mixed implementation. The Unicode consortium does not officially 81 define any conversion tables between Unicode and legacy character 82 sets so there cannot be standard one. 83 </p></li><li><p>The character set and conversion tables available in iconv() depends 84 on the iconv library that is available. Next to that, the Japanese locale 85 names may be different on different systems. This means that the value of 86 the charset parameters depends on the implementation of iconv() you are using. 87 </p><p>Though 2 byte fixed UCS-2 encoding is used in Windows internally, 88 Shift_JIS series encoding is usually used in Japanese environments 89 as ASCII encoding is in English environments. 90 </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608179"></a>Basic Parameter Setting</h3></div></div></div><p> 91 <a class="indexterm" name="id2608186"></a>dos charset and 92 <a class="indexterm" name="id2608193"></a>display charset 93 should be set to the locale compatible with the character set 94 and encoding method used on Windows. This is usually CP932 95 but sometimes has a different name. 96 </p><p> 97 <a class="indexterm" name="id2608206"></a>unix charset can be either Shift_JIS series, 98 EUC-JP series and UTF-8. UTF-8 is always available but the availability of other locales 99 and its name itself depends on the system. 100 </p><p> 101 Additionally, you can consider to use the Shift_JIS series as the 102 value of the <a class="indexterm" name="id2608221"></a>unix charset 103 parameter by using the vfs_cap module, which does the same thing as 104 setting “<span class="quote"><span class="emphasis"><em>coding system = CAP</em></span></span>” in the Samba 2.2 series. 105 </p><p> 106 Where to set <a class="indexterm" name="id2608238"></a>unix charset 107 to is a difficult question. Here is a list of details, advantages and 108 disadvantages of using a certain value. 109 </p><div class="variablelist"><dl><dt><span class="term">Shift_JIS series</span></dt><dd><p> 110 Shift_JIS series means a locale which is equivalent to <tt class="constant">Shift_JIS</tt>, 111 used as a standard on Japanese Windows. In the case of <tt class="constant">Shift_JIS</tt>, 112 for example if a Japanese file name consist of 0x8ba4 and 0x974c 113 (a 4 bytes Japanese character string meaning “<span class="quote"><span class="emphasis"><em>share</em></span></span>”) and “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” 114 is written from Windows on Samba, the file name on UNIX becomes 115 0x8ba4, 0x974c, “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” (a 8 bytes BINARY string), same as Windows. 116 </p><p>Since Shift_JIS series is usually used on some commercial based 117 UNIX's; hp-ux and AIX as Japanese locale (however, it is also possible 118 to use the EUC-JP series), To use Shift_JIS series on these platforms, 119 Japanese file names created from Windows can be referred to also on 120 UNIX.</p><p> 121 If your UNIX is already working with Shift_JIS and there is a user 122 who needs to use Japanese file names written from Windows, the 123 Shift_JIS series is the best choice. However, broken file names 124 may be displayed and some commands which cannot handle non-ASCII 125 filenames may be aborted during parsing filenames. especially there 126 may be “<span class="quote"><span class="emphasis"><em>\ (0x5c)</em></span></span>” in file names, which need to be handled carefully. 127 So you had better not touch file names written from Windows on UNIX. 128 </p><p> 129 Note that most Japanized free software actually works with EUC-JP 130 only. You had better verify if the Japanized free software can work 131 with Shift_JIS. 132 </p></dd><dt><span class="term">EUC-JP series</span></dt><dd><p> 133 EUC-JP series means a locale which is equivalent to the industry 134 standard called EUC-JP, widely used in Japanese UNIX (although EUC 135 contains specifications for languages other than Japanese, such as 136 EUC-KR). In the case of EUC-JP series, for example if a Japanese 137 file name consist of 0x8ba4 and 0x974c and “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” is written from 138 Windows on Samba, the file name on UNIX becomes 0xb6a6, 0xcdad, 139 “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” (a 8 bytes BINARY string). 140 </p><p> 141 Since EUC-JP is usually used on Open source UNIX, Linux and FreeBSD, 142 and on commercial based UNIX, Solaris, IRIX and Tru64 UNIX as 143 Japanese locale (however, it is also possible on Solaris to use 144 Shift_JIS and UTF-8, on Tru64 UNIX to use Shift_JIS). To use EUC-JP 145 series, most Japanese file names created from Windows can be 146 referred to also on UNIX. Also, most Japanized free software work 147 mainly with EUC-JP only. 148 </p><p> 149 It is recommended to choose EUC-JP series when using Japanese file 150 names on these UNIX. 151 </p><p> 152 Although there is no character which needs to be carefully treated 153 like “<span class="quote"><span class="emphasis"><em>\ (0x5c)</em></span></span>”, broken file names may be displayed and some 154 commands which cannot handle non-ASCII filenames may be aborted 155 during parsing filenames. 156 </p><p> 157 Moreover, if you built Samba using differently installed libiconv, 158 eucJP-ms locale included in libiconv and EUC-JP series locale 159 included in OS may not be compatible. In this case, you may need to 160 avoid using incompatible characters for file names. 161 </p></dd><dt><span class="term">UTF-8</span></dt><dd><p> 162 UTF-8 means a locale which is equivalent to UTF-8, the international 163 standard defined by Unicode consortium. In UTF-8, a <i class="parameter"><tt>character</tt></i> is 164 expressed using 1-3 bytes. In case of Japanese, most characters 165 are expressed using 3 bytes. Since on Windows Shift_JIS, where a 166 character is expressed with 1 or 2 bytes, is used to express 167 Japanese, basically a byte length of a UTF-8 string grows 1.5 times 168 the length of a original Shift_JIS string. In the case of UTF-8, 169 for example if a Japanese file name consist of 0x8ba4 and 0x974c and 170 “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” is written from Windows on Samba, the file name on UNIX 171 becomes 0xe585, 0xb1e6, 0x9c89, “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” (a 10 bytes BINARY string). 172 </p><p> 173 For systems where iconv() is not available or where iconv()'s locales 174 are not compatible with Windows, UTF-8 is the only locale available. 175 </p><p> 176 There are no systems that use UTF-8 as default locale for Japanese. 177 </p><p> 178 Some broken file names may be displayed and some commands which 179 cannot handle non-ASCII filenames may be aborted during parsing 180 filenames. especially there may be “<span class="quote"><span class="emphasis"><em>\ (0x5c)</em></span></span>” in file names, which 181 need to be handled carefully. So you had better not touch file names 182 written from Windows on UNIX. 183 </p><p> 184 In addition, although it is not directly concerned with Samba, since 185 there is a delicate difference between iconv() function, which is 186 generally used on UNIX and the functions used on other platforms, 187 such as Windows and Java about the conversion table between 188 Shift_JIS and Unicode, you should be carefully to handle UTF-8. 189 </p><p> 190 Although Mac OS X uses UTF-8 as its encoding method for filenames, 191 it uses an extended UTF-8 specification that Samba cannot handle so 192 UTF-8 locale is not available for Mac OS X. 193 </p></dd><dt><span class="term">Shift_JIS series + vfs_cap (CAP encoding)</span></dt><dd><p> 194 CAP encoding means a specification using in CAP and NetAtalk, file 195 server software for Macintosh. In the case of CAP encoding, for 196 example if a Japanese file name consist of 0x8ba4 and 0x974c and 197 “<span class="quote"><span class="emphasis"><em>.txt</em></span></span>” is written from Windows on Samba, the file name on UNIX 198 becomes “<span class="quote"><span class="emphasis"><em>:8b:a4:97L.txt</em></span></span>” (a 14 bytes ASCII string). 199 </p><p> 200 For CAP encoding a byte which cannot be expressed as an ASCII 201 character (0x80 or above) is encoded as “<span class="quote"><span class="emphasis"><em>:xx</em></span></span>” form. You need to take 202 care of containing a “<span class="quote"><span class="emphasis"><em>\(0x5c)</em></span></span>” in a filename but filenames are not 203 broken in a system which cannot handle non-ASCII filenames. 204 </p><p> 205 The greatest merit of CAP encoding is the compatibility of encoding 206 filenames with CAP or NetAtalk, file server software of Macintosh. 207 Since they usually write a file name on UNIX with CAP encoding, if a 208 directory is shared with both Samba and NetAtalk, you need to use 209 CAP encoding to avoid non-ASCII filenames are broken. 210 </p><p> 211 However, recently there are some systems where NetAtalk has been 212 patched to write filenames with EUC-JP (i.e. Japanese original Vine Linux). 213 Here you need to choose EUC-JP series instead of CAP encoding. 214 </p><p> 215 vfs_cap itself is available for non Shift_JIS series locales for 216 systems which cannot handle non-ASCII characters or systems which 217 shares files with NetAtalk. 218 </p><p> 219 To use CAP encoding on Samba-3, you should use the unix charset parameter and VFS 220 as follows: 221 </p><div class="example"><a name="id2608528"></a><p class="title"><b>Example�28.1.�VFS CAP</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># the locale name "CP932" may be different</td></tr><tr><td><a class="indexterm" name="id2608553"></a><i class="parameter"><tt> 222 223 dos charset = CP932</tt></i></td></tr><tr><td><a class="indexterm" name="id2608568"></a><i class="parameter"><tt> 224 225 unix charset = CP932</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[cap-share]</tt></i></td></tr><tr><td><a class="indexterm" name="id2608592"></a><i class="parameter"><tt> 226 227 vfs option = cap</tt></i></td></tr></table></div><p> 228 You should set CP932 if using GNU libiconv for unix charset. Setting this, 229 filenames in the “<span class="quote"><span class="emphasis"><em>cap-share</em></span></span>” share are written with CAP encoding. 230 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608622"></a>Individual Implementations</h3></div></div></div><p> 231Here is some additional information regarding individual implementations: 232</p><div class="variablelist"><dl><dt><span class="term">GNU libiconv</span></dt><dd><p> 233 To handle Japanese correctly, you should apply the patch 234 <a href="http://www2d.biglobe.ne.jp/~msyk/software/libiconv-patch.html" target="_top">libiconv-1.8-cp932-patch.diff.gz</a> 235 to libiconv-1.8. 236 </p><p> 237 Using the patched libiconv-1.8, these settings are available: 238 </p><pre class="programlisting"> 239dos charset = CP932 240unix charset = CP932 / eucJP-ms / UTF-8 241 | | 242 | +-- EUC-JP series 243 +-- Shift_JIS series 244display charset = CP932 245</pre><p> 246 Other Japanese locales (for example Shift_JIS and EUC-JP) should not 247 be used for the lack of the compatibility with Windows. 248 </p></dd><dt><span class="term">GNU glibc</span></dt><dd><p> 249 To handle Japanese correctly, you should apply a <a href="http://www2d.biglobe.ne.jp/~msyk/software/glibc/" target="_top">patch</a> 250 to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later. 251 </p><p> 252 Using the above glibc, these setting are available: 253 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2608703"></a><i class="parameter"><tt> 254 255 dos charset = CP932</tt></i></td></tr><tr><td><a class="indexterm" name="id2608718"></a><i class="parameter"><tt> 256 257 unix charset = CP932 / eucJP-ms / UTF-8</tt></i></td></tr><tr><td><a class="indexterm" name="id2608735"></a><i class="parameter"><tt> 258 259 display charset = CP932</tt></i></td></tr></table><p> 260 Other Japanese locales (for example Shift_JIS and EUC-JP) should not 261 be used for the lack of the compatibility with Windows. 262 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608759"></a>Migration from Samba-2.2 Series</h3></div></div></div><p> 263Prior to Samba-2.2 series “<span class="quote"><span class="emphasis"><em>coding system</em></span></span>” parameter is used as 264<a class="indexterm" name="id2608773"></a>unix charset parameter of the Samba-3 series. 265<a href="unicode.html#japancharsets" title="Table�28.1.�Japanese Character Sets in Samba-2.2 and Samba-3">Next table</a> shows the mapping table when migrating from the Samba-2.2 series to Samba-3. 266</p><div class="table"><a name="japancharsets"></a><p class="title"><b>Table�28.1.�Japanese Character Sets in Samba-2.2 and Samba-3</b></p><table summary="Japanese Character Sets in Samba-2.2 and Samba-3" border="1"><colgroup><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Samba-2.2 Coding System</th><th align="center">Samba-3 unix charset</th></tr></thead><tbody><tr><td align="center">SJIS</td><td align="center">Shift_JIS series</td></tr><tr><td align="center">EUC</td><td align="center">EUC-JP series</td></tr><tr><td align="center">EUC3<sup>[<a name="id2608850" href="#ftn.id2608850">a</a>]</sup></td><td align="center">EUC-JP series</td></tr><tr><td align="center">CAP</td><td align="center">Shift_JIS series + VFS</td></tr><tr><td align="center">HEX</td><td align="center">currently none</td></tr><tr><td align="center">UTF8</td><td align="center">UTF-8</td></tr><tr><td align="center">UTF8-Mac<sup>[<a name="id2608881" href="#ftn.id2608881">b</a>]</sup></td><td align="center">currently none</td></tr><tr><td align="center">others</td><td align="center">none</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2608850" href="#id2608850">a</a>] </sup>Only exists in Japanese Samba version</p></div><div class="footnote"><p><sup>[<a name="ftn.id2608881" href="#id2608881">b</a>] </sup>Only exists in Japanese Samba version</p></div></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2608901"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608907"></a>CP850.so Can't Be Found</h3></div></div></div><p>“<span class="quote"><span class="emphasis"><em>Samba is complaining about a missing <tt class="filename">CP850.so</tt> file.</em></span></span>”</p><p><span class="emphasis"><em>Answer:</em></span> CP850 is the default <a class="indexterm" name="id2608930"></a>dos charset. 267 The <a class="indexterm" name="id2608937"></a>dos charset is used to convert data to the codepage used by your dos clients. 268 If you do not have any dos clients, you can safely ignore this message. </p><p>CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. 269 If you compiled Samba from source, make sure to configure found iconv.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="Backup.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�27.�Integrating MS Windows Networks with Samba�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�29.�Backup Techniques</td></tr></table></div></body></html> 270