1
0
mirror of https://github.com/samba-team/samba.git synced 2025-03-05 20:58:40 +03:00

save as we go. More pages done.

(This used to be commit ec1dfb80b39f816faed702ace20a385aba9caf6b)
This commit is contained in:
Gerald Carter 2001-02-22 21:48:19 +00:00
parent 4bca9fd8d4
commit cbf0f980c9
6 changed files with 1103 additions and 464 deletions

View File

@ -0,0 +1,197 @@
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<refentry id="findsmb">
<refmeta>
<refentrytitle>make_smbcodepage</refentrytitle>
<manvolnum>1</manvolnum>
</refmeta>
<refnamediv>
<refname>make_smbcodepage</refname>
<refpurpose>construct a codepage file for Samba</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>make_smbcodepage</command>
<arg choice="req">c|d</arg>
<arg choice="req">codepage</arg>
<arg choice="req">inputfile</arg>
<arg choice="req">outputfile</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This tool is part of the <ulink url="samba.7.html">
Samba</ulink> suite.</para>
<para><command>make_smbcodepage</command> compiles or de-compiles
codepage files for use with the internationalization features
of Samba 2.2</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<variablelist>
<varlistentry>
<term>c|d</term>
<listitem><para>This tells <command>make_smbcodepage</command>
if it is compiling (<parameter>c</parameter>) a text format code
page file to binary, or (<parameter>d</parameter>) de-compiling
a binary codepage file to text. </para></listitem>
</varlistentry>
<varlistentry>
<term>codepage</term>
<listitem><para>This is the codepage we are processing (a
number, e.g. 850). </para></listitem>
</varlistentry>
<varlistentry>
<term>inputfile</term>
<listitem><para>This is the input file to process. In t
he '<parameter>c</parameter>' case this will be a text
codepage definition file such as the ones found in the Samba
<filename>source/codepages</filename> directory. In
the '<parameter>d</parameter>' case this will be the
binary format codepage definition file normally found in
the <filename>lib/codepages</filename> directory in the
Samba install directory path.</para></listitem>
</varlistentry>
<varlistentry>
<term>outputfile</term>
<listitem><para>This is the output file to produce.</para></listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Samba Codepage Files</title>
<para>A text Samba codepage definition file is a description
that tells Samba how to map from upper to lower case for
characters greater than ascii 127 in the specified DOS code page.
Note that for certain DOS codepages (437 for example) mapping
from lower to upper case may be non-symmetrical. For example, in
code page 437 lower case a acute maps to a plain upper case A
when going from lower to upper case, but plain upper case A maps
to plain lower case a when lower casing a character. </para>
<para>A binary Samba codepage definition file is a binary
representation of the same information, including a value that
specifies what codepage this file is describing. </para>
<para>As Samba does not yet use UNICODE (current for Samba version 2.2)
you must specify the client code page that your DOS and Windows
clients are using if you wish to have case insensitivity done
correctly for your particular language. The default codepage Samba
uses is 850 (Western European). Text codepage definition sample files
are provided in the Samba distribution for codepages 437 (USA), 737 (Greek),
850 (Western European) 852 (MS-DOS Latin 2), 861 (Icelandic), 866 (Cyrillic),
932 (Kanji SJIS), 936 (Simplified Chinese), 949 (Hangul) and 950 (Traditional
Chinese). Users are encouraged to write text codepage definition files for
their own code pages and donate them to samba@samba.org. All codepage files
in the Samba <filename>source/codepages</filename> directory are
compiled and installed when a <command>'make install'</command>
command is issued there. </para>
<para>The client codepage used by the <command>smbd</command> server
is configured using the <command>client code page</command> parameter
in the <command>smb.conf</command> file. </para>
</refsect1>
<refsect1>
<title>Files</title>
<para><command>codepage_def.&lt;codepage&gt;</command></para>
<para>These are the input (text) codepage files provided in the
Samba <filename>source/codepages</filename> directory.</para>
<para>A text codepage definition file consists of multiple lines
containing four fields. These fields are:</para>
<itemizedlist>
<listitem><para><command>lower</command>: which is the
(hex) lower case character mapped on this line.</para>
</listitem>
<listitem><para><command>upper</command>: which is the (hex)
upper case character that the lower case character will map to.
</para></listitem>
<listitem><para><command>map upper to lower</command> which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given upper case character to the
given lower case character when lower casing a filename.
</para></listitem>
<listitem><para><command>map lower to upper</command> which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given lower case character to the
given upper case character when upper casing a filename.
</para></listitem>
</itemizedlist>
<para><command>codepage.&lt;codepage&gt;</command> - These are the
output (binary) codepage files produced and placed in the Samba
destination <filename>lib/codepage</filename> directory. </para>
</refsect1>
<refsect1>
<title>Installation</title>
<para>The location of the server and its support files is a
matter for individual system administrators. The following are
thus suggestions only. </para>
<para>It is recommended that the <command>make_smbcodepage
</command> program be installed under the <filename>/usr/local/samba
</filename> hierarchy, in a directory readable by all, writeable
only by root. The program itself should be executable by all. The
program should NOT be setuid or setgid! </para>
</refsect1>
<refsect1>
<title>VERSION</title>
<para>This man page is correct for version 2.2 of
the Samba suite.</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>,
<ulink url="smb.conf.5.html">smb.conf(5)</ulink>
</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</para>
<para>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</para>
</refsect1>
</refentry>

View File

@ -0,0 +1,103 @@
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<refentry id="findsmb">
<refmeta>
<refentrytitle>smbsh</refentrytitle>
<manvolnum>1</manvolnum>
</refmeta>
<refnamediv>
<refname>smbsh</refname>
<refpurpose>Allows access to Windows NT filesystem
using UNIX commands</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>smbsh</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This tool is part of the <ulink url="samba.7.html">
Samba</ulink> suite.</para>
<para><command>smbsh</command> allows you to access an NT filesystem
using UNIX commands such as <command>ls</command>, <command>
egrep</command>, and <command>rcp</command>. You must use a
shell that is dynmanically linked in order for <command>smbsh</command>
to work correctly.</para>
<para>To use the <command>smbsh</command> command, execute <command>
smbsh</command> from the prompt and enter the username and password
that authenticate you to the machine running the Windows NT
operating system.</para>
<para><programlisting>
<prompt>system% </prompt><userinput>smbsh</userinput>
<prompt>Username: </prompt><userinput>user</userinput>
<prompt>Password: </prompt><userinput>XXXXXXX</userinput>
</programlisting></para>
<para>Any dynamically linked command you execute from
this shell will access the <filename>/smb</filename> directory
using the smb protocol. For example, the command <command>ls /smb
</command> will show all the machines in your workgroup. The command
<command>ls /smb/&lt;machine-name&gt;</command> will show the share
names for that machine. You could then, for example, use the <command>
cd</command> command to change directories, <command>vi</command> to
edit files, and <command>rcp</command> to copy files.</para>
</refsect1>
<refsect1>
<title>VERSION</title>
<para>This man page is correct for version 2.2 of
the Samba suite.</para>
</refsect1>
<refsect1>
<title>BUGS</title>
<para><command>smbsh</command> works by intercepting the standard
libc calls with the dynamically loaded versions in <filename>
smbwrapper.o</filename>. Not all calls have been "wrapped", so
some programs may not function correctly under <command>smbsh
</command>.</para>
<para>Programs which are not dynamically linked cannot make
use of <command>smbsh</command>'s functionality. Most versions
of UNIX have a <command>file</command> command that will
describe how a program was linked.</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>,
<ulink url="smb.conf.5.html">smb.conf(5)</ulink>
</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</para>
<para>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</para>
</refsect1>
</refentry>

View File

@ -1,144 +1,354 @@
<html><head><title>make_smbcodepage (1)</title>
<link rev="made" href="mailto:samba@samba.org">
</head>
<body>
<hr>
<h1>make_smbcodepage (1)</h1>
<h2>Samba</h2>
<h2>23 Oct 1998</h2>
<p><a name="NAME"></a>
<h2>NAME</h2>
make_codepage - Construct a codepage file for Samba
<p><a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p><strong>make_smbcodepage</strong> [<a href="make_smbcodepage.1.html#cord">c|d</a>] <a href="make_smbcodepage.1.html#codepage">codepage</a> <a href="make_smbcodepage.1.html#inputfile">inputfile</a> <a href="make_smbcodepage.1.html#outputfile">outputfile</a>
<p><a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p>This program is part of the <strong>Samba</strong> suite.
<p><strong>make_smbcodepage</strong> compiles or de-compiles codepage files for use
with the internationalization features of Samba 2.0
<p><a name="OPTIONS"></a>
<h2>OPTIONS</h2>
<p><dl>
<p><a name="cord"></a>
<p></p><dt><strong>c|d</strong><dd> This tells <strong>make_smbcodepage</strong> if it is compiling (<strong>c</strong>) a text
format code page file to binary, or (<strong>d</strong>) de-compiling a binary codepage
file to text.
<p><a name="codepage"></a>
<p></p><dt><strong>codepage</strong><dd> This is the codepage we are processing (a number, e.g. 850).
<p><a name="inputfile"></a>
<p></p><dt><strong>inputfile</strong><dd> This is the input file to process. In the '<strong>c</strong>' case this
will be a text codepage definition file such as the ones found in the
Samba <em>source/codepages</em> directory. In the '<strong>d</strong>' case this will be the
binary format codepage definition file normally found in the
<em>lib/codepages</em> directory in the Samba install directory path.
<p><a name="outputfile"></a>
<p></p><dt><strong>outputfile</strong><dd> This is the output file to produce.
<p></dl>
<p><a name="SambaCodepageFiles"></a>
<h2>Samba Codepage Files</h2>
<p>A text Samba codepage definition file is a description that tells
Samba how to map from upper to lower case for characters greater than
ascii 127 in the specified DOS code page. Note that for certain DOS
codepages (437 for example) mapping from lower to upper case may be
non-symmetrical. For example, in code page 437 lower case a acute maps to
a plain upper case A when going from lower to upper case, but
plain upper case A maps to plain lower case a when lower casing a
character.
<p>A binary Samba codepage definition file is a binary representation of
the same information, including a value that specifies what codepage
this file is describing.
<p>As Samba does not yet use UNICODE (current for Samba version 2.0) you
must specify the client code page that your DOS and Windows clients
are using if you wish to have case insensitivity done correctly for
your particular language. The default codepage Samba uses is 850
(Western European). Text codepage definition sample files are
provided in the Samba distribution for codepages 437 (USA), 737
(Greek), 850 (Western European) 852 (MS-DOS Latin 2), 861 (Icelandic),
866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949
(Hangul) and 950 (Traditional Chinese). Users are encouraged to write
text codepage definition files for their own code pages and donate
them to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. All codepage files in the
Samba <em>source/codepages</em> directory are compiled and installed when a
<em>'make install'</em> command is issued there.
<p>The client codepage used by the <a href="smbd.8.html"><strong>smbd</strong></a> server is
configured using the <a href="smb.conf.5.html#clientcodepage"><strong>client code
page</strong></a> parameter in the
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
<p><a name="FILES"></a>
<h2>FILES</h2>
<p><strong>codepage_def.&lt;codepage&gt;</strong>
<p>These are the input (text) codepage files provided in the Samba
<em>source/codepages</em> directory.
<p>A text codepage definition file consists of multiple lines
containing four fields. These fields are :
<p><dl>
<p><li > <strong>lower</strong>: which is the (hex) lower case character mapped on this
line.
<p><li > <strong>upper</strong>: which is the (hex) upper case character that the lower
case character will map to.
<p><li > <strong>map upper to lower</strong> which is a boolean value (put either True
or False here) which tells Samba if it is to map the given upper case
character to the given lower case character when lower casing a
filename.
<p><li > <strong>map lower to upper</strong> which is a boolean value (put either True
or False here) which tells Samba if it is to map the given lower case
character to the given upper case character when upper casing a
filename.
<p></dl>
<p><strong>codepage.&lt;codepage&gt;</strong> These are the output (binary) codepage files
produced and placed in the Samba destination <em>lib/codepage</em>
directory.
<p><a name="INSTALLATION"></a>
<h2>INSTALLATION</h2>
<p>The location of the server and its support files is a matter for
individual system administrators. The following are thus suggestions
only.
<p>It is recommended that the <strong>make_smbcodepage</strong> program be installed
under the <em>/usr/local/samba</em> hierarchy, in a directory readable by
all, writeable only by root. The program itself should be executable
by all. The program should NOT be setuid or setgid!
<p><a name="VERSION"></a>
<h2>VERSION</h2>
<p>This man page is correct for version 2.0 of the Samba suite.
<p><a name="SEEALSO"></a>
<h2>SEE ALSO</h2>
<p><a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
<p><a name="AUTHOR"></a>
<h2>AUTHOR</h2>
<p>The original Samba software and related utilities were created by
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
by the Samba Team as an Open Source project similar to the way the
Linux kernel is developed.
<p>The original Samba man pages were written by Karl Auer. The man page
sources were converted to YODL format (another excellent piece of Open
Source software, available at
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
and updated for the Samba2.0 release by Jeremy Allison.
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
list of contributors and details on how to submit bug reports,
comments etc.
</body>
</html>
<HTML
><HEAD
><TITLE
>make_smbcodepage</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
>make_smbcodepage</A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN5"
></A
><H2
>Name</H2
>make_smbcodepage&nbsp;--&nbsp;construct a codepage file for Samba</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>make_smbcodepage</B
> {c|d} {codepage} {inputfile} {outputfile}</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN15"
></A
><H2
>DESCRIPTION</H2
><P
>This tool is part of the <A
HREF="samba.7.html"
TARGET="_top"
> Samba</A
> suite.</P
><P
><B
CLASS="COMMAND"
>make_smbcodepage</B
> compiles or de-compiles
codepage files for use with the internationalization features
of Samba 2.2</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN21"
></A
><H2
>OPTIONS</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>c|d</DT
><DD
><P
>This tells <B
CLASS="COMMAND"
>make_smbcodepage</B
>
if it is compiling (<TT
CLASS="PARAMETER"
><I
>c</I
></TT
>) a text format code
page file to binary, or (<TT
CLASS="PARAMETER"
><I
>d</I
></TT
>) de-compiling
a binary codepage file to text. </P
></DD
><DT
>codepage</DT
><DD
><P
>This is the codepage we are processing (a
number, e.g. 850). </P
></DD
><DT
>inputfile</DT
><DD
><P
>This is the input file to process. In t
he '<TT
CLASS="PARAMETER"
><I
>c</I
></TT
>' case this will be a text
codepage definition file such as the ones found in the Samba
<TT
CLASS="FILENAME"
>source/codepages</TT
> directory. In
the '<TT
CLASS="PARAMETER"
><I
>d</I
></TT
>' case this will be the
binary format codepage definition file normally found in
the <TT
CLASS="FILENAME"
>lib/codepages</TT
> directory in the
Samba install directory path.</P
></DD
><DT
>outputfile</DT
><DD
><P
>This is the output file to produce.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN47"
></A
><H2
>Samba Codepage Files</H2
><P
>A text Samba codepage definition file is a description
that tells Samba how to map from upper to lower case for
characters greater than ascii 127 in the specified DOS code page.
Note that for certain DOS codepages (437 for example) mapping
from lower to upper case may be non-symmetrical. For example, in
code page 437 lower case a acute maps to a plain upper case A
when going from lower to upper case, but plain upper case A maps
to plain lower case a when lower casing a character. </P
><P
>A binary Samba codepage definition file is a binary
representation of the same information, including a value that
specifies what codepage this file is describing. </P
><P
>As Samba does not yet use UNICODE (current for Samba version 2.2)
you must specify the client code page that your DOS and Windows
clients are using if you wish to have case insensitivity done
correctly for your particular language. The default codepage Samba
uses is 850 (Western European). Text codepage definition sample files
are provided in the Samba distribution for codepages 437 (USA), 737 (Greek),
850 (Western European) 852 (MS-DOS Latin 2), 861 (Icelandic), 866 (Cyrillic),
932 (Kanji SJIS), 936 (Simplified Chinese), 949 (Hangul) and 950 (Traditional
Chinese). Users are encouraged to write text codepage definition files for
their own code pages and donate them to samba@samba.org. All codepage files
in the Samba <TT
CLASS="FILENAME"
>source/codepages</TT
> directory are
compiled and installed when a <B
CLASS="COMMAND"
>'make install'</B
>
command is issued there. </P
><P
>The client codepage used by the <B
CLASS="COMMAND"
>smbd</B
> server
is configured using the <B
CLASS="COMMAND"
>client code page</B
> parameter
in the <B
CLASS="COMMAND"
>smb.conf</B
> file. </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN58"
></A
><H2
>Files</H2
><P
><B
CLASS="COMMAND"
>codepage_def.&lt;codepage&gt;</B
></P
><P
>These are the input (text) codepage files provided in the
Samba <TT
CLASS="FILENAME"
>source/codepages</TT
> directory.</P
><P
>A text codepage definition file consists of multiple lines
containing four fields. These fields are:</P
><P
></P
><UL
><LI
><P
><B
CLASS="COMMAND"
>lower</B
>: which is the
(hex) lower case character mapped on this line.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>upper</B
>: which is the (hex)
upper case character that the lower case character will map to.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>map upper to lower</B
> which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given upper case character to the
given lower case character when lower casing a filename.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>map lower to upper</B
> which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given lower case character to the
given upper case character when upper casing a filename.
</P
></LI
></UL
><P
><B
CLASS="COMMAND"
>codepage.&lt;codepage&gt;</B
> - These are the
output (binary) codepage files produced and placed in the Samba
destination <TT
CLASS="FILENAME"
>lib/codepage</TT
> directory. </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN81"
></A
><H2
>Installation</H2
><P
>The location of the server and its support files is a
matter for individual system administrators. The following are
thus suggestions only. </P
><P
>It is recommended that the <B
CLASS="COMMAND"
>make_smbcodepage
</B
> program be installed under the <TT
CLASS="FILENAME"
>/usr/local/samba
</TT
> hierarchy, in a directory readable by all, writeable
only by root. The program itself should be executable by all. The
program should NOT be setuid or setgid! </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN87"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN90"
></A
><H2
>SEE ALSO</H2
><P
><A
HREF="smbd.8.html"
TARGET="_top"
><B
CLASS="COMMAND"
>smbd(8)</B
></A
>,
<A
HREF="smb.conf.5.html"
TARGET="_top"
>smb.conf(5)</A
>
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN96"
></A
><H2
>AUTHOR</H2
><P
>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</P
><P
>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<A
HREF="ftp://ftp.icce.rug.nl/pub/unix/"
TARGET="_top"
> ftp://ftp.icce.rug.nl/pub/unix/</A
>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</P
></DIV
></BODY
></HTML
>

View File

@ -1,91 +1,237 @@
<html><head><title>smbsh (1)</title>
<link rev="made" href="mailto:samba@samba.org">
</head>
<body>
<hr>
<h1>smbsh (1)</h1>
<h2>Samba</h2>
<h2>23 Oct 1998</h2>
<p><a name="NAME"></a>
<h2>NAME</h2>
smbsh - Allows access to Windows NT filesystem using UNIX commands
<p><a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p><strong>smbsh</strong>
<p><a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p>This program is part of the <strong>Samba</strong> suite.
<p><strong>smbsh</strong> allows you to access an NT filesystem using UNIX commands
such as <strong>ls</strong>, <strong>egrep</strong>, and <strong>rcp</strong>. You must use a shell that
is dynmanically linked in order for <strong>smbsh</strong> to work correctly.
<p>To use the <strong>smbsh</strong> command, execute <strong>smbsh</strong> from the prompt and
enter the username and password that authenticate you to the
machine running the Windows NT operating system.
<p><pre>
system% smbsh
Username: user
Password:
</pre>
<p>Any dynamically linked command you execute from this shell will
access the <strong>/smb</strong> directory using the smb protocol.
For example, the command
<p><code>ls /smb</code>
<p>will show all the machines in your workgroup.
The command
<p><code>ls /smb/&lt;machine-name&gt;</code>
<p>will show the share names for that machine. You could then, for example, use the
<strong>cd</strong> command to change directories, <strong>vi</strong> to edit files, and <strong>rcp</strong>
to copy files.
<p><a name="VERSION"></a>
<h2>VERSION</h2>
<p>This man page is correct for the 2.0.3 of the Samba suite.
<p><a name="BUGS"></a>
<h2>BUGS</h2>
<p><strong>smbsh</strong> works by intercepting the standard libc calls with the dynamically loaded
versions in <strong>smbwrapper.o</strong>. Not all calls have been "wrapped" so some programs
may not function correctly under <strong>smbsh</strong>.
<p>Programs which are not dynamically linked cannot make use of <strong>smbsh</strong>'s
functionality. Most versions of UNIX have a <strong>file</strong> command that will describe how
a program was linked.
<p><a name="SEEALSO"></a>
<h2>SEE ALSO</h2>
<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>,
<a href="smbd.8.html"><strong>smbd (8)</strong></a>.
<p><a name="AUTHOR"></a>
<h2>AUTHOR</h2>
<p>The original Samba software and related utilities were created by
Andrew Tridgell (samba@samba.org). Samba is now developed
by the Samba Team as an Open Source project similar to the way the
Linux kernel is developed.
<p>The original Samba man pages were written by Karl Auer. The man page
sources were converted to YODL format (another excellent piece of Open
Source software, available at
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
and updated for the Samba2.0 release by Jeremy Allison.
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
list of contributors and details on how to submit bug reports,
comments etc.
<p></body>
</html>
<HTML
><HEAD
><TITLE
>smbsh</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
>smbsh</A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN5"
></A
><H2
>Name</H2
>smbsh&nbsp;--&nbsp;Allows access to Windows NT filesystem
using UNIX commands</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>smbsh</B
> </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN11"
></A
><H2
>DESCRIPTION</H2
><P
>This tool is part of the <A
HREF="samba.7.html"
TARGET="_top"
> Samba</A
> suite.</P
><P
><B
CLASS="COMMAND"
>smbsh</B
> allows you to access an NT filesystem
using UNIX commands such as <B
CLASS="COMMAND"
>ls</B
>, <B
CLASS="COMMAND"
> egrep</B
>, and <B
CLASS="COMMAND"
>rcp</B
>. You must use a
shell that is dynmanically linked in order for <B
CLASS="COMMAND"
>smbsh</B
>
to work correctly.</P
><P
>To use the <B
CLASS="COMMAND"
>smbsh</B
> command, execute <B
CLASS="COMMAND"
> smbsh</B
> from the prompt and enter the username and password
that authenticate you to the machine running the Windows NT
operating system.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> <TT
CLASS="PROMPT"
>system% </TT
><TT
CLASS="USERINPUT"
><B
>smbsh</B
></TT
>
<TT
CLASS="PROMPT"
>Username: </TT
><TT
CLASS="USERINPUT"
><B
>user</B
></TT
>
<TT
CLASS="PROMPT"
>Password: </TT
><TT
CLASS="USERINPUT"
><B
>XXXXXXX</B
></TT
>
</PRE
></P
><P
>Any dynamically linked command you execute from
this shell will access the <TT
CLASS="FILENAME"
>/smb</TT
> directory
using the smb protocol. For example, the command <B
CLASS="COMMAND"
>ls /smb
</B
> will show all the machines in your workgroup. The command
<B
CLASS="COMMAND"
>ls /smb/&lt;machine-name&gt;</B
> will show the share
names for that machine. You could then, for example, use the <B
CLASS="COMMAND"
> cd</B
> command to change directories, <B
CLASS="COMMAND"
>vi</B
> to
edit files, and <B
CLASS="COMMAND"
>rcp</B
> to copy files.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN39"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN42"
></A
><H2
>BUGS</H2
><P
><B
CLASS="COMMAND"
>smbsh</B
> works by intercepting the standard
libc calls with the dynamically loaded versions in <TT
CLASS="FILENAME"
> smbwrapper.o</TT
>. Not all calls have been "wrapped", so
some programs may not function correctly under <B
CLASS="COMMAND"
>smbsh
</B
>.</P
><P
>Programs which are not dynamically linked cannot make
use of <B
CLASS="COMMAND"
>smbsh</B
>'s functionality. Most versions
of UNIX have a <B
CLASS="COMMAND"
>file</B
> command that will
describe how a program was linked.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN51"
></A
><H2
>SEE ALSO</H2
><P
><A
HREF="smbd.8.html"
TARGET="_top"
><B
CLASS="COMMAND"
>smbd(8)</B
></A
>,
<A
HREF="smb.conf.5.html"
TARGET="_top"
>smb.conf(5)</A
>
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN57"
></A
><H2
>AUTHOR</H2
><P
>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</P
><P
>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<A
HREF="ftp://ftp.icce.rug.nl/pub/unix/"
TARGET="_top"
> ftp://ftp.icce.rug.nl/pub/unix/</A
>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</P
></DIV
></BODY
></HTML
>

View File

@ -1,144 +1,140 @@
.TH "make_smbcodepage " "1" "23 Oct 1998" "Samba" "SAMBA"
.PP
.SH "NAME"
make_codepage \- Construct a codepage file for Samba
.PP
.SH "SYNOPSIS"
.PP
\fBmake_smbcodepage\fP [c|d] codepage inputfile outputfile
.PP
.SH "DESCRIPTION"
.PP
This program is part of the \fBSamba\fP suite\&.
.PP
\fBmake_smbcodepage\fP compiles or de-compiles codepage files for use
with the internationalization features of Samba 2\&.0
.PP
.SH "OPTIONS"
.PP
.IP
.IP "c|d"
This tells \fBmake_smbcodepage\fP if it is compiling (\fBc\fP) a text
format code page file to binary, or (\fBd\fP) de-compiling a binary codepage
file to text\&.
.IP
.IP "codepage"
This is the codepage we are processing (a number, e\&.g\&. 850)\&.
.IP
.IP "inputfile"
This is the input file to process\&. In the \'\fBc\fP\' case this
will be a text codepage definition file such as the ones found in the
Samba \fIsource/codepages\fP directory\&. In the \'\fBd\fP\' case this will be the
binary format codepage definition file normally found in the
\fIlib/codepages\fP directory in the Samba install directory path\&.
.IP
.IP "outputfile"
This is the output file to produce\&.
.IP
.PP
.SH "Samba Codepage Files"
.PP
A text Samba codepage definition file is a description that tells
Samba how to map from upper to lower case for characters greater than
ascii 127 in the specified DOS code page\&. Note that for certain DOS
codepages (437 for example) mapping from lower to upper case may be
non-symmetrical\&. For example, in code page 437 lower case a acute maps to
a plain upper case A when going from lower to upper case, but
plain upper case A maps to plain lower case a when lower casing a
character\&.
.PP
A binary Samba codepage definition file is a binary representation of
the same information, including a value that specifies what codepage
this file is describing\&.
.PP
As Samba does not yet use UNICODE (current for Samba version 2\&.0) you
must specify the client code page that your DOS and Windows clients
are using if you wish to have case insensitivity done correctly for
your particular language\&. The default codepage Samba uses is 850
(Western European)\&. Text codepage definition sample files are
provided in the Samba distribution for codepages 437 (USA), 737
(Greek), 850 (Western European) 852 (MS-DOS Latin 2), 861 (Icelandic),
866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949
(Hangul) and 950 (Traditional Chinese)\&. Users are encouraged to write
text codepage definition files for their own code pages and donate
them to samba@samba\&.org\&. All codepage files in the
Samba \fIsource/codepages\fP directory are compiled and installed when a
\fI\'make install\'\fP command is issued there\&.
.PP
The client codepage used by the \fBsmbd\fP server is
configured using the \fBclient code
page\fP parameter in the
\fBsmb\&.conf\fP file\&.
.PP
.SH "FILES"
.PP
\fBcodepage_def\&.<codepage>\fP
.PP
These are the input (text) codepage files provided in the Samba
\fIsource/codepages\fP directory\&.
.PP
A text codepage definition file consists of multiple lines
containing four fields\&. These fields are :
.PP
.IP
.IP o
\fBlower\fP: which is the (hex) lower case character mapped on this
line\&.
.IP
.IP o
\fBupper\fP: which is the (hex) upper case character that the lower
case character will map to\&.
.IP
.IP o
\fBmap upper to lower\fP which is a boolean value (put either True
or False here) which tells Samba if it is to map the given upper case
character to the given lower case character when lower casing a
filename\&.
.IP
.IP o
\fBmap lower to upper\fP which is a boolean value (put either True
or False here) which tells Samba if it is to map the given lower case
character to the given upper case character when upper casing a
filename\&.
.IP
.PP
\fBcodepage\&.<codepage>\fP These are the output (binary) codepage files
produced and placed in the Samba destination \fIlib/codepage\fP
directory\&.
.PP
.SH "INSTALLATION"
.PP
The location of the server and its support files is a matter for
individual system administrators\&. The following are thus suggestions
only\&.
.PP
It is recommended that the \fBmake_smbcodepage\fP program be installed
under the \fI/usr/local/samba\fP hierarchy, in a directory readable by
all, writeable only by root\&. The program itself should be executable
by all\&. The program should NOT be setuid or setgid!
.PP
.SH "VERSION"
.PP
This man page is correct for version 2\&.0 of the Samba suite\&.
.PP
.SH "SEE ALSO"
.PP
\fBsmb\&.conf(5)\fP, \fBsmbd (8)\fP
.PP
.SH "AUTHOR"
.PP
The original Samba software and related utilities were created by
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
by the Samba Team as an Open Source project similar to the way the
Linux kernel is developed\&.
.PP
The original Samba man pages were written by Karl Auer\&. The man page
sources were converted to YODL format (another excellent piece of Open
Source software, available at
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
and updated for the Samba2\&.0 release by Jeremy Allison\&.
samba@samba\&.org\&.
.PP
See \fBsamba (7)\fP to find out how to get a full
list of contributors and details on how to submit bug reports,
comments etc\&.
.\" This manpage has been automatically generated by docbook2man-spec
.\" from a DocBook document. docbook2man-spec can be found at:
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "MAKE_SMBCODEPAGE" "1" "22 February 2001" "" ""
.SH NAME
make_smbcodepage \- construct a codepage file for Samba
.SH SYNOPSIS
.sp
\fBmake_smbcodepage\fR \fBc|d\fR \fBcodepage\fR \fBinputfile\fR \fBoutputfile\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
.PP
\fBmake_smbcodepage\fR compiles or de-compiles
codepage files for use with the internationalization features
of Samba 2.2
.SH "OPTIONS"
.TP
\fBc|d\fR
This tells \fBmake_smbcodepage\fR
if it is compiling (\fIc\fR) a text format code
page file to binary, or (\fId\fR) de-compiling
a binary codepage file to text.
.TP
\fBcodepage\fR
This is the codepage we are processing (a
number, e.g. 850).
.TP
\fBinputfile\fR
This is the input file to process. In t
he '\fIc\fR' case this will be a text
codepage definition file such as the ones found in the Samba
\fIsource/codepages\fR directory. In
the '\fId\fR' case this will be the
binary format codepage definition file normally found in
the \fIlib/codepages\fR directory in the
Samba install directory path.
.TP
\fBoutputfile\fR
This is the output file to produce.
.SH "SAMBA CODEPAGE FILES"
.PP
A text Samba codepage definition file is a description
that tells Samba how to map from upper to lower case for
characters greater than ascii 127 in the specified DOS code page.
Note that for certain DOS codepages (437 for example) mapping
from lower to upper case may be non-symmetrical. For example, in
code page 437 lower case a acute maps to a plain upper case A
when going from lower to upper case, but plain upper case A maps
to plain lower case a when lower casing a character.
.PP
A binary Samba codepage definition file is a binary
representation of the same information, including a value that
specifies what codepage this file is describing.
.PP
As Samba does not yet use UNICODE (current for Samba version 2.2)
you must specify the client code page that your DOS and Windows
clients are using if you wish to have case insensitivity done
correctly for your particular language. The default codepage Samba
uses is 850 (Western European). Text codepage definition sample files
are provided in the Samba distribution for codepages 437 (USA), 737 (Greek),
850 (Western European) 852 (MS-DOS Latin 2), 861 (Icelandic), 866 (Cyrillic),
932 (Kanji SJIS), 936 (Simplified Chinese), 949 (Hangul) and 950 (Traditional
Chinese). Users are encouraged to write text codepage definition files for
their own code pages and donate them to samba@samba.org. All codepage files
in the Samba \fIsource/codepages\fR directory are
compiled and installed when a \fB'make install'\fR
command is issued there.
.PP
The client codepage used by the \fBsmbd\fR server
is configured using the \fBclient code page\fR parameter
in the \fBsmb.conf\fR file.
.SH "FILES"
.PP
\fBcodepage_def.<codepage>\fR
.PP
These are the input (text) codepage files provided in the
Samba \fIsource/codepages\fR directory.
.PP
A text codepage definition file consists of multiple lines
containing four fields. These fields are:
.TP 0.2i
\(bu
\fBlower\fR: which is the
(hex) lower case character mapped on this line.
.TP 0.2i
\(bu
\fBupper\fR: which is the (hex)
upper case character that the lower case character will map to.
.TP 0.2i
\(bu
\fBmap upper to lower\fR which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given upper case character to the
given lower case character when lower casing a filename.
.TP 0.2i
\(bu
\fBmap lower to upper\fR which
is a boolean value (put either True or False here) which tells
Samba if it is to map the given lower case character to the
given upper case character when upper casing a filename.
.PP
\fBcodepage.<codepage>\fR - These are the
output (binary) codepage files produced and placed in the Samba
destination \fIlib/codepage\fR directory.
.PP
.SH "INSTALLATION"
.PP
The location of the server and its support files is a
matter for individual system administrators. The following are
thus suggestions only.
.PP
It is recommended that the \fBmake_smbcodepage
\fRprogram be installed under the \fI/usr/local/samba
\fRhierarchy, in a directory readable by all, writeable
only by root. The program itself should be executable by all. The
program should NOT be setuid or setgid!
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.
.PP
The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter

View File

@ -1,85 +1,72 @@
.TH SMBSH 1 "26 Apr 2000" "smbsh 2.0.7"
.PP
.SH "NAME"
smbsh \- Allows access to Windows NT filesystem using UNIX commands
.PP
.SH "SYNOPSIS"
.PP
\fBsmbsh\fP
.PP
.SH "DESCRIPTION"
.PP
This program is part of the \fBSamba\fP suite\&.
.PP
\fBsmbsh\fP allows you to access an NT filesystem using UNIX commands
such as \fBls\fP, \fBegrep\fP, and \fBrcp\fP\&. You must use a shell that
is dynmanically linked in order for \fBsmbsh\fP to work correctly\&.
.PP
To use the \fBsmbsh\fP command, execute \fBsmbsh\fP from the prompt and
enter the username and password that authenticate you to the
machine running the Windows NT operating system\&.
.PP
.DS
system% smbsh
Username: user
Password:
.DE
.PP
Any dynamically linked command you execute from this shell will
access the \fB/smb\fP directory using the smb protocol\&.
For example, the command
.PP
\f(CWls /smb\fP
.PP
will show all the machines in your workgroup\&.
The command
.PP
\f(CWls /smb/<machine-name>\fP
.PP
will show the share names for that machine\&. You could then, for example, use the
\fBcd\fP command to change directories, \fBvi\fP to edit files, and \fBrcp\fP
to copy files\&.
.PP
.SH "VERSION"
.PP
This man page is correct for the 2\&.0\&.3 of the Samba suite\&.
.PP
.SH "BUGS"
.PP
\fBsmbsh\fP works by intercepting the standard libc calls with the dynamically loaded
versions in \fBsmbwrapper\&.o\fP\&. Not all calls have been "wrapped" so some programs
may not function correctly under \fBsmbsh\fP\&.
.PP
Programs which are not dynamically linked cannot make use of \fBsmbsh\fP\'s
functionality\&. Most versions of UNIX have a \fBfile\fP command that will describe how
a program was linked\&.
.PP
.SH "SEE ALSO"
.PP
\fBsmb\&.conf (5)\fP,
\fBsmbd (8)\fP\&.
.PP
.SH "AUTHOR"
.PP
The original Samba software and related utilities were created by
Andrew Tridgell (samba@samba\&.org)\&. Samba is now developed
by the Samba Team as an Open Source project similar to the way the
Linux kernel is developed\&.
.PP
The original Samba man pages were written by Karl Auer\&. The man page
sources were converted to YODL format (another excellent piece of Open
Source software, available at
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
and updated for the Samba2\&.0 release by Jeremy Allison\&.
samba@samba\&.org\&.
.PP
See \fBsamba (7)\fP to find out how to get a full
list of contributors and details on how to submit bug reports,
comments etc\&.
.PP
.\" This manpage has been automatically generated by docbook2man-spec
.\" from a DocBook document. docbook2man-spec can be found at:
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBSH" "1" "22 February 2001" "" ""
.SH NAME
smbsh \- Allows access to Windows NT filesystem using UNIX commands
.SH SYNOPSIS
.sp
\fBsmbsh\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
.PP
\fBsmbsh\fR allows you to access an NT filesystem
using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR. You must use a
shell that is dynmanically linked in order for \fBsmbsh\fR
to work correctly.
.PP
To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password
that authenticate you to the machine running the Windows NT
operating system.
.PP
.sp
.nf
system% \fBsmbsh\fR
Username: \fBuser\fR
Password: \fBXXXXXXX\fR
.sp
.fi
.PP
Any dynamically linked command you execute from
this shell will access the \fI/smb\fR directory
using the smb protocol. For example, the command \fBls /smb
\fRwill show all the machines in your workgroup. The command
\fBls /smb/<machine-name>\fR will show the share
names for that machine. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to
edit files, and \fBrcp\fR to copy files.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
the Samba suite.
.SH "BUGS"
.PP
\fBsmbsh\fR works by intercepting the standard
libc calls with the dynamically loaded versions in \fI smbwrapper.o\fR. Not all calls have been "wrapped", so
some programs may not function correctly under \fBsmbsh
\fR\&.
.PP
Programs which are not dynamically linked cannot make
use of \fBsmbsh\fR's functionality. Most versions
of UNIX have a \fBfile\fR command that will
describe how a program was linked.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.
.PP
The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter