mirror of
https://github.com/samba-team/samba.git
synced 2024-12-25 23:21:54 +03:00
parent
907b568c8d
commit
65bd1e3775
@ -401,19 +401,16 @@
|
||||
|
||||
<smbconfexample id="sbent4smb">
|
||||
<title>NT4 Migration Samba-3 Server <filename>smb.conf</filename> &smbmdash; Part: A</title>
|
||||
<smbconfcomment>Global parameters</smbconfcomment>
|
||||
<smbconfsection name="[global]"/>
|
||||
<smbconfoption name="workgroup">DAMNATION</smbconfoption>
|
||||
<smbconfoption name="netbios name">MERLIN</smbconfoption>
|
||||
<smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
|
||||
<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
|
||||
<smbconfoption name="log level">1</smbconfoption>
|
||||
<smbconfoption name="syslog">0</smbconfoption>
|
||||
<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
|
||||
<smbconfoption name="max log size">0</smbconfoption>
|
||||
<smbconfoption name="smb ports">139 445</smbconfoption>
|
||||
<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
|
||||
<smbconfoption name="show add printer wizard">Yes</smbconfoption>
|
||||
<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m '%u'</smbconfoption>
|
||||
<smbconfoption name="#delete user script">/opt/IDEALX/sbin/smbldap-userdel '%u'</smbconfoption>
|
||||
<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd '%g'</smbconfoption>
|
||||
|
@ -2255,7 +2255,8 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
|
||||
Now install all four printers onto the staging system. The printers you install
|
||||
include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers. You will
|
||||
also configure identical printers that are located in the financial services department.
|
||||
Install printers on each machine using the steps shown in <link linkend="sbewinclntptrprep"/>.
|
||||
Install printers on each machine following the steps shown in the Windows client printer
|
||||
preparation procedure below.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
|
@ -4,102 +4,86 @@
|
||||
<preface lang="en-US">
|
||||
<title>Foreword</title>
|
||||
|
||||
<sect1><title>By Dan Kusnetzky, IDC</title>
|
||||
<sect1><title>By John Weathersby, OSSI</title>
|
||||
<blockquote>
|
||||
<attribution>
|
||||
Dan Kusnetzky, Vice President System Software Research, International Data Corporation
|
||||
Executive Director, Open Source Software Institute
|
||||
</attribution>
|
||||
|
||||
<para>
|
||||
IDC's software research group has been conducting research on the market for software,
|
||||
including operating environments, for over twenty years. In 1994, the system software
|
||||
research team started to field questions from its subscribers on Linux. We had very
|
||||
little empirical data to offer when these queries first were heard, so IDC added Linux
|
||||
to its operating environment research agenda. The first demand and supply side research
|
||||
containing IDC's findings on Linux started to appear in early 1995.
|
||||
The Open Source Software Institute (OSSI) is comprised of representatives from a broad spectrum of business and
|
||||
non-business organizations that share a common interest in the promotion of development and implementation
|
||||
of open-source software solutions globally, and in particular within the United States of America.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
IDC has watched as Linux marched from being software for computer hobbyists to being
|
||||
a mainstream choice in many markets worldwide. This march is very similar to the adoption
|
||||
cycle UNIX experienced in the 1970s and 1980s. Windows repeated this pattern of adoption
|
||||
during the 1980s and 1990s. IDC has long projected that Linux would be a mainstream
|
||||
choice in nearly all markets by the end of 2005. The software is well down that path
|
||||
now and just might beat IDC's projections.
|
||||
The OSSI has global affiliations with like-minded organizations. Our affiliate in the United Kingdom is the
|
||||
Open Source Consortium. Both the OSSI and the OSC share a common objective to expand the use of open-source
|
||||
software in federal, state and municipal government agencies and in academic institutions. We represent
|
||||
businesses that provide professional support services that answer the needs of our target organizational
|
||||
information technology consumers in an effective and cost efficient manner.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
As of the end of 2002, Linux was the number three desktop or client operating environment,
|
||||
responsible for nearly 3% of the worldwide shipments of client operating environment
|
||||
software. Linux was the number two server operating environment, responsible for nearly
|
||||
25% of the worldwide shipments of server operating environment software. This is an amazing
|
||||
level of growth from its rather humble beginnings of holding less than 1% share of either
|
||||
client or server operating environment market when IDC first started publishing its findings
|
||||
on Linux.
|
||||
Open source software has matured greatly over the past 5 years with the result that an increasing number of
|
||||
people who hold key influential decision-making positions want to know how the business model works. They
|
||||
want to understand how problems get resolved, how questions get answered, and how the development model
|
||||
is sustained. Information and Communications Technology directors in defense organizations, and in other
|
||||
government agencies that deal with sensitive information, want to become familiar with development roadmaps
|
||||
and, in particular, seek to evaluate the track record of the main-stream open-source project teams.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
IDC's demand-side studies have indicated that Linux is most often utilized as a platform
|
||||
for basic infrastructure services, such as supporting access to shared files and printers
|
||||
or supporting basic networking functions. IDC's most recent survey, conducted in late 2003,
|
||||
indicated that supporting file and print services was the most common use of Linux. Samba
|
||||
and NFS are the most commonly mentioned approaches to offering file and print services on
|
||||
Linux.
|
||||
Wherever the OSSI gains entrance to new opportunities we find that Microsoft Windows technologies are the
|
||||
benchmark against which open-source software solutions are measured. Two open-source software projects
|
||||
are key to our ability to present a structured, and convincing, proposition that there are alternatives
|
||||
to the incumbent proprietary means of meeting information technology needs. They are the Apache Web server
|
||||
and Samba.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Nearly all of IDC's operating environment studies have shown that Linux is being added
|
||||
into organizational networks that already include Windows, UNIX, and mainframe operating
|
||||
environments. This, of course, means that interoperability with these operating environments
|
||||
is a crucial success factor for Linux.
|
||||
Just as the Apache web server is the standard in web serving technology, Samba is the definitive standard
|
||||
for providing inter-operability with UNIX systems and other non-Microsoft operating system platforms. Both
|
||||
open-source applications have a truly remarkable track record that extends well over a decade. Both have
|
||||
demonstrated unique capacity to innovate and to maintain a level of development that has not only kept
|
||||
pace with demands, but in many areas each project has also proven to be an industry leader.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
All of this leads to the book in hand, <emphasis>Samba-3 By Example</emphasis>, by John H. Terpstra, It addresses
|
||||
the most commonly heard questions about bringing Linux and Samba into a Windows or UNIX
|
||||
focused environment. Namely, organizations voice concerns about staff having sufficient
|
||||
levels of expertise to facilitate development, administration, operations and support activities
|
||||
around the adoption of Linux and Samba. I expect <emphasis>Samba-3</emphasis> by Example will be of enormous help
|
||||
to Windows or UNIX administrators hoping to gain a level of comfort and familiarity with both
|
||||
Linux and Samba.
|
||||
One of the areas in which the Samba project has demonstrated key leadership is in documentation. The OSSI
|
||||
was delighted when we saw the Samba Team, and John H. Terpstra in particular, release two amzingly well
|
||||
written books to help Samba software users to deploy, maintain and trouble-shoot Windows networking
|
||||
installations. We were concerned that, given the large volume of documentation, the challenge to maintain
|
||||
it and keep it current might prove difficult.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Samba is a mature open source software product that is well established as a leading Windows
|
||||
file and print technology in use on large-scale UNIX systems. Its stability and scalability
|
||||
appears to be well respected. This book demonstrates easy approaches to implementing Samba-3
|
||||
no matter whether your network is large or small. It is a book that would make a fine addition
|
||||
to the network administrators' library!
|
||||
</para>
|
||||
</blockquote>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>By Andrew Tridgell, Samba Team</title>
|
||||
|
||||
<blockquote><attribution>
|
||||
Andrew Tridgell, President, Samba Team
|
||||
</attribution>
|
||||
|
||||
<para>
|
||||
I've always been the sort of computer user that learns best by
|
||||
example. Seeing a complete example matching a real-world use of a
|
||||
piece of software gives me an understanding of that software far
|
||||
better than reading detailed manuals. If, like me, you are the sort of
|
||||
computer user that learns best by example then this book is for you.
|
||||
This second edition of the book, <quote>Samba-3 by Example</quote> barely one year following the release
|
||||
of the first edition has removed all concerns and is proof that open-source solutiosn are a compelling choice.
|
||||
The first edition was released shortly following the release of Samba version 3.0 itself, and has become
|
||||
the authorative instrument for training and for guiding deployment.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
I was also delighted to see the use of ethereal to illustrate the
|
||||
network protocols used by Samba. Ethereal has developed into a very
|
||||
sophisticated network analysis tool, and familiarity with using
|
||||
ethereal is a very useful skill for any system administrator.
|
||||
I am personally aware how much effort has gone into this second edition. John Terpstra has worked with
|
||||
government bodies and with large organizations that have deployed Samba-3 since it was released. He also
|
||||
worked to ensure that this book gained community following. He asking those who have worked at the coal-face
|
||||
of large and small organizations alike, to contribute their experiences. He has captured that in this book
|
||||
and has succeeded yet again. His recipe is persistence, intuition, and a high level of respect for the people
|
||||
who use Samba.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Enjoy this book, and make the most of Samba!
|
||||
This book is the first source you should turn to before you deploy Samba and as you are mastering its
|
||||
deployment. I am proud and excited to be associated in a small way with such a useful tool. This book has
|
||||
reached maturity that is demonstrated by reiteration that at every step in deployment must be validated.
|
||||
This book makes it easy to succeed, and dificutly to fail to gain a stable working network environment.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
I recommend this book for use by all IT managers and network administrators.
|
||||
</para>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</sect1>
|
||||
|
Loading…
Reference in New Issue
Block a user