From b968848a1697dfc7216e1802883b5f7e55025111 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Tue, 9 Sep 2003 03:11:56 +0000 Subject: removing files not in 3.0 (This used to be commit d5c32f8881f33667c9bfa067cb7f2113bd55c724) --- docs/announce | 153 -- docs/docbook/faq/config.xml | 37 - docs/docbook/faq/printing.xml | 38 - docs/docbook/manpages/profiles.1.sgml | 86 - docs/docbook/smbdotconf/base/adsserver.xml | 15 - docs/docbook/smbdotconf/expand-smb.conf.xsl | 87 - docs/docbook/smbdotconf/ldap/ldaptrustids.xml | 23 - .../docbook/smbdotconf/printing/totalprintjobs.xml | 22 - .../smbdotconf/security/nonunixaccountrange.xml | 25 - docs/docbook/smbdotconf/smb.conf.5.xml | 14 +- docs/docbook/smbdotconf/tuning/statcachesize.xml | 12 - docs/docbook/smbdotconf/vfs/vfsoptions.xml | 12 - docs/docbook/smbdotconf/vfs/vfspath.xml | 13 - docs/docbook/xslt/db2latex/VERSION.xml | 21 - docs/docbook/xslt/db2latex/abstract.mod.xsl | 92 - docs/docbook/xslt/db2latex/admonition.mod.xsl | 222 -- docs/docbook/xslt/db2latex/authorgroup.mod.xsl | 78 - docs/docbook/xslt/db2latex/biblio.mod.xsl | 605 ----- docs/docbook/xslt/db2latex/block.mod.xsl | 174 -- docs/docbook/xslt/db2latex/book-article.mod.xsl | 540 ---- docs/docbook/xslt/db2latex/bridgehead.mod.xsl | 71 - docs/docbook/xslt/db2latex/callout.mod.xsl | 61 - docs/docbook/xslt/db2latex/citation.mod.xsl | 63 - docs/docbook/xslt/db2latex/common/ca.xml | 100 - docs/docbook/xslt/db2latex/common/common.xsl | 1927 -------------- docs/docbook/xslt/db2latex/common/cs.xml | 110 - docs/docbook/xslt/db2latex/common/da.xml | 98 - docs/docbook/xslt/db2latex/common/de.xml | 102 - docs/docbook/xslt/db2latex/common/el.xml | 104 - docs/docbook/xslt/db2latex/common/en.xml | 107 - docs/docbook/xslt/db2latex/common/es.xml | 98 - docs/docbook/xslt/db2latex/common/et.xml | 104 - docs/docbook/xslt/db2latex/common/fi.xml | 98 - docs/docbook/xslt/db2latex/common/fr.xml | 114 - docs/docbook/xslt/db2latex/common/hu.xml | 94 - docs/docbook/xslt/db2latex/common/id.xml | 104 - docs/docbook/xslt/db2latex/common/it.xml | 103 - docs/docbook/xslt/db2latex/common/ja.xml | 104 - docs/docbook/xslt/db2latex/common/ko.xml | 96 - docs/docbook/xslt/db2latex/common/l10n.dtd | 25 - docs/docbook/xslt/db2latex/common/l10n.xml | 59 - docs/docbook/xslt/db2latex/common/l10n.xsl | 248 -- docs/docbook/xslt/db2latex/common/nl.xml | 105 - docs/docbook/xslt/db2latex/common/no.xml | 97 - docs/docbook/xslt/db2latex/common/pl.xml | 96 - docs/docbook/xslt/db2latex/common/pt.xml | 98 - docs/docbook/xslt/db2latex/common/pt_br.xml | 98 - docs/docbook/xslt/db2latex/common/ro.xml | 104 - docs/docbook/xslt/db2latex/common/ru.xml | 113 - docs/docbook/xslt/db2latex/common/sk.xml | 104 - docs/docbook/xslt/db2latex/common/sl.xml | 104 - docs/docbook/xslt/db2latex/common/sv.xml | 99 - docs/docbook/xslt/db2latex/common/zh_cn.xml | 95 - docs/docbook/xslt/db2latex/common/zh_tw.xml | 98 - docs/docbook/xslt/db2latex/component.mod.xsl | 91 - docs/docbook/xslt/db2latex/dedication.mod.xsl | 126 - docs/docbook/xslt/db2latex/dingbat.mod.xsl | 69 - docs/docbook/xslt/db2latex/docbook.xsl | 149 -- docs/docbook/xslt/db2latex/email.mod.xsl | 62 - docs/docbook/xslt/db2latex/errors.mod.xsl | 16 - docs/docbook/xslt/db2latex/example.mod.xsl | 76 - docs/docbook/xslt/db2latex/figure.mod.xsl | 127 - docs/docbook/xslt/db2latex/font.mod.xsl | 55 - docs/docbook/xslt/db2latex/footnote.mod.xsl | 82 - docs/docbook/xslt/db2latex/formal.mod.xsl | 173 -- docs/docbook/xslt/db2latex/glossary.mod.xsl | 218 -- docs/docbook/xslt/db2latex/graphic.mod.xsl | 87 - docs/docbook/xslt/db2latex/html.mod.xsl | 15 - docs/docbook/xslt/db2latex/index.mod.xsl | 213 -- docs/docbook/xslt/db2latex/info.mod.xsl | 66 - docs/docbook/xslt/db2latex/inline.mod.xsl | 523 ---- docs/docbook/xslt/db2latex/keywords.mod.xsl | 59 - docs/docbook/xslt/db2latex/labelid.mod.xsl | 476 ---- docs/docbook/xslt/db2latex/latex.mapping.dtd | 13 - docs/docbook/xslt/db2latex/latex.mapping.xml | 290 -- docs/docbook/xslt/db2latex/latex.mapping.xsl | 174 -- docs/docbook/xslt/db2latex/lists.mod.xsl | 452 ---- docs/docbook/xslt/db2latex/mathelem.mod.xsl | 222 -- docs/docbook/xslt/db2latex/mathml/ent/isoamsa.ent | 173 -- docs/docbook/xslt/db2latex/mathml/ent/isoamsb.ent | 146 -- docs/docbook/xslt/db2latex/mathml/ent/isoamsc.ent | 49 - docs/docbook/xslt/db2latex/mathml/ent/isoamsn.ent | 117 - docs/docbook/xslt/db2latex/mathml/ent/isoamso.ent | 77 - docs/docbook/xslt/db2latex/mathml/ent/isoamsr.ent | 205 -- docs/docbook/xslt/db2latex/mathml/ent/isobox.ent | 67 - docs/docbook/xslt/db2latex/mathml/ent/isocyr1.ent | 94 - docs/docbook/xslt/db2latex/mathml/ent/isocyr2.ent | 53 - docs/docbook/xslt/db2latex/mathml/ent/isodia.ent | 41 - docs/docbook/xslt/db2latex/mathml/ent/isogrk1.ent | 75 - docs/docbook/xslt/db2latex/mathml/ent/isogrk2.ent | 46 - docs/docbook/xslt/db2latex/mathml/ent/isogrk3.ent | 70 - docs/docbook/xslt/db2latex/mathml/ent/isogrk4.ent | 69 - docs/docbook/xslt/db2latex/mathml/ent/isolat1.ent | 89 - docs/docbook/xslt/db2latex/mathml/ent/isolat2.ent | 148 -- docs/docbook/xslt/db2latex/mathml/ent/isomfrk.ent | 79 - docs/docbook/xslt/db2latex/mathml/ent/isomopf.ent | 53 - docs/docbook/xslt/db2latex/mathml/ent/isomscr.ent | 79 - docs/docbook/xslt/db2latex/mathml/ent/isonum.ent | 103 - docs/docbook/xslt/db2latex/mathml/ent/isopub.ent | 111 - docs/docbook/xslt/db2latex/mathml/ent/isotech.ent | 183 -- docs/docbook/xslt/db2latex/mathml/ent/mmlalias.ent | 529 ---- docs/docbook/xslt/db2latex/mathml/ent/mmlextra.ent | 134 - .../xslt/db2latex/mathml/latex.entities.dtd | 7 - .../xslt/db2latex/mathml/latex.entities.xml | 12 - .../mathml/mathml.content.constsymb.mod.xsl | 99 - .../mathml/mathml.content.functions.mod.xsl | 723 ----- .../xslt/db2latex/mathml/mathml.content.mod.xsl | 97 - .../db2latex/mathml/mathml.content.token.mod.xsl | 230 -- docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl | 49 - .../db2latex/mathml/mathml.presentation.mod.xsl | 491 ---- docs/docbook/xslt/db2latex/mediaobject.mod.xsl | 224 -- docs/docbook/xslt/db2latex/msgset.mod.xsl | 76 - docs/docbook/xslt/db2latex/normalize-scape.mod.xsl | 398 --- docs/docbook/xslt/db2latex/para.mod.xsl | 74 - docs/docbook/xslt/db2latex/part-chap-app.mod.xsl | 132 - docs/docbook/xslt/db2latex/pi.mod.xsl | 181 -- docs/docbook/xslt/db2latex/preamble.mod.xsl | 810 ------ docs/docbook/xslt/db2latex/preface.mod.xsl | 109 - docs/docbook/xslt/db2latex/procedure.mod.xsl | 162 -- docs/docbook/xslt/db2latex/qandaset.mod.xsl | 406 --- docs/docbook/xslt/db2latex/refentry.mod.xsl | 184 -- docs/docbook/xslt/db2latex/revision.mod.xsl | 215 -- docs/docbook/xslt/db2latex/sections.mod.xsl | 147 -- docs/docbook/xslt/db2latex/set.mod.xsl | 50 - docs/docbook/xslt/db2latex/sgmltag.mod.xsl | 154 -- docs/docbook/xslt/db2latex/synop-oop.mod.xsl | 689 ----- docs/docbook/xslt/db2latex/synop-struct.mod.xsl | 246 -- docs/docbook/xslt/db2latex/table.mod.xsl | 743 ------ docs/docbook/xslt/db2latex/texmath.mod.xsl | 117 - docs/docbook/xslt/db2latex/vars.mod.xsl | 937 ------- docs/docbook/xslt/db2latex/verbatim.mod.xsl | 144 - docs/docbook/xslt/db2latex/xref.mod.xsl | 657 ----- docs/faq/FAQ-Config.html | 16 - docs/faq/FAQ-Printing.html | 16 - docs/htmldocs/ads.html | 467 ---- docs/htmldocs/advancednetworkmanagement.html | 555 ---- docs/htmldocs/appendixes.html | 140 - docs/htmldocs/browsing-quick.html | 805 ------ docs/htmldocs/cups-printing.html | 2773 -------------------- docs/htmldocs/domain-security.html | 427 --- docs/htmldocs/groupprofiles.html | 568 ---- docs/htmldocs/improved-browsing.html | 1094 -------- docs/htmldocs/index.html | 76 - docs/htmldocs/interdomaintrusts.html | 451 ---- docs/htmldocs/introsmb.html | 659 ----- docs/htmldocs/nt4migration.html | 356 --- docs/htmldocs/other-clients.html | 734 ------ docs/htmldocs/policymgmt.html | 758 ------ docs/htmldocs/portability.html | 418 --- docs/htmldocs/profilemgmt.html | 1753 ------------- docs/htmldocs/samba-howto-collection.html | 1394 ---------- docs/htmldocs/securitylevels.html | 212 -- docs/htmldocs/servertype.html | 368 --- docs/htmldocs/swat.html | 233 -- docs/htmldocs/unix-permissions.html | 194 -- docs/htmldocs/vfs.html | 490 ---- docs/textdocs/README.NOW | 6 - docs/textdocs/README.jis | 149 -- 158 files changed, 6 insertions(+), 37763 deletions(-) delete mode 100644 docs/announce delete mode 100644 docs/docbook/faq/config.xml delete mode 100644 docs/docbook/faq/printing.xml delete mode 100644 docs/docbook/manpages/profiles.1.sgml delete mode 100644 docs/docbook/smbdotconf/base/adsserver.xml delete mode 100644 docs/docbook/smbdotconf/expand-smb.conf.xsl delete mode 100644 docs/docbook/smbdotconf/ldap/ldaptrustids.xml delete mode 100644 docs/docbook/smbdotconf/printing/totalprintjobs.xml delete mode 100644 docs/docbook/smbdotconf/security/nonunixaccountrange.xml delete mode 100644 docs/docbook/smbdotconf/tuning/statcachesize.xml delete mode 100644 docs/docbook/smbdotconf/vfs/vfsoptions.xml delete mode 100644 docs/docbook/smbdotconf/vfs/vfspath.xml delete mode 100644 docs/docbook/xslt/db2latex/VERSION.xml delete mode 100644 docs/docbook/xslt/db2latex/abstract.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/admonition.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/authorgroup.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/biblio.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/block.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/book-article.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/bridgehead.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/callout.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/citation.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/common/ca.xml delete mode 100644 docs/docbook/xslt/db2latex/common/common.xsl delete mode 100644 docs/docbook/xslt/db2latex/common/cs.xml delete mode 100644 docs/docbook/xslt/db2latex/common/da.xml delete mode 100644 docs/docbook/xslt/db2latex/common/de.xml delete mode 100644 docs/docbook/xslt/db2latex/common/el.xml delete mode 100644 docs/docbook/xslt/db2latex/common/en.xml delete mode 100644 docs/docbook/xslt/db2latex/common/es.xml delete mode 100644 docs/docbook/xslt/db2latex/common/et.xml delete mode 100644 docs/docbook/xslt/db2latex/common/fi.xml delete mode 100644 docs/docbook/xslt/db2latex/common/fr.xml delete mode 100644 docs/docbook/xslt/db2latex/common/hu.xml delete mode 100644 docs/docbook/xslt/db2latex/common/id.xml delete mode 100644 docs/docbook/xslt/db2latex/common/it.xml delete mode 100644 docs/docbook/xslt/db2latex/common/ja.xml delete mode 100644 docs/docbook/xslt/db2latex/common/ko.xml delete mode 100644 docs/docbook/xslt/db2latex/common/l10n.dtd delete mode 100644 docs/docbook/xslt/db2latex/common/l10n.xml delete mode 100644 docs/docbook/xslt/db2latex/common/l10n.xsl delete mode 100644 docs/docbook/xslt/db2latex/common/nl.xml delete mode 100644 docs/docbook/xslt/db2latex/common/no.xml delete mode 100644 docs/docbook/xslt/db2latex/common/pl.xml delete mode 100644 docs/docbook/xslt/db2latex/common/pt.xml delete mode 100644 docs/docbook/xslt/db2latex/common/pt_br.xml delete mode 100644 docs/docbook/xslt/db2latex/common/ro.xml delete mode 100644 docs/docbook/xslt/db2latex/common/ru.xml delete mode 100644 docs/docbook/xslt/db2latex/common/sk.xml delete mode 100644 docs/docbook/xslt/db2latex/common/sl.xml delete mode 100644 docs/docbook/xslt/db2latex/common/sv.xml delete mode 100644 docs/docbook/xslt/db2latex/common/zh_cn.xml delete mode 100644 docs/docbook/xslt/db2latex/common/zh_tw.xml delete mode 100644 docs/docbook/xslt/db2latex/component.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/dedication.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/dingbat.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/docbook.xsl delete mode 100644 docs/docbook/xslt/db2latex/email.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/errors.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/example.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/figure.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/font.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/footnote.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/formal.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/glossary.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/graphic.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/html.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/index.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/info.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/inline.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/keywords.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/labelid.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/latex.mapping.dtd delete mode 100644 docs/docbook/xslt/db2latex/latex.mapping.xml delete mode 100644 docs/docbook/xslt/db2latex/latex.mapping.xsl delete mode 100644 docs/docbook/xslt/db2latex/lists.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathelem.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamsa.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamsb.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamsc.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamsn.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamso.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isoamsr.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isobox.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isocyr1.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isocyr2.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isodia.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isogrk1.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isogrk2.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isogrk3.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isogrk4.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isolat1.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isolat2.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isomfrk.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isomopf.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isomscr.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isonum.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isopub.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/isotech.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/mmlalias.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/ent/mmlextra.ent delete mode 100644 docs/docbook/xslt/db2latex/mathml/latex.entities.dtd delete mode 100644 docs/docbook/xslt/db2latex/mathml/latex.entities.xml delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/mediaobject.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/msgset.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/normalize-scape.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/para.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/part-chap-app.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/pi.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/preamble.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/preface.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/procedure.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/qandaset.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/refentry.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/revision.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/sections.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/set.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/sgmltag.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/synop-oop.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/synop-struct.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/table.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/texmath.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/vars.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/verbatim.mod.xsl delete mode 100644 docs/docbook/xslt/db2latex/xref.mod.xsl delete mode 100644 docs/faq/FAQ-Config.html delete mode 100644 docs/faq/FAQ-Printing.html delete mode 100644 docs/htmldocs/ads.html delete mode 100644 docs/htmldocs/advancednetworkmanagement.html delete mode 100644 docs/htmldocs/appendixes.html delete mode 100644 docs/htmldocs/browsing-quick.html delete mode 100644 docs/htmldocs/cups-printing.html delete mode 100644 docs/htmldocs/domain-security.html delete mode 100644 docs/htmldocs/groupprofiles.html delete mode 100644 docs/htmldocs/improved-browsing.html delete mode 100755 docs/htmldocs/index.html delete mode 100644 docs/htmldocs/interdomaintrusts.html delete mode 100644 docs/htmldocs/introsmb.html delete mode 100644 docs/htmldocs/nt4migration.html delete mode 100644 docs/htmldocs/other-clients.html delete mode 100644 docs/htmldocs/policymgmt.html delete mode 100644 docs/htmldocs/portability.html delete mode 100644 docs/htmldocs/profilemgmt.html delete mode 100644 docs/htmldocs/samba-howto-collection.html delete mode 100644 docs/htmldocs/securitylevels.html delete mode 100644 docs/htmldocs/servertype.html delete mode 100644 docs/htmldocs/swat.html delete mode 100644 docs/htmldocs/unix-permissions.html delete mode 100644 docs/htmldocs/vfs.html delete mode 100644 docs/textdocs/README.NOW delete mode 100644 docs/textdocs/README.jis diff --git a/docs/announce b/docs/announce deleted file mode 100644 index 7310bdd737..0000000000 --- a/docs/announce +++ /dev/null @@ -1,153 +0,0 @@ -This document is out of date - - - Announcing Samba version 2.2 - ============================ - -What is Samba? --------------- - -Samba is a SMB file server that runs on Unix and other operating -systems. It allows these operating systems (currently Unix, Netware, -OS/2 and AmigaDOS) to act as a file and print server for SMB and CIFS -clients. There are many Lan-Manager compatible clients such as -LanManager for DOS, Windows for Workgroups, Windows NT, Windows 95, -Linux smbfs, OS/2, Pathworks and more. - -The package also includes a SMB client for accessing other SMB servers, -and an advanced netbios/WINS nameserver for browsing support. - - -What can it do for me? ----------------------- - -If you have any PCs running SMB clients, such as a PC running Windows -for Workgroups, then you can mount file space or printers on a Samba -host, so that directories, files and printers on the host are -available on the PC. - -If you have any SMB servers such as Windows NT Server, Warp Server or -Pathworks you may be able to replace them by or supplement them with -Samba. One of Samba's big strengths is integration, so you can use it -to tie together your Unix (or VMS etc) hosts and PC clients. If you -are tired of the insecurity, expense and instability of PCNFS then Samba -may be for you. - -The client part of the package will also allow you to attach to other -SMB-based servers (such as windows NT and windows for workgroups) so -that you can copy files to and from your unix host. The client also -allows you to access a SMB printer (such as one attached to an OS/2 or -WfWg server) from Unix, using an entry in /etc/printcap, or by -explicitly specifying the command used to print files. - - -What are its features? ------------------------- - -Samba supports many features that are not supported in other SMB -implementations (all of which are commercial). These include host as -well as username/password security, a client, automatic home directory -exporting, automatic printer exporting, dead connection timeouts, -umask support, guest connections, name mangling and hidden and system -attribute mapping. Look at the FAQs included with the package for -a full list of features. - - -What's new since 2.0? ---------------------- - -Lots of stuff. See the change log and man pages for details. -In particular, please check the WHATSNEW.txt file in the root directory -of each release. This file has current change/update information. - - -Where can I get a client for my PC? ------------------------------------ - -There is a free client for MS-DOS based PCs available from -ftp.microsoft.com in the directory bussys/Clients/MSCLIENT/. Please -read the licencing information before downloading. The add-on 32-bit -TCP/IP Windows for Workgroups client is also very good. Windows 95/98/ME, -Windows NT/2000 and OS/2 come with suitable clients by default. - - -What network protocols are supported? -------------------------------------- - -Currently only TCP/IP is supported. There has been some discussion -about ports to other protocols but nothing is yet available. - -There is a free TCP/IP implementation for Windows for Workgroups -available from ftp.microsoft.com (it's small, fast and quite reliable). - - -How much does it cost? ----------------------- - -Samba software is free software. It is available under the -GNU Public licence in source code form at no cost. Please read the -file COPYING that comes with the package for more information. - - -What operating systems does it support? ---------------------------------------- - -The code has been written to be as portable as possible. It has been -"ported" to many unixes, which mostly required changing only a few -lines of code. It has been run (to my knowledge) on at least these -unixes: - -Linux, SunOS, Solaris, SVR4, Ultrix, OSF1, AIX, BSDI, NetBSD, -Sequent, HP-UX, SGI, FreeBSD, NeXT, ISC, A/UX, SCO, Intergraph, -Silicon Graphics Inc., Domain/OS and DGUX. - -Some of these have received more testing than others. If it doesn't -work with your unix then it should be easy to fix. It has also been ported -to Netware, OS/2 and the Amiga. A VMS port is available too. See the web site -for more details. - - -Who wrote it? -------------- - -Many people on the internet have contributed to the development of -Samba. The maintainer and original author is Andrew Tridgell, but -large parts of the package were contributed by several people from all -over the world. Please look at the file `change-log' for information -on who did what bits. - - -Where can I get it? -------------------- - -The package is available via anonymous ftp from samba.org in -the directory pub/samba/. - - -What about SMBServer? ---------------------- - -Samba used to be known as SMBServer, until it was pointed out that -Syntax, who make a commercial Unix SMB based server, have trademarked -that name. The name was then changed to Samba. Also, in 1992 a very -early incarnation of Samba was distributed as nbserver. - -If you see any copies of nbserver or smbserver on ftp sites please let -me or the ftp archive maintainer know, as I want to get them deleted. - - -Where can I get more info? ---------------------------- - -Please join the mailing list if you want to discuss the development or -use of Samba. To join the mailing list, please read the instructions -at http://lists.samba.org/ - -There is also often quite a bit of discussion about Samba on the -newsgroup comp.protocols.smb. - -A WWW site with lots of Samba info can be found at -http://samba.org/samba/ - -The Samba Team (Contact: samba@samba.org) -March 2001 diff --git a/docs/docbook/faq/config.xml b/docs/docbook/faq/config.xml deleted file mode 100644 index 2c17c86c4e..0000000000 --- a/docs/docbook/faq/config.xml +++ /dev/null @@ -1,37 +0,0 @@ - -Configuration problems - - -I have set 'force user' and samba still makes 'root' the owner of all the files I touch! - -When you have a user in 'admin users', samba will always do file operations for -this user as 'root', even if 'force user' has been set. - - - - -I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins! - - -Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these -passwords to the unix password database, so it needs it's own user database. You can -add users to this database using "smbpasswd -a user-name". - - - -See also the "User database" chapter of the samba HOWTO Collection. - - - - -How can I make samba use netbios scope ID's - -By default Samba uses a blank scope ID. This means -all your windows boxes must also have a blank scope ID. -If you really want to use a non-blank scope ID then you will -need to use the 'netbios scope' smb.conf option. -All your PCs will need to have the same setting for -this to work. Scope ID's are not recommended. - - - diff --git a/docs/docbook/faq/printing.xml b/docs/docbook/faq/printing.xml deleted file mode 100644 index be2acbd905..0000000000 --- a/docs/docbook/faq/printing.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - - - RonanWaide - - - -Printing problems - - -setdriver or cupsaddsmb failes - -setdriver expects the following setup: - - -you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code. -printer admins has to be defined in [global] -upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories. -Make sure that the user you're connecting as is able to write to the print$ directories -Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out) -Use setdriver to associate the driver with a printer - - - - -The setdriver call will fail if the printer doesn't already exist in -samba's view of the world. Either create the printer in cups and -restart samba, or create an add printer command (see smb.conf doco) -and use RPC calls to create a printer. NB the add printer command MUST -return a single line of text indicating which port the printer was -added on. If it doesn't, Samba won't reload the printer -definitions. Although samba doesn't really support the notion of -ports, suitable add printer command and enumport command settings can -allow you pretty good remote control of the samba printer setup. - - - diff --git a/docs/docbook/manpages/profiles.1.sgml b/docs/docbook/manpages/profiles.1.sgml deleted file mode 100644 index 6fd2b6fd86..0000000000 --- a/docs/docbook/manpages/profiles.1.sgml +++ /dev/null @@ -1,86 +0,0 @@ - %globalentities; -]> - - - - profiles - 1 - - - - - profiles - A utility to report and change SIDs in registry files - - - - - - profiles - -v - -c SID - -n SID - file - - - - - DESCRIPTION - - This tool is part of the Samba - 7 suite. - - profiles is a utility that - reports and changes SIDs in windows registry files. It currently only - supports NT. - - - - - - OPTIONS - - - - file - Registry file to view or edit. - - - - - -v,--verbose - Increases verbosity of messages. - - - - - -c SID1 -n SID2 - Change all occurences of SID1 in file by SID2. - - - - &stdarg.help; - - - - - - VERSION - - This man page is correct for version 3.0 of the Samba - suite. - - - - AUTHOR - - 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. - - The profiles man page was written by Jelmer Vernooij. - - - diff --git a/docs/docbook/smbdotconf/base/adsserver.xml b/docs/docbook/smbdotconf/base/adsserver.xml deleted file mode 100644 index 4dd2a4b635..0000000000 --- a/docs/docbook/smbdotconf/base/adsserver.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - If this option is specified, samba does not try to figure out what - ads server to use itself, but uses the specified ads server. Either one - DNS name or IP address can be used. - - Default: ads server = - - Example: ads server = 192.168.1.2 - - - diff --git a/docs/docbook/smbdotconf/expand-smb.conf.xsl b/docs/docbook/smbdotconf/expand-smb.conf.xsl deleted file mode 100644 index 62fc4a9ccf..0000000000 --- a/docs/docbook/smbdotconf/expand-smb.conf.xsl +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - - - - - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - -<!ENTITY % globalentities SYSTEM './../global.ent'> %globalentities; -]> - - - - - - - - - - - - - - - - - - - Processing samba:parameter ( - - ) - - - - - - - - - - - - - - - ( - - ) - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/smbdotconf/ldap/ldaptrustids.xml b/docs/docbook/smbdotconf/ldap/ldaptrustids.xml deleted file mode 100644 index 36bbcb2fb4..0000000000 --- a/docs/docbook/smbdotconf/ldap/ldaptrustids.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - Normally, Samba validates each entry in the LDAP server - against getpwnam(). This allows LDAP to be used for Samba with - the unix system using NIS (for example) and also ensures that - Samba does not present accounts that do not otherwise exist. - - - This option is used to disable this functionality, and - instead to rely on the presence of the appropriate attributes - in LDAP directly, which can result in a significant performance - boost in some situations. Setting this option to yes effectivly - assumes that the local machine is running nss_ldap against the same LDAP - server. - - Default: ldap trust ids = No - - diff --git a/docs/docbook/smbdotconf/printing/totalprintjobs.xml b/docs/docbook/smbdotconf/printing/totalprintjobs.xml deleted file mode 100644 index ccdb137a69..0000000000 --- a/docs/docbook/smbdotconf/printing/totalprintjobs.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - This parameter accepts an integer value which defines - a limit on the maximum number of print jobs that will be accepted - system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbd - 8 will return an - error indicating that no space is available on the server. The - default value of 0 means that no such limit exists. This parameter - can be used to prevent a server from exceeding its capacity and is - designed as a printing throttle. See also - max print jobs. - - - Default: total print jobs = 0 - - Example: total print jobs = 5000 - - diff --git a/docs/docbook/smbdotconf/security/nonunixaccountrange.xml b/docs/docbook/smbdotconf/security/nonunixaccountrange.xml deleted file mode 100644 index 4004af2d94..0000000000 --- a/docs/docbook/smbdotconf/security/nonunixaccountrange.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - The non unix account range parameter specifies - the range of 'user ids' that are allocated by the various 'non unix - account' passdb backends. These backends allow - the storage of passwords for users who don't exist in /etc/passwd. - This is most often used for machine account creation. - This range of ids should have no existing local or NIS users within - it as strange conflicts can occur otherwise. - - - These userids never appear on the system and Samba will never - 'become' these users. They are used only to ensure that the algorithmic - RID mapping does not conflict with normal users. - - - - Default: non unix account range = <empty string> - - Example: non unix account range = 10000-20000 - - diff --git a/docs/docbook/smbdotconf/smb.conf.5.xml b/docs/docbook/smbdotconf/smb.conf.5.xml index db8eb81c28..2a5d190f69 100644 --- a/docs/docbook/smbdotconf/smb.conf.5.xml +++ b/docs/docbook/smbdotconf/smb.conf.5.xml @@ -396,10 +396,10 @@ alias|alias|alias|alias... the architecture of the remote machine. Only some are recognized, and those may not be 100% reliable. It currently recognizes Samba, WfWg, Win95, - WinNT, Win2k, WinXP, and Win2K3. Anything else will be known as + WinNT and Win2k. Anything else will be known as "UNKNOWN". If it gets it wrong then sending a level - 3 log to samba-technical@samba.org - should allow it to be fixed. + 3 log to samba@samba.org + should allow it to be fixed. @@ -507,11 +507,9 @@ alias|alias|alias|alias... case sensitive = yes/no - controls whether filenames are case sensitive. - Windows clients will break if you enable - this parameter. It is only included for case insentive - file systems (such as VFAT) and performance testing. - Default no. + controls whether filenames are case sensitive. If + they aren't then Samba must do a filename search and match on passed + names. Default no. diff --git a/docs/docbook/smbdotconf/tuning/statcachesize.xml b/docs/docbook/smbdotconf/tuning/statcachesize.xml deleted file mode 100644 index 0c8d4e0c72..0000000000 --- a/docs/docbook/smbdotconf/tuning/statcachesize.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - This parameter determines the number of - entries in the stat cache. You should - never need to change this parameter. - - Default: stat cache size = 50 - - diff --git a/docs/docbook/smbdotconf/vfs/vfsoptions.xml b/docs/docbook/smbdotconf/vfs/vfsoptions.xml deleted file mode 100644 index d07ec461e2..0000000000 --- a/docs/docbook/smbdotconf/vfs/vfsoptions.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - This parameter allows parameters to be passed - to the vfs layer at initialization time. - See also - vfs object. - - Default: no value - - diff --git a/docs/docbook/smbdotconf/vfs/vfspath.xml b/docs/docbook/smbdotconf/vfs/vfspath.xml deleted file mode 100644 index c6718a0076..0000000000 --- a/docs/docbook/smbdotconf/vfs/vfspath.xml +++ /dev/null @@ -1,13 +0,0 @@ - - - This parameter specifies the directory - to look in for vfs modules. The name of every vfs object - will be prepended by this directory. - - Default: vfs path = - - Example: vfs path = /usr/lib/samba/vfs - - diff --git a/docs/docbook/xslt/db2latex/VERSION.xml b/docs/docbook/xslt/db2latex/VERSION.xml deleted file mode 100644 index 70bbf95e88..0000000000 --- a/docs/docbook/xslt/db2latex/VERSION.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - -0.7.1 -0.7 - - - - HEAD - - - - - - - diff --git a/docs/docbook/xslt/db2latex/abstract.mod.xsl b/docs/docbook/xslt/db2latex/abstract.mod.xsl deleted file mode 100644 index a9bc2e02ce..0000000000 --- a/docs/docbook/xslt/db2latex/abstract.mod.xsl +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000200120022003 - Ramon Casellas - - - Abstract <filename>abstract.mod.xsl</filename> - -
Introduction - This file abstract.mod.xsl contains a single - XSL template for abstract. - - Calls map.begin. - Processes children with xsl:apply-templates. - Calls map.end - The abstract/title template is empty. - -
- - - - - - - - - - - - Abstract XSL template. - - Calls template (map.begin), - to output the opening command (by default): - - % -------------------------------------------- - % Abstract - % -------------------------------------------- - \begin{abstract} - - Calls "apply-templates" for all the children, and calls template - (map.end) to output the closing - command. - Remarks and Bugs - - The title of the abstract is lost. - The template for abstract/title is defined EMPTY. - - - - Default Behaviour - - Fill - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/admonition.mod.xsl b/docs/docbook/xslt/db2latex/admonition.mod.xsl deleted file mode 100644 index 56042a610e..0000000000 --- a/docs/docbook/xslt/db2latex/admonition.mod.xsl +++ /dev/null @@ -1,222 +0,0 @@ - - - - - - - - - - - - - Ramon Casellas - James Devenish - - 2000200120022003 - Ramon Casellas - - - - Admonition XSL Variables and Templates <filename>admonition.mod.xsl</filename> - - -
Introduction - DocBook includes admonitions, which are set off from the main text. -
- Pertinent Variables - - - - - - - - - - - - - - - Declares a new environment to be used for admonitions - (warning, tip, important, caution, note). - - - - A LaTeX environment is emitted. That environment has two mandatory parameters. - Instances of the environment are customised for each admonition via those parameters. - Instances will be typeset as boxed areas in the document flow. - - - The first argument is the filename for graphics (e.g $latex.admonition.path/warning). - The second argument is the admonition title or the associated generic text. - - - It requires the LaTeX fancybox package. - It also uses graphics, by default. - - - Processing the <sgmltag class="element">warning</sgmltag> admonition - When processing the admonition, the following code is generated: - - - - - - - - -% ---------------------------------------------- -% Define a new LaTeX environment (adminipage) -% ---------------------------------------------- -\newenvironment{admminipage}% -{ % this code corresponds to the \begin{adminipage} command - \begin{Sbox}% - \begin{minipage}% -} %done -{ % this code corresponds to the \end{adminipage} command - \end{minipage} - \end{Sbox} - \fbox{\TheSbox} -} %done -% ---------------------------------------------- -% Define a new LaTeX length (admlength) -% ---------------------------------------------- -\newlength{\admlength} -% ---------------------------------------------- -% Define a new LaTeX environment (admonition) -% With 2 parameters: -% #1 The file (e.g. note.pdf) -% #2 The caption -% ---------------------------------------------- -\newenvironment{admonition}[2] -{ % this code corresponds to the \begin{admonition} command - \hspace{0mm}\newline\hspace*\fill\newline - \noindent - \setlength{\fboxsep}{5pt} - \setlength{\admlength}{\linewidth} - \addtolength{\admlength}{-10\fboxsep} - \addtolength{\admlength}{-10\fboxrule} - \admminipage{\admlength} - {\bfseries \sc\large{#2}} - \newline - \\[1mm] - \sffamily - - - % - - \includegraphics[ ]{#1} - \addtolength{\admlength}{-1cm} - \addtolength{\admlength}{-20pt} - \begin{minipage}[lt]{\admlength} - \parskip=0.5\baselineskip \advance\parskip by 0pt plus 2pt -} %done -{ % this code corresponds to the \end{admonition} command - \vspace{5mm} - \end{minipage} - \endadmminipage - \vspace{.5em} - \par -} - - - - - - - - - Choose an admonition graphic - - For each admonition element (note, warning, caution, top, important), - this template chooses the graphics filename. If the admonition element is - not known, the note graphic is used. - - - - - - - - - note - warning - caution - tip - important - note - - - - - - - - XSL Template for admonitions - - Uses the . - - An admonition will look something like this. - Remarks and Bugs - - - - There can be excessive whitespace between - the bottom of the admonition area and a subsequent paragraph. - - - - - - - - - - - admonition - - { - / - - }{ - - - - - - - - - - - } - - - - - admonition - - - - - - - diff --git a/docs/docbook/xslt/db2latex/authorgroup.mod.xsl b/docs/docbook/xslt/db2latex/authorgroup.mod.xsl deleted file mode 100644 index 6ec7460def..0000000000 --- a/docs/docbook/xslt/db2latex/authorgroup.mod.xsl +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Authorgroup <filename>authorgroup.mod.xsl</filename> - -
Introduction - Pertinent Variables - - - - -
- - - - - - - - Authorgroup XSL template. - - - - - - - - - \and - - - - - - - - - - - AuthorInitials XSL template. - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/biblio.mod.xsl b/docs/docbook/xslt/db2latex/biblio.mod.xsl deleted file mode 100644 index 9524015b1e..0000000000 --- a/docs/docbook/xslt/db2latex/biblio.mod.xsl +++ /dev/null @@ -1,605 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000200120022003 - Ramon Casellas - - - - Bibliography related XSL Variables and Templates <filename>biblio.mod.xsl</filename> - - -
Introduction - This reference describes the templates and parameters relevant - to formatting DocBook bibliography markup. -
-
All Vs. Cited mode - Using this option, only the biblioentries that have been - cited somewhere in the document are output. Otherwise (in All mode) - all bibentries found are output (as the HTML stylesheets do). -
- - - - - - - - - - - - bibliography XSL template - - Remarks and Bugs - - - - - - - - - DB2LaTeX: Processing BIBLIOGRAPHY - DB2LaTeX: Output Mode : - % ------------------------------------------- - % - % Bibliography - % - % ------------------------------------------- - \bibliography{} - - \begin{thebibliography}{ - - } - - - - - - - - - - - - - - - - - - - - - - - - - - \end{thebibliography} - - - - - - - - - - - - - - - bibliography XSL template - - Remarks and Bugs - - - - - - - - - DB2LaTeX: Processing BIBLIOGRAPHY - BIBLIODIV - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - bibliography XSL template - - Remarks and Bugs - - - - - - - - - - - - - - - - - - - - - - bibliography XSL template - - Remarks and Bugs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - % -------------- biblioentry - - - \bibitem - - - \bibitem[ - - - - ] - - - { - - }\docbooktolatexbibaux{ - - }{ - - } \hypertarget{ - - }{\emph{ }} - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ldquo - - - - rdquo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - copyright - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/block.mod.xsl b/docs/docbook/xslt/db2latex/block.mod.xsl deleted file mode 100644 index 49aba64ca2..0000000000 --- a/docs/docbook/xslt/db2latex/block.mod.xsl +++ /dev/null @@ -1,174 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000200120022003 - Ramon Casellas - - - Block Objects <filename>block.mod.xsl</filename> - -
Introduction - Sundry block-formatted objects. -
- - - - - - - - Generic handler for block-formatted objects. - - - - Calls and then applies templates. - - - - - - - - - - - - A quotation set off from the main text (not inline). - - - - Uses the LaTeX quote environment. - If an attribution is present, it will be set at the end. - - - - - - \begin{quote} - - - \end{quote} - - - - - A short inscription that occurs at the beginning of a section, chapter, or document. - - - - Uses the LaTeX quote environment. - If an attribution is present, it will be set at the end. - - - - - - \begin{quote} - - - \end{quote} - - - - - This template produces no output. - - - - The attribution element only occurs within - and . - However, the templates for those elements use a mode mechanism. - Therefore, this template is intentionally suppressed and a replacement exists. - See instead. - - - - - - - - - The source of a block quote or epigraph. - - - - Starts a new line with right-aligned text preceded by an em dash. - - - - - - \hspace*\fill--- - - - - - - A block of text that is isolated from the main flow. - - - - This is formatted as a plain block. - - - - - - - - - - - Title lines for sundry block elements. - - - - This is formatted as a line on its own. - - - - - - - - - - - - Acknowledgements in an Article. - - - - This is formatted as a plain block. - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/book-article.mod.xsl b/docs/docbook/xslt/db2latex/book-article.mod.xsl deleted file mode 100644 index 042ec556aa..0000000000 --- a/docs/docbook/xslt/db2latex/book-article.mod.xsl +++ /dev/null @@ -1,540 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Books and Articles <filename>book-article.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - Book XSL Template - - Most DocBook documents are either articles or books, so the book - XSL template is one classical entry point - when processign docbook documents. - - Tasks - - - - - - Remarks and Bugs - - - - - - - - colwidth - - The CALS column width specification. - - - - - - :Outputs the LaTeX Code corresponding to a book. - - - - - - - - - - - - - - - - \title{ - - - - - - - - - - - } - - \author{ - - - - - - - - - \and - - - - - } - - - - \setcounter{tocdepth}{} - \setcounter{secnumdepth}{} - - - - - - \InputIfFileExists{ - }{\typeout{WARNING: Using cover page - - }} - - - - - - - - - - - - - - - - - - - - - - \bfseries - \\[12pt]\normalsize - \bfseries - \\[12pt]\normalsize - - - - - - - - - - - - - - - - Article XSL Template - - Most DocBook documents are either articles or books, so the article - XSL template is one classical entry point - when processign docbook documents. - - Tasks - - Calls generate.latex.article.preamble. - Outputs \title, \author, \date, getting the information from its children. - Calls latex.article.begindocument. - Calls latex.article.maketitle. - Applies templates. - Calls latex.article.end template. - - - - Remarks and Bugs - - EMPTY templates: article/title and article/subtitle - - - - - - - colwidth - - The CALS column width specification. - - - - - - Outputs the LaTeX Code corresponding to an article. - - - - - - - \makeatletter\if@openright\cleardoublepage\else\clearpage\fi - - \makeatother - - - - - - - - - - - - - - - \begin{center}{ - - { - - }}\par - - - - \textsf{ - - - - \and - - - }\par - - - \textsf{ - - }\par - - - \textsf{ - - - - \and - - - }\par - - - \textsf{ - - }\par - - - \textsf{ - - - - \and - - - }\par - - - - \end{center} - - - - - - - - - - - - - - - - - - - - - - - - - - - - \title{ - - { - - }} - - - - - - \date{ - - } - - \author{ - - - - - - - - - - - - \and - - - - - - - - \and - - - - - - - - \and - - - - - } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - copyright - - - - - - - - - - - - - , - - - - - - , - - - - - - - - - - - - - - - - - - legalnotice - - - - - - - - - - - \vspace{-.3em} - \if@twocolumn - \noindent\small{\itshape - - }\/\bfseries---$\!$% - \else - \noindent\begin{center}\small\bfseries - - \end{center}\quotation\small - \fi - - \vspace{0.6em}\par\if@twocolumn\else\endquotation\fi - \normalsize\rmfamily - - - - - - - - - - - - - - \tableofcontents - - - - - - - - \listoffigures - - - \listoftables - - - \listoffigures - \listoftables - - - - - \listoffigures - \listoftables - - - - - - - - - - - - - - Choose the preferred page style for document body - - - If no page style is preferred by the user, the defaults will be - "empty" for articles, "plain" for books, or "fancy" (if the - fancyhdr packages is permitted). - - Pertinent Variables - - - - - - - - - \pagestyle{ - - - - - fancy - plain - - - empty - - } - - - - diff --git a/docs/docbook/xslt/db2latex/bridgehead.mod.xsl b/docs/docbook/xslt/db2latex/bridgehead.mod.xsl deleted file mode 100644 index a09ca15dda..0000000000 --- a/docs/docbook/xslt/db2latex/bridgehead.mod.xsl +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - BridgeHead <filename>bridgehead.mod.xsl</filename> - -
Introduction - Handle the bridgehead element. -
- - - - - - - A free-floating heading. - - - - Renders un-numbered section headings. - For renderas values of sect1, sect2, and sect3, LaTeX star commands (such as \section*) are used. - Otherwise, a bold heading is put on a line of its own. - - - - - - - - \ - sub - subsub - section*{ - - } - - - - - - \noindent{\bfseries } \\ - - - - - - diff --git a/docs/docbook/xslt/db2latex/callout.mod.xsl b/docs/docbook/xslt/db2latex/callout.mod.xsl deleted file mode 100644 index ab67cf8e23..0000000000 --- a/docs/docbook/xslt/db2latex/callout.mod.xsl +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Callout <filename>callout.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - ( - - ) - - - diff --git a/docs/docbook/xslt/db2latex/citation.mod.xsl b/docs/docbook/xslt/db2latex/citation.mod.xsl deleted file mode 100644 index 46c69af0eb..0000000000 --- a/docs/docbook/xslt/db2latex/citation.mod.xsl +++ /dev/null @@ -1,63 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Citation <filename>citation.mod.xsl</filename> - -
Introduction - This file contais a single (and simple!) XSL template, that maps the - citation SGML tag to the LaTeX \cite{} - command. -
- - - - - - - - Citation XSL template. - - Outputs a simple \cite{ } Command, - containing the result of processing the citation's children - - - - - - - - - \docbooktolatexcite{ - - }{} - - - - - diff --git a/docs/docbook/xslt/db2latex/common/ca.xml b/docs/docbook/xslt/db2latex/common/ca.xml deleted file mode 100644 index fec3efff1a..0000000000 --- a/docs/docbook/xslt/db2latex/common/ca.xml +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/common.xsl b/docs/docbook/xslt/db2latex/common/common.xsl deleted file mode 100644 index 2506bd71ed..0000000000 --- a/docs/docbook/xslt/db2latex/common/common.xsl +++ /dev/null @@ -1,1927 +0,0 @@ - - - - - - - - - Ramon - Casellas - - - 19992000 - Norman Walsh - - -Common Template Reference - - -
Introduction - -This is technical reference documentation for the DocBook XSL -Stylesheets; it documents (some of) the parameters, templates, and -other elements of the stylesheets. - -This is not intended to be user documentation. -It is provided for developers writing customization layers for the -stylesheets, and for anyone who's interested in how it -works. - -Although I am trying to be thorough, this documentation is known -to be incomplete. Don't forget to read the source, too :-) -
- - - - - - - - - - - - - - -Tests if a given node is a component-level element - - -This template returns '1' if the specified node is a component -(Chapter, Appendix, etc.), and '0' otherwise. - - - - -node - -The node which is to be tested. - - - - - - -This template returns '1' if the specified node is a component -(Chapter, Appendix, etc.), and '0' otherwise. - - - - - - - 1 - 0 - - - - - - -Tests if a given node is a section-level element - - -This template returns '1' if the specified node is a section -(Section, Sect1, Sect2, etc.), and '0' otherwise. - - - - -node - -The node which is to be tested. - - - - - - -This template returns '1' if the specified node is a section -(Section, Sect1, Sect2, etc.), and '0' otherwise. - - - - - - - 1 - 0 - - - - - - -Returns the hierarchical level of a section. - - -This template calculates the hierarchical level of a section. -Hierarchically, components are top level, so a -sect1 is at level 2, sect3 is -at level 3, etc. - -Recursive sections are calculated down to the sixth level. - - - - -node - -The section node for which the level should be calculated. -Defaults to the context node. - - - - - - -The section level, 2, 3, etc. - - - - - - - - 2 - 3 - 4 - 5 - 6 - - - 6 - 5 - 4 - 3 - 2 - - - - - 3 - 4 - 5 - 6 - 6 - - - 6 - 5 - 4 - 3 - - - 2 - - - 2 - - - - -Returns the hierarchical level of a QandASet. - - -This template calculates the hierarchical level of a QandASet. - - - - -The level, 1, 2, etc. - - - - - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - , - - - and - - - - - - - - - - - - -[ -] -{ -} - - -[ -] -... - - - | -4pi - - - - - -Provides access to element labels - -Processing an element in the -label.content mode produces the -element label. -If the label is non-null, either because the -label attribute was present on the -element or the stylesheet automatically generated a label, trailing -punctuation is automatically added. - - - - - - Request for label of unexpected element: - - - - - - . - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - . - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - . - - - - - . - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - . - - - - - - - - - - . - - - - - - - - - - - - - - - - - . - - - - . - - - - - - - - - - - - - - - - - - - - - - - label.content: this can't happen! - - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - . - - - - - - - - - - - . - - - - - - - - - - - - - - - . - - - - - - - - - - -Returns true if $section should be labelled - -Returns true if the specified section should be labelled. -By default, this template simply returns $section.autolabel, but -custom stylesheets may override it to get more selective behavior. - - - - - - - -Provides access to element titles - -Processing an element in the -title.content mode produces the -title of the element. This does not include the label. If -text-only is true, the text of the title -is returned, without inline markup, otherwise inline markup is processed -(in the default mode). By default, text-only -is false. - - - - - - - - - - - - - - - - - Request for title of unexpected element: - - - ???TITLE??? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - REFENTRY WITHOUT TITLE??? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Provides access to element subtitles - -Processing an element in the -subtitle.content mode produces the -subtitle of the element. If -text-only is true, the text of the title -is returned, without inline markup, otherwise inline markup is processed -(in the default mode). By default, text-only -is false. - - - - - - - Request for subtitle of unexpected element: - - - ???SUBTITLE??? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Provides reference text for an element - -Processing an element in the -title.ref mode produces the -label and title of the element. - - - - -text-only - - If -text-only is true, the text of the title -is returned, without inline markup, otherwise inline markup is processed -(in the default mode). By default, text-only -is false. - - -label-wrapper - -If label-wrapper is not the emtpy string, -it must be the name of an element. The element so named will be wrapped -around labels on output. - - -title-wrapper - -If title.wrapper is not the emtpy string, -it must be the name of an element. The element so named will be wrapped -around titles on output. - - -label-wrapper-class - -If a label-wrapper is provided and -label-wrapper-class is not the emtpy string, -it be used as the value for a class -attribute on the label-wrapper element. -This is a dirty hack because it only makes sense for the HTML -stylesheet (there's no class attribute -on the FO elements). What I'd really like to do is pass an attribute -set as a parameter, but I can't. - - -title-wrapper-class - -If a title-wrapper is provided and -title-wrapper-class is not the emtpy string, -it be used as the value for a class -attribute on the title-wrapper element. -This is a dirty hack because it only makes sense for the HTML -stylesheet (there's no class attribute -on the FO elements). What I'd really like to do is pass an attribute -set as a parameter, but I can't. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - %g - - - - - - - - - - - - - - - - - - - - - - %t - - - - - - - - - - - - - - - - - - - - - - - - - - - - %n - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Selects an appropriate media object from a list - - -This template examines a list of media objects (usually the -children of a mediaobject or inlinemediaobject) and processes -the "right" object. - -This template relies on a template named "is.acceptable.mediaobject" -to determine if a given object is an acceptable graphic. The semantics -of media objects is that the first acceptable graphic should be used. - - -If no acceptable object is located, nothing happens. - - - - -olist - -The node list of potential objects to examine. - - - - - - -Calls <xsl:apply-templates> on the selected object. - - - - - - 1 - - - - - - - - - 0 - - - - 1 - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Returns '1' if the specified media object is recognized. - - -This template examines a media object and returns '1' if the -object is recognized as a graphic. - - - - -object - -The media object to consider. - - - - - - -0 or 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - 1 - 0 - - - - - - 1 - - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - . - - - - - - - - - - - - - - - - -Warn users about references to non-unique IDs - -If passed an ID in linkend, -check.id.unique prints -a warning message to the user if either the ID does not exist or -the ID is not unique. - - - - - - - - - - - - Error: no ID for constraint linkend: - - . - - - - - - Warning: multiple "IDs" for constraint linkend: - - . - - - - - - -Warn users about incorrectly typed references - -If passed an ID in linkend, -check.idref.targets makes sure that the element -pointed to by the link is one of the elements listed in -element-list and warns the user otherwise. - - - - - - - - - - - - - - Error: linkend ( - - ) points to " - - " not (one of): - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/cs.xml b/docs/docbook/xslt/db2latex/common/cs.xml deleted file mode 100644 index 81c9c5a9cb..0000000000 --- a/docs/docbook/xslt/db2latex/common/cs.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/da.xml b/docs/docbook/xslt/db2latex/common/da.xml deleted file mode 100644 index 959050230f..0000000000 --- a/docs/docbook/xslt/db2latex/common/da.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/de.xml b/docs/docbook/xslt/db2latex/common/de.xml deleted file mode 100644 index 8c458b0f5e..0000000000 --- a/docs/docbook/xslt/db2latex/common/de.xml +++ /dev/null @@ -1,102 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/el.xml b/docs/docbook/xslt/db2latex/common/el.xml deleted file mode 100644 index ad93032047..0000000000 --- a/docs/docbook/xslt/db2latex/common/el.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/en.xml b/docs/docbook/xslt/db2latex/common/en.xml deleted file mode 100644 index 2e8500135f..0000000000 --- a/docs/docbook/xslt/db2latex/common/en.xml +++ /dev/null @@ -1,107 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/es.xml b/docs/docbook/xslt/db2latex/common/es.xml deleted file mode 100644 index 78483dfb65..0000000000 --- a/docs/docbook/xslt/db2latex/common/es.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/et.xml b/docs/docbook/xslt/db2latex/common/et.xml deleted file mode 100644 index 4c63adbe7a..0000000000 --- a/docs/docbook/xslt/db2latex/common/et.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/fi.xml b/docs/docbook/xslt/db2latex/common/fi.xml deleted file mode 100644 index 5d25725512..0000000000 --- a/docs/docbook/xslt/db2latex/common/fi.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/fr.xml b/docs/docbook/xslt/db2latex/common/fr.xml deleted file mode 100644 index bf53bc57d6..0000000000 --- a/docs/docbook/xslt/db2latex/common/fr.xml +++ /dev/null @@ -1,114 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/hu.xml b/docs/docbook/xslt/db2latex/common/hu.xml deleted file mode 100644 index d37e06ff8a..0000000000 --- a/docs/docbook/xslt/db2latex/common/hu.xml +++ /dev/null @@ -1,94 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/id.xml b/docs/docbook/xslt/db2latex/common/id.xml deleted file mode 100644 index f85b02154b..0000000000 --- a/docs/docbook/xslt/db2latex/common/id.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/it.xml b/docs/docbook/xslt/db2latex/common/it.xml deleted file mode 100644 index a7e1063ef4..0000000000 --- a/docs/docbook/xslt/db2latex/common/it.xml +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/ja.xml b/docs/docbook/xslt/db2latex/common/ja.xml deleted file mode 100644 index 9180e8e186..0000000000 --- a/docs/docbook/xslt/db2latex/common/ja.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/ko.xml b/docs/docbook/xslt/db2latex/common/ko.xml deleted file mode 100644 index 06dd7cb217..0000000000 --- a/docs/docbook/xslt/db2latex/common/ko.xml +++ /dev/null @@ -1,96 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/l10n.dtd b/docs/docbook/xslt/db2latex/common/l10n.dtd deleted file mode 100644 index 0336baf208..0000000000 --- a/docs/docbook/xslt/db2latex/common/l10n.dtd +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/l10n.xml b/docs/docbook/xslt/db2latex/common/l10n.xml deleted file mode 100644 index a7ef90e905..0000000000 --- a/docs/docbook/xslt/db2latex/common/l10n.xml +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - -]> - -&ca; -&cs; -&da; -&de; -⪙ -&en; -&es; -&et; -&fi; -&fr; -&hu; -&id; -⁢ -&ja; -&ko; -&nl; -&no; -&pl; -&pt; -&pt_br; -&ro; -&ru; -&sk; -&sl; -&sv; -&zh_cn; -&zh_tw; - diff --git a/docs/docbook/xslt/db2latex/common/l10n.xsl b/docs/docbook/xslt/db2latex/common/l10n.xsl deleted file mode 100644 index a8b526fc60..0000000000 --- a/docs/docbook/xslt/db2latex/common/l10n.xsl +++ /dev/null @@ -1,248 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _ - - - - - - - - - - - - - - - - - - - - - - - - - No " - - " cross reference text for " - - " exists and no default specified. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - No " - - " localization of " - - " exists; using "en". - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Editedby - - - - - - by - - - - - bullet - - - - - - - - - - - - No " - - " localization of dingbat - - exists; using "en". - - - - - - - - - - - - - startquote - - - - - - endquote - - - - - - nestedstartquote - - - - - - nestedendquote - - - - - - nav-prev - - - - - - nav-next - - - - - - nav-home - - - - - - nav-up - - - - - diff --git a/docs/docbook/xslt/db2latex/common/nl.xml b/docs/docbook/xslt/db2latex/common/nl.xml deleted file mode 100644 index 56ead54d30..0000000000 --- a/docs/docbook/xslt/db2latex/common/nl.xml +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/no.xml b/docs/docbook/xslt/db2latex/common/no.xml deleted file mode 100644 index b3aba44fde..0000000000 --- a/docs/docbook/xslt/db2latex/common/no.xml +++ /dev/null @@ -1,97 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/pl.xml b/docs/docbook/xslt/db2latex/common/pl.xml deleted file mode 100644 index 8582bbebe8..0000000000 --- a/docs/docbook/xslt/db2latex/common/pl.xml +++ /dev/null @@ -1,96 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/pt.xml b/docs/docbook/xslt/db2latex/common/pt.xml deleted file mode 100644 index af0c22f4b4..0000000000 --- a/docs/docbook/xslt/db2latex/common/pt.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/pt_br.xml b/docs/docbook/xslt/db2latex/common/pt_br.xml deleted file mode 100644 index cf63d1ebf2..0000000000 --- a/docs/docbook/xslt/db2latex/common/pt_br.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/ro.xml b/docs/docbook/xslt/db2latex/common/ro.xml deleted file mode 100644 index a59ffd8217..0000000000 --- a/docs/docbook/xslt/db2latex/common/ro.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/ru.xml b/docs/docbook/xslt/db2latex/common/ru.xml deleted file mode 100644 index a097cd419b..0000000000 --- a/docs/docbook/xslt/db2latex/common/ru.xml +++ /dev/null @@ -1,113 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/sk.xml b/docs/docbook/xslt/db2latex/common/sk.xml deleted file mode 100644 index 0c2fbc85fb..0000000000 --- a/docs/docbook/xslt/db2latex/common/sk.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/sl.xml b/docs/docbook/xslt/db2latex/common/sl.xml deleted file mode 100644 index fca0f5e348..0000000000 --- a/docs/docbook/xslt/db2latex/common/sl.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/sv.xml b/docs/docbook/xslt/db2latex/common/sv.xml deleted file mode 100644 index 27b45cce15..0000000000 --- a/docs/docbook/xslt/db2latex/common/sv.xml +++ /dev/null @@ -1,99 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/zh_cn.xml b/docs/docbook/xslt/db2latex/common/zh_cn.xml deleted file mode 100644 index ef373b4a33..0000000000 --- a/docs/docbook/xslt/db2latex/common/zh_cn.xml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/common/zh_tw.xml b/docs/docbook/xslt/db2latex/common/zh_tw.xml deleted file mode 100644 index 7168114f49..0000000000 --- a/docs/docbook/xslt/db2latex/common/zh_tw.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/component.mod.xsl b/docs/docbook/xslt/db2latex/component.mod.xsl deleted file mode 100644 index aedcadb550..0000000000 --- a/docs/docbook/xslt/db2latex/component.mod.xsl +++ /dev/null @@ -1,91 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Component <filename>component.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - {\sc } - - - - - - - - {\sc } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/dedication.mod.xsl b/docs/docbook/xslt/db2latex/dedication.mod.xsl deleted file mode 100644 index d8150bdd7f..0000000000 --- a/docs/docbook/xslt/db2latex/dedication.mod.xsl +++ /dev/null @@ -1,126 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Dedication <filename>dedication.mod.xsl</filename> - -
Introduction - -
- - - - - - -\sc - - - - - -\newpage -% ------------------------------------------------------------- -% Dedication -% ------------------------------------------------------------- - - - - - - - - - - - -{ - - - - - - - - - dedication - - - -} - - - - - - - - - - - - - - - - - { - - - - } - - - - - - - - - - - - - - \paragraph*{} - - - - - diff --git a/docs/docbook/xslt/db2latex/dingbat.mod.xsl b/docs/docbook/xslt/db2latex/dingbat.mod.xsl deleted file mode 100644 index 84b579515a..0000000000 --- a/docs/docbook/xslt/db2latex/dingbat.mod.xsl +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000200120022003 - Ramon Casellas - - - Dingbats <filename>dingbat.mod.xsl</filename> - -
Introduction -
- - - - - - - bullet - - - - - - - bullet - - $\bullet$ - \copyright{} - \texttrademark{} - \textregistered{} - ~ - `` - '' - ` - ' - --- - --- - -- - -- - - [dingbat?] - - - - - diff --git a/docs/docbook/xslt/db2latex/docbook.xsl b/docs/docbook/xslt/db2latex/docbook.xsl deleted file mode 100644 index 56e000cd02..0000000000 --- a/docs/docbook/xslt/db2latex/docbook.xsl +++ /dev/null @@ -1,149 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ################################################################################ - XSLT stylesheets DocBook - LaTeX 2e - Reqs: LaTeX 2e installation common packages - ################################################################################ - WWW : http://db2latex.sourceforge.net - SUMMARY : http://www.sourceforge.net/projects/db2latex - AUTHOR : Ramon Casellas casellas@infres.enst.fr - AUTHOR : James Devenish j-devenish@users.sf.net - USING : - ################################################################################ - - - - - - - - - - - - - SAXON 6.4.X - - - SAXON 6.2.X - - - SAXON - - - XALAN - - - XALAN - - - libxslt/xsltproc - - - XT - - - UNKNOWN - - - - - - diff --git a/docs/docbook/xslt/db2latex/email.mod.xsl b/docs/docbook/xslt/db2latex/email.mod.xsl deleted file mode 100644 index 6461334ac8..0000000000 --- a/docs/docbook/xslt/db2latex/email.mod.xsl +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Email <filename>email.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - XSL template for email - - Outputs the mail in {\texttt }. Calls the normalize-scape template in order to get a - normalized email string. It does not process email content model. - Remarks and Bugs - - - - - - - - \texttt{< - - - - >} - - - diff --git a/docs/docbook/xslt/db2latex/errors.mod.xsl b/docs/docbook/xslt/db2latex/errors.mod.xsl deleted file mode 100644 index 37b273c01d..0000000000 --- a/docs/docbook/xslt/db2latex/errors.mod.xsl +++ /dev/null @@ -1,16 +0,0 @@ - - - - - - - DB2LaTeX: Need to process XPath match - [] - - [/] - - diff --git a/docs/docbook/xslt/db2latex/example.mod.xsl b/docs/docbook/xslt/db2latex/example.mod.xsl deleted file mode 100644 index fb973a27e7..0000000000 --- a/docs/docbook/xslt/db2latex/example.mod.xsl +++ /dev/null @@ -1,76 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Example <filename>example.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - \caption{ - - } - - - - \captionswapskip{} - - \captionswapskip{} - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/figure.mod.xsl b/docs/docbook/xslt/db2latex/figure.mod.xsl deleted file mode 100644 index 823877aa17..0000000000 --- a/docs/docbook/xslt/db2latex/figure.mod.xsl +++ /dev/null @@ -1,127 +0,0 @@ - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Figures and InformalFigures <filename>figure.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - XSL template for figure|informalfigure - - Outputs \begin{figure}, - applies templates and outputs \end{figure}. - Remarks and Bugs - - The figure.title can be typset in italics by specifying $latex.figure.title.style (\itshape would be common). - If a figure.mediaobject.caption exists, it will be typeset after the figure.title (but only if there is a single figure.mediaobject.caption). - - - - - - - - - -\caption{{ - -{ - -}} - - . - - -} - - - - - - - - - - - \captionswapskip{} - - \captionswapskip{} - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/font.mod.xsl b/docs/docbook/xslt/db2latex/font.mod.xsl deleted file mode 100644 index 20e2814520..0000000000 --- a/docs/docbook/xslt/db2latex/font.mod.xsl +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Font <filename>font.mod.xsl</filename> - -
Introduction - -
- - - - - - - - Document Font - - Possible values: default, times, palatcm, charter, helvet, palatino, avant, newcent, bookman - - - - - palatino - - - - diff --git a/docs/docbook/xslt/db2latex/footnote.mod.xsl b/docs/docbook/xslt/db2latex/footnote.mod.xsl deleted file mode 100644 index 6e7d39a36a..0000000000 --- a/docs/docbook/xslt/db2latex/footnote.mod.xsl +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - FootNotes <filename>footnote.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - \begingroup\catcode`\#=12\footnote{ - - }\endgroup\docbooktolatexmakefootnoteref{ - - } - - - - Construct a footnote that copes with URLs - This template exists in this file so that all - the footnote-generating templates are close to each other. However, - it is actually a part of the ulink template in xref.mod.xsl - - - - - - \begingroup\catcode`\#=12\footnote{ - - - - - }\endgroup\docbooktolatexmakefootnoteref{ - - } - - - - - - - - - - - \docbooktolatexusefootnoteref{ - - } - - - diff --git a/docs/docbook/xslt/db2latex/formal.mod.xsl b/docs/docbook/xslt/db2latex/formal.mod.xsl deleted file mode 100644 index 6908119225..0000000000 --- a/docs/docbook/xslt/db2latex/formal.mod.xsl +++ /dev/null @@ -1,173 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Formal Objects <filename>formal.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - before - - - - - - - - - - - - - - - - - - - - - - - \caption{ - - } - - - - \captionswapskip{} - - \captionswapskip{} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/glossary.mod.xsl b/docs/docbook/xslt/db2latex/glossary.mod.xsl deleted file mode 100644 index f429187aee..0000000000 --- a/docs/docbook/xslt/db2latex/glossary.mod.xsl +++ /dev/null @@ -1,218 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Glossary <filename>glossary.mod.xsl</filename> - -
Introduction - This reference applies to the glossary element name. Altough LaTeX - provides some glossary support, the better glossary management support - motivates the bypass of the LaTeX \makeglossary - command. -
- - - - - - - - - Glossary XSL template / entry point - The glossary element is the entry point - to a docbook glossary. The DB2LaTeX processing of the element is quite straight- - forward. First thing is to check whether the document is a book or article. In - both cases two new LaTeX commands are defined. \dbglossary - and \dbglossdiv. In the former case, they are mapped to - \chapter* and \section*. In the second - case to \section* and \subsection*. - - - Call template map.begin. - Apply Templates for Preamble, GlossDivs and GlossEntries (serial). - Call template map.end. - - Remarks and Bugs - - Template for glossary/glossaryinfo is EMPTY. - Template for glossary/title | glossary/subtitle is EMPTY. - Template for glossary/titleabbrev is EMPTY. - - - - - - - - - - - - \newcommand{\dbglossary}[1]{\chapter*{#1}}% - \newcommand{\dbglossdiv}[1]{\section*{#1}}% - - - \newcommand{\dbglossary}[1]{\section*{#1}}% - \newcommand{\dbglossdiv}[1]{\subsection*{#1}}% - - - - - - - - - - - - - - - - - - - - - - - - Glossary Division and Glossary Lists XSL templates. - T.B.D - - - Call template map.begin. - Apply Templates. - Call template map.end. - - Remarks and Bugs - - Template for glossdiv/glossaryinfo is EMPTY. - - - - - - - - - - - - - - - - - - - Glossary Entry XSL template / entry point - - T.B.D. - - - Apply Templates. - - Remarks and Bugs - - Explicit Templates for glossentry/glossterm - Explicit Templates for glossentry/acronym - Explicit Templates for glossentry/abbrev - Explicit Templates for glossentry/glossdef - Explicit Templates for glossentry/glosssee - Explicit Templates for glossentry/glossseealso - Template for glossentry/revhistory is EMPTY. - - - - - - - - - - - - - \item[ - - \hypertarget{ - - } - - { - - - - }] - - - - ( \texttt { } ) - - - - [ ] - - - - - - - - - - - - - - - - - - - \hyperlink{ - }{} - - - - - - - . - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/graphic.mod.xsl b/docs/docbook/xslt/db2latex/graphic.mod.xsl deleted file mode 100644 index 1c9845c93e..0000000000 --- a/docs/docbook/xslt/db2latex/graphic.mod.xsl +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Graphics <filename>graphic.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - \includegraphics{ } - - - - \includegraphics{ } - - - - - - - - - - \includegraphics{ - - - - } - - - - - - - - - - - \includegraphics{ - - - - } - - - - diff --git a/docs/docbook/xslt/db2latex/html.mod.xsl b/docs/docbook/xslt/db2latex/html.mod.xsl deleted file mode 100644 index a94ac3c80f..0000000000 --- a/docs/docbook/xslt/db2latex/html.mod.xsl +++ /dev/null @@ -1,15 +0,0 @@ - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/index.mod.xsl b/docs/docbook/xslt/db2latex/index.mod.xsl deleted file mode 100644 index 0ca975bd50..0000000000 --- a/docs/docbook/xslt/db2latex/index.mod.xsl +++ /dev/null @@ -1,213 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Index <filename>index.mod.xsl</filename> - -
Introduction - -
- - - - - -1 - - - - - - - - - - - - - - \printindex - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Error: Only one attribut (@class or @zone) is in indexterm possible! - - - - - \index{ - - |(} - - - - - Error: No indexterm with - id=' - ' found! - Check your attributs id/startref in your indexterms! - - - - - \index{ - - |)} - - - - - \index{ - Simple case: - - } - - - - - - - - - WARNING: Element '' in indexterm not supported! - - - - - - - - - - -! - - - - -! - - - - -|see{ - -} - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/info.mod.xsl b/docs/docbook/xslt/db2latex/info.mod.xsl deleted file mode 100644 index a2a35d4629..0000000000 --- a/docs/docbook/xslt/db2latex/info.mod.xsl +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Info <filename>info.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/inline.mod.xsl b/docs/docbook/xslt/db2latex/inline.mod.xsl deleted file mode 100644 index 5a6d8cc214..0000000000 --- a/docs/docbook/xslt/db2latex/inline.mod.xsl +++ /dev/null @@ -1,523 +0,0 @@ - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Inline <filename>inline.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - \docbookhyphenatedot - - - - {\texttt{ - - { - - }}} - - - - - - - {\bfseries - - } - - - - - - - {\em - - } - - - - \docbookhyphenatedot - - - - {\texttt\bfseries{ - - { - - }}} - - - - \docbookhyphenatedot - - - - {\texttt\itshape{ - - { - - }}} - - - - - - - $^\text{ - - }$ - - - - - - - $_\text{ - - }$ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \docbookhyphenatefilename - - - - - - - - - - - - - ( - - ) - - - - - - - - - - - , - - - - - - - , - - - - - {\sffamily \bfseries - - } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A span of text - - This is a regular inline sequence. - However, if the role attribute is 'tex' or 'latex', the content - will be output without LaTeX active-character escaping. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - trademark - - - - - - - - - - - - - - - - - + - -- - -- - -- - - -- - - - - - - - - - - - - - - - ( - - ) - - - - - - - - - - - - - - - - - - - - - $\to$ - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/keywords.mod.xsl b/docs/docbook/xslt/db2latex/keywords.mod.xsl deleted file mode 100644 index 80d5457199..0000000000 --- a/docs/docbook/xslt/db2latex/keywords.mod.xsl +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Keywords <filename>keywords.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - , - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/labelid.mod.xsl b/docs/docbook/xslt/db2latex/labelid.mod.xsl deleted file mode 100644 index 5305e07c5a..0000000000 --- a/docs/docbook/xslt/db2latex/labelid.mod.xsl +++ /dev/null @@ -1,476 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Labels <filename>labelid.mod.xsl</filename> - -
Introduction - -
- - - - - - - Marks the current object with a label. - - This template marks the current object with a - \label{.}. The passed argument indicates the object whose - id attribute is used to generate the label. - In this sense, in most cases its the current node itself. - If the used object has not an id attribute, a unique id is - obtained by means of the generate-id function. - Moreover, if we are using the hyperref package, a hypertarget is - also defined for this object. - - - - object - The node whose id is to be used. - - - - - This template returns the id that has been used to label the - object. - - - - - \label{ - - } - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/latex.mapping.dtd b/docs/docbook/xslt/db2latex/latex.mapping.dtd deleted file mode 100644 index 361ce5a18d..0000000000 --- a/docs/docbook/xslt/db2latex/latex.mapping.dtd +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/latex.mapping.xml b/docs/docbook/xslt/db2latex/latex.mapping.xml deleted file mode 100644 index 1616774046..0000000000 --- a/docs/docbook/xslt/db2latex/latex.mapping.xml +++ /dev/null @@ -1,290 +0,0 @@ - - - - - - - - - - - - - - % -------------------------------------------- - % Abstract - % -------------------------------------------- - \begin{abstract} - - - - - \begin{admonition}%title% NOTICE: see the db2latex FAQ w.r.t db2latex variable $latex.admonition.path - - - - % ------------------------------------------------------------- - % Appendixes start here - % ------------------------------------------------------------- - \appendix - - - - - % ------------------------------------------------------------- - % appendix: %title - % ------------------------------------------------------------- - \dbappendix{%title} - \label{%id}\hypertarget{%id}{}% - - - - - % ------------------------------------------------------------- - % Chapter %title - % ------------------------------------------------------------- - \chapter{%title} - \label{%id}\hypertarget{%id}{}% - - - - - % figure ------------------------------------------------------ - \begin{figure}[hbt] - \begin{center}% - \hypertarget{%id}{}% - - - - - - % keywords ------------------------------------------------------ - \begin{keywords} - - - - - % table ------------------------------------------------------ - \begin{table}[hbt] - \begin{center}% - \hypertarget{%id}{}% - - - - - % tabular ------------------------------------------------------ - \begin{center} - \label{%id}\hypertarget{%id}{}% - - - - \begin{dbequation} - \begin{center} - - - - % ------------------------------------------------------------- - % - % GLOSSARY %title - % - % ------------------------------------------------------------- - \dbglossary{%title} - \label{%id}\hypertarget{%id}{}% - - - - % - % ------------------------------------------------------------- - \dbglossdiv{%title} - \label{%id}\hypertarget{%id}{}% - \noindent% - \begin{description}% - - - - % ------------------------------------------------------------- - % - % PART %title - % - % ------------------------------------------------------------- - \part{%title} - \label{%id}\hypertarget{%id}{}% - - - - % - % ------------------------------------------------------------- - % Refentry - % ------------------------------------------------------------- - \section*{%title} - \label{%id}\hypertarget{%id}{}% - - - - % - % ------------------------------------------------------------- - % Reference - % ------------------------------------------------------------- - \chapter*{%title} - \label{%id}\hypertarget{%id}{}% - - - - - % ------------------------ - % RevHistory - % ------------------------ - \pagebreak - \section*{%title} - \label{%id}\hypertarget{%id}{}% - \begin{center} - \begin{tt} - \begin{tabular}{|l||l|l|} \hline - - - - - - - - - % ------------------------ - % Section - \section{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subsection{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subsubsection{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subparagraph*{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subparagraph*{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subparagraph*{%title} - \label{%id}\hypertarget{%id}{}% - - - - \subsubsection*{\small{%title}} - \label{%id}\hypertarget{%id}{}% - - - - - - - - - - - - - - - - - \end{abstract} - - - - - \end{admonition} - - - - - - \end{document} - - - - - - - \label{%id}\hypertarget{%id}{}% - \end{example} - - - - - \label{%id} - \end{center} - \end{figure} - - - - \label{%id}\hypertarget{%id}{}% - \end{center} - \end{dbequation} - - - - - - - - \end{description}% - - - - - \end{keywords} - - - - - - - \label{%id} - \end{center} - \end{table} - - - - - \end{center} - - - - - \label{%id}\hypertarget{%id}{}% - \end{center} - \end{program} - - - - - \end{tabular} - \end{tt} - \end{center} - % ------------------------ - % End RevHistory - % ------------------------ - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/latex.mapping.xsl b/docs/docbook/xslt/db2latex/latex.mapping.xsl deleted file mode 100644 index 2ab53de9bf..0000000000 --- a/docs/docbook/xslt/db2latex/latex.mapping.xsl +++ /dev/null @@ -1,174 +0,0 @@ - - - - - - - - - - - - - - - - RamonCasellas - - - 2000 2001 2002 2003 - Ramon Casellas - - - The DB2LaTeX mapping system <filename>latex.mapping.xsl</filename> - -
Introduction - The DB2LaTeX mapping system centralizes mapping docbook tags (e.g. chapter) - to LaTeX commands \chapter. It used an auxiliary file, latex.mapping.xml - that defines how the mapping is to be done. -
- - - - - - - - - - - - Remarks and Bugs - - - - Default Behaviour - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - %id - - - - %title - - - - - - - - - - - - %id - - - - %title - - - - - - - - - - - - - - - - - - - - - - - begin - - - - - - - - - - - - - - - - - end - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/lists.mod.xsl b/docs/docbook/xslt/db2latex/lists.mod.xsl deleted file mode 100644 index cdd093b3d0..0000000000 --- a/docs/docbook/xslt/db2latex/lists.mod.xsl +++ /dev/null @@ -1,452 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Lists <filename>lists.mod.xsl</filename> - -
Introduction - -
- - - - - - - {\sc - - } - - - - - - \begin{itemize} - - \end{itemize} - - - - - - - - - - - - - - - - \begin{enumerate} - - - [1] - [A] - [a] - [I] - [i] - - - - \end{enumerate} - - - - - - - - - \noindent - \begin{description} - - \end{description} - - - - - %--- Item - \item - - - - - - - - - - \item[]\mbox{} % mbox is a trick to induce different typesetting decisions - - - - - - , - - - - - - - - - - - - - - - - - - l - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - 1 - - - - \begin{tabular*}{\linewidth}{ - - - - } - - - - \end{tabular*} - - - - - - - 1 - 1 - - - - - - - - - \\ - - - - - - - - - - 1 - 1 - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - - - - - \begin{tabular*}{\linewidth}{ - - - - - } - - - - \end{tabular*} - - - - - - - 1 - 1 - - - - - - - - - - - \\ - - - - - - - - - - - - - 1 - 1 - 1 - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - {\sc - - } \\ - - - - - - - - - - - - - - \\ - - - - - - - - - - - - - - { \em - - :} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - callout ??? - - - - \href{ - - }{ - } - - - callout ??? - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathelem.mod.xsl b/docs/docbook/xslt/db2latex/mathelem.mod.xsl deleted file mode 100644 index 2b085aa98d..0000000000 --- a/docs/docbook/xslt/db2latex/mathelem.mod.xsl +++ /dev/null @@ -1,222 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Math Elements <filename>mathelems.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - \begin{hypothesis}[ - - - - ] - - - \end{rem} - - - - - \begin{rem}[ - - - - ] - - - \end{rem} - - - - - - \begin{exm}[ - - - - ] - - - \end{exm} - - - - - - \begin{prop}[ - - - - ] - - - \end{prop} - - - - - - \begin{thm}[ - - - - ] - - - \end{thm} - - - - - - - \begin{defn}[ - - - - ] - - - \end{defn} - - - - - - - \begin{lem}[ - - - - ] - - - \end{lem} - - - - - - \begin{proof} - - - \end{proof} - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamsa.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamsa.ent deleted file mode 100644 index 5ecf4db216..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamsa.ent +++ /dev/null @@ -1,173 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamsb.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamsb.ent deleted file mode 100644 index 08e646c2bd..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamsb.ent +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamsc.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamsc.ent deleted file mode 100644 index cce399cf9d..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamsc.ent +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamsn.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamsn.ent deleted file mode 100644 index cddeba066e..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamsn.ent +++ /dev/null @@ -1,117 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamso.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamso.ent deleted file mode 100644 index 8ac4bdb619..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamso.ent +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isoamsr.ent b/docs/docbook/xslt/db2latex/mathml/ent/isoamsr.ent deleted file mode 100644 index 7fec582555..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isoamsr.ent +++ /dev/null @@ -1,205 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isobox.ent b/docs/docbook/xslt/db2latex/mathml/ent/isobox.ent deleted file mode 100644 index 630edc5597..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isobox.ent +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isocyr1.ent b/docs/docbook/xslt/db2latex/mathml/ent/isocyr1.ent deleted file mode 100644 index 4bcc9e416e..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isocyr1.ent +++ /dev/null @@ -1,94 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isocyr2.ent b/docs/docbook/xslt/db2latex/mathml/ent/isocyr2.ent deleted file mode 100644 index 67c477b24d..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isocyr2.ent +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isodia.ent b/docs/docbook/xslt/db2latex/mathml/ent/isodia.ent deleted file mode 100644 index ba6496300f..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isodia.ent +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isogrk1.ent b/docs/docbook/xslt/db2latex/mathml/ent/isogrk1.ent deleted file mode 100644 index 63b9f14ce8..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isogrk1.ent +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isogrk2.ent b/docs/docbook/xslt/db2latex/mathml/ent/isogrk2.ent deleted file mode 100644 index 424786cabb..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isogrk2.ent +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isogrk3.ent b/docs/docbook/xslt/db2latex/mathml/ent/isogrk3.ent deleted file mode 100644 index fa03355048..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isogrk3.ent +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isogrk4.ent b/docs/docbook/xslt/db2latex/mathml/ent/isogrk4.ent deleted file mode 100644 index 71f834042b..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isogrk4.ent +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isolat1.ent b/docs/docbook/xslt/db2latex/mathml/ent/isolat1.ent deleted file mode 100644 index 849d360aea..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isolat1.ent +++ /dev/null @@ -1,89 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isolat2.ent b/docs/docbook/xslt/db2latex/mathml/ent/isolat2.ent deleted file mode 100644 index 3049be7f1f..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isolat2.ent +++ /dev/null @@ -1,148 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isomfrk.ent b/docs/docbook/xslt/db2latex/mathml/ent/isomfrk.ent deleted file mode 100644 index 397212a643..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isomfrk.ent +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isomopf.ent b/docs/docbook/xslt/db2latex/mathml/ent/isomopf.ent deleted file mode 100644 index 806b2fb4fe..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isomopf.ent +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isomscr.ent b/docs/docbook/xslt/db2latex/mathml/ent/isomscr.ent deleted file mode 100644 index a1bb39c36c..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isomscr.ent +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isonum.ent b/docs/docbook/xslt/db2latex/mathml/ent/isonum.ent deleted file mode 100644 index e5a7002fb4..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isonum.ent +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isopub.ent b/docs/docbook/xslt/db2latex/mathml/ent/isopub.ent deleted file mode 100644 index 5591fc390e..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isopub.ent +++ /dev/null @@ -1,111 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/isotech.ent b/docs/docbook/xslt/db2latex/mathml/ent/isotech.ent deleted file mode 100644 index dc1fc01354..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/isotech.ent +++ /dev/null @@ -1,183 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/mmlalias.ent b/docs/docbook/xslt/db2latex/mathml/ent/mmlalias.ent deleted file mode 100644 index f5901b3846..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/mmlalias.ent +++ /dev/null @@ -1,529 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/ent/mmlextra.ent b/docs/docbook/xslt/db2latex/mathml/ent/mmlextra.ent deleted file mode 100644 index e76de448cc..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/ent/mmlextra.ent +++ /dev/null @@ -1,134 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/latex.entities.dtd b/docs/docbook/xslt/db2latex/mathml/latex.entities.dtd deleted file mode 100644 index 7ec703e2c7..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/latex.entities.dtd +++ /dev/null @@ -1,7 +0,0 @@ - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/latex.entities.xml b/docs/docbook/xslt/db2latex/mathml/latex.entities.xml deleted file mode 100644 index e5290aba10..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/latex.entities.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - - - \delta - \kappa - \pi - - - \beta - \sphat - \hat - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl deleted file mode 100644 index 585c744109..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl +++ /dev/null @@ -1,99 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - - \bbold Z - - - - - \bbold R - - - - - \bbold Q - - - - - \bbold N - - - - - \bbold C - - - - - \bbold P - &#x1D547; - - - - - - - - - - - \textrm{e} - - - - - \textrm{i} - - - - \NaN - - - - - true - - - - - false - - - - - \empty - - - - - \pi - - - - - \Gamma - - - - - \infty - - - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl deleted file mode 100644 index f197ca1924..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl +++ /dev/null @@ -1,723 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - - - - - - - - - {} - - - - - - - - - - - - - - - - - - - - - - - {} - {} - - - {} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - integer part of - - - - - - - - - - / - - - - - - - - - - - - - - - - { - - - {} - - - - - - !(fact) - } - - - - - - { \frac - { - - } - { - - } - } - - - - - - - { - - - \max_{ - - - , - - - } - - - \max - - - \left\{ - - , - RCAS: MathML mml:apply[mml:min] Applying templates to - - - - - | - - \right\} - } - - - - - - - { - - - \min_{ - - - , - - - } - - - \min - - - \left\{ - - RCAS: MathML mml:apply[mml:min] Applying templates to - - , - - - - - | - - \right\} - } - - - - - - - - - - - - -{ - - - - - - - - \left( \right) - - - - - - - - - - - - - \left( - - \right) - - - - - - - -} - - - - - - - - - - - - - - - - - - - - + - - - + - - - - - - - - + - - - - + - - - - - - - { - - - \left( - - \rigth) - - - - - - }^{ - - } - - - - - - - - - - - - - - mod - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - gcd - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - xor - - - - - xor - - - xor - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - , - - - - : - - - : - - - - - - - - { - - \in - - } - - - - - { - - \notin - - } - - - - - - - - - , - - - - - , - - - - : - - - : - - - - - - - - || - - - - - - - - - - - - - - arg - - - - - - - &#x0211C; - - - - - - - - - &#x02111; - - - - - - - - - lcm - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl deleted file mode 100644 index d93ea22393..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl +++ /dev/null @@ -1,97 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \left( - \right) - - - - - - \left( - \right] - - - - - - \left[ - \right) - - - - - - \left[ - \right] - - - - - - - - - - - - - - - , - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl deleted file mode 100644 index 1f3f566763..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl +++ /dev/null @@ -1,230 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - - - - - - { - { - - - - - - - - - - - + - - - \dot\textrm{i} - - - \textrm{Polar}(, - - ) - - - \frac{}{ - - } - - - - - - } - - _{} - - } - - - - - - - - - - - - - { - - - \textrm{} - - - \textrm{} - - - - - -\textrm{ - - - - - - - - - } - \dot\textrm{i} - - - +\textrm{ - - - - - - - - - } - \dot\textrm{i} - - - } - - - \dot\textrm{} - - - - - - - { - Polar - - - - - - - - - - - - - } - - - - - - - - - - { - - - - - - / - - - - - - } - - - - - - - - - - - - - - - - - - - - - - - {} - - - - - - - - - - - - - - - - - { - - \left( - - - - \right) - } - - - - - - - - - { } - - - \textrm{ } - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl deleted file mode 100644 index f37edfb4ed..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl +++ /dev/null @@ -1,49 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - - - - \begin{displaymath} - - \end{displaymath} - - - - \begin{math} - - \end{math} - - - - \begin{displaymath} - - \end{displaymath} - - - - - \section{ } - - - - diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl deleted file mode 100644 index ce3c7c9a4d..0000000000 --- a/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl +++ /dev/null @@ -1,491 +0,0 @@ - - %mmlalias; - %mmlextra; -]> - - - - - - { } - - - - - - - - - - - - - - - - - - \textrm{e} - - - \textrm{i} - - - \infty - - - - { - - } - - - - \textrm - - { - - } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \thinspace - - - \thinspace - - - \int - - - \prod - - - \sum - - - \sphat - - - \longrightarrow - - - \in - - - | - - - \textrm{d} - - - {\left( - - - \right)} - - - {\left\{ - - - \right\}} - - - {\left[ - - - \right]} - - - \max - - - \min - - - - - - - - - \operatorname{ - - } - - - - - - - \textrm{ - - } - - - - - RCAS mtext, - \textrm{ - - } - - - - - - \textrm{\hspace{ - - }} - - - Warning: mspace support does not include height or depth. - - - - - - - - - - ^{} - - - - - _{} - - - - - - - - _{} - - ^{} - - - - {} - - _{} - - ^{} - - - - - - - - - - { - - _{ - - }} - - - - - - - - - - - - - - - { - - { - - }} - - - { - - ^{ - - }} - - - - - { - - ^{ - - }} - - - - - - - - - { - - _{ - - } - ^{ - - }} - - - - - - - - - - - {\left( - - - {\left\{ - - - {\left[\, - - - {\left( - - - - - - \right)} - - - \right\}} - - - \,\right]} - - - \right)} - - - - - - - - - - - - - \frac[1pt]{ - - - \frac[1.1pt]{ - - - \frac[1.2pt]{ - - - \frac[]{ - - - - - \frac{ - - - - - }{ - - - } - - - - - - \sqrt{ - - } - - - - - - \sqrt[]{ - } - - - - - - - - - - - - - c - - - - - - - - - - - - -\begin{array}{ - -}\hline - -\end{array} - - - - - - - - - - & - - - - \\ \hline - - - - \\ \hline - - - - - - - - - - - - \textrm{e} - - - \textrm{i} - - - \textrm{ } - - - - diff --git a/docs/docbook/xslt/db2latex/mediaobject.mod.xsl b/docs/docbook/xslt/db2latex/mediaobject.mod.xsl deleted file mode 100644 index bfdd2c8c87..0000000000 --- a/docs/docbook/xslt/db2latex/mediaobject.mod.xsl +++ /dev/null @@ -1,224 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - MediaObjects <filename>mediaobject.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - XSL template for images. - - - Remarks and Bugs - - If both @width and @scale are given but @scalefit='0', whitespace is added to the left and right in order to match the specified width. - If @width is given and either @scalefit=1 or no @scale is given, then the image is scale to @width. Otherwise, @scale is used, if it is present. - If this is not the only imagedata within the figure, this will be rendered as a 'subfigure', including the caption of its enclosing mediaobject. - - - - - - - - - - - - - - - - - - \textwidth - - - - - - - - \makebox[] - - { - - - \subfigure[ - - - - ] - - {\includegraphics[ - - - scale= - - - - width= - - - height= - - - - ,angle=270 - - ]{ - - - - - - - - - }}} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/msgset.mod.xsl b/docs/docbook/xslt/db2latex/msgset.mod.xsl deleted file mode 100644 index 52ad63a87c..0000000000 --- a/docs/docbook/xslt/db2latex/msgset.mod.xsl +++ /dev/null @@ -1,76 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - : - - -

- - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl b/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl deleted file mode 100644 index 058695d71d..0000000000 --- a/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl +++ /dev/null @@ -1,398 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - 2000200120022003 - Ramon Casellas - - - Normalize and Scape strings. - -
Introduction - -
- - - - - - - - Abstract XSL template. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - /\- - / - - - - - - - - - - - /\- - / - - - - - - - - - - - - - - - - - - - - - - \textless{} - < - - - \textgreater{} - > - - - \textasciitilde{} - ~ - - - \^{} - ^ - - - \& - & - - - \# - # - - - \_ - _ - - - \$ - $ - - - \% - % - - - \{ - { - - - \} - } - - - \textbackslash \ - \textbackslash - - - \textbackslash - \ - - - - - - - - - - - - - - - - - - - - - \textasciitilde{} - ~ - - - \^{} - ^ - - - \& - & - - - \# - # - - - \_ - _ - - - \$ - $ - - - \% - % - - - \docbooktolatexgobble\string\{ - { - - - \docbooktolatexgobble\string\} - } - - - \docbooktolatexgobble\string\\ - \ - - - - - - - - - - - - - - - - - - - \& - & - - - \% - % - - - \{ - { - - - \{ - { - - - \docbooktolatexgobble\string\\ - \ - - - - - - - - - - - - - - Escape the ] character in LaTeX optional arguments (experimental) - - - - - - - {\rbrack} - ] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/para.mod.xsl b/docs/docbook/xslt/db2latex/para.mod.xsl deleted file mode 100644 index 64d6d8f01d..0000000000 --- a/docs/docbook/xslt/db2latex/para.mod.xsl +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - - - - - - $Id: para.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $ - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Paragraphs <filename>para.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - \textbf{ - - } - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl b/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl deleted file mode 100644 index 38c15e9331..0000000000 --- a/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Parts, Chapters and Appendixes <filename>part-chap-app.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - XSL template for Chapters. - - This is the main entry point for a chapter subtree. - This template processes any chapter. Outputs \chapter{title}, calls - templates and apply-templates. Since chapters only apply in books, - some assumptions could be done in order to optimize the stylesheet behaviour. - - Remarks and Bugs - - - EMPTY templates: chapter/title, - chapter/titleabbrev, - chapter/subtitle, - chapter/docinfo|chapterinfo. - - - - Affected by map. - - - - - - - - - - - - - - - - - - - - - - - - - \newcommand{\dbappendix}[1]{\chapter{#1}}% - - - \newcommand{\dbappendix}[1]{\section{#1}}% - - - - appendixes - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/pi.mod.xsl b/docs/docbook/xslt/db2latex/pi.mod.xsl deleted file mode 100644 index a4409583c8..0000000000 --- a/docs/docbook/xslt/db2latex/pi.mod.xsl +++ /dev/null @@ -1,181 +0,0 @@ - - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 200120022003 - Ramon Casellas - - - - Processing Instructions - - -
Introduction - -
- - - - - - Processing Instruction XSL template. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - No cmdsynopsis elements matched dbcmdlist PI, perhaps it's nested too deep? - - - -
- - - -
- - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - No funcsynopsis elements matched dbfunclist PI, perhaps it's nested too deep? - - - -
- - - -
- - - - - diff --git a/docs/docbook/xslt/db2latex/preamble.mod.xsl b/docs/docbook/xslt/db2latex/preamble.mod.xsl deleted file mode 100644 index ec9e5a8afc..0000000000 --- a/docs/docbook/xslt/db2latex/preamble.mod.xsl +++ /dev/null @@ -1,810 +0,0 @@ - - - - - - - - - - - - Ramon Casellas - James Devenish - - 2000200120022003 - Ramon Casellas - - - - Variables and Templates used in LaTeX Preamble Generation - - -
Introduction - This section described the variables and templates that are used in the generation of - the outtput LaTeX preamble. Basically, the LaTeX preamble depends on the XML document, that is, - on whether it is an article or a book. -
- -
Flow -
Articles - -
-
Books - -
-
- - - - - - - - - - Top level template, called by article template, - responsible of generating the LaTeX preamble according to user - XSL variables and templates. - - - Overview - If the xsl:variable latex.override - is empty, the template outputs latex.article.preamblestart - and calls generate.latex.common.preamble. Otherwise, - it outputs the value of latex.override and - exists. - - - Ramon Casellas casellas@aist.enst.fr - - - - - - - - - - - - - - - - - - - - - - - Top level template, called by book template, - responsible of generating the LaTeX preamble according to user - XSL variables and templates. - - - Overview - If the xsl:variable latex.override - is empty, the template outputs latex.book.preamblestart - and calls generate.latex.common.preamble. Otherwise, - it outputs the value of latex.override and - exists. - - - Ramon Casellas casellas@aist.enst.fr - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Generated Document class for articles. - - - - - % -------------------------------------------- - % Autogenerated LaTeX file for articles - % -------------------------------------------- - \ifx\pdfoutput\undefined - \documentclass[spanish,french,english,a4paper,10pt,twoside,twocolumn]{article} - \else - \documentclass[pdftex,spanish,french,english,a4paper,10pt,twoside,twocolumn]{article} - \fi - - - - - - % -------------------------------------------- - % Autogenerated LaTeX file for articles - % -------------------------------------------- - \ifx\pdfoutput\undefined - \documentclass[ - - , - - , - - ]{ - - - article - - } - \else - \documentclass[pdftex, - - , - - , - - ]{ - - - article - - } - \fi - - - - Generated Document class for books. - - - - - % ------------------------------------------------------------ - % Autogenerated LaTeX file for books - % ------------------------------------------------------------ - \ifx\pdfoutput\undefined - \documentclass[spanish,french,english,a4paper,twoside,openright,10pt,final]{report} - \else - \documentclass[pdftex,spanish,french,english,a4paper,twoside,openright,10pt,final]{report} - \fi - - - - - - % ------------------------------------------------------------ - % Autogenerated LaTeX file for books - % ------------------------------------------------------------ - \ifx\pdfoutput\undefined - \documentclass[ - - , - - , - - ]{ - - - report - - } - \else - \documentclass[pdftex, - - , - - , - - ]{ - - - report - - } - \fi - - - - - - Common LaTeX preamble shared by articles and books, and other - document classes. Most of the packages and package options are managed here - - - - The LaTeX preamble, after the document class and before the \begin{document} - command. - - - - - - - - - \usepackage{graphicx} - - - - - - - - - \usepackage{fancyhdr} - - - - \renewcommand{\headrulewidth}{0.4pt} - \renewcommand{\footrulewidth}{0.4pt} - - - % ---------------------- - % Most Common Packages - % ---------------------- - \usepackage{makeidx} - \usepackage{varioref} - \usepackage{latexsym} - \usepackage{enumerate} - - - \usepackage{fancybox} - - \usepackage{float} - \usepackage{ragged2e} - - \usepackage[]{babel} - - - - \usepackage{fancyvrb} - \makeatletter\@namedef{FV@fontfamily@default}{\def\FV@FontScanPrep{}\def\FV@FontFamily{}}\makeatother - - \fvset{obeytabs=true,tabsize= - - } - - - \usepackage{isolatin1} - \usepackage{parskip} - \usepackage{rotating} - \usepackage{subfigure} - \usepackage{tabularx} - \usepackage{umoline} - \usepackage{url} - - - - % --------------- - % Document Font - % --------------- - \usepackage{} - - - \def\keywords{\vspace{-.3em} - \if@twocolumn - \small{\itshape - - keywords - - }\/\bfseries---$\!$% - \else - \begin{center}\small\bfseries - - keywords - - \end{center}\quotation\small - \fi} - \def\endkeywords{\vspace{0.6em}\par\if@twocolumn\else\endquotation\fi - \normalsize\rmfamily} - - - - - - - - - - - % -------------------------------------------- - % $latex.caption.swapskip enabled for $formal.title.placement support - \newlength{\docbooktolatextempskip} - \newcommand{\captionswapskip}{\setlength{\docbooktolatextempskip}{\abovecaptionskip} - \setlength{\abovecaptionskip}{\belowcaptionskip} - \setlength{\belowcaptionskip}{\docbooktolatextempskip}} - - - \newcommand{\captionswapskip}{} - - - - % -------------------------------------------- - % Better linebreaks - \newcommand{\docbookhyphenatedot}[1]{{\hyphenchar\font=`\.\relax #1\hyphenchar\font=`\-}} - \newcommand{\docbookhyphenatefilename}[1]{{\hyphenchar\font=`\.\relax #1\hyphenchar\font=`\-}} - \newcommand{\docbookhyphenateurl}[1]{{\hyphenchar\font=`\/\relax #1\hyphenchar\font=`\-}} - - - - - Unavoidable LaTeX preamble shared by articles and books - - Contains custom commands that you just can't get rid of! - - - - % -------------------------------------------- - \makeatletter - - \newcommand{\href}[1]{{}} - \newcommand{\hyperlink}[1]{{}} - \newcommand{\hypertarget}[2]{#2} - - - \usepackage[ - - ]{ucs} - - - \catcode`\&=\active\def&{\@ifnextchar##{\@docbooktolatexunicode\@gobble}{\&}} - - - - \def\@docbooktolatexunicode#1;{\edef\@dbtemp{#1}\unichar{\@dbtemp}} - - - \usepackage[utf8]{inputenc} - - s -% Blame j-devenish (at) users.sourceforge.net -% In any other LaTeX context, this would probably go into a style file. -\newcommand{\docbooktolatexusefootnoteref}[1]{\@ifundefined{@fn@label@#1}% - {\hbox{\@textsuperscript{\normalfont ?}}% - \@latex@warning{Footnote label `#1' was not defined}}% - {\@nameuse{@fn@label@#1}}} -\newcommand{\docbooktolatexmakefootnoteref}[1]{% - \protected@write\@auxout{}% - {\global\string\@namedef{@fn@label@#1}{\@makefnmark}}% - \@namedef{@fn@label@#1}{\hbox{\@textsuperscript{\normalfont ?}}}% - } -% -------------------------------------------- -% Hacks for honouring row/entry/@align -% (\hspace not effective when in paragraph mode) -% Naming convention for these macros is: -% 'docbooktolatex' 'align' {alignment-type} {position-within-entry} -% where r = right, l = left, c = centre -\newcommand{\docbooktolatexalignrl}{\protect\ifvmode\raggedleft\else\hfill\fi} -\newcommand{\docbooktolatexalignrr}{\protect} -\newcommand{\docbooktolatexalignll}{\protect\ifvmode\raggedright\else\fi} -\newcommand{\docbooktolatexalignlr}{\protect\ifvmode\else\hspace*\fill\fi} -\newcommand{\docbooktolatexaligncl}{\protect\ifvmode\centering\else\hfill\fi} -\newcommand{\docbooktolatexaligncr}{\protect\ifvmode\else\hspace*\fill\fi} -\ifx\captionswapskip\@undefined\newcommand{\captionswapskip}{}\fi -\makeatother -]]> - - - - - - - - - - - - - - % -------------------------------------------- - % Commands to manage/style/create floats - % figures, tables, algorithms, examples, eqn - % -------------------------------------------- - \floatstyle{ruled} - \restylefloat{figure} - \floatstyle{ruled} - \restylefloat{table} - \floatstyle{ruled} - \newfloat{program}{ht}{lop}[section] - \floatstyle{ruled} - \newfloat{example}{ht}{loe}[section] - \floatname{example}{ - - example - - } - \floatstyle{ruled} - \newfloat{dbequation}{ht}{loe}[section] - \floatname{dbequation}{ - - equation - - } - \floatstyle{boxed} - \newfloat{algorithm}{ht}{loa}[section] - \floatname{algorithm}{Algorithm} - - - - - - - - - - - Default Value: - - \usepackage{ifthen} - % -------------------------------------------- - % Check for PDFLaTeX/LaTeX - % -------------------------------------------- - \newif\ifpdf - \ifx\pdfoutput\undefined - \pdffalse % we are not running PDFLaTeX - \else - \pdfoutput=1 % we are running PDFLaTeX - \pdftrue - \fi - % -------------------------------------------- - % Load graphicx package with pdf if needed - % -------------------------------------------- - \ifpdf - \usepackage[pdftex]{graphicx} - \pdfcompresslevel=9 - \else - \usepackage{graphicx} - \fi - - - - Ramon Casellas casellas@aist.enst.fr - - - - - \usepackage{ifthen} - % -------------------------------------------- - % Check for PDFLaTeX/LaTeX - % -------------------------------------------- - \newif\ifpdf - \ifx\pdfoutput\undefined - \pdffalse % we are not running PDFLaTeX - \else - \pdfoutput=1 % we are running PDFLaTeX - \pdftrue - \fi - % -------------------------------------------- - % Load graphicx package with pdf if needed - % -------------------------------------------- - \ifpdf - \usepackage[pdftex]{graphicx} - \pdfcompresslevel=9 - \else - \usepackage{graphicx} - \fi - - - - - - - Manage the part of the preamble that handles the hyperref package. - - This template outputs the LaTeX code \usepackage[...]{hyperref} - in order to use hyperlinks, backrefs and other goodies. If PDF support is activated, - outputs laTeX code to detect whether the document is being compiled with - pdflatex or latex to supply the - right parameters (pdftex, dvips, etc). - To Do The package options should be optained - from XSL variables. - Default Value with PDF support - - % -------------------------------------------- - % Load hyperref package with pdf if needed - % -------------------------------------------- - \ifpdf - \usepackage[pdftex,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref} - \else - \usepackage[dvips,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref} - \fi - % -------------------------------------------- - - - Default Value without PDF support - - % -------------------------------------------- - % Load hyperref package - % -------------------------------------------- - \usepackage[dvips,bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage]{hyperref} - - - - - - - - - % -------------------------------------------- - % Load hyperref package with pdf if needed - % -------------------------------------------- - \ifpdf - \usepackage[pdftex, - - , - - ]{hyperref} - \else - \usepackage[dvips, - - , - - ]{hyperref} - \fi - % -------------------------------------------- - - - % -------------------------------------------- - % Load hyperref package - % -------------------------------------------- - \usepackage[dvips, - - , - - ]{hyperref} - - - - - - - - - - - - - - - - - - - - - Manage the math related preamble - - - - - - - % -------------------------------------------- - % Math support - % -------------------------------------------- - \usepackage{amsmath,amsthm, amsfonts, amssymb, amsxtra,amsopn} - %\newtheorem{thm}{Theorem}[section] - %\newtheorem{cor}[section]{Corollary} - %\newtheorem{lem}[section]{Lemma} - %\newtheorem{defn}[section]{Definition} - %\newtheorem{prop}[section]{Proposition} - %\newtheorem{ax}{Axiom} - %\newtheorem{theorem}[section]{Theorem} - %\newtheorem{corollary}{Corollary} - %\newtheorem{lemma}{Lemma} - %\newtheorem{proposition}{Proposition} - %\theoremstyle{definition} - %\newtheorem{definition}{Definition} - %\theoremstyle{remark} - %\newtheorem{rem}{Remark} - %\newtheorem*{notation}{Notation} - %\newcommand{\ntt}{\normalfont\ttfamily} - %\newcommand{\thmref}[1]{Theorem~\ref{#1}} - %\newcommand{\secref}[1]{\S\ref{#1}} - %\newcommand{\lemref}[1]{Lemma~\ref{#1}} - \newcommand{\bysame}{\mbox{\rule{3em}{.4pt}}\,} - \newcommand{\A}{\mathcal{A}} - \newcommand{\B}{\mathcal{B}} - \newcommand{\XcY}{{(X,Y)}} - \newcommand{\SX}{{S_X}} - \newcommand{\SY}{{S_Y}} - \newcommand{\SXY}{{S_{X,Y}}} - \newcommand{\SXgYy}{{S_{X|Y}(y)}} - \newcommand{\Cw}[1]{{\hat C_#1(X|Y)}} - \newcommand{\G}{{G(X|Y)}} - \newcommand{\PY}{{P_{\mathcal{Y}}}} - \newcommand{\X}{\mathcal{X}} - \newcommand{\wt}{\widetilde} - \newcommand{\wh}{\widehat} - % -------------------------------------------- - %\DeclareMathOperator{\per}{per} - \DeclareMathOperator{\cov}{cov} - \DeclareMathOperator{\non}{non} - \DeclareMathOperator{\cf}{cf} - \DeclareMathOperator{\add}{add} - \DeclareMathOperator{\Cham}{Cham} - \DeclareMathOperator{\IM}{Im} - \DeclareMathOperator{\esssup}{ess\,sup} - \DeclareMathOperator{\meas}{meas} - \DeclareMathOperator{\seg}{seg} - % -------------------------------------------- - - - - - - - - - Declared graphic extensions - -This template checks whether the user has overriden grafic.default.extension -Otherwise, declares .pdf, .png, .jpg if using pdflatex and .eps if using latex. - - - - \DeclareGraphicsExtensions{ - - . - - - } - - - - - \ifpdf - \DeclareGraphicsExtensions{.pdf,.png,.jpg} - \else - \DeclareGraphicsExtensions{.eps} - \fi - - - \DeclareGraphicsExtensions{.eps} - - - - - - - -]]> - - - - - - - - - \DeclareGraphicsExtensions{ - - . - - - } - - - - - \ifpdf - \DeclareGraphicsExtensions{.pdf,.png,.jpg} - \else - \DeclareGraphicsExtensions{.eps} - \fi - - - \DeclareGraphicsExtensions{.eps} - - - - - - - - - - \catcode`\&=4 &\catcode`\&=\active - - - & - - - - - diff --git a/docs/docbook/xslt/db2latex/preface.mod.xsl b/docs/docbook/xslt/db2latex/preface.mod.xsl deleted file mode 100644 index d56c0ec5cb..0000000000 --- a/docs/docbook/xslt/db2latex/preface.mod.xsl +++ /dev/null @@ -1,109 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Preface <filename>preface.mod.xsl</filename> - -
Introduction - -
- - - - - - -\newpage -% ------------------------------------------------------------- -% Preface -% ------------------------------------------------------------- -\chapter*{ - - - - - - - - preface - - - -} - - - - - - - - - - - - - - - - - - - - - \section*{ - -} - - - - - - \subsection*{ - -} - - - - - - \subsubsection*{ - -} - - - - - - diff --git a/docs/docbook/xslt/db2latex/procedure.mod.xsl b/docs/docbook/xslt/db2latex/procedure.mod.xsl deleted file mode 100644 index c53cf39c68..0000000000 --- a/docs/docbook/xslt/db2latex/procedure.mod.xsl +++ /dev/null @@ -1,162 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Procedures <filename>procedure.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - -Procedure XSL Template. - - - - - - - - - - - - - - - - - \begin{enumerate} - - \end{enumerate} - - - \begin{enumerate} - - \end{enumerate} - - - - - - - - - - - { - - { - - - - - - - - - }} - - - - - - - -Step XSL Template. - - - - - - - - - - - \item{{ - - { - - }} - - - \item{ - - - - } - - - - - - - - - - - - - - - - - -SubSteps XSL Template. - - - - \begin{enumerate} - - \end{enumerate} - -]]> - - - - - - \begin{enumerate} - - \end{enumerate} - - - - diff --git a/docs/docbook/xslt/db2latex/qandaset.mod.xsl b/docs/docbook/xslt/db2latex/qandaset.mod.xsl deleted file mode 100644 index c93d56e6b3..0000000000 --- a/docs/docbook/xslt/db2latex/qandaset.mod.xsl +++ /dev/null @@ -1,406 +0,0 @@ - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - QandaSet <filename>qandaset.mod.xsl</filename> - -
- Introduction -
- - - - - - - - - - - - - - - - - - - - - % ------------------------------------------------------------- - % QandASet - % ------------------------------------------------------------- - - - \subsubsection*{ - - - \subsection*{ - - - \section*{ - - - \chapter*{ - - - - - - - - F.A.Q. - - - } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - % ----------- - % QandADiv - % ----------- - \noindent\begin{minipage}{\linewidth} - \vspace{0.25em}\hrule\vspace{0.25em} - - - \paragraph*{ - - - \subsubsection*{ - - - \subsection*{ - - - \section*{ - - - - - - - - F.A.Q. Part - - - } - - - \hrule\vspace{0.25em} - \end{minipage} - - - - - - - - \noindent{} - - .~ - - \newline - - \vspace{0.25em}\hrule - - - \vspace{1em} - \noindent{} - - .~ - - \newline - - - - - \vspace{1em} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\textbf{Q:}~\textit{ - -} - - - - - - - - - - - - -\noindent\textbf{A:}~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - question - answer - qandadiv - qandaset - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/refentry.mod.xsl b/docs/docbook/xslt/db2latex/refentry.mod.xsl deleted file mode 100644 index 52d2b297d5..0000000000 --- a/docs/docbook/xslt/db2latex/refentry.mod.xsl +++ /dev/null @@ -1,184 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - References and Entries <filename>refentry.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - - ) - - - - - - - - - - - - - - - - - \subsection*{ - - - - } - - - - , - - - - - - $-$ - - - - - - - - - - - : - - - - - - - - - - - \subsection*{Synopsis} - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/revision.mod.xsl b/docs/docbook/xslt/db2latex/revision.mod.xsl deleted file mode 100644 index a041aed5c3..0000000000 --- a/docs/docbook/xslt/db2latex/revision.mod.xsl +++ /dev/null @@ -1,215 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Revision Management <filename>revision.mod.xsl</filename> - -
Introduction - - This file defines the DB2LaTeX XSL templates for revision - and its children. The basic mapping is to output a LaTeX table and a table - row for each revision. - -
- - - - - - - - - - - revhistory XSL template - - User variables - - latex.output.revhistory - - - This XSL template depends on the value of latex.output.revhistory. - If this variable is "1", the XSL template calls map.begin, then - applies templates and finally calls map.end - - - - - - RCAS: Processing Revision History - - - - - - - - - - - - - - revhistory/revision XSL template - - Each revhistory/revision corresponds to a LaTeX table row (see revhistory) - containing the revision number, the date, author initials and the description/ - remarks of the revision. - - - - - - - - - - - - - - - - & - - & - - - - nbsp - - - - - - - - \\ \hline - - - \multicolumn{3}{|l|}{ - - - } \\ \hline - - - - - - - - - - - revision/authorinitials XSL template - - Applies templates and outputs a "comma" if the node position is not - last() - - - - - - - - , - - - - - - - - - - - revision/revnumber XSL template - - Applies templates. - - - - - - - - - - - - - - - - - revision/date XSL template - - Applies templates. - - - - - - - - - - - - - - - revision/revremark XSL template - - Applies templates. - - - - - - - - - - - - - - - revision/revdescription XSL template - - Applies templates. - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/sections.mod.xsl b/docs/docbook/xslt/db2latex/sections.mod.xsl deleted file mode 100644 index 2e74ce3890..0000000000 --- a/docs/docbook/xslt/db2latex/sections.mod.xsl +++ /dev/null @@ -1,147 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Sections <filename>sections.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DB2LaTeX: recursive section|simplesect > 5 Not well Supported - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DB2LaTeX: recursive section|simplesect > 5 Not well Supported - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/set.mod.xsl b/docs/docbook/xslt/db2latex/set.mod.xsl deleted file mode 100644 index 8f87fb1071..0000000000 --- a/docs/docbook/xslt/db2latex/set.mod.xsl +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Sets <filename>set.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/sgmltag.mod.xsl b/docs/docbook/xslt/db2latex/sgmltag.mod.xsl deleted file mode 100644 index 893a2b6d4d..0000000000 --- a/docs/docbook/xslt/db2latex/sgmltag.mod.xsl +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - SGML Tags <filename>sgmltag.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - - - - - - - - element - - - - - - - - - - - - - - - - - </ - - > - - - - - - - \& - - ; - - - - - - - \&\# - - ; - - - - - - - \% - - ; - - - - - - - <? - - ?> - - - - - - - <? - - ?> - - - - - - - < - - > - - - - - - - < - - /> - - - - - - - <!-- - - --> - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/synop-oop.mod.xsl b/docs/docbook/xslt/db2latex/synop-oop.mod.xsl deleted file mode 100644 index 93b29c1229..0000000000 --- a/docs/docbook/xslt/db2latex/synop-oop.mod.xsl +++ /dev/null @@ -1,689 +0,0 @@ - - ]> - - - - - - - - - - - - - - - - - - - - - - - - - Unrecognized language on classsynopsis: - - - - - - - - - - - - - - - 
-	    
-	    
-		 extends
-		
-		
-		    &RE;    
-		
-	    
-	    
-		implements
-		
-		
-		    &RE;    
-		
-	    
-	    
-		throws
-		
-	    
-	     {&RE;&RE;
-	    
-	    }
-
- - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - , - - - - - - - - - , - - - - - - - - - - - ; - - - - - - - - - - - - - - - - - - - - = - - - - - - - void - - - - - - - - - - - - - - 0 - - ,&RE; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - - - - ) - - &RE; throws - - - ; - - - - - - - 
-	    
-	    
-		: 
-		
-		
-		    &RE;    
-		
-	    
-	    
-		 implements
-		
-		
-		    &RE;    
-		
-	    
-	    
-		 throws
-		
-	    
-	     {&RE;&RE;
-	    
-	    }
-
- - - - - - - - - , - - - - - - - - - - - - - - - - , - - - - - - - - - , - - - - - - - - - , - - - - - - - - - - - ; - - - - - - - - - - - - - - - - - - - - = - - - - - - - void - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - - ) - - &RE; throws - - - ; - - - - - - - 
-	    interface 
-	    
-	    
-		: 
-		
-		
-		    &RE;    
-		
-	    
-	    
-		 implements
-		
-		
-		    &RE;    
-		
-	    
-	    
-		 throws
-		
-	    
-	     {&RE;&RE;
-	    
-	    }
-
- - - - - - - - - , - - - - - - - - - - - - - - - - , - - - - - - - - - , - - - - - - - - - , - - - - - - - - - - - ; - - - - - - - - - - - - - - - - - - - - = - - - - - - - void - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - - ) - - &RE; raises( - - ) - - ; - - - - - - - - - - - 
-	    package 
-	    
-	    ;&RE;
-
-	    
-		@ISA = (
-		
-		);&RE;
-	    
-
-	    
-
- - - - - - - - - , - - - - - - - - - - - - - - - - , - - - - - - - - - , - - - - - - - - - , - - - - - - - - - - - ; - - - - - - - - - - - - - - - - - - - - = - - - - - - - void - - - - - - - - - - - , - - - - - - - - - - - - - - - sub - - - { ... }; - - - diff --git a/docs/docbook/xslt/db2latex/synop-struct.mod.xsl b/docs/docbook/xslt/db2latex/synop-struct.mod.xsl deleted file mode 100644 index 1ffe2fc463..0000000000 --- a/docs/docbook/xslt/db2latex/synop-struct.mod.xsl +++ /dev/null @@ -1,246 +0,0 @@ - - - - - - - - - - - - - \begin{list}{}{\setlength{\itemindent}{-\leftmargin}\setlength{\parsep}{0mm}} - - \item\textbf{ - - } - - \item\raggedright\texttt{ - - } - \end{list} - - - - - - - - - - {\itshape - - } - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - {\em ( ) } - - - - - - - - - - -

- - ( - - ) - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - \textbf{ } - - - - - - - - - - - - (void); - - - (); - - - - - - ( ... ); - - - - - - - ( - - - - - - - - - - - , - - - ); - - - - - - - - - - - - - - - - - , - - - - - - - \newline - - ; - - - - ( - - ) - - - diff --git a/docs/docbook/xslt/db2latex/table.mod.xsl b/docs/docbook/xslt/db2latex/table.mod.xsl deleted file mode 100644 index 0edb4ad2cc..0000000000 --- a/docs/docbook/xslt/db2latex/table.mod.xsl +++ /dev/null @@ -1,743 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - Tables <filename>table.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - - XSL template for docbook tables. - - - Remarks and Bugs - - - - Default Behaviour - - - - - - - - - - - - - - \caption{ - - } - - - - \captionswapskip{} - - \captionswapskip{} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >{ - - - \hsize= - - \hsize - - - \RaggedRight - \RaggedLeft - \Centering - Table column char alignment is not supported. - - } - - - X - - - p{} - - - - | - - - - - l - r - c - X - cTable column char alignment is not supported. - c - - - | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >{\RaggedRight} - >{\RaggedLeft} - >{\Centering} - Table column char alignment is not supported. - - p{} - - | - - - - - l - r - c - l - cTable column char alignment is not supported. - c - - - | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - all - - - - - - - - - - - 1 - - - - 1 - - - - 1 - - - 0 - - - - - - 1 - - - - \begin{tabularx}{\linewidth}{ - - - \begin{minipage}{\linewidth} - \begin{tabular}{ - - - - | - - - - - - - - - - - - - - - - - - - - | - - } - - \hline - - - - - - \hline - - - - \end{tabularx} - - - \end{tabular} - \end{minipage} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \tabularnewline - - - - - - - - - - - - - - - - - - - \hline - - - - - - - - - - \tabularnewline - - - - - - - - - - - - - - - - - - -1 - - - - \multicolumn{ - - |}{ - - l - r - c - cTable entry char alignment is not supported. - c - - - } - - - - - \docbooktolatexalignll - \docbooktolatexalignrl - \docbooktolatexaligncl - Table entry char alignment is not supported. - - - { - - \rotatebox{90} - entry[@rotate='1' and @align!=''] probably doesn't work. - - { - - The morerows attribute is not supported. - - - - }} - - - - \docbooktolatexalignlr - \docbooktolatexalignrr - \docbooktolatexaligncr - - - - - - - - - - - - - - - - - - td - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -   - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - - 1 - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/texmath.mod.xsl b/docs/docbook/xslt/db2latex/texmath.mod.xsl deleted file mode 100644 index 47036c56ac..0000000000 --- a/docs/docbook/xslt/db2latex/texmath.mod.xsl +++ /dev/null @@ -1,117 +0,0 @@ - - - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - - LaTeX Only Commands <filename>texmath.mod.xsl</filename> - -
Introduction - -
- - - - - - - \ensuremath{ - - } - - - \begin{displaymath} - - - \end{displaymath} - - - - - - - - - - - - - - - - \input{} - - - - \input{} - - - - - \input{} - - - - - - - - \input{} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/vars.mod.xsl b/docs/docbook/xslt/db2latex/vars.mod.xsl deleted file mode 100644 index e20fb59ce2..0000000000 --- a/docs/docbook/xslt/db2latex/vars.mod.xsl +++ /dev/null @@ -1,937 +0,0 @@ - - - - - - - - - - - - CasellasRamon - DevenishJames - - - 2000200120022003 - Ramon Casellas - - - - XSL Variables and Parameters - - -
Introduction - - This is technical reference documentation for the DocBook XSL - Stylesheets. It documents (some of) the parameters, templates, and - other elements of the stylesheets. -
- - - - - - java - - - - kr - - 0 - - - - Display comment elements? - - Control the display of comments and remarks. - - - - - - - - - - - - - number - , - - Cull table-of-contents entries that are deeply nested - - Specifies the maximum depth before sections are omitted from the table of contents. - - - 4 - - - Control the automatic numbering of section, parts, and chapters - - - Specifies the maximum depth before sections cease to be uniquely numbered. - This is passed to LaTeX using the secnumdepth counter. - Therefore, it is possible to use a value of 0 (zero) to disable section numbering. - A value of -1 will disable the numbering of parts and chapters, too. - - - - 4 - - 1 - - - - Control mediaobject selection methods - - This controls how DB2LaTeX behaves when a figure contains - multiple mediaobjects. When enabled, DB2LaTeX will choose - the mediaobject with the "LaTeX" or "TeX" role, if present. Otherwise, the first mediaobject - is chosen. - - - 1 - - - Control mediaobject selection methods - - When is enabled, this variable - can be used to specify the mediaobject role that your document uses for LaTeX output. - DB2LaTeX will try to use this role before using the "LaTeX" or "TeX" roles. - For example, some authors may choose to set this to "PDF". - - - - - - Specifies where formal object titles should occur - - - Titles for the formal object types (figure, example, quation, table, and procedure) - can be placed before or after those objects. The keyword before - is recognised. All other strings qualify as after. - - - - - figure not_before - example before - equation not_before - table before - procedure before - - - - Control the appearance of page numbers in cross references - - - When enabled, xrefs will include page - numbers after their generated cross-reference text. - - - - 0 - - - Control the display of URLs after ulinks - - - When this option is enabled, and a ulink has a URL that is different - from the displayed content, the URL will be typeset after the content. - If the URL and content are identical, only one of them will appear. - Otherwise, the URL is hyperlinked and the content is not. - - - - 0 - - - Control the generation of footnotes for ulinks - - - When this option is enabled, a ulink that has content different to its - URL will have an associated footnote. The contents of the footnote - will be the URL. If the ulink is within a footnote, the URL is shown - after the content. - - - - 0 - - - - - Override DB2LaTeX's preamble with a custom preamble. - - - When this variable is set, the entire DB2LaTeX premable will be superseded. - You should not normally need or want to use this. - It may cause LaTeX typesetting problems. This is a last resort or - expert feature. - - - - - - - Control Unicode character handling. - - - Normally, XSLT processors will convert SGML character entities into - Unicode characters and DB2LaTeX doesn't have much chance to do anything - toward converting them to LaTeX equivalents. We do not yet know how we - can solve this problem best. - - - Proposed values: 'catcode', 'unicode', 'extension'. - Currently only 'catcode' is supported. All other values will - cause no special handling except for certain mappings in MathML. - In future, perhaps the 'unicode' LaTeX package could be of assistance. - 'Extension' could be an XSLT extension that handles the characters - using a mapping table. - - - - - - - Control the escaping of alt text - - - Text within alt elements is assumed to - be valid LaTeX and is passed through unescaped by default. If this is not - appropriate for your document, set this variable to something other than - '1'. - - - - 1 - - - Control the use of alt text - - - By default, DB2LaTeX assumes that alt - text should be typeset in preference to any - mediaobjects. - - - - 1 - - - - - Whether to apply templates for section titles. - - - Controls whether section titles will be generated by - applying templates or by conversion to string values. - When enabled, templates will be applied. This enables template - expression in titles but may have problematic side-effects such - as nested links. - - - - This variable does not influence all title - elements. Some may have their own variables or not be configurable. - - - - - 1 - - - - - - - Whether to apply templates for admonition titles. - - - Controls whether admonition titles will be generated by - applying templates or by conversion to string values. - When enabled, templates will be applied. - - - - 1 - - - - - - - - Control imagedata selection. - - This controls how DB2LaTeX behaves when a mediaobject contains - multiple imagedata. When non-empty, DB2LaTeX will exclude - imagedata that have a format no listed within this variable. - - - - - - - - - - - Improved typesetting of captions - - - DB2LaTeX supports $formal.title.placement - as a mechanism for choosing whether captions will appear above or below the objects they describe. - - However, LaTeX will often produce an ugly result when captions occur - above their corresponding content. This usually arises because of - unsuitable \abovecaptionskip and \belowcaptionskip. - - - This variable, when set to '1', authorises DB2LaTeX to swap the caption - 'skip' lengths when a caption is placed above its - corresponding content. This is enabled by default. - - - - 1 - - - - - - - DB2LaTeX allows using an (externally generated) cover page - - - You may supply a LaTeX file that will supersede DB2LaTeX's default - cover page or title. If the value of this variable is non-empty, the - generated LaTeX code includes \input{filename}. Otherwise, it uses the - \maketitle command. - - - Bear in mind that using an external cover page breaks the - "encapsulation" of DocBook. Further revisions of these stylesheets - will add chunking support, and the automation of the cover file - generation. - - - - title - - - - - - DB2LaTeX document class - - - This variable is normally empty and the stylesheets will determine - the correct document class according to whether the document is a - book or an article. If you wish to use your own document class, - put its non-empty value in this variable. It will apply for both - books and articles. - - - - - - - DB2LaTeX document class options - - - These are the first options to be passed to \documentclass - The common options are set to french,english by default. - They will be augmented or superseded by article/book options (see $latex.documentclass.article and $latex.documentclass.book) and pdftex/dvips options (see $latex.documentclass.pdftex and $latex.documentclass.dvips). - - - - french,english - - - DB2LaTeX document class options for articles - - - The article options are set to a4paper,10pt,twoside,twocolumn by default. - These are the intermediate options to be passed to \documentclass, - between the common options and the pdftex/dvips options. - - - - a4paper,10pt,twoside,twocolumn - - - DB2LaTeX document class options for books - - - The book options are set to a4paper,10pt,twoside,openright by default. - These are the intermediate options to be passed to \documentclass, - between the common options and the pdftex/dvips options. - - - - a4paper,10pt,twoside,openright - - - DB2LaTeX document class options for pdfTeX output - - - The pdfTeX options are empty by default. - These are the last options to be passed to \documentclass - and override the common/article/book options. - - - - - - - DB2LaTeX document class options for dvips output - - - The dvips options are empty by default. - These are the last options to be passed to \documentclass - and override the common/article/book options. - - - - - - - LaTeX location for admonition graphics - - The file path that will be passed to LaTeX in order to find admonition graphics. - An empty value suppresses the use of admonition graphics. - If your figures are in the current directory then use a value of - . (i.e. the full stop or period on its own) to signify this. - - - figures - - - - DB2LaTeX graphics admonitions size - - - Is passed as an optional parameter for \includegraphics and - can take on any such legal values (or be empty). - - - - width=1cm - - - - - - - Control which references are cited in the bibliography - - - The DB2LaTeX generated bibliography (bibitems) may either - include all biblioentries found in the document, or only thee ones explicitly - cited with citation. - - Two values are possible: all or cited. - - - all - - - - - Control the output of the \bibliography{.bib}. - - - The value of this parameter is output. - An example is citations.bib, - if your BibTeX file has that name. - - - - - - - Adjust bibliography formatting - - The environment bibliography accepts a parameter that indicates - the widest label, which is used to correctly format the bibliography - output. The value of this parameter is output inside the - \begin{thebibliography[]} LaTeX command. - - - WIDELABEL - - - - - Choose whether to use the unicode LaTeX package - See the unicode documentation for details. - - 0 - - - Select the optional parameter(s) for the unicode LaTeX package - See the unicode documentation for details. - - - - - Select the optional parameter for the babel LaTeX package - See the babel documentation for details. - - french - - - Toggle the use of the isolatin1 LaTeX package - - 1 - - - Toggle the use of the hyperref LaTeX package - This is used extensively for hyperlinking within documents. - - 1 - - - Toggle the use of the fancybox LaTeX package - This is essential for admonitions. - - 1 - - - Toggle the use of the fancyvrb LaTeX package - Provides support for tabbed whitespace in verbatim environments. - See also . - - 1 - - - Choose indentation for tabs in verbatim environments - When is enabled, - this variable sets the width of a tab in terms of an equivalent number of spaces. - - 3 - - - Toggle the use of the fancyhdr LaTeX package - Provides page headers and footers. Disabling support for - this package will make headers and footer go away. - - 1 - - - Toggle the use of the parskip LaTeX package - Support a block paragraph style as opposed to - indented. - - 0 - - - Toggle the use of the subfigure LaTeX package - Used to provide nice layout of multiple mediaobjects in figures. - - 1 - - - Toggle the use of the rotating LaTeX package - - 1 - - - Toggle the use of the tabularx LaTeX package - Used to provide certain table features. Has some incompatabilities - with packages, but also solves some conflicts that the regular tabular - environment has. - - 1 - - - Toggle the use of the umoline LaTeX package - Provide underlining. - - 0 - - - Toggle the use of the url LaTeX package - Provide partial support for hyperlinks. - - 1 - - - Toggle the use of the makeidx LaTeX package - Support index generation. - - 1 - - - DB2LaTeX hyphenation linebreak tricks - - - Usually, LaTeX does not perform hyphenation in teletype (monospace) - text. This can lead to formatting problems. But certain monospace texts, such as - URLs and filenames, have natural breakpoints such as full stops - and slashes. DB2LaTeX's tttricks exploit a hyphenation trick in - order to provide line wrapping in the middle of monospace text. Set this to '1' - to enable these tricks (they are not enabled by default). See also the FAQ. - - - - 0 - - - DB2LaTeX hyperref options - - - The hyperref options are set to bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage by default. - You may wish to specify additional options using latex.hyperref.param.pdftex - or latex.hyperref.param.dvips. - - - - bookmarksnumbered,colorlinks,backref, bookmarks, breaklinks, linktocpage - - - DB2LaTeX hyperref options for pdfTeX output - - - This variable is empty by default. See the hyperref documentation for further information. - - - - pdfstartview=FitH - - - DB2LaTeX hyperref options for dvips output - - - This variable is empty by default. See the hyperref documentation for further information. - - - - - - Left Header - Center Header - Right Header - Left Footer - Center Footer - Right Footer - - - Control the style of step titles - - Step titles are typeset in small caps but if - this option is set to a LaTeX command, such as \itshape{}, then - that command will precede the title and it will be typeset accordingly. - - - \bf - - - Control the style of article titles within books - - - - \Large\textbf - - - Control the style of article titles - - - - \textbf - - - Override DB2LaTeX's choice of LaTeX page numbering style - - By default, DB2LaTeX will choose the 'plain' or 'fancy' page styles, - depending on . If non-empty, this - variable overrides the automatic selection. An example would be the literal - string 'empty', to eliminate headers and page numbers. - - - - - - Control the style of procedure titles - - Procedure titles are typeset in small caps but if - this option is set to a LaTeX command, such as \itshape{}, then - that command will precede the title and it will be typeset accordingly. - - - \sc - - - Control the style of figure titles - - Figure titles are typeset in the default typeface (usually 'roman') but if - this option is set to a LaTeX command, such as \itshape{}, then - that command will precede the title and it will be typeset accordingly. - - - - - - Controls the output of LaTeX commands to support the generation - of PDF files. - - If this parameter is set to 1, the stylesheets generate code to - detect if it is either latex or pdflatex - the shell command that is being used to compile the LaTeX text file. Some - packages (graphicx, hyperref) are used - with the right parameters. Finally, the graphic extensions declared, to use in - \includegraphics commands depends also on which command is - being used. If this parameter is set to zero, such code is not generated (which - does not mean that the file cannot compile with pdflatex, but some strange issues - may appear). DEFAULT: 1 Only more code is generated. - - - - 1 - - - - - Format the output of tabular headings. - - - - - - - - - - - Controls the output of LaTeX packages and commands to support - documents with math commands and environments.. - - If this parameter is set to 1, the stylesheets generate code to - DEFAULT: 1 Only more code is generated. - - - - 1 - - - - - Controls if the revision history table is generated as the first document - table. - - - If this parameter is set to 1, the stylesheets generate code to - DEFAULT: 1 Only more code is generated. - - - - 1 - - - - - - - - - - - - - All purpose commands to change text width, height, counters, etc. - Defaults to a two-sided margin layout. - - - - - - \usepackage{anysize} - \marginsize{3cm}{2cm}{1.25cm}{1.25cm} - - - - - Begin document command - - - - - - \begin{document} - - - - - - - - - LaTeX code that is output after the author (e.g. - \makeindex, \makeglossary - - - - - - % -------------------------------------------- - \makeindex - \makeglossary - % -------------------------------------------- - - - - - - - - LaTeX code that is output at the end of the document - \end{document} - - - - - - % -------------------------------------------- - % End of document - % -------------------------------------------- - \end{document} - - - - - - - - - - - - - - - - The begin document - The value of this variable is output from the article template - after the author command. The default value - (shown below) is just the begin document command. Users of the XSL LaTeX - stylesheet may override this parameter in order to output what they want. - - \begin{document} - - - \begin{document} - - - - - Controls what is output after the LaTeX preamble. - - Default values decrease edge margins and allow a large quantity of figures to be set on each page. - - - - - - \usepackage{anysize} - \marginsize{2cm}{2cm}{2cm}{2cm} - \renewcommand\floatpagefraction{.9} - \renewcommand\topfraction{.9} - \renewcommand\bottomfraction{.9} - \renewcommand\textfraction{.1} - - - - - - - - The \maketitle for books and articles. - - Some users may wish to override or eliminate \maketitle. - Does not apply to articles within books. - By default, uses LaTeX \maketitle with the 'empty' pagestyle - for the first page. The page style of subsequent pages is determined by - . - - - - {\maketitle - - \thispagestyle{empty}} - - - - - Controls what is output at the end of the article. Basically the \end{document} - command, with some markup comments. - - - - - - % -------------------------------------------- - % End of document - % -------------------------------------------- - \end{document} - - - - - - diff --git a/docs/docbook/xslt/db2latex/verbatim.mod.xsl b/docs/docbook/xslt/db2latex/verbatim.mod.xsl deleted file mode 100644 index 549883869b..0000000000 --- a/docs/docbook/xslt/db2latex/verbatim.mod.xsl +++ /dev/null @@ -1,144 +0,0 @@ - - - - - - - - - - - - - - Ramon Casellas - James Devenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - Verbatim <filename>verbatim.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - Template for literal - - Template for literal template - - - - - - {\verb - - } - - - - - - - - - - Auxiliary template to output verbatim LaTeX code in verbatim mode - - Takes into account whether the user is using fancyvrb or not. It allows - veratim line numbering and other fancy stuff. - In order to use a small or large font, you may also wanto to use - the role attribute : - - - - - ]]> - - - - - - - - Problem with inside table entries. - \texttt{ - - } - - - - \begin{Verbatim}[ - - ,numbers=left - - - ,fontfamily=default - - - - - ,fontsize=\small - - - ,fontsize=\large - - - - ] - - - - - - - - - - \end{Verbatim} - - - \begin{verbatim} - - \end{verbatim} - - - - - - - - - - - - Environments in which whitespace is significant - - - Known Bugs - Templates are not applied within programlistings. - - - - - - - - diff --git a/docs/docbook/xslt/db2latex/xref.mod.xsl b/docs/docbook/xslt/db2latex/xref.mod.xsl deleted file mode 100644 index 82289b19df..0000000000 --- a/docs/docbook/xslt/db2latex/xref.mod.xsl +++ /dev/null @@ -1,657 +0,0 @@ - - - - - - - - - - - - - - - CasellasRamon - JamesDevenish - - - 2000 2001 2002 2003 - Ramon Casellas - - - -Xref, Cross References <filename>xref.mod.xsl</filename> - -
Introduction - -
- - - - - - - - - Anchor XSL template - - The anchor element - The DB2LaTeX processing of the element is quite straightforward : - Map to a \label. - - - - - - \hypertarget{ - - }{} - - - - - - - - - Auxiliary named template - - This template returns 1 if there exists somewhere an xref - whose linkend is the target's id. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Auxiliary named template - - Called to process an xreflabel...you might use this to make - xreflabels come out in the right font for different targets, - for example. - - - - - - - - - - - - - - - - - Xref and Link XSL Template - - - - - - - - - - - - - XRef to nonexistent id: - XrefId[? - - ?] - - - - - - - - - - - - - - - - - - - - Endterm points to nonexistent ID: - - - [NONEXISTENT ID] - - - - - - - - - - - - - - - {[ - - - - ]} - - - - - - - - - - - - - - - - - - [%p] - - - - - - - - - Choose hyperlink syntax - - Will use hyperref, if it is available. Otherwise, just outputs - unlinked text. If the destination is a citation, a backreference is - emitted (even though it is technically a hyperlink, not a citation). - If the 'text' arises from an @endterm, then the 'optional argument' - syntax of \cite is used. - - - - - - - - - - \docbooktolatexcite - { - - }{ - - - - } - - - - \hyperlink{ - - } - - { - - \docbooktolatexbackcite{ - - } - - - } - - - - - - Insert page number into xrefs - - - - - - %p - - - - \pageref*{ - - } - - - - - - - - - - - - - - - - - Numbering template - - - Let LaTeX manage the numbering. Otherwise sty files that - do specify another numberic (e.g I,II) get messed - - - - - - - {\ref*{}} - - - - - - - - - - - - FIXME - - - FIXME - - - - - - - - - - - - %g %n - - - - - - - - - - - - - - - - - [Don't know what gentext to create for xref to: " - - "] - - UNKGENTEXT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [ - - - - - - - - - ] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - {\em } - - - - - - - - - - - - - - - - - A link that addresses its target by means of a URL (Uniform Resource Locator) - - - Pertinent Variables - - - - - - - - - - - - - \docbookhyphenateurl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \href{ - - - - } - { - - } - - - - - - - - - - OLink XSL template - - - - - - - - - - - - - - - - - - - - - - - - - - - {\em } - - - - - - - - - - - - - - - - - - - - - - - - \url{ - - } - - - \href{ - - - - }{\texttt{ - - - - - }} - - - - - - - Escape and hyphenate a string as a teletype URL. - - - This template typsets teletype text using slash.hyphen if - $latex.hyphenation.tttricks is disabled. - Has two parameters: 'hyphenation' and 'string'. - - - - - - - - - - - - { - - } - - - - - - - - - diff --git a/docs/faq/FAQ-Config.html b/docs/faq/FAQ-Config.html deleted file mode 100644 index 785522ec4e..0000000000 --- a/docs/faq/FAQ-Config.html +++ /dev/null @@ -1,16 +0,0 @@ - -Chapter 3. Configuration problems
Chapter 3. Configuration problems
Prev   Next

Chapter 3. Configuration problems

Table of Contents

I have set 'force user' and samba still makes 'root' the owner of all the files I touch!
I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!
How can I make samba use netbios scope ID's

I have set 'force user' and samba still makes 'root' the owner of all the files I touch!

-When you have a user in 'admin users', samba will always do file operations for -this user as 'root', even if 'force user' has been set. -

I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!

-Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these -passwords to the unix password database, so it needs it's own user database. You can -add users to this database using "smbpasswd -a user-name". -

-See also the "User database" chapter of the samba HOWTO Collection. -

How can I make samba use netbios scope ID's

By default Samba uses a blank scope ID. This means -all your windows boxes must also have a blank scope ID. -If you really want to use a non-blank scope ID then you will -need to use the 'netbios scope' smb.conf option. -All your PCs will need to have the same setting for -this to work. Scope ID's are not recommended.

Prev Up Next
Chapter 2. Compiling and installing Samba on a Unix host Home Chapter 4. Specific client application problems
diff --git a/docs/faq/FAQ-Printing.html b/docs/faq/FAQ-Printing.html deleted file mode 100644 index a924d40cd5..0000000000 --- a/docs/faq/FAQ-Printing.html +++ /dev/null @@ -1,16 +0,0 @@ - -Chapter 7. Printing problems
Chapter 7. Printing problems
Prev   

Chapter 7. Printing problems

Ronan Waide

Table of Contents

setdriver or cupsaddsmb failes

setdriver or cupsaddsmb failes

-setdriver expects the following setup: - -

you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.
printer admins has to be defined in [global]
upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.
Make sure that the user you're connecting as is able to write to the print$ directories
Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)
Use setdriver to associate the driver with a printer

-

-The setdriver call will fail if the printer doesn't already exist in -samba's view of the world. Either create the printer in cups and -restart samba, or create an add printer command (see smb.conf doco) -and use RPC calls to create a printer. NB the add printer command MUST -return a single line of text indicating which port the printer was -added on. If it doesn't, Samba won't reload the printer -definitions. Although samba doesn't really support the notion of -ports, suitable add printer command and enumport command settings can -allow you pretty good remote control of the samba printer setup. -

Prev Up 
Chapter 6. Features Home 
diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html deleted file mode 100644 index b7468eb091..0000000000 --- a/docs/htmldocs/ads.html +++ /dev/null @@ -1,467 +0,0 @@ - -Samba as a ADS domain member
SAMBA Project Documentation
PrevNext

Chapter 9. Samba as a ADS domain member

Table of Contents
9.1. Setup your smb.conf
9.2. Setup your /etc/krb5.conf
9.3. Create the computer account
9.4. Test your server setup
9.5. Testing with smbclient
9.6. Notes

This is a rough guide to setting up Samba 3.0 with kerberos authentication against a -Windows2000 KDC.

9.1. Setup your smb.conf

You must use at least the following 3 options in smb.conf:

  realm = YOUR.KERBEROS.REALM
-  security = ADS
-  encrypt passwords = yes

In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: -

  ads server = your.kerberos.server

You do *not* need a smbpasswd file, and older clients will - be authenticated as if security = domain, - although it won't do any harm - and allows you to have local users not in the domain. - I expect that the above required options will change soon when we get better - active directory integration.

9.2. Setup your /etc/krb5.conf

The minimal configuration for krb5.conf is:

[realms]
-    YOUR.KERBEROS.REALM = {
-	kdc = your.kerberos.server
-    }

Test your config by doing a kinit USERNAME@REALM and making sure that - your password is accepted by the Win2000 KDC.

The realm must be uppercase.

You also must ensure that you can do a reverse DNS lookup on the IP -address of your KDC. Also, the name that this reverse lookup maps to -must either be the netbios name of the KDC (ie. the hostname with no -domain attached) or it can alternatively be the netbios name -followed by the realm.

The easiest way to ensure you get this right is to add a -/etc/hosts entry mapping the IP address of your KDC to -its netbios name. If you don't get this right then you will get a -"local error" when you try to join the realm.

If all you want is kerberos support in smbclient then you can skip -straight to Test with smbclient now. -Creating a computer account -and testing your servers -is only needed if you want kerberos -support for smbd and winbindd.

9.3. Create the computer account

As a user that has write permission on the Samba private directory -(usually root) run: -net ads join

9.3.1. Possible errors

"ADS support not compiled in"

Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.

9.4. Test your server setup

On a Windows 2000 client try net use * \\server\share. You should -be logged in with kerberos without needing to know a password. If -this fails then run klist tickets. Did you get a ticket for the -server? Does it have an encoding type of DES-CBC-MD5 ?

9.5. Testing with smbclient

On your Samba server try to login to a Win2000 server or your Samba -server using smbclient and kerberos. Use smbclient as usual, but -specify the -k option to choose kerberos authentication.

9.6. Notes

You must change administrator password at least once after DC -install, to create the right encoding types

w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in - their defaults DNS setup. Maybe fixed in service packs?

PrevHomeNext
Samba Backup Domain Controller to Samba Domain ControlUpSamba as a NT4 or Win2k domain member
\ No newline at end of file diff --git a/docs/htmldocs/advancednetworkmanagement.html b/docs/htmldocs/advancednetworkmanagement.html deleted file mode 100644 index b55eed16bc..0000000000 --- a/docs/htmldocs/advancednetworkmanagement.html +++ /dev/null @@ -1,555 +0,0 @@ - -Advanced Network Manangement
SAMBA Project Documentation
PrevNext

Chapter 16. Advanced Network Manangement

Table of Contents
16.1. Configuring Samba Share Access Controls
16.2. Remote Server Administration
16.3. Network Logon Script Magic

This section attempts to document peripheral issues that are of great importance to network -administrators who want to improve network resource access control, to automate the user -environment, and to make their lives a little easier.

16.1. Configuring Samba Share Access Controls

This section deals with how to configure Samba per share access control restrictions. -By default samba sets no restrictions on the share itself. Restrictions on the share itself -can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can -connect to a share. In the absence of specific restrictions the default setting is to allow -the global user Everyone Full Control (ie: Full control, Change and Read).

At this time Samba does NOT provide a tool for configuring access control setting on the Share -itself. Samba does have the capacity to store and act on access control settings, but the only -way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for -Computer Management.

Samba stores the per share access control settings in a file called share_info.tdb. -The location of this file on your system will depend on how samba was compiled. The default location -for samba's tdb files is under /usr/local/samba/var. If the tdbdump -utility has been compiled and installed on your system then you can examine the contents of this file -by: tdbdump share_info.tdb.

16.1.1. Share Permissions Management

The best tool for the task is platform dependant. Choose the best tool for your environmemt.

16.1.1.1. Windows NT4 Workstation/Server

The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. -Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. -You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.

Instructions

  1. Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu -select Computer, then click on the Shared Directories entry.

  2. Now click on the share that you wish to manage, then click on the Properties tab, next click on - the Permissions tab. Now you can Add or change access control settings as you wish.

16.1.1.2. Windows 200x/XP

On MS Windows NT4/200x/XP system access control lists on the share itself are set using native -tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, -then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows -Everyone Full Control on the Share.

MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the -Microsoft Management Console (MMC). This tool is located by clicking on Control Panel -> -Administrative Tools -> Computer Management.

Instructions

  1. After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', - select 'Connect to another computer'. If you are not logged onto a domain you will be prompted - to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered.

  2. If the Samba server is not shown in the Select Computer box, then type in the name of the target -Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] -next to 'Shared Folders' in the left panel.

  3. Now in the right panel, double-click on the share you wish to set access control permissions on. -Then click on the tab 'Share Permissions'. It is now possible to add access control entities -to the shared folder. Do NOT forget to set what type of access (full control, change, read) you -wish to assign for each entry.

Be careful. If you take away all permissions from the Everyone user without removing this user -then effectively no user will be able to access the share. This is a result of what is known as -ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone -will have no access even if this user is given explicit full control access.

16.2. Remote Server Administration

How do I get 'User Manager' and 'Server Manager'?

Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', -the 'Server Manager'?

Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me -systems. The tools set includes:

  • Server Manager

  • User Manager for Domains

  • Event Viewer

Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE

The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE

16.3. Network Logon Script Magic

This section needs work. Volunteer contributions most welcome. Please send your patches or updates -to John Terpstra.

There are several opportunities for creating a custom network startup configuration environment.

No Logon Script
Simple universal Logon Script that applies to all users
Use of a conditional Logon Script that applies per user or per group attirbutes
Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create - a custom Logon Script and then execute it.
User of a tool such as KixStart

The Samba source code tree includes two logon script generation/execution tools. See examples directory genlogon and ntlogon subdirectories.

The following listings are from the genlogon directory.

This is the genlogon.pl file: - -

	#!/usr/bin/perl
-	#
-	# genlogon.pl
-	#
-	# Perl script to generate user logon scripts on the fly, when users
-	# connect from a Windows client.  This script should be called from smb.conf
-	# with the %U, %G and %L parameters. I.e:
-	#
-	#       root preexec = genlogon.pl %U %G %L
-	#
-	# The script generated will perform
-	# the following:
-	#
-	# 1. Log the user connection to /var/log/samba/netlogon.log
-	# 2. Set the PC's time to the Linux server time (which is maintained
-	#    daily to the National Institute of Standard's Atomic clock on the
-	#    internet.
-	# 3. Connect the user's home drive to H: (H for Home).
-	# 4. Connect common drives that everyone uses.
-	# 5. Connect group-specific drives for certain user groups.
-	# 6. Connect user-specific drives for certain users.
-	# 7. Connect network printers.
-
-	# Log client connection
-	#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
-	($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
-	open LOG, ">>/var/log/samba/netlogon.log";
-	print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
-	close LOG;
-
-	# Start generating logon script
-	open LOGON, ">/shared/netlogon/$ARGV[0].bat";
-	print LOGON "\@ECHO OFF\r\n";
-
-	# Connect shares just use by Software Development group
-	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
-	{
-		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
-	}
-
-	# Connect shares just use by Technical Support staff
-	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
-	{
-		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
-	}
-
-	# Connect shares just used by Administration staff
-	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
-	{
-		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
-		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
-	}
-
-	# Now connect Printers.  We handle just two or three users a little
-	# differently, because they are the exceptions that have desktop
-	# printers on LPT1: - all other user's go to the LaserJet on the
-	# server.
-	if ($ARGV[0] eq 'jim'
-	    || $ARGV[0] eq 'yvonne')
-	{
-		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
-		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
-	}
-	else
-	{
-		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
-		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
-	}
-
-	# All done! Close the output file.
-	close LOGON;

Those wishing to use more elaborate or capable logon processing system should check out the following sites:

http://www.craigelachie.org/rhacer/ntlogon
http://www.kixtart.org

PrevHomeNext
Unified Logons between Windows NT and UNIX using WinbindUpSystem and Account Policies
\ No newline at end of file diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html deleted file mode 100644 index 8015702c51..0000000000 --- a/docs/htmldocs/appendixes.html +++ /dev/null @@ -1,140 +0,0 @@ - -Appendixes
SAMBA Project Documentation
PrevNext

IV. Appendixes

PrevHomeNext
Unicode/Charsets How to compile SAMBA
\ No newline at end of file diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html deleted file mode 100644 index 4611db7195..0000000000 --- a/docs/htmldocs/browsing-quick.html +++ /dev/null @@ -1,805 +0,0 @@ - -Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
SAMBA Project Documentation
PrevNext

Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

Table of Contents
3.1. Discussion
3.2. How browsing functions and how to deploy stable and -dependable browsing using Samba
3.3. Use of the Remote Announce parameter
3.4. Use of the Remote Browse Sync parameter
3.5. Use of WINS
3.5.1. WINS Replication
3.5.2. Static WINS Entries
3.6. Do NOT use more than one (1) protocol on MS Windows machines
3.7. Name Resolution Order

This document should be read in conjunction with Browsing and may -be taken as the fast track guide to implementing browsing across subnets -and / or across workgroups (or domains). WINS is the best tool for resolution -of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling -except by way of name to address mapping.

MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation.

3.1. Discussion

Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. -MS Windows products can do likewise. NetBIOS based networking uses broadcast -messaging to affect browse list management. When running NetBIOS over -TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.

Normally, only unicast UDP messaging can be forwarded by routers. The -remote announce -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -remote browse sync parameter of smb.conf -implements browse list collation using unicast UDP.

Secondly, in those networks where Samba is the only SMB server technology -wherever possible nmbd should be configured on one (1) machine as the WINS -server. This makes it easy to manage the browsing environment. If each network -segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the -remote announce and the remote browse sync -parameters to your smb.conf file.

If only one WINS server is used for an entire multi-segment network then -the use of the remote announce and the -remote browse sync parameters should NOT be necessary.

As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation.

Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one nmbd configured -as a WINS server on the network. Some sites have used multiple Samba WINS -servers for redundancy (one server per subnet) and then used -remote browse sync and remote announce -to affect browse list collation across all -segments. Note that this means clients will only resolve local names, -and must be configured to use DNS to resolve names on other subnets in -order to resolve the IP addresses of the servers they can see on other -subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario).

Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments.

3.2. How browsing functions and how to deploy stable and -dependable browsing using Samba

As stated above, MS Windows machines register their NetBIOS names -(i.e.: the machine name for each service type in operation) on start -up. Also, as stated above, the exact method by which this name registration -takes place is determined by whether or not the MS Windows client/server -has been given a WINS server address, whether or not LMHOSTS lookup -is enabled, or if DNS for NetBIOS name resolution is enabled, etc.

In the case where there is no WINS server all name registrations as -well as name lookups are done by UDP broadcast. This isolates name -resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the -remote announce parameter).

Where a WINS server is used, the MS Windows client will use UDP -unicast to register with the WINS server. Such packets can be routed -and thus WINS allows name resolution to function across routed networks.

During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local -master browser (found by asking WINS or from LMHOSTS) and exchanging browse -list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election -is held to determine which machine will be the master browser. By the nature of -the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser.

Clients wishing to browse the network make use of this list, but also depend -on the availability of correct name resolution to the respective IP -address/addresses.

Any configuration that breaks name resolution and/or browsing intrinsics -will annoy users because they will have to put up with protracted -inability to use the network services.

Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the remote -browse sync parameter in the smb.conf file. -This causes Samba to contact the local master browser on a remote network and -to request browse list synchronisation. This effectively bridges -two networks that are separated by routers. The two remote -networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the remote -browse sync parameter provides browse list synchronisation - and -that is distinct from name to address resolution, in other -words, for cross subnet browsing to function correctly it is -essential that a name to address resolution mechanism be provided. -This mechanism could be via DNS, /etc/hosts, -and so on.

3.3. Use of the Remote Announce parameter

The remote announce parameter of -smb.conf can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the remote announce parameter is: -

	remote announce = a.b.c.d [e.f.g.h] ...
-_or_ -
	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
- -where: -

a.b.c.d and -e.f.g.h

is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.

WORKGROUP

is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided.

3.4. Use of the Remote Browse Sync parameter

The remote browse sync parameter of -smb.conf is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our -Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment.

The syntax of the remote browse sync parameter is: - -

remote browse sync = a.b.c.d
- -where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

3.5. Use of WINS

Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly -recommended. Every NetBIOS machine registers it's name together with a -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name.

All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information).

WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -lmhosts files that must reside on all clients in the -absence of WINS.

WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only.

Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors.

To configure Samba as a WINS server just add -wins support = yes to the smb.conf -file [globals] section.

To configure Samba to register with a WINS server just add -"wins server = a.b.c.d" to your smb.conf file [globals] section.

Never use both wins support = yes together -with wins server = a.b.c.d -particularly not using it's own IP address. -Specifying both will cause nmbd to refuse to start!

3.5.1. WINS Replication

Samba-3 permits WINS replication through the use of the wrepld utility. -This tool is not currently capable of being used as it is still in active development. -As soon as this tool becomes moderately functional we will prepare man pages and enhance this -section of the documentation to provide usage and technical details.

3.5.2. Static WINS Entries

New to Samba-3 is a tool called winsedit that may be used to add -static WINS entries to the WINS database. This tool can be used also to modify entries -existing in the WINS database.

The development of the winsedit tool was made necessary due to the migration -of the older style wins.dat file into a new tdb binary backend data store.

3.6. Do NOT use more than one (1) protocol on MS Windows machines

A very common cause of browsing problems results from installing more than -one protocol on an MS Windows machine.

Every NetBIOS machine takes part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role.

The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail.

Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols.

The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

3.7. Name Resolution Order

Resolution of NetBIOS names to IP addresses can take place using a number -of methods. The only ones that can provide NetBIOS name_type information -are:

WINS: the best tool!
LMHOSTS: is static and hard to maintain.
Broadcast: uses UDP and can not resolve names across remote segments.

Alternative means of name resolution includes:

/etc/hosts: is static, hard to maintain, and lacks name_type info
DNS: is a good choice but lacks essential name_type info.

Many sites want to restrict DNS lookups and want to avoid broadcast name -resolution traffic. The "name resolve order" parameter is of great help here. -The syntax of the "name resolve order" parameter is: -

name resolve order = wins lmhosts bcast host
-_or_ -
name resolve order = wins lmhosts  	(eliminates bcast and host)
-The default is: -
name  resolve order = host lmhost wins bcast
. -where "host" refers the the native methods used by the Unix system -to implement the gethostbyname() function call. This is normally -controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.

PrevHomeNext
How to Install and Test SAMBAUpUser information database
\ No newline at end of file diff --git a/docs/htmldocs/cups-printing.html b/docs/htmldocs/cups-printing.html deleted file mode 100644 index 8dd4a94f4f..0000000000 --- a/docs/htmldocs/cups-printing.html +++ /dev/null @@ -1,2773 +0,0 @@ - -CUPS Printing Support
SAMBA Project Documentation
PrevNext

Chapter 14. CUPS Printing Support

Table of Contents
14.1. Introduction
14.2. Configuring smb.conf for CUPS
14.3. CUPS - RAW Print Through Mode
14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients
14.5. Windows Terminal Servers (WTS) as CUPS clients
14.6. Setting up CUPS for driver download
14.7. Sources of CUPS drivers / PPDs
14.8. The CUPS Filter Chains
14.9. CUPS Print Drivers and Devices
14.10. Limiting the number of pages users can print
14.11. Advanced Postscript Printing from MS Windows
14.12. Auto-Deletion of CUPS spool files

14.1. Introduction

The Common Unix Print System (CUPS) has become very popular, but to many it is -a very mystical tool. There is a great deal of uncertainty regarding CUPS and how -it works. The result is seen in a large number of posting on the samba mailing lists -expressing frustration when MS Windows printers appear not to work with a CUPS -backr-end.

This is a good time to point out how CUPS can be used and what it does. CUPS is more -than just a print spooling system - it is a complete printer management system that -complies with HTTP and IPP protocols. It can be managed remotely via a web browser -and it can print using http and ipp protocols.

CUPS allows to creation of RAW printers (ie: NO file format translation) as well as -SMART printers (ie: CUPS does file format conversion as required for the printer). In -many ways this gives CUPS similar capabilities to the MS Windows print monitoring -system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! -In any case, let us now move on to explore how one may configure CUPS for interfacing -with MS Windows print clients via Samba.

CUPS is a newcomer in the UNIX printing scene, -which has convinced many people upon first trial already. However, it has quite a few -new features, which make it different from other, more traditional printing systems.

14.2. Configuring smb.conf for CUPS

Printing with CUPS in the most basic smb.conf -setup in Samba-3 only needs two settings: printing = cups and -printcap = cups. While CUPS itself doesn't need a printcap -anymore, the cupsd.conf configuration file knows two directives -(example: Printcap /etc/printcap and PrintcapFormat -BSD), which control if such a file should be created for the -convenience of third party applications. Make sure it is set! For details see -man cupsd.conf and other CUPS-related documentation.

If SAMBA is compiled against libcups, then printcap = cups uses the -CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands -with an additional -oraw option for printing. On a Linux system, -you can use the ldd command to find out details (ldd may not be -present on other OS platforms, or its function may be embodied by a different command):

transmeta:/home/kurt # ldd `which smbd`
-        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
-        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
-        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
-        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
-        libc.so.6 => /lib/libc.so.6 (0x4020b000)
-        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

The line "libcups.so.2 => /usr/lib/libcups.so.2 -(0x40123000)" shows there is CUPS support compiled into this version of -Samba. If this is the case, and printing = cups is set, then any -otherwise manually set print command in smb.conf is ignored.

14.3. CUPS - RAW Print Through Mode

When used in raw print through mode is will be necessary to use the printer -vendor's drivers in each Windows client PC.

When CUPS printers are configured for RAW print-through mode operation it is the -responsibility of the Samba client to fully render the print job (file) in a format -that is suitable for direct delivery to the printer. In this case CUPS will NOT -do any print file format conversion work.

The CUPS files that need to be correctly set for RAW mode printers to work are: - -

  • /etc/cups/mime.types

  • /etc/cups/mime.convs

- -Both contain entries that must be uncommented to allow RAW mode -operation.

Firstly, to enable CUPS based printing from Samba the following options must be -enabled in your smb.conf file [globals] section: - -

  • printing = CUPS

  • printcap = CUPS

- -When these parameters are specified the print directives in smb.conf (as well as in -samba itself) will be ignored because samba will directly interface with CUPS through -it's application program interface (API) - so long as Samba has been compiled with -CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the -oraw -option automatically passing through.

Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) -on the Samba/CUPS server does *not* add any features if a file is really -printed "raw". However, if you have loaded the driver for the Windows client from -the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using -a "Foomatic" PPD, the PJL header in question is already added on the Windows client, -at the time when the driver initially generated the PostScript data and CUPS in true -"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its -printer communication backend.

NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.

Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids -the process of determining proper treatment while in the print queue system. - -

  • Files generated by PCL drivers and directed at PCK printers get auto-typed as - application/octet-stream. Unknown file format types also - get auto-typed with this tag. -

  • Files generated by a Postscript driver and directed at a Postscript printer - are auto-typed depending on the auto-detected most suitable MIME type as: - -

    • * application/postscript

    • * application/vnd.cups-postscript

    -

"application/postscript" first goes thru the "pstops" filter (where the page counting -and accounting takes place). The outcome will be of MIME type -"application/vnd.cups-postscript". The pstopsfilter reads and uses information from -the PPD and inserts user-provided options into the PostScript file. As a consequence, -the filtered file could possibly have an unwanted PJL header.

"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or ">04<%".

"application/vnd.cups-postscript" will files which contain the string -"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the -first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS -or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced -with a "Generic PostScript driver" will just be tagged "application/postscript".

Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" -or "cupsomatic" will take over (depending on the printer configuration, as -determined by the PPD in use).

A printer queue with *no* PPD associated to it is a "raw" printer and all files -will go directly there as received by the spooler. The exeptions are file types -"application/octet-stream" which need "passthrough feature" enabled. -"Raw" queues don't do any filtering at all, they hand the file directly to the -CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, -parallel:/, serial:/, usb:/ etc.)

"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. -They are a Third Party add-on, developed at Linuxprinting.org. As such, they are -a brilliant hack to make all models (driven by Ghostscript drivers/filters in -traditional spoolers) also work via CUPS, with the same (good or bad!) quality -as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript -commandline at that stage in the CUPS filtering chain, where "normally" the native -CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" -the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, -because the associated CUPS-O-Matic-/Foomatic-PPD specifies:

   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"

This line persuades CUPS to hand the file to cupsomatic, once it has successfully -converted it to the MIME type "application/vnd.cups-postscript". This conversion will not -happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", -with the according changes in "/etc/cups/mime.types" in place.

CUPS is widely configurable and flexible, even regarding its filtering mechanism. -Another workaround in some situations would be to have -in "/etc/cups/mime.types" entries as follows:

   application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -

This would prevent all Postscript files from being filtered (rather, they will go -thru the virtual "nullfilter" denoted with "-"). This could only be useful for -PS printers. If you want to print PS code on non-PS printers an entry as follows -could be useful:

   */*           application/vnd.cups-raw  0  -

and would effectively send *all* files to the backend without further processing.

Lastly, you could have the following entry:

   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter

You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that -parses the PostScript and removes the unwanted PJL. This would need to conform to -CUPS filter design (mainly, receive and pass the parameters printername, job-id, -username, jobtitle, copies, print options and possibly the filename). It would -be installed as world executable into "/usr/lib/cups/filters/" and will be called -by CUPS if it encounters a MIME type "application/vnd.cups-postscript".

CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue -"on hold". It will only be printed upon manual release by the printer operator. -This is a requirement in many "central reproduction departments", where a few -operators manage the jobs of hundreds of users on some big machine, where no -user is allowed to have direct access. (The operators often need to load the -proper paper type before running the 10.000 page job requested by marketing -for the mailing, etc.).

14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients

CUPS is perfectly able to use PPD files (PostScript -Printer Descriptions). PPDs can control all print device options. They -are usually provided by the manufacturer -- if you own a PostSript printer, -that is. PPD files are always a component of PostScript printer drivers on MS -Windows or Apple Mac OS systems. They are ASCII files containing -user-selectable print options, mapped to appropriate PostScript, PCL or PJL -commands for the target printer. Printer driver GUI dialogs translate these -options "on-the-fly" into buttons and drop-down lists for the user to -select.

CUPS can load, without any conversions, the PPD file from -any Windows (NT is recommended) PostScript driver and handle the options. -There is a web browser interface to the print options (select -http://localhost:631/printers/ and click on one "Configure Printer" button -to see it), a commandline interface (see man lpoptions or -try if you have lphelp on your system) plus some different GUI frontends on Linux -UNIX, which can present PPD options to the users. PPD options are normally -meant to become evaluated by the PostScript RIP on the real PostScript -printer.

CUPS doesn't stop at "real" PostScript printers in its -usage of PPDs. The CUPS developers have extended the PPD concept, to also -describe available device and driver options for non-PostScript printers -through CUPS-PPDs.

This is logical, as CUPS includes a fully featured -PostScript interpreter (RIP). This RIP is based on Ghostscript. It can -process all received PostScript (and additionally many other file formats) -from clients. All CUPS-PPDs geared to non-PostScript printers contain an -additional line, starting with the keyword *cupsFilter. -This line -tells the CUPS print system which printer-specific filter to use for the -interpretation of the accompanying PostScript. Thus CUPS lets all its -printers appear as PostScript devices to its clients, because it can act as a -PostScript RIP for those printers, processing the received PostScript code -into a proper raster print format.

CUPS-PPDs can also be used on Windows-Clients, on top of a -PostScript driver (recommended is the Adobe one).

This feature enables CUPS to do a few tricks no other -spooler can do:

  • act as a networked PostScript RIP (Raster Image Processor), handling - printfiles from all client platforms in a uniform way;

  • act as a central accounting and billing server, as all files are passed - through the pstops Filter and are therefor logged in - the CUPS page_log. - NOTE: this - can not happen with "raw" print jobs, which always remain unfiltered - per definition;

  • enable clients to consolidate on a single PostScript driver, even for - many different target printers.

14.5. Windows Terminal Servers (WTS) as CUPS clients

This setup may be of special interest to people -experiencing major problems in WTS environments. WTS need often a multitude -of non-PostScript drivers installed to run their clients' variety of -different printer models. This often imposes the price of much increased -instability. In many cases, in an attempt to overcome this problem, site -administrators have resorted to restrict the allowed drivers installed on -their WTS to one generic PCL- and one PostScript driver. This however -restricts the clients in the amount of printer options available for them -- -often they can't get out more then simplex prints from one standard paper -tray, while their devices could do much better, if driven by a different -driver!

Using an Adobe PostScript driver, enabled with a CUPS-PPD, -seems to be a very elegant way to overcome all these shortcomings. The -PostScript driver is not known to cause major stability problems on WTS (even -if used with many different PPDs). The clients will be able to (again) chose -paper trays, duplex printing and other settings. However, there is a certain -price for this too: a CUPS server acting as a PostScript RIP for its clients -requires more CPU and RAM than just to act as a "raw spooling" device. Plus, -this setup is not yet widely tested, although the first feedbacks look very -promising...

14.6. Setting up CUPS for driver download

The cupsadsmb utility (shipped with all current -CUPS versions) makes the sharing of any (or all) installed CUPS printers very -easy. Prior to using it, you need the following settings in smb.conf:

[global]
-		 load printers = yes
-		 printing = cups
-		 printcap name = cups
-
-	[printers]
-		 comment = All Printers
-		 path = /var/spool/samba
-		 browseable = no
-		 public = yes
-		 guest ok = yes
-		 writable = no
-		 printable = yes
-		 printer admin = root
-
-	[print$]
-		 comment = Printer Drivers
-		 path = /etc/samba/drivers
-		 browseable = yes
-		 guest ok = no
-		 read only = yes
-		 write list = root
-

For licensing reasons the necessary files of the Adobe -Postscript driver can not be distributed with either Samba or CUPS. You need -to download them yourself from the Adobe website. Once extracted, create a -drivers directory in the CUPS data directory (usually -/usr/share/cups/). Copy the Adobe files using -UPPERCASE filenames, to this directory as follows:

		ADFONTS.MFM
-		ADOBEPS4.DRV
-		ADOBEPS4.HLP
-		ADOBEPS5.DLL
-		ADOBEPSU.DLL
-		ADOBEPSU.HLP
-		DEFPRTR2.PPD
-		ICONLIB.DLL
-

Users of the ESP Print Pro software are able to install -their "Samba Drivers" package for this purpose with no problem.

14.7. Sources of CUPS drivers / PPDs

On the internet you can find now many thousand CUPS-PPD -files (with their companion filters), in many national languages, -supporting more than 1.000 non-PostScript models.

NOTE: the cupsomatic trick from Linuxprinting.org is -working different from the other drivers. While the other drivers take the -generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as -their input, cupsomatic "kidnaps" the PostScript inside CUPS, before -RIP-ping, deviates it to an external Ghostscript installation (which now -becomes the RIP) and gives it back to a CUPS backend once Ghostscript is -finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster -PostScript RIP function again inside a system-wide Ghostscript -installation rather than in "their own" pstoraster filter. (This -CUPS-enabling Ghostscript version may be installed either as a -patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). -However, this will not change the cupsomatic approach of guiding the printjob -along a different path through the filtering system than the standard CUPS -way...

Once you installed a printer inside CUPS with one of the -recommended methods (the lpadmin command, the web browser interface or one of -the available GUI wizards), you can use cupsaddsmb to share the -printer via Samba. cupsaddsmb prepares the driver files for -comfortable client download and installation upon their first contact with -this printer share.

14.7.1. cupsaddsmb

The cupsaddsmb command copies the needed files -for convenient Windows client installations from the previously prepared CUPS -data directory to your [print$] share. Additionally, the PPD -associated with this printer is copied from /etc/cups/ppd/ to -[print$].

root#  cupsaddsmb -U root infotec_IS2027
-Password for root required to access localhost via SAMBA: [type in password 'secret']

To share all printers and drivers, use the -a -parameter instead of a printer name.

Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

Note: The following line shave been wrapped so that information is not lost.
- 
-root#  cupsaddsmb -v -U root infotec_IS2027
-    Password for root required to access localhost via SAMBA:
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
-       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
-       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
-       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
-      (average 17395.2 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
-      (average 11343.0 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
-      (average 9260.4 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
-      (average 9247.1 kb/s)
-
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
-      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
-      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
-      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
-      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
-      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
-      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
-      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
-      (average 26092.8 kb/s)
-    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
-      (average 11812.9 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
-      (average 14679.3 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
-      (average 14281.5 kb/s)
-    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
-      (average 12944.0 kb/s)
-    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
-      (average 13169.7 kb/s)
-    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
-      (average 13266.7 kb/s)
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
-       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
-    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
-       ADOBEPSU.HLP:NULL:RAW:NULL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
-       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
-       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
-       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret'
-       -c 'setdriver infotec_IS2027 infotec_IS2027'
-    cmd = setdriver infotec_IS2027 infotec_IS2027
-    Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
-    root#

If you look closely, you'll discover your root password was transfered unencrypted over -the wire, so beware! Also, if you look further her, you'll discover error messages like -NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because -the directories WIN40 and W32X86 already -existed in the [print$] driver download share (from a previous driver -installation). They are harmless here.

Now your printer is prepared for the clients to use. From -a client, browse to the CUPS/Samba server, open the "Printers" -share, right-click on this printer and select "Install..." or -"Connect..." (depending on the Windows version you use). Now their -should be a new printer in your client's local "Printers" folder, -named (in my case) "infotec_IS2027 on kdebitshop"

NOTE: -cupsaddsmb will only reliably work i -with CUPS version 1.1.15 or higher -and Samba from 2.2.4. If it doesn't work, or if the automatic printer -driver download to the clients doesn't succeed, you can still manually -install the CUPS printer PPD on top of the Adobe PostScript driver on -clients and then point the client's printer queue to the Samba printer -share for connection, should you desire to use the CUPS networked -PostScript RIP functions.

14.8. The CUPS Filter Chains

The following diagrams reveal how CUPS handles print jobs.

#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#    somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rastertosomething                          V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend >------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     gsrip
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#    somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rastertosomething                          V
-#      |   (= "raster driver")      +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend >------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript                                     |
-#                  | at work...                                      |
-#                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
-#                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
-#                  |                                                 |
-#                  +------------------v------------------------------+
-#                                     |
-#                                     |
-# APPLICATION/VND.CUPS-RASTER >-------+
-#      |
-#      |
-#      V
-#     rastertosomething
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-#       Ghostscript. GNU Ghostscript needs to be patched to handle the
-#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rastertosomething"
-#       Note the difference to "cupsomatic", which will *not* output
-#       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
-#       devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            s.th."        |
-#                  | "-sDEVICE=cups")   .                            |
-#                  |                    .                            |
-#                  | (CUPS standard)    .      (cupsomatic)          |
-#                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
-#                  |                    .                            |
-#                  +------------------v--------------v---------------+
-#                                     |              |
-#                                     |              |
-# APPLICATION/VND.CUPS-RASTER >-------+              |
-#      |                                             |
-#      |                                             |
-#      V                                             |
-#     rastertosomething                            |
-#      |   (= "raster driver")                       |
-#      |                                             |
-#      V                                             |
-# SOMETHING-DEVICE-SPECIFIC >------------------------+
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-##########################################################################

14.9. CUPS Print Drivers and Devices

CUPS ships with good support for HP LaserJet type printers. You can install -the driver as follows: - -

  • lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd -

- -(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository -for not-yet-installed-PPDs, which CUPS typically stores in -/usr/share/cups/model. Alternatively, you may use -"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").

14.9.1. Further printing steps

Always also consult the database on linuxprinting.org for all recommendations -about which driver is best used for each printer:

http://www.linuxprinting.org/printer_list.cgi

There select your model and click on "Show". You'll arrive at a page listing -all drivers working with your model. There will always be *one* -recommended one. Try this one first. In your case -("HP LaserJet 4 Plus"), you'll arrive here:

http://www.linuxprinting.org/show_printer.cgi?recnum=75104

The recommended driver is "ljet4". It has a link to the page for the ljet4 -driver too:

http://www.linuxprinting.org/show_driver.cgi?driver=ljet4

On the driver's page, you'll find important and detailed info about how to use -that driver within the various available spoolers. You can generate a PPD for -CUPS. The PPD contains all the info about how to use your model and the driver; -this is, once installed, working transparently for the user -- you'll only -need to choose resolution, paper size etc. from the web-based menu or from -the print dialog GUI or from the commandline...

On the driver's page, choose to use the "PPD-O-Matic" online PPD generator -program. Select your model and click "Generate PPD file". When you safe the -appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt -line endings and tabs), but use "Save as..." in your browser's menu. Save it -at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

Then install the printer:

    "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
-          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need -a special "CUPS filter" named "cupsomatic". Get the latest version of -"cupsomatic" from:

http://www.linuxprinting.org/cupsomatic

This needs to be copied to /usr/lib/cups/filter/cupsomatic -and be made world executable. This filter is needed to read and act upon the -specially encoded Foomatic comments, embedded in the printfile, which in turn -are used to construct (transparently for you, the user) the complicated -ghostscript command line needed for your printer/driver combo.

You can have a look at all the options for the Ghostscript commandline supported -by your printer and the ljet4 driver by going to the section "Execution details", -selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". -This will bring up this web page:

http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details

The ingenious thing is that the database is kept current. If there -is a bug fix and an improvement somewhere in the database, you will -always get the most current and stable and feature-rich driver by following -the steps described above.

Till Kamppeter from MandrakeSoft is doing an excellent job here that too few -people are aware of. (So if you use it often, please send him a note showing -your appreciation).

The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it.

"cupsomatic" is documented here:

http://www.linuxprinting.org/cups-doc.html

More printing tutorial info may be found here:

http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/

Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now -approaching the "all-time high" number of 1.000 for the supported models) -are using a special filtering chain involving Ghostscript, as described -in this document.

Summary - You need:

A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
The "cupsomatic" filter script (Perl) in /usr/lib/cups/filters/
Perl to make cupsomatic run
Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")

In the case of the "hpijs" driver, you need a Ghostscript version, which -has "ijs" amongst its supported devices in "gs -h". In the case of -"hpijs+foomatic", a valid ghostscript commandline would be reading like this:

       gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
-             -sIjsServer=hpijsPageSize -dDuplex=Duplex Model        \
-             -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \
-             -sOutputFile=- -

Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) -you don't need to remember this. You can choose the available print options -thru a GUI print command (like "glp" from ESP's commercially supported -PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent -"xpp") or the CUPS web interface via human-readable drop-down selection -menus.

If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software -Products, the makers of CUPS, downloadable from -http://www.cups.org/software.html, -co-maintained by the developers of linuxprinting.org), you are guaranteed to -have in use the most uptodate, bug-fixed, enhanced and stable version of a Free -Ghostscript. It contains support for ~300 devices, whereas plain vanilla -GNU Ghostscript 7.05 only has ~200.

If you print only one CUPS test page, from the web interface and when you try to -print a windows test page, it acts like the job was never sent: - -

Can you print "standard" jobs from the CUPS machine?
Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
Most important: What kind of printer driver are you using on the Windows clients?

- -You can try to get a more detailed debugging info by setting "LogLevel debug" in -/etc/cups/cupsd.conf, re-start cupsd and investigate /var/log/cups/error_log -for the whereabouts of your Windows-originating printjobs:

what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
are there "filter" available for this MIME type?
are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?

14.10. Limiting the number of pages users can print

The feature you want is dependent on the real print subsystem you're using. -Samba's part is always to receive the job files from the clients (filtered -*or* unfiltered) and hand it over to this printing subsystem.

Of course one could "hack" things with one's own scripts.

But there is CUPS (Common Unix Printing System). CUPS supports "quotas". -Quotas can be based on sizes of jobs or on the number of pages or both, -and are spanning any time period you want.

This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter":

  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
-       -o job-page-limit=100

This would limit every single user to print 100 pages or 1024 KB of -data (whichever comes first) within the last 604.800 seconds ( = 1 week).

For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, -otherwise it uses a "dummy" count of "1". Some printfiles don't pass it -(eg: image files) but then those are mostly 1 page jobs anyway. This also means, -proprietary drivers for the target printer running on the client computers and -CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too!

You need to send PostScript from the clients (i.e. run a PostScript driver there) -for having the chance to get accounting done. If the printer is a non-PostScript model, -you need to let CUPS do the job to convert the file to a print-ready format for the -target printer. This will be working for currently ~1.000 different printer models, see

     http://www.linuxprinting.org/printer_list.cgi

Before CUPS-1.1.16 your only option was to use the Adobe PostScript -Driver on the Windows clients. The output of this driver was not always -passed thru the "pstops" filter on the CUPS/Samba side, and therefor was -not counted correctly (the reason is that it often --- depending on the -"PPD" being used --- did write a "PJL"-header in front of the real -PostScript which made CUPS to skip the pstops and go directy to -the "pstoraster" stage).

From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver -for Windows NT/2K/XP clients" (it is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). -It is *not* working for Win9x/ME clients. But it:

it guarantees to not write an PJL-header
it guarantees to still read and support all PJL-options named in the driver PPD with its own means
it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
it guarantees to page-count correctly the printfile

You can read more about the setup of this combination in the -manpage for "cupsaddsmb" (only present with CUPS installed, only -current with CUPS 1.1.16).

These are the items CUPS logs in the "page_log" for every single *page* of a job:

Printer name
User name
Job ID
Time of printing
the page number
the number of copies
a billing info string (optional)

Here is an extract of my CUPS server's page_log file to illustrate -the format and included items:

infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing

This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job -printed in 2 copies and billed to "#marketing"...

What flaws or shortcomings are there?

the ones named above
CUPS really counts the job pages being *processsed in software* - (going thru the "RIP") rather than the physical sheets successfully - leaving the printing device -- if there is a jam while printing - the 5th sheet out of 1000 and the job is aborted by the printer, - the "page count" will still show the figure of 1000 for that job -
all quotas are the same for all users (no flexibility to give the - boss a higher quota than the clerk) no support for groups -
no means to read out the current balance or "used-up" number of current quota -
a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job -
a user being denied a job because of a filled-up quota doesn't get a meaningful - error message from CUPS other than "client-error-not-possible". -

But this is the best system out there currently. And there are -huge improvements under development:

page counting will go into the "backends" (these talk - directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)
quotas will be handled more flexibly
probably there will be support for users to inquire their "accounts" in advance
probably there will be support for some other tools around this topic

Other than the current stage of the CUPS development, I don't -know any other ready-to-use tool which you could consider.

You can download the driver files from -http://www.cups.org/software.html. -It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 -Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to -download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal -the files:

cups-samba.install - cups-samba.license - cups-samba.readme - cups-samba.remove - cups-samba.ss - -

These have been packaged with the ESP meta packager software "EPM". The -*.install and *.remove files are simple shell script, which untars the -*.ss (which is nothing else than a tar-archive) and puts its contents -into /usr/share/cups/drivers/. Its contents are 3 files:

cupsdrvr.dll - cupsui.dll - cups.hlp - -

Due to a bug one CUPS release puts the cups.hlp -into /usr/share/drivers/ instead of -/usr/share/cups/drivers/. To work around this, copy/move -the file after running the "./cups-samba.install" script manually to the right place:

cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ - -

This new CUPS PostScript driver is currently binary-only, but free -no source code is provided (yet). The reason is this: it has -been developed with the help of the Microsoft Driver Developer Kit (DDK) -and compiled with Microsoft Visual Studio 6. It is not clear to the driver -developers if they are allowed to distribute the whole of the source code -as Free Software. However, they will likely release the "diff" in source -code under the GPL, so anybody with a license of Visual Studio and a DDK -will be able to compile for him/herself.

Once you have run the install script (and possibly manually moved the -"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be -put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" -and contains a subdir tree with WIN40 and W32X86 branches), by running -"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to -put root into the smbpasswd file by running "smbpasswd" should you run -this whole procedure for the first time.] Once the driver files are in the -[print$] share, they are ready to be downloaded and installed by the -Win NT/2k/XP clients.

Win 9x/ME clients won't work with this driver. For these you'd - still need to use the ADOBE*.* drivers as previously. -

It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. - The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). -

Should your Win clients have had the old ADOBE*.* files and the - Adobe PostScript drivers installed, the download and installation - of the new CUPS PostScript driver for Windows NT/2k/XP will fail - at first. -

It is not enough to "delete" the printer (as the driver files - will still be kept by the clients and re-used if you try to - re-install the printer). To really get rid of the Adobe driver - files on the clients, open the "Printers" folder (possibly via - "Start --> Settings --> Control Panel --> Printers"), right-click - onto the folder background and select "Server Properties". A - new dialog opens; select the "Drivers" tab; on the list select - the driver you want to delete and click on the "Delete" button. - (This will only work if there is no single printer left which - uses that particular driver -- you need to "delete" all printers - using this driver in the "Printers" folder first.) -

Once you have successfully downloaded the CUPS PostScript driver - to a client, you can easily switch all printers to this one - by proceeding as described elsewhere in the "Samba HOWTO - Collection" to change a driver for an existing printer. -

What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" -as compared to the Adobe drivers?

  • no hassle with the Adobe EULA -

  • no hassle with the question "where do I get the ADOBE*.* driver files from?" -

  • the Adobe drivers (depending on the printer PPD associated with them) - often put a PJL header in front of the core PostScript part of the print - file (thus the file starts with "1B%-12345X" or "escape%-12345X" - instead of "%!PS"). This leads to the CUPS daemon autotyping the - arriving file as a print-ready file, not requiring a pass thru the - "pstops" filter (to speak more technical, it is not regarded as the - generic MIME type "application/postscript", but as the more special - MIME type "application/cups.vnd-postscript"), which therefore also - leads to the page accounting in "/var/log/cups/page_log" not receiving - the exact mumber of pages; instead the dummy page number of "1" is - logged in a standard setup) -

  • the Adobe driver has more options to "mis-configure" the PostScript - generated by it (like setting it inadvertedly to "Optimize for Speed", - instead of "Optimize for Portability", which could lead to CUPS being - unable to process it) -

  • the CUPS PostScript driver output sent by Windows clients to the CUPS - server will be guaranteed to be auto-typed as generic MIME type - "application/postscript", thusly passing thru the CUPS "pstops" filter - and logging the correct number of pages in the page_log for accounting - and quota purposes -

  • the CUPS PostScript driver supports the sending of additional print - options by the Win NT/2k/XP clients, such as naming the CUPS standard - banner pages (or the custom ones, should they be installed at the time - of driver download), using the CUPS "page-label" option, setting a - job-priority and setting the scheduled time of printing (with the option - to support additional useful IPP job attributes in the future). -

  • the CUPS PostScript driver supports the inclusion of the new - "*cupsJobTicket" comments at the beginnig of the PostScript file (which - could be used in the future for all sort of beneficial extensions on - the CUPS side, but which will not disturb any other application as those - will regard it as a comment and simply ignore it). -

  • the CUPS PostScript driver will be the heart of the fully fledged CUPS - IPP client for Windows NT/2k/XP to be released soon (probably alongside - the first Beta release for CUPS 1.2). -

14.11. Advanced Postscript Printing from MS Windows

Let the Windows Clients use a PostScript driver to deliver poistscript to -the samba print server (just like any Linux or Unix Client would also use -PostScript to send to the server)

Make the Unix printing subsystem to which Samba sends the job convert the -incoming PostScript files to the native print format of the target printers -(would be PCL if you have an HP printer)

Now if you are afraid that this would just mean using a *Generic* PostScript -driver for the clients that has no Simplex/Duplex selection, and no paper tray -choice, but you need them to be able to set up print jobs, with all the bells -and whistles of your printers:-

Not possible with traditional spooling systems
But perfectly supported by CUPS (which uses "PPD" files to - describe how to control the print options for PostScript and - non-PostScript devices alike... -

CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript -drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use -them to setup the job to their liking and CUPS will use the received job options -to make the (PCL-, ESC/P- or PostScript-) printer behave as required.

If you want to have the additional benefit of page count logging and accounting -then the CUPS PostScript driver is the best choice (better than the Adobe one).

If you want to make the drivers downloadable for the clients then "cupsaddsmb" is -your friend. It will setup the [print$] share on the Samba host to be ready to serve -the clients for a "point and print" driver installation.

What strings are attached?

There are some. But, given the sheer CPU power you can buy nowadays, -these can be overcome easily. The strings:

Well, if the CUPS/Samba side will have to print to many printers serving many users, -you probably will need to set up a second server (which can do automatic load balancing -with the first one, plus a degree of fail-over mechanism). Converting the incoming -PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work -of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM -than for the mere "raw spooling" task your current setup is solving. It all depends -on the avarage and peak printing load the server should be able to handle.

14.12. Auto-Deletion of CUPS spool files

Samba print files pass thru two "spool" directories. One the incoming directory -managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers] -section of smb.conf). Second is the spool directory of your UNIX print subsystem. -For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive -"RequestRoot /var/spool/cups".

I am not sure, which one of your directories keeps the files. From what you say, -it is most likely the Samba part.

For the CUPS part, you may want to consult:

http://localhost:631/sam.html#PreserveJobFiles
http://localhost:631/sam.html#PreserveJobHistory
http://localhost:631/sam.html#MaxJobs

There are the settings described for your CUPS daemon, which could lead to completed -job files not being deleted.

"PreserveJobHistory Yes" -- keeps some details of jobs in -cupsd's mind (well it keeps the "c12345", "c12346" etc. files -in the CUPS spool directory, which do a similar job as the -old-fashioned BSD-LPD control files). This is set to "Yes" -as a default.

"PreserveJobFiles Yes" -- keeps the job files themselves in -cupsd's mind (well it keeps the "d12345", "d12346" etc. files -in the CUPS spool directory...). This is set to "No" as the -CUPS default.

"MaxJobs 500" -- this directive controls the maximum number -of jobs that are kept in memory. Once the number of jobs -reaches the limit, the oldest completed job is automatically -purged from the system to make room for the new one. If all -of the known jobs are still pending or active then the new -job will be rejected. Setting the maximum to 0 disables this -functionality. The default setting is 0.

(There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...)

For everything to work as announced, you need to have three things:

a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`) -
a Samba-smb.conf setting of printing = cups -
another Samba-smb.conf setting of printcap = cups -

Note, that in this case all other manually set printing-related -commands (like "print command", "lpq command", "lprm command", -"lppause command" or "lpresume command") are ignored and they -should normally have no influence what-so-ever on your printing.

If you want to do things manually, replace the "printing = cups" -by "printing = bsd". Then your manually set commands may work -(haven't tested this), and a "print command = lp -d %P %s; rm %s" -may do what you need.

You forgot to mention the CUPS version you're using. If you did -set things up as described in the man pages, then the Samba -spool files should be deleted. Otherwise it may be a bug. On -the CUPS side, you can control the behaviour as described -above.

If you have more problems, post the output of these commands:

grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ - grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

(adapt paths as needed). These commands sanitize the files -and cut out the empty lines and lines with comments, providing -the "naked settings" in a compact way.

PrevHomeNext
Printing SupportUpUnified Logons between Windows NT and UNIX using Winbind
\ No newline at end of file diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html deleted file mode 100644 index ddbc4624b8..0000000000 --- a/docs/htmldocs/domain-security.html +++ /dev/null @@ -1,427 +0,0 @@ - -Samba as a NT4 or Win2k domain member
SAMBA Project Documentation
PrevNext

Chapter 9. Samba as a NT4 or Win2k domain member

9.1. Joining an NT Domain with Samba 3.0

Assume you have a Samba 3.0 server with a NetBIOS name of - SERV1 and are joining an or Win2k NT domain called - DOM, which has a PDC with a NetBIOS name - of DOMPDC and two backup domain controllers - with NetBIOS names DOMBDC1 and DOMBDC2 - .

Firstly, you must edit your smb.conf file to tell Samba it should - now use domain security.

Change (or add) your security = line in the [global] section - of your smb.conf to read:

security = domain

Next change the workgroup = line in the [global] section to read:

workgroup = DOM

as this is the name of the domain we are joining.

You must also have the parameter encrypt passwords set to yes - in order for your users to authenticate to the NT PDC.

Finally, add (or modify) a password server = line in the [global] - section to read:

password server = DOMPDC DOMBDC1 DOMBDC2

These are the primary and backup domain controllers Samba - will attempt to contact in order to authenticate users. Samba will - try to contact each of these servers in order, so you may want to - rearrange this list in order to spread out the authentication load - among domain controllers.

Alternatively, if you want smbd to automatically determine - the list of Domain controllers to use for authentication, you may - set this line to be :

password server = *

This method, allows Samba to use exactly the same - mechanism that NT does. This - method either broadcasts or uses a WINS database in order to - find domain controllers to authenticate against.

In order to actually join the domain, you must run this - command:

root# net rpc join -S DOMPDC - -UAdministrator%password

as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. The Administrator%password is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:

Joined domain DOM. - or Joined 'SERV1' to realm 'MYREALM' -

in your terminal window. See the net(8) man page for more details.

This process joins the server to thedomain - without having to create the machine trust account on the PDC - beforehand.

This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :

/usr/local/samba/private/secrets.tdb

This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.

Finally, restart your Samba daemons and get ready for - clients to begin using domain security!

9.2. Why is this better than security = server?

Currently, domain security in Samba doesn't free you from - having to create local Unix users to represent the users attaching - to your server. This means that if domain user DOM\fred - attaches to your domain security Samba server, there needs - to be a local Unix user fred to represent that user in the Unix - filesystem. This is very similar to the older Samba security mode - security = server, - where Samba would pass through the authentication request to a Windows - NT server in the same way as a Windows 95 or Windows 98 server would. -

Please refer to the Winbind - paper for information on a system to automatically - assign UNIX uids and gids to Windows NT Domain users and groups. - This code is available in development branches only at the moment, - but will be moved to release branches soon.

The advantage to domain-level security is that the - authentication in domain-level security is passed down the authenticated - RPC channel in exactly the same way that an NT server would do it. This - means Samba servers now participate in domain trust relationships in - exactly the same way NT servers do (i.e., you can add Samba servers into - a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC.

In addition, with security = server every Samba - daemon on a server has to keep a connection open to the - authenticating server for as long as that daemon lasts. This can drain - the connection resources on a Microsoft NT server and cause it to run - out of available connections. With security = domain, - however, the Samba daemons connect to the PDC/BDC only for as long - as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.

And finally, acting in the same manner as an NT server - authenticating to a PDC means that as part of the authentication - reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc.

Much of the text of this document - was first published in the Web magazine - LinuxWorld as the article Doing - the NIS/NT Samba.

PrevHomeNext
Samba as a ADS domain memberUpAdvanced Configuration
\ No newline at end of file diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html deleted file mode 100644 index 9c25717238..0000000000 --- a/docs/htmldocs/groupprofiles.html +++ /dev/null @@ -1,568 +0,0 @@ - -Creating Group Prolicy Files
SAMBA Project Documentation
PrevNext

Chapter 21. Creating Group Prolicy Files

21.1. Windows '9x

You need the Win98 Group Policy Editor to -set Group Profiles up under Windows '9x. It can be found on the Original -full product Win98 installation CD under -tools/reskit/netadmin/poledit. You install this -using the Add/Remove Programs facility and then click on the 'Have Disk' -tab.

Use the Group Policy Editor to create a policy file that specifies the -location of user profiles and/or the My Documents etc. -stuff. You then save these settings in a file called -Config.POL that needs to be placed in -the root of the [NETLOGON] share. If your Win98 is configured to log onto -the Samba Domain, it will automatically read this file and update the -Win9x/Me registry of the machine that is logging on.

All of this is covered in the Win98 Resource Kit documentation.

If you do not do it this way, then every so often Win9x/Me will check the -integrity of the registry and will restore it's settings from the back-up -copy of the registry it stores on each Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.

The following all refers to Windows NT/200x profile migration - not to policies. -We need a separate section on policies (NTConfig.Pol) for NT4/200x.

21.2. Windows NT 4

Unfortunately, the Resource Kit info is Win NT4 or 200x specific.

Here is a quick guide:

  • On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'.

  • Select a user profile you want to migrate and click on it.

    I am using the term "migrate" lossely. You can copy a profile to -create a group profile. You can give the user 'Everyone' rights to the -profile you copy this to. That is what you need to do, since your samba -domain is not a member of a trust relationship with your NT4 PDC.

  • Click the 'Copy To' button.

  • In the box labelled 'Copy Profile to' add your new path, eg: -c:\temp\foobar

  • Click on the button labelled 'Change' in the "Permitted to use" box.

  • Click on the group 'Everyone' and then click OK. This closes the -'chose user' box.

  • Now click OK.

Follow the above for every profile you need to migrate.

21.2.1. Side bar Notes

You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users.

21.2.2. Mandatory profiles

The above method can be used to create mandatory profiles also. To convert -a group profile into a mandatory profile simply locate the NTUser.DAT file -in the copied profile and rename it to NTUser.MAN.

21.2.3. moveuser.exe

The W2K professional resource kit has moveuser.exe. moveuser.exe changes -the security of a profile from one user to another. This allows the account -domain to change, and/or the user name to change.

21.2.4. Get SID

You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 -Resource Kit.

Windows NT 4.0 stores the local profile information in the registry under -the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Under the ProfileList key, there will be subkeys named with the SIDs of the -users who have logged on to this computer. (To find the profile information -for the user whose locally cached profile you want to move, find the SID for -the user with the GetSID.exe utility.) Inside of the appropriate user's -subkey, you will see a string value named ProfileImagePath.

21.3. Windows 2000/XP

You must first convert the profile from a local profile to a domain -profile on the MS Windows workstation as follows:

  • Log on as the LOCAL workstation administrator.

  • Right click on the 'My Computer' Icon, select 'Properties'

  • Click on the 'User Profiles' tab

  • Select the profile you wish to convert (click on it once)

  • Click on the button 'Copy To'

  • In the "Permitted to use" box, click on the 'Change' button.

  • Click on the 'Look in" area that lists the machine name, when you click -here it will open up a selection box. Click on the domain to which the -profile must be accessible.

    You will need to log on if a logon box opens up. Eg: In the connect -as: MIDEARTH\root, password: mypassword.

  • To make the profile capable of being used by anyone select 'Everyone'

  • Click OK. The Selection box will close.

  • Now click on the 'Ok' button to create the profile in the path you -nominated.

Done. You now have a profile that can be editted using the samba-3.0.0 -profiles tool.

Under NT/2K the use of mandotory profiles forces the use of MS Exchange -storage of mail data. That keeps desktop profiles usable.

  • This is a security check new to Windows XP (or maybe only -Windows XP service pack 1). It can be disabled via a group policy in -Active Directory. The policy is:

    "Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders"

    ...and it should be set to "Enabled". -Does the new version of samba have an Active Directory analogue? If so, -then you may be able to set the policy through this.

    If you cannot set group policies in samba, then you may be able to set -the policy locally on each machine. If you want to try this, then do -the following (N.B. I don't know for sure that this will work in the -same way as a domain group policy):

  • On the XP workstation log in with an Administrator account.

  • Click: "Start", "Run"

  • Type: "mmc"

  • Click: "OK"

  • A Microsoft Management Console should appear.

  • Click: File, "Add/Remove Snap-in...", "Add"

  • Double-Click: "Group Policy"

  • Click: "Finish", "Close"

  • Click: "OK"

  • In the "Console Root" window:

  • Expand: "Local Computer Policy", "Computer Configuration",

  • "Administrative Templates", "System", "User Profiles"

  • Double-Click: "Do not check for user ownership of Roaming Profile

  • Folders"

  • Select: "Enabled"

  • Click: OK"

  • Close the whole console. You do not need to save the settings (this -refers to the console settings rather than the policies you have -changed).

  • Reboot

PrevHomeNext
Samba performance issuesUpSecuring Samba
\ No newline at end of file diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html deleted file mode 100644 index 209dfaaf54..0000000000 --- a/docs/htmldocs/improved-browsing.html +++ /dev/null @@ -1,1094 +0,0 @@ - -Improved browsing in samba
SAMBA Project Documentation
PrevNext

Chapter 24. Improved browsing in samba

Table of Contents
24.1. Overview of browsing
24.2. Browsing support in samba
24.3. Problem resolution
24.4. Browsing across subnets
24.5. Setting up a WINS server
24.6. Setting up Browsing in a WORKGROUP
24.7. Setting up Browsing in a DOMAIN
24.8. Forcing samba to be the master
24.9. Making samba the domain master
24.10. Note about broadcast addresses
24.11. Multiple interfaces

24.1. Overview of browsing

SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called browse list. This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document.

MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.

Where NetBIOS over TCP/IP is enabled use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution.

24.2. Browsing support in samba

Samba facilitates browsing. The browsing is supported by nmbd -and is also controlled by options in the smb.conf file. -Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available.

Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server.

Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service.

Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.

To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in smb.conf -to control what workgroup Samba becomes a part of.

Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the -smb.conf man page.

24.3. Problem resolution

If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.

Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then -hit enter and filemanager should display the list of available shares.

Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must -have a valid guest account.

MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.

The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in smb.conf)

24.4. Browsing across subnets

Since the release of Samba 1.9.17(alpha1) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings.

To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server.

Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the smb.conf file.

24.4.1. How does cross subnet browsing work ?

Cross subnet browsing is a complicated dance, containing multiple -moving parts. It has taken Microsoft several years to get the code -that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly.

Consider a network set up as follows :

                                   (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)

Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it.

As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser.

On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list.

For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'.

At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now).

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

Note that at this point all the subnets are separate, no -machine is seen across any of the subnets.

Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted.

Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like :

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.

At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet.

The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like.

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.

At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on -subnet 2 will still only see the servers on subnets 1 and 2, but not 3.

Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing -server entries. Finally - and as a steady state (if no machines -are removed or shut off) the browse lists will look like :

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-	
-Servers with a (*) after them are non-authoritative names.

Synchronizations between the domain master browser and local -master browsers will continue to occur, but this should be a -steady state situation.

If either router R1 or R2 fails the following will occur:

  1. Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. -

  2. Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. -

  3. If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. -

24.5. Setting up a WINS server

Either a Samba machine or a Windows NT Server machine may be set up -as a WINS server. To set a Samba machine to be a WINS server you must -add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line

wins support = yes

Versions of Samba prior to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to a recent version, or at the very -least set the parameter to 'no' on all these machines.

Machines with wins support = yes will keep a list of -all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

You should set up only ONE wins server. Do NOT set the -wins support = yes option on more than one Samba -server.

To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the -wins support = yes parameter set.

After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files :

wins server = >name or IP address<

where >name or IP address< is either the DNS name of the WINS server -machine or its IP address.

Note that this line MUST NOT BE SET in the smb.conf file of the Samba -server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then -nmbd will fail to start.

There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains.

24.6. Setting up Browsing in a WORKGROUP

To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup.

In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the smb.conf file :

domain master = yes

The domain master browser should also preferrably be the local master -browser for its own subnet. In order to achieve this set the following -options in the [global] section of the smb.conf file :

domain master = yes
-local master = yes
-preferred master = yes
-os level = 65

The domain master browser may be the same machine as the WINS -server, if you require.

Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the -smb.conf file :

domain master = no
-local master = yes
-preferred master = yes
-os level = 65

Do not do this for more than one Samba server on each subnet, -or they will war with each other over which is to be the local -master browser.

The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level -parameter sets Samba high enough so that it should win any browser elections.

If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the [global] section of the -smb.conf file :

domain master = no
-local master = no
-preferred master = no
-os level = 0

24.7. Setting up Browsing in a DOMAIN

If you are adding Samba servers to a Windows NT Domain then -you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN<1B>) -with WINS instead of the PDC.

For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the [global] section -of the smb.conf file :

domain master = no
-local master = yes
-preferred master = yes
-os level = 65

If you wish to have a Samba server fight the election with machines -on the same subnet you may set the os level parameter -to lower levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section Forcing samba to be the master browser -below.

If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the [global] section of the smb.conf -file :

domain master = no - local master = no - preferred master = no - os level = 0

24.8. Forcing samba to be the master

Who becomes the master browser is determined by an election -process using broadcasts. Each election packet contains a number of parameters -which determine what precedence (bias) a host should have in the -election. By default Samba uses a very low precedence and thus loses -elections to just about anyone else.

If you want Samba to win elections then just set the os level global -option in smb.conf to a higher number. It defaults to 0. Using 34 -would make it win all elections over every other system (except other -samba systems!)

A os level of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

The maximum os level is 255

If you want samba to force an election on startup, then set the -preferred master global option in smb.conf to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with preferred master to -"yes", then periodically and continually they will force an election -in order to become the local master browser.

If you want samba to be a domain master browser, then it is -recommended that you also set preferred master to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet.

It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail.

24.9. Making samba the domain master

The domain master is responsible for collating the browse lists of -multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting domain master = yes -in smb.conf. By default it will not be a domain master.

Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain.

When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists.

If you want samba to be the domain master then I suggest you also set -the os level high enough to make sure it wins elections, and set -preferred master to "yes", to get samba to force an election on -startup.

Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur:

  1. your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. -

  2. if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. -

If, however, both samba and your clients are using a WINS server, then:

  1. your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address - as its domain master browser. -

  2. when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. -

24.10. Note about broadcast addresses

If your network uses a "0" based broadcast address (for example if it -ends in a 0) then you will strike problems. Windows for Workgroups -does not seem to support a 0's broadcast and you will probably find -that browsing and name lookups won't work.

24.11. Multiple interfaces

Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces -option in smb.conf to configure them.

PrevHomeNext
Integrating MS Windows networks with SambaUpSecuring Samba
\ No newline at end of file diff --git a/docs/htmldocs/index.html b/docs/htmldocs/index.html deleted file mode 100755 index f7bc47b7c8..0000000000 --- a/docs/htmldocs/index.html +++ /dev/null @@ -1,76 +0,0 @@ -SAMBA Project Documentation
SAMBA Project Documentation
   Next

SAMBA Project Documentation

Edited by

Jelmer R. Vernooij

John H. Terpstra

Gerald (Jerry) Carter

-This documentation is distributed under the GNU General Public License (GPL) -version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt -

Attributions.  -

Introduction to Samba
How to Install and Test SAMBA
Fast Start for the Impatient
Server Types and Security Modes
Domain Control
Backup Domain Control
Domain Membership
Stand-Alone Servers
MS Windows Network Configuration Guide
Samba / MS Windows Network Browsing Guide
Account Information Databases
Mapping MS Windows and Unix Groups
File, Directory and Share Access Controls
File and Record Locking
Securing Samba
Interdomain Trust Relationships
Hosting a Microsoft Distributed File System tree on Samba
Classical Printing Support
CUPS Printing Support in Samba 3.0
Stackable VFS modules

  • Jelmer Vernooij <jelmer@samba.org>

  • John Terpstra <jht@samba.org>

  • Tim Potter

  • Simo Sorce (original vfs_skel README)

  • Alexander Bokovoy (original vfs_netatalk docs)

  • Stefan Metzmacher (Update for multiple modules)

Integrated Logon Support using Winbind
Advanced Network Management
System and Account Policies
Desktop Profile Management
PAM based Distributed Authentication
Integrating MS Windows networks with Samba
Unicode/Charsets
Samba Backup Techniques
High Availability Options
Upgrading from Samba-2.x to Samba-3.0.0
Migration from NT4 PDC to Samba-3 PDC
SWAT - The Samba Web Administration Tool
The Samba checklist
Analysing and solving samba problems
Reporting Bugs
How to compile SAMBA
Portability
Samba and other CIFS clients
Samba Performance Tuning
DNS and DHCP Configuration Guide
Further Resources

- -

Monday April 21, 2003

Abstract

-This book is a collection of HOWTOs added to Samba documentation over the years. -Samba is always under development, and so is its' documentation. This release of the -documentation represents a major revision or layout as well as contents. -The most recent version of this document can be found at -http://www.samba.org/ -on the "Documentation" page. Please send updates to -Jelmer Vernooij, -John H. Terpstra or -Gerald (Jerry) Carter. -

-The Samba-Team would like to express sincere thanks to the many people who have with -or without their knowledge contributed to this update. The size and scope of this -project would not have been possible without significant community contribution. A not -insignificant number of ideas for inclusion (if not content itself) has been obtained -from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. -Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and -application knowledge that is most to be desired by many Samba users and administrators. -

Table of Contents

I. General Installation
1. Introduction to Samba
Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous
2. How to Install and Test SAMBA
Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your - server
Try connecting with the unix client
Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
What If Things Don't Work?
Common Errors
Why are so many smbd processes eating memory?
I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
3. Fast Start for the Impatient
Note
II. Server Configuration Basics
4. Server Types and Security Modes
Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Seamless Windows Network Integration
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server
5. Domain Control
Features and Benefits
Basics of Domain Control
Domain Controller Types
Preparing for Domain Control
Domain Control - Example Configuration
Samba ADS Domain Control
Domain and Network Logon Configuration
Domain Network Logon Service
Security Mode and Master Browsers
Common Problems and Errors
I cannot include a '$' in a machine name
I get told "You already have a connection to the Domain...." -or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.
The system can not log you on (C000019B)....
The machine trust account for this computer either does not -exist or is not accessible.
When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"
6. Backup Domain Control
Features And Benefits
Essential Background Information
MS Windows NT4 Style Domain Control
Active Directory Domain Control
What qualifies a Domain Controller on the network?
How does a Workstation find its domain controller?
Backup Domain Controller Configuration
Example Configuration
Common Errors
Machine Accounts keep expiring, what can I do?
Can Samba be a Backup Domain Controller to an NT4 PDC?
How do I replicate the smbpasswd file?
Can I do this all with LDAP?
7. Domain Membership
Features and Benefits
MS Windows Workstation/Server Machine Trust Accounts
Manual Creation of Machine Trust Accounts
Using NT4 Server Manager to Add Machine Accounts to the Domain
"On-the-Fly" Creation of Machine Trust Accounts
Making an MS Windows Workstation or Server a Domain Member
Domain Member Server
Joining an NT4 type Domain with Samba-3
Why is this better than security = server?
Samba ADS Domain Membership
Setup your smb.conf
Setup your /etc/krb5.conf
Create the computer account
Test your server setup
Testing with smbclient
Notes
Common Errors
Can Not Add Machine Back to Domain
Adding Machine to Domain Fails
8. Stand-Alone Servers
Features and Benefits
Background
Example Configuration
Reference Documentation Server
Central Print Serving
Common Errors
9. MS Windows Network Configuration Guide
Note
III. Advanced Configuration
10. Samba / MS Windows Network Browsing Guide
Features and Benefits
What is Browsing?
Discussion
NetBIOS over TCP/IP
TCP/IP - without NetBIOS
DNS and Active Directory
How Browsing Functions
Setting up WORKGROUP Browsing
Setting up DOMAIN Browsing
Forcing Samba to be the master
Making Samba the domain master
Note about broadcast addresses
Multiple interfaces
Use of the Remote Announce parameter
Use of the Remote Browse Sync parameter
WINS - The Windows Internetworking Name Server
Setting up a WINS server
WINS Replication
Static WINS Entries
Helpful Hints
Windows Networking Protocols
Name Resolution Order
Technical Overview of browsing
Browsing support in Samba
Problem resolution
Browsing across subnets
Common Errors
How can one flush the Samba NetBIOS name cache without restarting Samba?
My client reports "This server is not configured to list shared resources"
11. Account Information Databases
Features and Benefits
Technical Information
Important Notes About Security
Mapping User Identifiers between MS Windows and Unix
Account Management Tools
The smbpasswd Command
The pdbedit Command
Password Backends
Plain Text
smbpasswd - Encrypted Password Database
tdbsam
ldapsam
MySQL
XML
Common Errors
Users can not logon - Users not in Samba SAM
Users are being added to the wrong backend database
auth methods does not work
12. Mapping MS Windows and Unix Groups
Features and Benefits
Discussion
Example Configuration
Configuration Scripts
Sample smb.conf add group script
Script to configure Group Mapping
Common Errors
Adding Groups Fails
Adding MS Windows Groups to MS Windows Groups Fails
13. File, Directory and Share Access Controls
Features and Benefits
File System Access Controls
MS Windows NTFS Comparison with Unix File Systems
Managing Directories
File and Directory Access Control
Share Definition Access Controls
User and Group Based Controls
File and Directory Permissions Based Controls
Miscellaneous Controls
Access Controls on Shares
Share Permissions Management
MS Windows Access Control Lists and Unix Interoperability
Managing UNIX permissions Using NT Security Dialogs
Viewing File Security on a Samba Share
Viewing file ownership
Viewing File or Directory Permissions
Modifying file or directory permissions
Interaction with the standard Samba create mask - parameters
Interaction with the standard Samba file attribute - mapping
Common Errors
Users can not write to a public share
I have set force user and Samba still makes root the owner of all the files - I touch!
14. File and Record Locking
Features and Benefits
Discussion
Opportunistic Locking Overview
Samba Opportunistic Locking Control
Example Configuration
MS Windows Opportunistic Locking and Caching Controls
Workstation Service Entries
Server Service Entries
Persistent Data Corruption
Common Errors
locking.tdb error messages
Additional Reading
15. Securing Samba
Introduction
Features and Benefits
Technical Discussion of Protective Measures and Issues
Using host based protection
User based protection
Using interface protection
Using a firewall
Using a IPC$ share deny
NTLMv2 Security
Upgrading Samba
Common Errors
Smbclient works on localhost, but the network is dead
Why can users access home directories of other users?
16. Interdomain Trust Relationships
Features and Benefits
Trust Relationship Background
Native MS Windows NT4 Trusts Configuration
NT4 as the Trusting Domain (ie. creating the trusted account)
NT4 as the Trusted Domain (ie. creating trusted account's password)
Configuring Samba NT-style Domain Trusts
Samba-3 as the Trusting Domain
Samba-3 as the Trusted Domain
Common Errors
Tell me about Trust Relationships using Samba
17. Hosting a Microsoft Distributed File System tree on Samba
Features and Benefits
Common Errors
18. Classical Printing Support
Features and Benefits
Technical Introduction
What happens if you send a Job from a Client
Printing Related Configuration Parameters
Parameters Recommended for Use
Parameters for Backwards Compatibility
Parameters no longer in use
A simple Configuration to Print with Samba-3
Verification of "Settings in Use" with testparm
A little Experiment to warn you
Extended Sample Configuration to Print with Samba-3
Detailed Explanation of the Example's Settings
The [global] Section
The [printers] Section
Any [my_printer_name] Section
Print Commands
Default Print Commands for various Unix Print Subsystems
Setting up your own Print Commands
Innovations in Samba Printing since 2.2
Client Drivers on Samba Server for Point'n'Print
The [printer$] Section is removed from Samba-3
Creating the [print$] Share
Parameters in the [print$] Section
Subdirectory Structure in [print$]
Installing Drivers into [print$]
Setting Drivers for existing Printers with a Client GUI
Setting Drivers for existing Printers with -rpcclient
"The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
The first Client Driver Installation
IMPORTANT! Setting Device Modes on new Printers
Further Client Driver Install Procedures
Always make first Client Connection as root or "printer admin"
Other Gotchas
Setting Default Print Options for the Client Drivers
Supporting large Numbers of Printers
Adding new Printers with the Windows NT APW
Weird Error Message Cannot connect under a -different Name
Be careful when assembling Driver Files
Samba and Printer Ports
Avoiding the most common Misconfigurations of the Client Driver
The Imprints Toolset
What is Imprints?
Creating Printer Driver Packages
The Imprints Server
The Installation Client
Add Network Printers at Logon without User Interaction
The addprinter command
Migration of "Classical" printing to Samba-3
Publishing Printer Information in Active Directory or LDAP
Common Errors and Problems
I give my root password but I don't get access
My printjobs get spooled into the spooling directory, but then get lost
19. CUPS Printing Support in Samba 3.0
Introduction
Features and Benefits
Overview
Basic Configuration of CUPS support
Linking of smbd with libcups.so
Simple smb.conf Settings for CUPS
More complex smb.conf Settings for -CUPS
Advanced Configuration
Central spooling vs. "Peer-to-Peer" printing
CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
Driver Installation Methods on Windows Clients
Explicitly enable "raw" printing for -application/octet-stream!
Three familiar Methods for driver upload plus a new one
Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download
GDI on Windows -- PostScript on Unix
Windows Drivers, GDI and EMF
Unix Printfile Conversion and GUI Basics
PostScript and Ghostscript
Ghostscript -- the Software RIP for non-PostScript Printers
PostScript Printer Description (PPD) Specification
CUPS can use all Windows-formatted Vendor PPDs
CUPS also uses PPDs for non-PostScript Printers
The CUPS Filtering Architecture
MIME types and CUPS Filters
MIME type Conversion Rules
Filter Requirements
Prefilters
pstops
pstoraster
imagetops and imagetoraster
rasterto [printers specific]
CUPS Backends
cupsomatic/Foomatic -- how do they fit into the Picture?
The Complete Picture
mime.convs
"Raw" printing
"application/octet-stream" printing
PostScript Printer Descriptions (PPDs) for non-PS Printers
Difference between cupsomatic/foomatic-rip and -native CUPS printing
Examples for filtering Chains
Sources of CUPS drivers / PPDs
Printing with Interface Scripts
Network printing (purely Windows)
From Windows Clients to an NT Print Server
Driver Execution on the Client
Driver Execution on the Server
Network Printing (Windows clients -- UNIX/Samba Print -Servers)
From Windows Clients to a CUPS/Samba Print Server
Samba receiving Jobfiles and passing them to CUPS
Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
PPDs for non-PS Printers on UNIX
PPDs for non-PS Printers on Windows
Windows Terminal Servers (WTS) as CUPS Clients
Printer Drivers running in "Kernel Mode" cause many -Problems
Workarounds impose Heavy Limitations
CUPS: a "Magical Stone"?
PostScript Drivers with no major problems -- even in Kernel -Mode
Setting up CUPS for driver Download
cupsaddsmb: the unknown Utility
Prepare your smb.conf for -cupsaddsmb
CUPS Package of "PostScript Driver for WinNT/2k/XP"
Recognize the different Driver Files
Acquiring the Adobe Driver Files
ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
Caveats to be considered
What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
Run "cupsaddsmb" (quiet Mode)
Run "cupsaddsmb" with verbose Output
Understanding cupsaddsmb
How to recognize if cupsaddsm completed successfully
cupsaddsmb with a Samba PDC
cupsaddsmb Flowchart
Installing the PostScript Driver on a Client
Avoiding critical PostScript Driver Settings on the -Client
Installing PostScript Driver Files manually (using -rpcclient)
A Check of the rpcclient man Page
Understanding the rpcclient man Page
Producing an Example by querying a Windows Box
What is required for adddriver and setdriver to succeed
Manual Commandline Driver Installation in 15 little Steps
Troubleshooting revisited
The printing *.tdb Files
Trivial DataBase Files
Binary Format
Losing *.tdb Files
Using tdbbackup
CUPS Print Drivers from Linuxprinting.org
foomatic-rip and Foomatic explained
foomatic-rip and Foomatic-PPD Download and Installation
Page Accounting with CUPS
Setting up Quotas
Correct and incorrect Accounting
Adobe and CUPS PostScript Drivers for Windows Clients
The page_log File Syntax
Possible Shortcomings
Future Developments
Other Accounting Tools
Additional Material
Auto-Deletion or Preservation of CUPS Spool Files
CUPS Configuration Settings explained
Pre-conditions
Manual Configuration
When not to use Samba to print to -CUPS
In Case of Trouble.....
Where to find Documentation
How to ask for Help
Where to find Help
Appendix
Printing from CUPS to Windows attached -Printers
More CUPS filtering Chains
Trouble Shooting Guidelines to fix typical Samba printing -Problems
An Overview of the CUPS Printing Processes
20. Stackable VFS modules
Features and Benefits
Discussion
Included modules
audit
extd_audit
fake_perms
recycle
netatalk
VFS modules available elsewhere
DatabaseFS
vscan
Common Errors
21. Integrated Logon Support using Winbind
Features and Benefits
Introduction
What Winbind Provides
Target Uses
How Winbind Works
Microsoft Remote Procedure Calls
Microsoft Active Directory Services
Name Service Switch
Pluggable Authentication Modules
User and Group ID Allocation
Result Caching
Installation and Configuration
Introduction
Requirements
Testing Things Out
Conclusion
Common Errors
22. Advanced Network Management
Features and Benefits
Remote Server Administration
Remote Desktop Management
Remote Management from NoMachines.Com
Network Logon Script Magic
Adding printers without user intervention
Common Errors
23. System and Account Policies
Features and Benefits
Creating and Managing System Policies
Windows 9x/Me Policies
Windows NT4 Style Policy Files
MS Windows 200x / XP Professional Policies
Managing Account/User Policies
Samba Editreg Toolset
Windows NT4/200x
Samba PDC
System Startup and Logon Processing Overview
Common Errors
Policy Does Not Work
24. Desktop Profile Management
Features and Benefits
Roaming Profiles
Samba Configuration for Profile Handling
Windows Client Profile Configuration Information
Sharing Profiles between W9x/Me and NT4/200x/XP workstations
Profile Migration from Windows NT4/200x Server to Samba
Mandatory profiles
Creating/Managing Group Profiles
Default Profile for Windows Users
MS Windows 9x/Me
MS Windows NT4 Workstation
MS Windows 200x/XP
Common Errors
How does one set up roaming profiles for just one (or a few) user/s or group/s?
Can NOT use Roaming Profiles
Changing the default profile
25. PAM based Distributed Authentication
Features and Benefits
Technical Discussion
PAM Configuration Syntax
Example System Configurations
smb.conf PAM Configuration
Remote CIFS Authentication using winbindd.so
Password Synchronization using pam_smbpass.so
Common Errors
pam_winbind problem
26. Integrating MS Windows networks with Samba
Features and Benefits
Background Information
Name Resolution in a pure Unix/Linux world
/etc/hosts
/etc/resolv.conf
/etc/host.conf
/etc/nsswitch.conf
Name resolution as used within MS Windows networking
The NetBIOS Name Cache
The LMHOSTS file
HOSTS file
DNS Lookup
WINS Lookup
Common Errors
My Boomerang Won't Come Back
Very Slow Network Connections
Samba server name change problem
27. Unicode/Charsets
Features and Benefits
What are charsets and unicode?
Samba and charsets
Conversion from old names
Japanese charsets
28. Samba Backup Techniques
Note
Features and Benefits
29. High Availability Options
Note
IV. Migration and Updating
30. Upgrading from Samba-2.x to Samba-3.0.0
Charsets
Obsolete configuration options
Password Backend
31. Migration from NT4 PDC to Samba-3 PDC
Planning and Getting Started
Objectives
Steps In Migration Process
Migration Options
Planning for Success
Samba Implementation Choices
32. SWAT - The Samba Web Administration Tool
Features and Benefits
Enabling SWAT for use
Securing SWAT through SSL
The SWAT Home Page
Global Settings
Share Settings
Printers Settings
The SWAT Wizard
The Status Page
The View Page
The Password Change Page
V. Troubleshooting
33. The Samba checklist
Introduction
Assumptions
The tests
Still having troubles?
34. Analysing and solving samba problems
Diagnostics tools
Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
Useful URLs
Getting help from the mailing lists
How to get off the mailing lists
35. Reporting Bugs
Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches
VI. Appendixes
36. How to compile SAMBA
Access Samba source code via CVS
Introduction
CVS Access to samba.org
Accessing the samba sources via rsync and ftp
Verifying Samba's PGP signature
Building the Binaries
Compiling samba with Active Directory support
Starting the smbd and nmbd
Starting from inetd.conf
Alternative: starting it as a daemon
Common Errors
37. Portability
HPUX
SCO Unix
DNIX
RedHat Linux Rembrandt-II
AIX
Sequential Read Ahead
Solaris
Locking improvements
Winbind on Solaris 9
38. Samba and other CIFS clients
Macintosh clients?
OS2 Client
How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
How do I get printer driver download working - for OS/2 clients?
Windows for Workgroups
Use latest TCP/IP stack from Microsoft
Delete .pwl files after password change
Configure WfW password handling
Case handling of passwords
Use TCP/IP as default protocol
Speed improvement
Windows '95/'98
Speed improvement
Windows 2000 Service Pack 2
Windows NT 3.1
39. Samba Performance Tuning
Comparisons
Socket options
Read size
Max xmit
Log level
Read raw
Write raw
Slow Logins
Client tuning
Samba performance problem due changing kernel
Corrupt tdb Files
40. DNS and DHCP Configuration Guide
Note
41. Further Resources
Websites
Related updates from Microsoft
Books
Index

List of Figures

19.1. Windows Printing to a local Printer
19.2. Printing to a Postscript Printer
19.3. Ghostscript as a RIP for non-postscript printers
19.4. Prefiltering in CUPS to form Postscript
19.5. Adding Device-specific Print Options
19.6. Postscript to intermediate Raster format
19.7. CUPS-raster production using Ghostscript
19.8. Image format to CUPS-raster format conversion
19.9. Raster to Printer Specific formats
19.10. cupsomatic/foomatic processing versus Native CUPS
19.11. Print Driver execution on the Client
19.12. Print Driver execution on the Server
19.13. Printing via CUPS/samba server
19.14. cupsaddsmb flowchart
19.15. CUPS Printing Overview

List of Tables

7.1. Assumptions
10.1. Browse subnet example 1
10.2. Browse subnet example 2
10.3. Browse subnet example 3
10.4. Browse subnet example 4
11.1. Attributes in the sambaSamAccount objectclass (LDAP)
11.2. Basic smb.conf options for MySQL passdb backend
11.3. MySQL field names for MySQL passdb backend
13.1. Managing directories with unix and windows
13.2. User and Group Based Controls
13.3. File and Directory Permission Based Controls
13.4. Other Controls
20.1. Extended Auditing Log Information
24.1. User Shell Folder registry keys default values
24.2. Defaults of profile settings registry keys
24.3. Defaults of default user profile paths registry keys
25.1. Options recognized by pam_smbpass
31.1. The 3 Major Site Types
31.2. Nature of the Conversion Choices

List of Examples

12.1. smbgrpadd.sh
13.1. Example File
   Next
   Part I. General Installation
diff --git a/docs/htmldocs/interdomaintrusts.html b/docs/htmldocs/interdomaintrusts.html deleted file mode 100644 index c9fe4a533f..0000000000 --- a/docs/htmldocs/interdomaintrusts.html +++ /dev/null @@ -1,451 +0,0 @@ - -Interdomain Trust Relationships
SAMBA Project Documentation
PrevNext

Chapter 19. Interdomain Trust Relationships

Table of Contents
19.1. Trust Relationship Background
19.2. Native MS Windows NT4 Trusts Configuration
19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)
19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)
19.3. Configuring Samba NT-style Domain Trusts
19.3.1. Samba-3 as the Trusting Domain
19.3.2. Samba-3 as the Trusted Domain

Samba-3 supports NT4 style domain trust relationships. This is feature that many sites -will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to -adopt Active Directory or an LDAP based authentication back end. This section explains -some background information regarding trust relationships and how to create them. It is now -possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.

19.1. Trust Relationship Background

MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. -The limitations of this architecture as it affects the scalability of MS Windows networking -in large organisations is well known. Additionally, the flat-name space that results from -this design significantly impacts the delegation of administrative responsibilities in -large and diverse organisations.

Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means -of circumventing the limitations of the older technologies. Not every organisation is ready -or willing to embrace ADS. For small companies the older NT4 style domain security paradigm -is quite adequate, there thus remains an entrenched user base for whom there is no direct -desire to go through a disruptive change to adopt ADS.

Microsoft introduced with MS Windows NT the ability to allow differing security domains -to affect a mechanism so that users from one domain may be given access rights and privileges -in another domain. The language that describes this capability is couched in terms of -Trusts. Specifically, one domain will trust the users -from another domain. The domain from which users are available to another security domain is -said to be a trusted domain. The domain in which those users have assigned rights and privileges -is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, -thus if users in both domains are to have privileges and rights in each others' domain, then it is -necessary to establish two (2) relationships, one in each direction.

In an NT4 style MS security domain, all trusts are non-transitive. This means that if there -are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust -relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no -implied trust between the RED and BLUE domains. ie: Relationships are explicit and not -transitive.

New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way -by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE -domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is -an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 -style Interdomain trusts and interoperates with MS Windows 200x ADS -security domains in similar manner to MS Windows NT4 style domains.

19.2. Native MS Windows NT4 Trusts Configuration

There are two steps to creating an interdomain trust relationship.

19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)

For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. -To affect a two way trust relationship it is necessary for each domain administrator to make -available (for use by an external domain) it's security resources. This is done from the Domain -User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and -"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that -will be able to assign user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password needs to be -typed twice (for standard confirmation).

19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)

A trust relationship will work only when the other (trusting) domain makes the appropriate connections -with the trusted domain. To consumate the trust relationship the administrator will launch the -Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the -"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in -which must be entered the name of the remote domain as well as the password assigned to that trust.

19.3. Configuring Samba NT-style Domain Trusts

This description is meant to be a fairly short introduction about how to set up a Samba server so -that it could participate in interdomain trust relationships. Trust relationship support in Samba -is in its early stage, so lot of things don't work yet.

Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after -reading this document, that combining Samba-specific parts of what's written below leads to trust -between domains in purely Samba environment.

19.3.1. Samba-3 as the Trusting Domain

In order to set Samba PDC to be trusted party of the relationship first you need -to create special account for the domain that will be the trusting party. To do that, -you can use the 'smbpasswd' utility. Creating the trusted domain account is very -similiar to creating a trusted machine account. Suppose, your domain is -called SAMBA, and the remote domain is called RUMBA. The first step -will be to issue this command from your favourite shell:

    deity# smbpasswd -a -i rumba
-    	New SMB password: XXXXXXXX
-    	Retype SMB password: XXXXXXXX
-    	Added user rumba$
- -where -a means to add a new account into the -passdb database and -i means: ''create this -account with the InterDomain trust flag''

The account name will be 'rumba$' (the name of the remote domain)

After issuing this command you'll be asked to enter the password for -the account. You can use any password you want, but be aware that Windows NT will -not change this password until 7 days following account creation. -After the command returns successfully, you can look at the entry for new account -(in the way depending on your configuration) and see that account's name is -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm -the trust by establishing it from Windows NT Server.

Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. -Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for -the trusted domain name and the relationship password. Type in SAMBA, as this is -your domain name, and the password used at the time of account creation. -Press OK and, if everything went without incident, you will see 'Trusted domain relationship -successfully established' message.

19.3.2. Samba-3 as the Trusted Domain

This time activities are somewhat reversed. Again, we'll assume that your domain -controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.

The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.

Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. -Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted -domain (SAMBA) and password securing the relationship.

The password can be arbitrarily chosen. It is easy to change it the password -from Samba server whenever you want. After confirming the password your account is -ready for use. Now it's Samba's turn.

Using your favourite shell while being logged in as root, issue this command:

deity# net rpc trustdom establish rumba

You will be prompted for the password you just typed on your Windows NT4 Server box. -Don not worry if you see an error message that mentions a returned code of -NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the -password you gave is correct and the NT4 Server says the account is -ready for interdomain connection and not for ordinary -connection. After that, be patient it can take a while (especially -in large networks), you should see the 'Success' message. Congratulations! Your trust -relationship has just been established.

Note that you have to run this command as root because you must have write access to -the secrets.tdb file.

PrevHomeNext
Desktop Profile ManagementUpPAM Configuration for Centrally Managed Authentication
\ No newline at end of file diff --git a/docs/htmldocs/introsmb.html b/docs/htmldocs/introsmb.html deleted file mode 100644 index 52db6a8a95..0000000000 --- a/docs/htmldocs/introsmb.html +++ /dev/null @@ -1,659 +0,0 @@ - -Introduction to Samba
SAMBA Project Documentation
PrevNext

Chapter 1. Introduction to Samba

Table of Contents
1.1. Background
1.2. Terminology
1.3. Related Projects
1.4. SMB Methodology
1.5. Additional Resources
1.6. Epilogue
1.7. Miscellaneous

"If you understand what you're doing, you're not learning anything." --- Anonymous

Samba is a file and print server for Windows-based clients using TCP/IP as the underlying -transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big -strengths is that you can use it to blend your mix of Windows and Linux machines together -without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed -by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.

1.1. Background

Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed -Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was -originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only -ran over UDP. When there was a need to run it over TCP so that it would be compatible -with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became -known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to -license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the -concept continued in the form of SMB (Server Message Block, or the "what") using the -NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can -run SMB (i.e., transport) over several different protocols; many different implementations -arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT -(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form -of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing -term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 -only. As of yet, direct-hosted TCP has yet to catch on.

Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS: -Common Insecurities Fail Scrutiny:

Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba -stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have -been dutifully waded through during the information-gathering stages of this project, and there -are *still* many missing pieces... While often tedious, at least the way has been generously -littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they -thinking?

1.2. Terminology

  • SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. -

  • CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently - decided that SMB needed the word "Internet" in it, so they changed it to CIFS. -

  • Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp - only using DNS for name resolution instead of WINS. -

  • IPC: Acronym for "Inter-Process Communication". A method to communicate specific - information between programs. -

  • Marshalling: - A method of serializing (i.e., sequential ordering of) variable data - suitable for transmission via a network connection or storing in a file. The source - data can be re-created using a similar process called unmarshalling. -

  • NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; - it is a method of communication across an existing protocol. This is a standard which - was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, - it can help to think of this in comparison your computer's BIOS -- it controls the - essential functions of your input/output hardware -- whereas NetBIOS controls the - essential functions of your input/output traffic via the network. Again, this is a bit - of an exaggeration but it should help that paradigm shift. What is important to realize - is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically - brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second - thought; this will cause no end (and no doubt) of confusion. -

  • NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI - is a protocol, not a standard. It is also not routable, so traffic on one side of a - router will be unable to communicate with the other side. Understanding NetBEUI is - not essential to deciphering SMB; however it helps to point out that it is not the - same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally - referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". - It is not often heard from these days. -

  • NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use - of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made - to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. - This is how file and printer sharing are accomplished in Windows 95/98/ME. They - traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137, - NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service - (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, - and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 - (Detailed specifications). -

  • W2K: Acronym for Windows 2000 Professional or Server -

  • W3K: Acronym for Windows 2003 Server -

If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at -http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com

1.3. Related Projects

Currently, there are two projects that are directly related to Samba: SMBFS and CIFS network -client file systems for Linux, both available in the Linux kernel itself.

  • SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol - that Microsoft Windows and OS/2 Lan Manager use to share files and printers - over local networks) and access them just like any other Unix directory. This is useful - if you just want to mount such filesystems without being a SMBFS server. -

  • CIFS (Common Internet File System) is the successor to SMB, and is actively being worked - on in the upcoming version of the Linux kernel. The intent of this module is to - provide advanced network file system functionality including support for dfs (heirarchical - name space), secure per-user session establishment, safe distributed caching (oplock), - optional packet signing, Unicode and other internationalization improvements, and optional - Winbind (nsswitch) integration. -

Again, it's important to note that these are implementations for client filesystems, and have -nothing to do with acting as a file and print server for SMB/CIFS clients.

1.4. SMB Methodology

Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), -UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS -session service, or netbios-ssn). Anyone looking at their network with a good -packet sniffer will be amazed at the amount of traffic generated by just opening -up a single file. In general, SMB sessions are established in the following order:

  • "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp - or 445/tcp. -

  • "NetBIOS Session Request" - using the following "Calling Names": The local - machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS - name plus the 16th character 0x20 -

  • "SMB Negotiate Protocol" - determine the protocol dialect to use, which will - be one of the following: PC Network Program 1.0 (Core) - share level security - mode only; Microsoft Networks 1.03 (Core Plus) - share level security - mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response - Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response - Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response - Authentication -

  • SMB Session Startup. Passwords are encrypted (or not) according to one of - the following methods: Null (no encryption); Cleartext (no encryption); LM - and NTLM; NTLM; NTLMv2 -

  • SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect - to a service type (e.g., IPC$ named pipe) -

A good way to examine this process in depth is to try out SecurityFriday's SWB program -at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to -walk through the establishment of a SMB/CIFS session step by step.

1.5. Additional Resources

  • CIFS: Common Insecurities Fail Scrutiny by "Hobbit", - http://hr.uoregon.edu/davidrl/cifs.txt -

  • Doing the Samba on Windows by Financial Review, - http://afr.com/it/2002/10/01/FFXDF43AP6D.html -

  • Implementing CIFS by Christopher R. Hertel, - http://ubiqx.org/cifs/ -

  • Just What Is SMB? by Richard Sharpe, - http://samba.anu.edu.au/cifs/docs/what-is-smb.html -

  • Opening Windows Everywhere by Mike Warfield, - http://www.linux-mag.com/1999-05/samba_01.html -

  • SMB HOWTO by David Wood, - http://www.tldp.org/HOWTO/SMB-HOWTO.html -

  • SMB/CIFS by The Root by "ledin", - http://www.phrack.org/phrack/60/p60-0x0b.txt -

  • The Story of Samba by Christopher R. Hertel, - http://www.linux-mag.com/1999-09/samba_01.html -

  • The Unofficial Samba HOWTO by David Lechnyr, - http://hr.uoregon.edu/davidrl/samba/ -

  • Understanding the Network Neighborhood by Christopher R. Hertel, - http://www.linux-mag.com/2001-05/smb_01.html -

  • Using Samba as a PDC by Andrew Bartlett, - http://www.linux-mag.com/2002-02/samba_01.html -

1.6. Epilogue

"What's fundamentally wrong is that nobody ever had any taste when they -did it. Microsoft has been very much into making the user interface look good, -but internally it's just a complete mess. And even people who program for Microsoft -and who have had years of experience, just don't know how it works internally. -Worse, nobody dares change it. Nobody dares to fix bugs because it's such a -mess that fixing one bug might just break a hundred programs that depend on -that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested -in making money. They don't have anybody who takes pride in Windows 95 as an -operating system.

People inside Microsoft know it's a bad operating system and they still -continue obviously working on it because they want to get the next version out -because they want to have all these new features to sell more copies of the -system.

The problem with that is that over time, when you have this kind of approach, -and because nobody understands it, because nobody REALLY fixes bugs (other than -when they're really obvious), the end result is really messy. You can't trust -it because under certain circumstances it just spontaneously reboots or just -halts in the middle of something that shouldn't be strange. Normally it works -fine and then once in a blue moon for some completely unknown reason, it's dead, -and nobody knows why. Not Microsoft, not the experienced user and certainly -not the completely clueless user who probably sits there shivering thinking -"What did I do wrong?" when they didn't do anything wrong at all.

That's what's really irritating to me."

-- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -(http://hr.uoregon.edu/davidrl/boot.txt)

1.7. Miscellaneous

This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0, -in case anyone asks.

This chapter is Copyright © 2003 David Lechnyr (david at lechnyr dot com). -Permission is granted to copy, distribute and/or modify this document under the terms -of the GNU Free Documentation License, Version 1.2 or any later version published by the Free -Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.

PrevHomeNext
General installationUpHow to Install and Test SAMBA
\ No newline at end of file diff --git a/docs/htmldocs/nt4migration.html b/docs/htmldocs/nt4migration.html deleted file mode 100644 index 2079c1b6c4..0000000000 --- a/docs/htmldocs/nt4migration.html +++ /dev/null @@ -1,356 +0,0 @@ - -Migration from NT4 PDC to Samba-3 PDC
SAMBA Project Documentation
PrevNext

Chapter 28. Migration from NT4 PDC to Samba-3 PDC

Table of Contents
28.1. Planning and Getting Started
28.1.1. Objectives
28.1.2. Steps In Migration Process
28.2. Managing Samba-3 Domain Control

This is a rough guide to assist those wishing to migrate from NT4 domain control to -Samba-3 based domain control.

28.1. Planning and Getting Started

In the IT world there is often a saying that all problems are encountered because of -poor planning. The corrollary to this saying is that not all problems can be anticpated -and planned for. Then again, good planning will anticpate most show stopper type situations.

Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control -environment would do well to develop a detailed migration plan. So here are a few pointers to -help migration get under way.

28.1.1. Objectives

The key objective for most organisations will be to make the migration from MS Windows NT4 -to Samba-3 domain control as painless as possible. One of the challenges you may experience -in your migration process may well be one of convincing management that the new environment -should remain in place. Many who have introduced open source technologies have experienced -pressure to return to a Microsoft based platform solution at the first sign of trouble.

It is strongly advised that before attempting a migration to a Samba-3 controlled network -that every possible effort be made to gain all-round commitment to the change. Firstly, you -should know precisely why the change is important for the organisation. -Possible motivations to make a change include:

  • Improve network manageability

  • Obtain better user level functionality

  • Reduce network operating costs

  • Reduce exposure caused by Microsoft withdrawal of NT4 support

  • Avoid MS License 6 implications

  • Reduce organisation's dependency on Microsoft

It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers -an alternative solution that is both different from MS Windows NT4 and that offers some -advantages compared with it. It should also be recognised that Samba-3 lacks many of the -features that Microsoft has promoted as core values in migration from MS Windows NT4 to -MS Windows 2000 and beyond (with or without Active Directory services).

What are the features the Samba-3 can NOT provide?

Active Directory Server
Group Policy Objects (in Active Direcrtory)
Machine Policy objects
Logon Scripts in Active Directorty
Software Application and Access Controls in Active Directory

28.1.2. Steps In Migration Process

This is not a definitive ste-by-step process yet - just a place holder so the info -is not lost. - -1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated - -2. Samba-3 set up as a DC with netlogon share, profile share, etc. - -3. Process: - a. Create a BDC account for the samba server using NT Server Manager - - Samba must NOT be running - - b. rpcclient NT4PDC -U Administrator%passwd - lsaquery - - Note the SID returned by step b. - - c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd - - Note the SID in step c. - - d. net getlocalsid - - Note the SID, now check that all three SIDS reported are the same! - - e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd - - f. net rpc vampire -S NT4PDC -U administrator%passwd - - g. pdbedit -l - - Note - did the users migrate? - - h. initGrps.sh DOMNAME - - i. smbgroupedit -v - - Now check that all groups are recognised - - j. net rpc campire -S NT4PDC -U administrator%passwd - - k. pdbedit -lv - - Note - check that all group membership has been migrated. - - -Now it is time to migrate all the profiles, then migrate all policy files. - -Moe later.

28.2. Managing Samba-3 Domain Control

Lots of blah blah here.

PrevHomeNext
How to compile SAMBAUpPortability
\ No newline at end of file diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html deleted file mode 100644 index 36513c672a..0000000000 --- a/docs/htmldocs/other-clients.html +++ /dev/null @@ -1,734 +0,0 @@ - -Samba and other CIFS clients
SAMBA Project Documentation
PrevNext

Chapter 30. Samba and other CIFS clients

Table of Contents
30.1. Macintosh clients?
30.2. OS2 Client
30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?
30.2.4. How do I get printer driver download working - for OS/2 clients?
30.3. Windows for Workgroups
30.3.1. Use latest TCP/IP stack from Microsoft
30.3.2. Delete .pwl files after password change
30.3.3. Configure WfW password handling
30.3.4. Case handling of passwords
30.3.5. Use TCP/IP as default protocol
30.4. Windows '95/'98
30.5. Windows 2000 Service Pack 2
30.6. Windows NT 3.1

This chapter contains client-specific information.

30.1. Macintosh clients?

Yes. Thursby now have a CIFS Client / Server called DAVE - see

They test it against Windows 95, Windows NT and samba for -compatibility issues. At the time of writing, DAVE was at version -1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from -the Thursby web site (the speed of finder copies has been greatly -enhanced, and there are bug-fixes included).

-Alternatives - There are two free implementations of AppleTalk for -several kinds of UNIX machnes, and several more commercial ones. -These products allow you to run file services and print services -natively to Macintosh users, with no additional support required on -the Macintosh. The two free omplementations are -Netatalk, and -CAP. -What Samba offers MS -Windows users, these packages offer to Macs. For more info on these -packages, Samba, and Linux (and other UNIX-based systems) see -http://www.eats.com/linux_mac_win.html

30.2. OS2 Client

30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?

A more complete answer to this question can be - found on http://carol.wins.uva.nl/~leeuw/samba/warp.html.

Basically, you need three components:

  • The File and Print Client ('IBM Peer') -

  • TCP/IP ('Internet support') -

  • The "NetBIOS over TCP/IP" driver ('TCPBEUI') -

Installing the first two together with the base operating - system on a blank system is explained in the Warp manual. If Warp - has already been installed, but you now want to install the - networking support, use the "Selective Install for Networking" - object in the "System Setup" folder.

Adding the "NetBIOS over TCP/IP" driver is not described - in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line - is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this - configuration.

If the Samba server(s) is not on your local subnet, you - can optionally add IP names and addresses of these servers - to the "Names List", or specify a WINS server ('NetBIOS - Nameserver' in IBM and RFC terminology). For Warp Connect you - may need to download an update for 'IBM Peer' to bring it on - the same level as Warp 4. See the webpage mentioned above.

30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?

You can use the free Microsoft LAN Manager 2.2c Client - for OS/2 from - ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. - See http://carol.wins.uva.nl/~leeuw/lanman.html for - more information on how to install and use this client. In - a nutshell, edit the file \OS2VER in the root directory of - the OS/2 boot partition and add the lines:

		20=setup.exe
-		20=netwksta.sys
-		20=netvdd.sys
-

before you install the client. Also, don't use the - included NE2000 driver because it is buggy. Try the NE2000 - or NS2000 driver from - ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead. -

30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?

When you do a NET VIEW or use the "File and Print - Client Resource Browser", no Samba servers show up. This can - be fixed by a patch from http://carol.wins.uva.nl/~leeuw/samba/fix.html. - The patch will be included in a later version of Samba. It also - fixes a couple of other problems, such as preserving long - filenames when objects are dragged from the Workplace Shell - to the Samba server.

30.2.4. How do I get printer driver download working - for OS/2 clients?

First, create a share called [PRINTDRV] that is - world-readable. Copy your OS/2 driver files there. Note - that the .EA_ files must still be separate, so you will need - to use the original install files, and not copy an installed - driver from an OS/2 system.

Install the NT driver first for that printer. Then, - add to your smb.conf a parameter, os2 driver map = - filename". Then, in the file - specified by filename, map the - name of the NT driver name to the OS/2 driver name as - follows:

nt driver name = os2 "driver - name"."device name", e.g.: - HP LaserJet 5L = LASERJET.HP LaserJet 5L

You can have multiple drivers mapped in this file.

If you only specify the OS/2 driver name, and not the - device name, the first attempt to download the driver will - actually download the files, but the OS/2 client will tell - you the driver is not available. On the second attempt, it - will work. This is fixed simply by adding the device name - to the mapping, after which it will work on the first attempt. -

30.3. Windows for Workgroups

30.3.1. Use latest TCP/IP stack from Microsoft

Use the latest TCP/IP stack from microsoft if you use Windows -for workgroups.

The early TCP/IP stacks had lots of bugs.

-Microsoft has released an incremental upgrade to their TCP/IP 32-Bit -VxD drivers. The latest release can be found on their ftp site at -ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe. -There is an update.txt file there that describes the problems that were -fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386, -WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.

30.3.2. Delete .pwl files after password change

WfWg does a lousy job with passwords. I find that if I change my -password on either the unix box or the PC the safest thing to do is to -delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.

-If you don't do this you may find that WfWg remembers and uses the old -password, even if you told it a new one.

-Often WfWg will totally ignore a password you give it in a dialog box.

30.3.3. Configure WfW password handling

There is a program call admincfg.exe -on the last disk (disk 8) of the WFW 3.11 disk set. To install it -type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon -for it via the "Progam Manager" "New" Menu. This program allows you -to control how WFW handles passwords. ie disable Password Caching etc -for use with security = user

30.3.4. Case handling of passwords

Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf(5) information on password level to specify what characters samba should try to uppercase when checking.

30.3.5. Use TCP/IP as default protocol

To support print queue reporting you may find -that you have to use TCP/IP as the default protocol under -WfWg. For some reason if you leave Netbeui as the default -it may break the print queue reporting on some systems. -It is presumably a WfWg bug.

30.4. Windows '95/'98

When using Windows 95 OEM SR2 the following updates are recommended where Samba -is being used. Please NOTE that the above change will affect you once these -updates have been installed.

-There are more updates than the ones mentioned here. You are referred to the -Microsoft Web site for all currently available updates to your specific version -of Windows 95.

  1. Kernel Update: KRNLUPD.EXE

  2. Ping Fix: PINGUPD.EXE

  3. RPC Update: RPCRTUPD.EXE

  4. TCP/IP Update: VIPUPD.EXE

  5. Redirector Update: VRDRUPD.EXE

Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This -fix may stop your machine from hanging for an extended period when exiting -OutLook and you may also notice a significant speedup when accessing network -neighborhood services.

30.5. Windows 2000 Service Pack 2

-There are several annoyances with Windows 2000 SP2. One of which -only appears when using a Samba server to host user profiles -to Windows 2000 SP2 clients in a Windows domain. This assumes -that Samba is a member of the domain, but the problem will -likely occur if it is not.

-In order to server profiles successfully to Windows 2000 SP2 -clients (when not operating as a PDC), Samba must have -nt acl support = no -added to the file share which houses the roaming profiles. -If this is not done, then the Windows 2000 SP2 client will -complain about not being able to access the profile (Access -Denied) and create multiple copies of it on disk (DOMAIN.user.001, -DOMAIN.user.002, etc...). See the -smb.conf(5) man page -for more details on this option. Also note that the -nt acl support parameter was formally a global parameter in -releases prior to Samba 2.2.2.

-The following is a minimal profile share:

	[profile]
-		path = /export/profile
-		create mask = 0600
-		directory mask = 0700
-		nt acl support = no
-		read only = no

The reason for this bug is that the Win2k SP2 client copies -the security descriptor for the profile which contains -the Samba server's SID, and not the domain SID. The client -compares the SID for SAMBA\user and realizes it is -different that the one assigned to DOMAIN\user. Hence the reason -for the "access denied" message.

By disabling the nt acl support parameter, Samba will send -the Win2k client a response to the QuerySecurityDescriptor -trans2 call which causes the client to set a default ACL -for the profile. This default ACL includes

DOMAIN\user "Full Control"

This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.

30.6. Windows NT 3.1

If you have problems communicating across routers with Windows -NT 3.1 workstations, read this Microsoft Knowledge Base article.

PrevHomeNext
PortabilityUpSWAT - The Samba Web Admininistration Tool
\ No newline at end of file diff --git a/docs/htmldocs/policymgmt.html b/docs/htmldocs/policymgmt.html deleted file mode 100644 index 5d0c9b19f9..0000000000 --- a/docs/htmldocs/policymgmt.html +++ /dev/null @@ -1,758 +0,0 @@ - -System and Account Policies
SAMBA Project Documentation
PrevNext

Chapter 17. System and Account Policies

Table of Contents
17.1. Creating and Managing System Policies
17.1.1. Windows 9x/Me Policies
17.1.2. Windows NT4 Style Policy Files
17.1.3. MS Windows 200x / XP Professional Policies
17.2. Managing Account/User Policies
17.2.1. With Windows NT4/200x
17.2.2. With a Samba PDC
17.3. System Startup and Logon Processing Overview

17.1. Creating and Managing System Policies

Under MS Windows platforms, particularly those following the release of MS Windows -NT4 and MS Windows 95) it is possible to create a type of file that would be placed -in the NETLOGON share of a domain controller. As the client logs onto the network -this file is read and the contents initiate changes to the registry of the client -machine. This file allows changes to be made to those parts of the registry that -affect users, groups of users, or machines.

For MS Windows 9x/Me this file must be called Config.POL and may -be generated using a tool called poledit.exe, better known as the -Policy Editor. The policy editor was provided on the Windows 98 installation CD, but -dissappeared again with the introduction of MS Windows Me (Millenium Edition). From -comments from MS Windows network administrators it would appear that this tool became -a part of the MS Windows Me Resource Kit.

MS Windows NT4 Server products include the System Policy Editor -under the Start -> Programs -> Administrative Tools menu item. -For MS Windows NT4 and later clients this file must be called NTConfig.POL.

New with the introduction of MS Windows 2000 was the Microsoft Management Console -or MMC. This tool is the new wave in the ever changing landscape of Microsoft -methods for management of network access and security. Every new Microsoft product -or technology seems to obsolete the old rules and to introduce newer and more -complex tools and methods. To Microsoft's credit though, the MMC does appear to -be a step forward, but improved functionality comes at a great price.

Before embarking on the configuration of network and system policies it is highly -advisable to read the documentation available from Microsoft's web site regarding -Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. -There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies".

What follows is a very brief discussion with some helpful notes. The information provided -here is incomplete - you are warned.

17.1.1. Windows 9x/Me Policies

You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. -It can be found on the Original full product Win98 installation CD under -tools/reskit/netadmin/poledit. Install this using the -Add/Remove Programs facility and then click on the 'Have Disk' tab.

Use the Group Policy Editor to create a policy file that specifies the location of -user profiles and/or the My Documents etc. stuff. Then -save these settings in a file called Config.POL that needs to -be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto -the Samba Domain, it will automatically read this file and update the Win9x/Me registry -of the machine as it logs on.

Further details are covered in the Win98 Resource Kit documentation.

If you do not take the right steps, then every so often Win9x/Me will check the -integrity of the registry and will restore it's settings from the back-up -copy of the registry it stores on each Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.

Install the group policy handler for Win9x to pick up group policies. Look on the -Win98 CD in \tools\reskit\netadmin\poledit. -Install group policies on a Win9x client by double-clicking -grouppol.inf. Log off and on again a couple of times and see -if Win98 picks up group policies. Unfortunately this needs to be done on every -Win9x/Me machine that uses group policies.

17.1.2. Windows NT4 Style Policy Files

To create or edit ntconfig.pol you must use the NT Server -Policy Editor, poledit.exe which is included with NT4 Server -but not NT Workstation. There is a Policy Editor on a NT4 -Workstation but it is not suitable for creating Domain Policies. -Further, although the Windows 95 Policy Editor can be installed on an NT4 -Workstation/Server, it will not work with NT clients. However, the files from -the NT Server will run happily enough on an NT4 Workstation.

You need poledit.exe, common.adm and winnt.adm. -It is convenient to put the two *.adm files in the c:\winnt\inf -directory which is where the binary will look for them unless told otherwise. Note also that that -directory is normally 'hidden'.

The Windows NT policy editor is also included with the Service Pack 3 (and -later) for Windows NT 4.0. Extract the files using servicepackname /x, -i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor, -poledit.exe and the associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft.

17.1.2.1. Registry Tattoos

With NT4 style registry based policy changes, a large number of settings are not - automatically reversed as the user logs off. Since the settings that were in the - NTConfig.POL file were applied to the client machine registry and that apply to the - hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known - as tattooing. It can have serious consequences down-stream and the administrator must - be extremely careful not to lock out the ability to manage the machine at a later date. -

17.1.3. MS Windows 200x / XP Professional Policies

Windows NT4 System policies allows setting of registry parameters specific to -users, groups and computers (client workstations) that are members of the NT4 -style domain. Such policy file will work with MS Windows 2000 / XP clients also.

New to MS Windows 2000 Microsoft introduced a new style of group policy that confers -a superset of capabilities compared with NT4 style policies. Obviously, the tool used -to create them is different, and the mechanism for implementing them is much changed.

The older NT4 style registry based policies are known as Administrative Templates -in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security -configurations, enforce Internet Explorer browser settings, change and redirect aspects of the -users' desktop (including: the location of My Documents files (directory), as -well as intrinsics of where menu items will appear in the Start menu). An additional new -feature is the ability to make available particular software Windows applications to particular -users and/or groups.

Remember: NT4 policy files are named NTConfig.POL and are stored in the root -of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password -and selects the domain name to which the logon will attempt to take place. During the logon -process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating -server, modifies the local registry values according to the settings in this file.

Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of -a Windows 200x policy file is stored in the Active Directory itself and the other part is stored -in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active -Directory domain controllers. The part that is stored in the Active Directory itself is called the -group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is -known as the group policy template (GPT).

With NT4 clients the policy file is read and executed upon only aas each user log onto the network. -MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine -startup (machine specific part) and when the user logs onto the network the user specific part -is applied. In MS Windows 200x style policy management each machine and/or user may be subject -to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows -the administrator to also set filters over the policy settings. No such equivalent capability -exists with NT4 style policy files.

17.1.3.1. Administration of Win2K / XP Policies

Instructions

Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the -executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows:

  1. Go to the Windows 200x / XP menu Start->Programs->Administrative Tools - and select the MMC snap-in called "Active Directory Users and Computers"

  2. Select the domain or organizational unit (OU) that you wish to manage, then right click -to open the context menu for that object, select the properties item.

  3. Now left click on the Group Policy tab, then left click on the New tab. Type a name -for the new policy you will create.

  4. Now left click on the Edit tab to commence the steps needed to create the GPO.

All policy configuration options are controlled through the use of policy administrative -templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. -Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. -The later introduces many new features as well as extended definition capabilities. It is -well beyond the scope of this documentation to explain how to program .adm files, for that -the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular -version of MS Windows.

The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used -to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you -use this powerful tool. Please refer to the resource kit manuals for specific usage information.

17.2. Managing Account/User Policies

Policies can define a specific user's settings or the settings for a group of users. The resulting -policy file contains the registry settings for all users, groups, and computers that will be using -the policy file. Separate policy files for each user, group, or computer are not not necessary.

If you create a policy that will be automatically downloaded from validating domain controllers, -you should name the file NTconfig.POL. As system administrator, you have the option of renaming the -policy file and, by modifying the Windows NT-based workstation, directing the computer to update -the policy from a manual path. You can do this by either manually changing the registry or by using -the System Policy Editor. This path can even be a local path such that each machine has its own policy file, -but if a change is necessary to all machines, this change must be made individually to each workstation.

When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain -controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then -applied to the user's part of the registry.

MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, -acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory -itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect. -This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.

Inaddition to user access controls that may be imposed or applied via system and/or group policies -in a manner that works in conjunction with user profiles, the user management environment under -MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. -Common restrictions that are frequently used includes:

Logon Hours
Password Aging
Permitted Logon from certain machines only
Account type (Local or Global)
User Rights

17.2.1. With Windows NT4/200x

The tools that may be used to configure these types of controls from the MS Windows environment are: -The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). -Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate -"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.

17.2.2. With a Samba PDC

With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -smbpasswd, pdbedit, smbgroupedit, net, rpcclient.. The administrator should read the -man pages for these tools and become familiar with their use.

17.3. System Startup and Logon Processing Overview

The following attempts to document the order of processing of system and user policies following a system -reboot and as part of the user logon:

  1. Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming - Convention Provider (MUP) start -

  2. Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded - and applied. The list may include GPOs that: -

    Apply to the location of machines in a Directory
    Apply only when settings have changed
    Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

    - No desktop user interface is presented until the above have been processed. -

  3. Execution of start-up scripts (hidden and synchronous by defaut). -

  4. A keyboard action to affect start of logon (Ctrl-Alt-Del). -

  5. User credentials are validated, User profile is loaded (depends on policy settings). -

  6. An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: - -

    Is user a domain member, thus subject to particular policies
    Loopback enablement, and the state of the loopback policy (Merge or Replace)
    Location of the Active Directory itself
    Has the list of GPOs changed. No processing is needed if not changed.

    -

  7. User Policies are applied from Active Directory. Note: There are several types. -

  8. Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group - Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal - window. -

  9. The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 - Domain) machine (system) policies are applied at start-up, User policies are applied at logon. -

PrevHomeNext
Advanced Network ManangementUpDesktop Profile Management
\ No newline at end of file diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html deleted file mode 100644 index ac3e5b9adb..0000000000 --- a/docs/htmldocs/portability.html +++ /dev/null @@ -1,418 +0,0 @@ - -Portability
SAMBA Project Documentation
PrevNext

Chapter 29. Portability

Table of Contents
29.1. HPUX
29.2. SCO Unix
29.3. DNIX
29.4. RedHat Linux Rembrandt-II
29.5. AIX
29.6. Solaris

Samba works on a wide range of platforms but the interface all the -platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using samba.

29.1. HPUX

HP's implementation of supplementary groups is, er, non-standard (for -hysterical reasons). There are two group files, /etc/group and -/etc/logingroup; the system maps UIDs to numbers using the former, but -initgroups() reads the latter. Most system admins who know the ropes -symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons -too stupid to go into here). initgroups() will complain if one of the -groups you're in in /etc/logingroup has what it considers to be an invalid -ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think) -60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody' -GIDs.

If you encounter this problem, make sure that the programs that are failing -to initgroups() be run as users not in any groups with GIDs outside the -allowed range.

This is documented in the HP manual pages under setgroups(2) and passwd(4).

On HPUX you must use gcc or the HP Ansi compiler. The free compiler -that comes with HP-UX is not Ansi compliant and cannot compile -Samba.

29.2. SCO Unix

-If you run an old version of SCO Unix then you may need to get important -TCP/IP patches for Samba to work correctly. Without the patch, you may -encounter corrupt data transfers using samba.

The patch you need is UOD385 Connection Drivers SLS. It is available from -SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).

29.3. DNIX

DNIX has a problem with seteuid() and setegid(). These routines are -needed for Samba to work correctly, but they were left out of the DNIX -C library for some reason.

For this reason Samba by default defines the macro NO_EID in the DNIX -section of includes.h. This works around the problem in a limited way, -but it is far from ideal, some things still won't work right.

-To fix the problem properly you need to assemble the following two -functions and then either add them to your C library or link them into -Samba.

-put this in the file setegid.s:

        .globl  _setegid
-_setegid:
-        moveq   #47,d0
-        movl    #100,a0
-        moveq   #1,d1
-        movl    4(sp),a1
-        trap    #9
-        bccs    1$
-        jmp     cerror
-1$:
-        clrl    d0
-        rts

put this in the file seteuid.s:

        .globl  _seteuid
-_seteuid:
-        moveq   #47,d0
-        movl    #100,a0
-        moveq   #0,d1
-        movl    4(sp),a1
-        trap    #9
-        bccs    1$
-        jmp     cerror
-1$:
-        clrl    d0
-        rts

after creating the above files you then assemble them using

as seteuid.s

as setegid.s

that should produce the files seteuid.o and -setegid.o

then you need to add these to the LIBSM line in the DNIX section of -the Samba Makefile. Your LIBSM line will then look something like this:

LIBSM = setegid.o seteuid.o -ln

-You should then remove the line:

#define NO_EID

from the DNIX section of includes.h

29.4. RedHat Linux Rembrandt-II

By default RedHat Rembrandt-II during installation adds an -entry to /etc/hosts as follows: -

	127.0.0.1 loopback "hostname"."domainname"

This causes Samba to loop back onto the loopback interface. -The result is that Samba fails to communicate correctly with -the world and therefor may fail to correctly negotiate who -is the master browse list holder and who is the master browser.

Corrective Action: Delete the entry after the word loopback - in the line starting 127.0.0.1

29.5. AIX

29.5.1. Sequential Read Ahead

Disabling Sequential Read Ahead using vmtune -r 0 improves -samba performance significally.

29.6. Solaris

Some people have been experiencing problems with F_SETLKW64/fcntl -when running samba on solaris. The built in file locking mechanism was -not scalable. Performance would degrade to the point where processes would -get into loops of trying to lock a file. It woul try a lock, then fail, -then try again. The lock attempt was failing before the grant was -occurring. So the visible manifestation of this would be a handful of -processes stealing all of the CPU, and when they were trussed they would -be stuck if F_SETLKW64 loops.

Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 -has not been released yet.

The patch revision for 2.6 is 105181-34 -for 8 is 108528-19 -and for 9 is 112233-04

After the install of these patches it is recommended to reconfigure -and rebuild samba.

Thanks to Joe Meslovich for reporting

PrevHomeNext
Migration from NT4 PDC to Samba-3 PDCUpSamba and other CIFS clients
\ No newline at end of file diff --git a/docs/htmldocs/profilemgmt.html b/docs/htmldocs/profilemgmt.html deleted file mode 100644 index 7357336193..0000000000 --- a/docs/htmldocs/profilemgmt.html +++ /dev/null @@ -1,1753 +0,0 @@ - -Desktop Profile Management
SAMBA Project Documentation
PrevNext

Chapter 18. Desktop Profile Management

Table of Contents
18.1. Roaming Profiles
18.1.1. Samba Configuration for Profile Handling
18.1.1.1. NT4/200x User Profiles
18.1.1.2. Windows 9x / Me User Profiles
18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
18.1.2. Windows Client Profile Configuration Information
18.1.2.1. Windows 9x / Me Profile Setup
18.1.2.2. Windows NT4 Workstation
18.1.2.3. Windows 2000/XP Professional
18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
18.1.4. Profile Migration from Windows NT4/200x Server to Samba
18.1.4.1. Windows NT4 Profile Management Tools
18.1.4.2. Side bar Notes
18.1.4.3. moveuser.exe
18.1.4.4. Get SID
18.2. Mandatory profiles
18.3. Creating/Managing Group Profiles
18.4. Default Profile for Windows Users
18.4.1. MS Windows 9x/Me
18.4.2. MS Windows NT4 Workstation
18.4.3. MS Windows 200x/XP

18.1. Roaming Profiles

Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

Before discussing how to configure roaming profiles, it is useful to see how -Windows 9x / Me and Windows NT4/200x clients implement these features.

Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's -profiles location. However, the response does not have room for a separate -profiles location field, only the user's home share. This means that Win9X/Me -profiles are restricted to being stored in the user's home directory.

Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles.

18.1.1. Samba Configuration for Profile Handling

This section documents how to configure Samba for MS Windows client profile support.

18.1.1.1. NT4/200x User Profiles

To support Windowns NT4/200x clients, in the [global] section of smb.conf set the -following (for example):

	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
- - This is typically implemented like: - -
		logon path = \\%L\Profiles\%u
-where %L translates to the name of the Samba server and %u translates to the user name

The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. -The \\N%\%U service is created automatically by the [homes] service. If you are using -a samba server for the profiles, you _must_ make the share specified in the logon path -browseable. Please refer to the man page for smb.conf in respect of the different -symantics of %L and %N, as well as %U and %u.

MS Windows NT/2K clients at times do not disconnect a connection to a server -between logons. It is recommended to NOT use the homes -meta-service name as part of the profile share path.

18.1.1.2. Windows 9x / Me User Profiles

To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has -now been fixed so that net use /home now works as well, and it, too, relies -on the logon home parameter.

By using the logon home parameter, you are restricted to putting Win9x / Me -profiles in the user's home directory. But wait! There is a trick you -can use. If you set the following in the [global] section of your smb.conf file:

	logon home = \\%L\%U\.profiles

then your Windows 9x / Me clients will dutifully put their clients in a subdirectory -of your home directory called .profiles (thus making them hidden).

Not only that, but net use/home will also work, because of a feature in -Windows 9x / Me. It removes any directory stuff off the end of the home directory area -and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for logon home.

18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles

You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example:

	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u

18.1.2. Windows Client Profile Configuration Information

18.1.2.1. Windows 9x / Me Profile Setup

When a user first logs in on Windows 9X, the file user.DAT is created, -as are folders "Start Menu", "Desktop", "Programs" and "Nethood". -These directories and their contents will be merged with the local -versions stored in c:\windows\profiles\username on subsequent logins, -taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short preserve case = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders.

The user.DAT file contains all the user's preferences. If you wish to -enforce a set of preferences, rename their user.DAT file to user.MAN, -and deny them write access to this file.

  1. On the Windows 9x / Me machine, go to Control Panel -> Passwords and - select the User Profiles tab. Select the required level of - roaming preferences. Press OK, but do _not_ allow the computer - to reboot. -

  2. On the Windows 9x / Me machine, go to Control Panel -> Network -> - Client for Microsoft Networks -> Preferences. Select 'Log on to - NT Domain'. Then, ensure that the Primary Logon is 'Client for - Microsoft Networks'. Press OK, and this time allow the computer - to reboot. -

Under Windows 9x / Me Profiles are downloaded from the Primary Logon. -If you have the Primary Logon as 'Client for Novell Networks', then -the profiles and logon script will be downloaded from your Novell -Server. If you have the Primary Logon as 'Windows Logon', then the -profiles will be loaded from the local machine - a bit against the -concept of roaming profiles, it would seem!

You will now find that the Microsoft Networks Login box contains -[user, password, domain] instead of just [user, password]. Type in -the samba server's domain name (or any other domain known to exist, -but bear in mind that the user will be authenticated against this -domain and profiles downloaded from it, if that domain logon server -supports it), user name and user's password.

Once the user has been successfully validated, the Windows 9x / Me machine -will inform you that 'The user has not logged on before' and asks you -if you wish to save the user's preferences? Select 'yes'.

Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the "logon path" -on the samba server and verify that the "Desktop", "Start Menu", -"Programs" and "Nethood" folders have been created.

These folders will be cached locally on the client, and updated when -the user logs off (if you haven't made them read-only by then). -You will find that if the user creates further folders or short-cuts, -that the client will merge the profile contents downloaded with the -contents of the profile directory already on the local client, taking -the newest folders and short-cuts from each set.

If you have made the folders / files read-only on the samba server, -then you will get errors from the Windows 9x / Me machine on logon and logout, as -it attempts to merge the local and the remote profile. Basically, if -you have any errors reported by the Windows 9x / Me machine, check the Unix file -permissions and ownership rights on the profile directory contents, -on the samba server.

If you have problems creating user profiles, you can reset the user's -local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time".

  1. instead of logging in under the [user, password, domain] dialog, - press escape. -

  2. run the regedit.exe program, and look in: -

    HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList -

    you will find an entry, for each user, of ProfilePath. Note the - contents of this key (likely to be c:\windows\profiles\username), - then delete the key ProfilePath for the required user. - - [Exit the registry editor]. - -

  3. WARNING - before deleting the contents of the - directory listed in the ProfilePath (this is likely to be - c:\windows\profiles\username), ask them if they - have any important files stored on their desktop or in their start menu. - Delete the contents of the directory ProfilePath (making a backup if any - of the files are needed). -

    This will have the effect of removing the local (read-only hidden - system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. -

  4. search for the user's .PWL password-caching file in the c:\windows - directory, and delete it. -

  5. log off the windows 9x / Me client. -

  6. check the contents of the profile path (see "logon path" described - above), and delete the user.DAT or user.MAN file for the user, - making a backup if required. -

If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as ethereal or netmon.exe, and -look for error messages.

If you have access to an Windows NT4/200x server, then first set up roaming profiles -and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine -the example packet traces provided with Windows NT4/200x server, and see what the -differences are with the equivalent samba trace.

18.1.2.2. Windows NT4 Workstation

When a user first logs in to a Windows NT Workstation, the profile -NTuser.DAT is created. The profile location can be now specified -through the "logon path" parameter.

There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to H: or any other drive, and -should be used in conjunction with the new "logon home" parameter.

The entry for the NT4 profile is a _directory_ not a file. The NT -help on profiles mentions that a directory is also created with a .PDS -extension. The user, while logging in, must have write permission to -create the full profile path (and the folder with the .PDS extension -for those situations where it might be created.)

In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -It creates "Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file -NTuser.DAT. Nothing appears to be stored in the .PDS directory, and -its purpose is currently unknown.

You can use the System Control Panel to copy a local profile onto -a samba server (see NT Help on profiles: it is also capable of firing -up the correct location in the System Control Panel for you). The -NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN -turns a profile into a mandatory one.

The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN.

18.1.2.3. Windows 2000/XP Professional

You must first convert the profile from a local profile to a domain -profile on the MS Windows workstation as follows:

  • Log on as the LOCAL workstation administrator. -

  • Right click on the 'My Computer' Icon, select 'Properties' -

  • Click on the 'User Profiles' tab -

  • Select the profile you wish to convert (click on it once) -

  • Click on the button 'Copy To' -

  • In the "Permitted to use" box, click on the 'Change' button. -

  • Click on the 'Look in" area that lists the machine name, when you click - here it will open up a selection box. Click on the domain to which the - profile must be accessible. -

    You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.

  • To make the profile capable of being used by anyone select 'Everyone' -

  • Click OK. The Selection box will close. -

  • Now click on the 'Ok' button to create the profile in the path you - nominated. -

Done. You now have a profile that can be editted using the samba-3.0.0 -profiles tool.

Under NT/2K the use of mandotory profiles forces the use of MS Exchange -storage of mail data. That keeps desktop profiles usable.

  • This is a security check new to Windows XP (or maybe only -Windows XP service pack 1). It can be disabled via a group policy in -Active Directory. The policy is:

    "Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders"

    ...and it should be set to "Enabled". -Does the new version of samba have an Active Directory analogue? If so, -then you may be able to set the policy through this.

    If you cannot set group policies in samba, then you may be able to set -the policy locally on each machine. If you want to try this, then do -the following (N.B. I don't know for sure that this will work in the -same way as a domain group policy):

  • On the XP workstation log in with an Administrator account.

  • Click: "Start", "Run"

  • Type: "mmc"

  • Click: "OK"

  • A Microsoft Management Console should appear.

  • Click: File, "Add/Remove Snap-in...", "Add"

  • Double-Click: "Group Policy"

  • Click: "Finish", "Close"

  • Click: "OK"

  • In the "Console Root" window:

  • Expand: "Local Computer Policy", "Computer Configuration",

  • "Administrative Templates", "System", "User Profiles"

  • Double-Click: "Do not check for user ownership of Roaming Profile

  • Folders"

  • Select: "Enabled"

  • Click: OK"

  • Close the whole console. You do not need to save the settings (this - refers to the console settings rather than the policies you have - changed).

  • Reboot

18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations

Sharing of desktop profiles between Windows versions is NOT recommended. -Desktop profiles are an evolving phenomenon and profiles for later versions -of MS Windows clients add features that may interfere with earlier versions -of MS Windows clients. Probably the more salient reason to NOT mix profiles -is that when logging off an earlier version of MS Windows the older format -of profile contents may overwrite information that belongs to the newer -version resulting in loss of profile information content when that user logs -on again with the newer version of MS Windows.

If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home.

If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory.

18.1.4. Profile Migration from Windows NT4/200x Server to Samba

There is nothing to stop you specifying any path that you like for the -location of users' profiles. Therefore, you could specify that the -profile be stored on a samba server, or any other SMB server, as long as -that SMB server supports encrypted passwords.

18.1.4.1. Windows NT4 Profile Management Tools

Unfortunately, the Resource Kit information is specific to the version of MS Windows -NT4/200x. The correct resource kit is required for each platform.

Here is a quick guide:

  • On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'.

  • Select a user profile you want to migrate and click on it.

    I am using the term "migrate" lossely. You can copy a profile to -create a group profile. You can give the user 'Everyone' rights to the -profile you copy this to. That is what you need to do, since your samba -domain is not a member of a trust relationship with your NT4 PDC.

  • Click the 'Copy To' button.

  • In the box labelled 'Copy Profile to' add your new path, eg: - c:\temp\foobar

  • Click on the button labelled 'Change' in the "Permitted to use" box.

  • Click on the group 'Everyone' and then click OK. This closes the - 'chose user' box.

  • Now click OK.

Follow the above for every profile you need to migrate.

18.1.4.2. Side bar Notes

You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users.

18.1.4.3. moveuser.exe

The W2K professional resource kit has moveuser.exe. moveuser.exe changes -the security of a profile from one user to another. This allows the account -domain to change, and/or the user name to change.

18.1.4.4. Get SID

You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 -Resource Kit.

Windows NT 4.0 stores the local profile information in the registry under -the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Under the ProfileList key, there will be subkeys named with the SIDs of the -users who have logged on to this computer. (To find the profile information -for the user whose locally cached profile you want to move, find the SID for -the user with the GetSID.exe utility.) Inside of the appropriate user's -subkey, you will see a string value named ProfileImagePath.

18.2. Mandatory profiles

A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. -During the user's session it may be possible to change the desktop environment, but -as the user logs out all changes made will be lost. If it is desired to NOT allow the -user any ability to change the desktop environment then this must be done through -policy settings. See previous chapter.

Under NO circumstances should the profile directory (or it's contents) be made read-only -as this may render the profile un-usable.

For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles -also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT -file in the copied profile and rename it to NTUser.MAN.

For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to -affect a mandatory profile.

18.3. Creating/Managing Group Profiles

Most organisations are arranged into departments. There is a nice benenfit in -this fact since usually most users in a department will require the same desktop -applications and the same desktop layout. MS Windows NT4/200x/XP will allow the -use of Group Profiles. A Group Profile is a profile that is created firstly using -a template (example) user. Then using the profile migration tool (see above) the -profile is assigned access rights for the user group that needs to be given access -to the group profile.

The next step is rather important. PLEASE NOTE: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned -the now modified profile.

Be careful with group profiles, if the user who is a member of a group also - has a personal profile, then the result will be a fusion (merge) of the two. -

18.4. Default Profile for Windows Users

MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom -a profile does not already exist. Armed with a knowledge of where the default profile -is located on the Windows workstation, and knowing which registry keys affect the path -from which the default profile is created, it is possible to modify the default profile -to one that has been optimised for the site. This has significant administrative -advantages.

18.4.1. MS Windows 9x/Me

To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly.

To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes.

To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive -HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.

18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?

When a user logs on to a Windows 9x / Me machine, the local profile path, -HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked -for an existing entry for that user:

If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached -version of the user profile. Windows 9x / Me also checks the user's home directory (or other -specified directory if the location has been modified) on the server for the User Profile. -If a profile exists in both locations, the newer of the two is used. If the User Profile exists -on the server, but does not exist on the local machine, the profile on the server is downloaded -and used. If the User Profile only exists on the local machine, that copy is used.

If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me -machine is used and is copied to a newly created folder for the logged on user. At log off, any -changes that the user made are written to the user's local profile. If the user has a roaming -profile, the changes are written to the user's profile on the server.

18.4.2. MS Windows NT4 Workstation

On MS Windows NT4 the default user profile is obtained from the location -%SystemRoot%\Profiles which in a default installation will translate to -C:\WinNT\Profiles. Under this directory on a clean install there will be -three (3) directories: Administrator, All Users, Default User.

The All Users directory contains menu settings that are common across all -system users. The Default User directory contains menu entries that are -customisable per user depending on the profile settings chosen/created.

When a new user first logs onto an MS Windows NT4 machine a new profile is created from:

All Users settings
Default User settings (contains the default NTUser.DAT file)

When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain -the following steps are followed in respect of profile handling:

  1. The users' account information which is obtained during the logon process contains - the location of the users' desktop profile. The profile path may be local to the - machine or it may be located on a network share. If there exists a profile at the location - of the path from the user account, then this profile is copied to the location - %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the - settings in the All Users profile in the %SystemRoot%\Profiles - location. -

  2. If the user account has a profile path, but at it's location a profile does not exist, - then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% - directory from reading the Default User profile. -

  3. If the NETLOGON share on the authenticating server (logon server) contains a policy file - (NTConfig.POL) then it's contents are applied to the NTUser.DAT - which is applied to the HKEY_CURRENT_USER part of the registry. -

  4. When the user logs out, if the profile is set to be a roaming profile it will be written - out to the location of the profile. The NTuser.DAT file is then - re-created from the contents of the HKEY_CURRENT_USER contents. - Thus, should there not exist in the NETLOGON share an NTConfig.POL at the - next logon, the effect of the provious NTConfig.POL will still be held - in the profile. The effect of this is known as tatooing. -

MS Windows NT4 profiles may be Local or Roaming. A Local profile -will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will -also remain stored in the same way, unless the following registry key is created:

	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
- -In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be -deleted on logout.

Under MS Windows NT4 default locations for common resources (like My Documents -may be redirected to a network share by modifying the following registry keys. These changes may be affected -via use of the System Policy Editor (to do so may require that you create your owns template extension -for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first -creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.

The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows NT4 is:

        HKEY_CURRENT_USER
-                \Software
-                        \Microsoft
-                                \Windows
-                                        \CurrentVersion
-                                                \Explorer
-                                                        \User Shell Folders\

The above hive key contains a list of automatically managed folders. The default entries are:

        Name            Default Value
-        --------------  -----------------------------------------
-        AppData         %USERPROFILE%\Application Data
-        Desktop         %USERPROFILE%\Desktop
-        Favorites       %USERPROFILE%\Favorites
-        NetHood         %USERPROFILE%\NetHood
-        PrintHood       %USERPROFILE%\PrintHood
-        Programs        %USERPROFILE%\Start Menu\Programs
-        Recent          %USERPROFILE%\Recent
-        SendTo          %USERPROFILE%\SendTo
-        Start Menu      %USERPROFILE%\Start Menu
-        Startup         %USERPROFILE%\Start Menu\Programs\Startup
-
-

The registry key that contains the location of the default profile settings is: - -

	HKEY_LOCAL_MACHINE
-		\SOFTWARE
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders
- -The default entries are: - -
	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
-	Common Programs		%SystemRoot%\Profiles\All Users\Programs
-	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
-	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup

18.4.3. MS Windows 200x/XP

MS Windows XP Home Edition does use default per user profiles, but can not participate - in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile - only from itself. While there are benefits in doing this the beauty of those MS Windows - clients that CAN participate in domain logon processes allows the administrator to create - a global default profile and to enforce it through the use of Group Policy Objects (GPOs). -

When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from -C:\Documents and Settings\Default User. The administrator can modify (or change -the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum -arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client -workstation.

When MS Windows 200x/XP participate in a domain security context, and if the default user -profile is not found, then the client will search for a default profile in the NETLOGON share -of the authenticating server. ie: In MS Windows parlance: -%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this -to the workstation to the C:\Documents and Settings\ under the Windows -login name of the user.

This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory - should be created at the root of this share and msut be called Default Profile. -

If a default profile does not exist in this location then MS Windows 200x/XP will use the local -default profile.

On loging out, the users' desktop profile will be stored to the location specified in the registry -settings that pertain to the user. If no specific policies have been created, or passed to the client -during the login process (as Samba does automatically), then the user's profile will be written to -the local machine only under the path C:\Documents and Settings\%USERNAME%.

Those wishing to modify the default behaviour can do so through up to three methods:

  • Modify the registry keys on the local machine manually and place the new default profile in the - NETLOGON share root - NOT recommended as it is maintenance intensive. -

  • Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file - in the root of the NETLOGON share along with the new default profile. -

  • Create a GPO that enforces this through Active Directory, and place the new default profile - in the NETLOGON share. -

The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows 200x/XP is:

	HKEY_CURRENT_USER
-		\Software
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders\

The above hive key contains a list of automatically managed folders. The default entries are:

	Name		Default Value
-	--------------	-----------------------------------------
-	AppData		%USERPROFILE%\Application Data
-	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
-	Cookies		%USERPROFILE%\Cookies
-	Desktop		%USERPROFILE%\Desktop
-	Favorites	%USERPROFILE%\Favorites
-	History		%USERPROFILE%\Local Settings\History
-	Local AppData	%USERPROFILE%\Local Settings\Application Data
-	Local Settings	%USERPROFILE%\Local Settings
-	My Pictures	%USERPROFILE%\My Documents\My Pictures
-	NetHood		%USERPROFILE%\NetHood
-	Personal	%USERPROFILE%\My Documents
-	PrintHood	%USERPROFILE%\PrintHood
-	Programs	%USERPROFILE%\Start Menu\Programs
-	Recent		%USERPROFILE%\Recent
-	SendTo		%USERPROFILE%\SendTo
-	Start Menu	%USERPROFILE%\Start Menu
-	Startup		%USERPROFILE%\Start Menu\Programs\Startup
-	Templates	%USERPROFILE%\Templates
-
-

There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ.

It makes a huge difference to the speed of handling roaming user profiles if all the folders are -stored on a dedicated location on a network server. This means that it will NOT be necessary to -write Outlook PST file over the network for every login and logout.

To set this to a network location you could use the following examples: - -

	%LOGONSERVER%\%USERNAME%\Default Folders
- -This would store the folders in the user's home directory under a directory called "Default Folders" - -You could also use: - -
	\\SambaServer\FolderShare\%USERNAME%
- -in which case the default folders will be stored in the server named SambaServer -in the share called FolderShare under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system.

Please note that once you have created a default profile share, you MUST migrate a user's profile -(default or custom) to it.

MS Windows 200x/XP profiles may be Local or Roaming. -A roaming profile will be cached locally unless the following registry key is created:

	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
- -In which case, the local cache copy will be deleted on logout.

PrevHomeNext
System and Account PoliciesUpInterdomain Trust Relationships
\ No newline at end of file diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html deleted file mode 100644 index 3d2a95873e..0000000000 --- a/docs/htmldocs/samba-howto-collection.html +++ /dev/null @@ -1,1394 +0,0 @@ - -SAMBA Project Documentation

SAMBA Project Documentation

SAMBA Team

Edited by

Jelmer R. Vernooij

John H. Terpstra

Gerald (Jerry) Carter

This book is a collection of HOWTOs added to Samba documentation over the years. -Samba is always under development, and so is it's documentation. -The most recent version of this document -can be found at http://www.samba.org/ -on the "Documentation" page. Please send updates to jerry@samba.org or -jelmer@samba.org.

This documentation is distributed under the GNU General Public License (GPL) -version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt

Table of Contents
I. General installation
1. Introduction to Samba
1.1. Background
1.2. Terminology
1.3. Related Projects
1.4. SMB Methodology
1.5. Additional Resources
1.6. Epilogue
1.7. Miscellaneous
2. How to Install and Test SAMBA
2.1. Obtaining and installing samba
2.2. Configuring samba
2.3. Try listing the shares available on your - server
2.4. Try connecting with the unix client
2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
2.6. What If Things Don't Work?
3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
3.1. Discussion
3.2. How browsing functions and how to deploy stable and -dependable browsing using Samba
3.3. Use of the Remote Announce parameter
3.4. Use of the Remote Browse Sync parameter
3.5. Use of WINS
3.6. Do NOT use more than one (1) protocol on MS Windows machines
3.7. Name Resolution Order
4. User information database
4.1. Introduction
4.2. Important Notes About Security
4.3. The smbpasswd Command
4.4. Plain text
4.5. TDB
4.6. LDAP
4.7. MySQL
4.8. XML
II. Type of installation
5. Nomenclature of Server Types
5.1. Stand Alone Server
5.2. Domain Member Server
5.3. Domain Controller
6. Samba as Stand-Alone Server
6.1. User and Share security level
7. Samba as an NT4 or Win2k Primary Domain Controller
7.1. Prerequisite Reading
7.2. Background
7.3. Configuring the Samba Domain Controller
7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
7.5. Common Problems and Errors
7.6. Domain Control for Windows 9x/ME
8. Samba Backup Domain Controller to Samba Domain Control
8.1. Prerequisite Reading
8.2. Background
8.3. What qualifies a Domain Controller on the network?
8.4. Can Samba be a Backup Domain Controller to an NT PDC?
8.5. How do I set up a Samba BDC?
9. Samba as a ADS domain member
9.1. Setup your smb.conf
9.2. Setup your /etc/krb5.conf
9.3. Create the computer account
9.4. Test your server setup
9.5. Testing with smbclient
9.6. Notes
10. Samba as a NT4 or Win2k domain member
10.1. Joining an NT Domain with Samba 3.0
10.2. Why is this better than security = server?
III. Advanced Configuration
11. UNIX Permission Bits and Windows NT Access Control Lists
11.1. Viewing and changing UNIX permissions using the NT - security dialogs
11.2. How to view file security on a Samba share
11.3. Viewing file ownership
11.4. Viewing file or directory permissions
11.5. Modifying file or directory permissions
11.6. Interaction with the standard Samba create mask - parameters
11.7. Interaction with the standard Samba file attribute - mapping
12. Configuring Group Mapping
13. Printing Support
13.1. Introduction
13.2. Configuration
13.3. The Imprints Toolset
13.4. Diagnosis
14. CUPS Printing Support
14.1. Introduction
14.2. Configuring smb.conf for CUPS
14.3. CUPS - RAW Print Through Mode
14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients
14.5. Windows Terminal Servers (WTS) as CUPS clients
14.6. Setting up CUPS for driver download
14.7. Sources of CUPS drivers / PPDs
14.8. The CUPS Filter Chains
14.9. CUPS Print Drivers and Devices
14.10. Limiting the number of pages users can print
14.11. Advanced Postscript Printing from MS Windows
14.12. Auto-Deletion of CUPS spool files
15. Unified Logons between Windows NT and UNIX using Winbind
15.1. Abstract
15.2. Introduction
15.3. What Winbind Provides
15.4. How Winbind Works
15.5. Installation and Configuration
15.6. Limitations
15.7. Conclusion
16. Advanced Network Manangement
16.1. Configuring Samba Share Access Controls
16.2. Remote Server Administration
16.3. Network Logon Script Magic
17. System and Account Policies
17.1. Creating and Managing System Policies
17.2. Managing Account/User Policies
17.3. System Startup and Logon Processing Overview
18. Desktop Profile Management
18.1. Roaming Profiles
18.2. Mandatory profiles
18.3. Creating/Managing Group Profiles
18.4. Default Profile for Windows Users
19. Interdomain Trust Relationships
19.1. Trust Relationship Background
19.2. Native MS Windows NT4 Trusts Configuration
19.3. Configuring Samba NT-style Domain Trusts
20. PAM Configuration for Centrally Managed Authentication
20.1. Samba and PAM
20.2. Distributed Authentication
20.3. PAM Configuration in smb.conf
21. Stackable VFS modules
21.1. Introduction and configuration
21.2. Included modules
21.3. VFS modules available elsewhere
22. Hosting a Microsoft Distributed File System tree on Samba
22.1. Instructions
23. Integrating MS Windows networks with Samba
23.1. Name Resolution in a pure Unix/Linux world
23.2. Name resolution as used within MS Windows networking
24. Improved browsing in samba
24.1. Overview of browsing
24.2. Browsing support in samba
24.3. Problem resolution
24.4. Browsing across subnets
24.5. Setting up a WINS server
24.6. Setting up Browsing in a WORKGROUP
24.7. Setting up Browsing in a DOMAIN
24.8. Forcing samba to be the master
24.9. Making samba the domain master
24.10. Note about broadcast addresses
24.11. Multiple interfaces
25. Securing Samba
25.1. Introduction
25.2. Using host based protection
25.3. Using interface protection
25.4. Using a firewall
25.5. Using a IPC$ share deny
25.6. Upgrading Samba
26. Unicode/Charsets
26.1. What are charsets and unicode?
26.2. Samba and charsets
26.3. Conversion from old names
26.4. Japanese charsets
IV. Appendixes
27. How to compile SAMBA
27.1. Access Samba source code via CVS
27.2. Accessing the samba sources via rsync and ftp
27.3. Verifying Samba's PGP signature
27.4. Building the Binaries
27.5. Starting the smbd and nmbd
28. Migration from NT4 PDC to Samba-3 PDC
28.1. Planning and Getting Started
28.2. Managing Samba-3 Domain Control
29. Portability
29.1. HPUX
29.2. SCO Unix
29.3. DNIX
29.4. RedHat Linux Rembrandt-II
29.5. AIX
29.6. Solaris
30. Samba and other CIFS clients
30.1. Macintosh clients?
30.2. OS2 Client
30.3. Windows for Workgroups
30.4. Windows '95/'98
30.5. Windows 2000 Service Pack 2
30.6. Windows NT 3.1
31. SWAT - The Samba Web Admininistration Tool
31.1. SWAT Features and Benefits
32. Samba performance issues
32.1. Comparisons
32.2. Socket options
32.3. Read size
32.4. Max xmit
32.5. Log level
32.6. Read raw
32.7. Write raw
32.8. Slow Clients
32.9. Slow Logins
32.10. Client tuning
33. The samba checklist
33.1. Introduction
33.2. Assumptions
33.3. The tests
33.4. Still having troubles?
34. Analysing and solving samba problems
34.1. Diagnostics tools
34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
34.3. Useful URL's
34.4. Getting help from the mailing lists
34.5. How to get off the mailinglists
35. Reporting Bugs
35.1. Introduction
35.2. General info
35.3. Debug levels
35.4. Internal errors
35.5. Attaching to a running process
35.6. Patches
  Next
  General installation
\ No newline at end of file diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html deleted file mode 100644 index ddfb22536b..0000000000 --- a/docs/htmldocs/securitylevels.html +++ /dev/null @@ -1,212 +0,0 @@ - -Chapter 4. Samba as Stand-Alone Server
Chapter 4. Samba as Stand-Alone Server
Prev Part II. Server Configuration Basics Next

Chapter 4. Samba as Stand-Alone Server

Andrew Tridgell

Samba Team

<tridge@samba.org>

Jelmer R. Vernooij

The Samba Team

<jelmer@samba.org>

Table of Contents

User and Share security level
User Level Security
Share Level Security
Server Level Security
Domain Level Security
ADS Level Security

-In this section the function and purpose of Samba's security -modes are described. -

User and Share security level

-A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed. -

User Level Security

-I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after -the protocol negotiation. This contains a username and password. The -server can either accept or reject that username/password -combination. Note that at this stage the server has no idea what -share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than: -

  1. the username/password

  2. the machine that the client is coming from

-If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without -specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup". -

-It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use -as an authentication tag for that username/password. The client can -maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this) -

Share Level Security

-Ok, now for share level security. In share level security the client -authenticates itself separately for each share. It will send a -password along with each "tree connection" (share mount). It does not -explicitly send a username with this operation. The client is -expecting a password to be associated with each share, independent of -the user. This means that samba has to work out what username the -client probably wants to use. It is never explicitly sent the -username. Some commercial SMB servers such as NT actually associate -passwords directly with shares in share level security, but samba -always uses the unix authentication scheme where it is a -username/password that is authenticated, not a "share/password". -

-Many clients send a "session setup" even if the server is in share -level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds -to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the user = smb.conf -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user. -

Server Level Security

-Finally "server level" security. In server level security the samba -server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba -server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same -username/password that it got from the client. If that server is in -user level security and accepts the password then samba accepts the -clients connection. This allows the samba server to use another SMB -server as the "password server". -

-You should also note that at the very start of all this, where the -server tells the client what security level it is in, it also tells -the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all -passwords in encrypted form. You have to compile samba with encryption -enabled to support this feature, and you have to maintain a separate -smbpasswd file with SMB style encrypted passwords. It is -cryptographically impossible to translate from unix style encryption -to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync. -

-"security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support. -

Note

-Server level security is incompatible with what is known -as schannel or "sign and seal" protocols. This means that -if you want to use server level security you must disable -the use of "sign and seal" on all machines on your network. -

Configuring Samba for Seemless Windows Network Integration

-MS Windows clients may use encrypted passwords as part of a challenege/response -authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple -password based authentication. It should be realized that with the SMB protocol -the password is passed over the network either in plain text or encrypted, but -not both in the same authentication request. -

-When encrypted passwords are used a password that has been entered by the user -is encrypted in two ways: -

  • An MD4 hash of the UNICODE of the password - string. This is known as the NT hash. -

  • The password is converted to upper case, - and then padded or trucated to 14 bytes. This string is - then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. - The resulting 16 bytes for the LanMan hash. -

-MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 -pre-service pack 3 will use either mode of password authentication. All -versions of MS Windows that follow these versions no longer support plain -text passwords by default. -

-MS Windows clients have a habit of dropping network mappings that have been idle -for 10 minutes or longer. When the user attempts to use the mapped drive -connection that has been dropped, the client re-establishes the connection using -a cached copy of the password. -

-When Microsoft changed the default password mode, support was dropped for caching -of the plain text password. This means that when the registry parameter is changed -to re-enable use of plain text passwords it appears to work, but when a dropped -service connection mapping attempts to revalidate it will fail if the remote -authentication server does not support encrypted passwords. This means that it -is definitely not a good idea to re-enable plain text password support in such clients. -

-The following parameters can be used to work around the issue of Windows 9x client -upper casing usernames and password before transmitting them to the SMB server -when using clear text authentication. -

-	passsword level = integer
-	username level = integer
-

-By default Samba will lower case the username before attempting to lookup the user -in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the username level parameter -is rarely needed. -

-However, passwords on UNIX systems often make use of mixed case characters. -This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level -must be set to the maximum number of upper case letter which could -appear is a password. Note that the server OS uses the traditional DES version -of crypt(), a password level of 8 will result in case -insensitive passwords as seen from Windows users. This will also result in longer -login times as Samba has to compute the permutations of the password string and -try them one by one until a match is located (or all combinations fail). -

-The best option to adopt is to enable support for encrypted passwords -where ever Samba is used. There are three configuration possibilities -for support of encrypted passwords: -

Use MS Windows NT as an authentication server

-This method involves the additions of the following parameters in the smb.conf file: -

-	encrypt passwords = Yes
-	security = server
-	password server = "NetBIOS_name_of_PDC"
-

-There are two ways of identifying whether or not a username and -password pair was valid or not. One uses the reply information provided -as part of the authentication messaging process, the other uses -just an error code. -

-The down-side of this mode of configuration is the fact that -for security reasons Samba will send the password server a bogus -username and a bogus password and if the remote server fails to -reject the username and password pair then an alternative mode -of identification of validation is used. Where a site uses password -lock out after a certain number of failed authentication attempts -this will result in user lockouts. -

-Use of this mode of authentication does require there to be -a standard Unix account for the user, this account can be blocked -to prevent logons by other than MS Windows clients. -

Domain Level Security

-When samba is operating in security = domain mode this means that -the Samba server has a domain security trust account (a machine account) and will cause -all authentication requests to be passed through to the domain controllers. -

Samba as a member of an MS Windows NT security domain

-This method involves addition of the following parameters in the smb.conf file: -

-	encrypt passwords = Yes
-	security = domain
-	workgroup = "name of NT domain"
-	password server = *
-

-The use of the "*" argument to password server will cause samba to locate the -domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour. -

-In order for this method to work the Samba server needs to join the -MS Windows NT security domain. This is done as follows: -

  • On the MS Windows NT domain controller using - the Server Manager add a machine account for the Samba server. -

  • Next, on the Linux system execute: - smbpasswd -r PDC_NAME -j DOMAIN_NAME (samba 2.x) - - net join -U administrator%password (samba-3) -

-Use of this mode of authentication does require there to be a standard Unix account -for the user in order to assign a uid once the account has been authenticated by -the remote Windows DC. This account can be blocked to prevent logons by clients other than -MS Windows through things such as setting an invalid shell in the -/etc/passwd entry. -

-An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the Winbind Overview chapter -in this HOWTO collection. -

ADS Level Security

-For information about the configuration option please refer to the entire section entitled -Samba as an ADS Domain Member. -

Prev Up Next
Chapter 3. Nomenclature of Server Types Home Chapter 5.  -Samba as an NT4 or Win2k Primary Domain Controller -
diff --git a/docs/htmldocs/servertype.html b/docs/htmldocs/servertype.html deleted file mode 100644 index 42a7604797..0000000000 --- a/docs/htmldocs/servertype.html +++ /dev/null @@ -1,368 +0,0 @@ - -Nomenclature of Server Types
SAMBA Project Documentation
PrevNext

Chapter 5. Nomenclature of Server Types

Table of Contents
5.1. Stand Alone Server
5.2. Domain Member Server
5.3. Domain Controller

Adminstrators of Microsoft networks often refer to there being three -different type of servers:

  • Stand Alone Server

  • Domain Member Server

  • Domain Controller

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

A network administrator who is familiar with these terms and who -wishes to migrate to or use Samba will want to know what these terms mean -within a Samba context.

5.1. Stand Alone Server

The term stand alone server means that the server -will provide local authentication and access control for all resources -that are available from it. In general this means that there will be a -local user database. In more technical terms, it means that resources -on the machine will either be made available in either SHARE mode or in -USER mode. SHARE mode and USER mode security are documented under -discussions regarding "security mode". The smb.conf configuration parameters -that control security mode are: "security = user" and "security = share".

No special action is needed other than to create user accounts. Stand-alone -servers do NOT provide network logon services, meaning that machines that -use this server do NOT perform a domain logon but instead make use only of -the MS Windows logon which is local to the MS Windows workstation/server.

Samba tends to blur the distinction a little in respect of what is -a stand alone server. This is because the authentication database may be -local or on a remote server, even if from the samba protocol perspective -the samba server is NOT a member of a domain security context.

Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) the source of authentication may reside on -another server. We would be inclined to call this the authentication server. -This means that the samba server may use the local Unix/Linux system -password database (/etc/passwd or /etc/shadow), may use a local smbpasswd -file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or -may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB -server for authentication.

5.2. Domain Member Server

This mode of server operation involves the samba machine being made a member -of a domain security context. This means by definition that all user authentication -will be done from a centrally defined authentication regime. The authentication -regime may come from an NT3/4 style (old domain technology) server, or it may be -provided from an Active Directory server (ADS) running on MS Windows 2000 or later.

Of course it should be clear that the authentication back end itself could be from any -distributed directory architecture server that is supported by Samba. This can be -LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.

Please refer to the section on Howto configure Samba as a Primary Domain Controller -and for more information regarding how to create a domain machine account for a -domain member server as well as for information regading how to enable the samba -domain member machine to join the domain and to be fully trusted by it.

5.3. Domain Controller

Over the years public perceptions of what Domain Control really is has taken on an -almost mystical nature. Before we branch into a brief overview of what Domain Control -is the following types of controller are known:

5.3.1. Domain Controller Types

Primary Domain Controller
Backup Domain Controller
ADS Domain Controller

The Primary Domain Controller or PDC plays an important role in the MS -Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many -expect. The PDC seeds the Domain Control database (a part of the Windows registry) and -it plays a key part in synchronisation of the domain authentication database.

New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as -the NT4 style SAM (Security Account Manager) database (one of the registry files). -The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and -valid options include smbpasswd tdbsam ldapsam nisplussam plugin unixsam. -The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix -Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux -system accounts, provided a uid range is defined from which SAM accounts can be created.

The Backup Domain Controller or BDC plays a key role in servicing network -authentication requests. The BDC is biased to answer logon requests so that on a network segment -that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will -answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to -a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is -automatically demoted to a BDC.

At this time Samba is NOT capable of acting as an ADS Domain Controller.

PrevHomeNext
Type of installationUpSamba as Stand-Alone Server
\ No newline at end of file diff --git a/docs/htmldocs/swat.html b/docs/htmldocs/swat.html deleted file mode 100644 index e70fac5403..0000000000 --- a/docs/htmldocs/swat.html +++ /dev/null @@ -1,233 +0,0 @@ - -SWAT - The Samba Web Admininistration Tool
SAMBA Project Documentation
PrevNext

Chapter 31. SWAT - The Samba Web Admininistration Tool

This is a rough guide to SWAT.

31.1. SWAT Features and Benefits

You must use at least the following ...

31.1.2. Global Settings

Document steps right here!

31.1.3. The SWAT Wizard

Lots of blah blah here.

31.1.4. Share Settings

Document steps right here!

31.1.5. Printing Settings

Document steps right here!

31.1.6. The Status Page

Document steps right here!

31.1.7. The Password Change Page

Document steps right here!

PrevHomeNext
Samba and other CIFS clientsUpSamba performance issues
\ No newline at end of file diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html deleted file mode 100644 index e9a3b5e671..0000000000 --- a/docs/htmldocs/unix-permissions.html +++ /dev/null @@ -1,194 +0,0 @@ - -Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists
Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists
Prev Part III. Advanced Configuration Next

Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists

Jeremy Allison

Samba Team

<jra@samba.org>

12 Apr 1999

Table of Contents

Viewing and changing UNIX permissions using the NT - security dialogs
How to view file security on a Samba share
Viewing file ownership
Viewing file or directory permissions
File Permissions
Directory Permissions
Modifying file or directory permissions
Interaction with the standard Samba create mask - parameters
Interaction with the standard Samba file attribute - mapping

Viewing and changing UNIX permissions using the NT - security dialogs

Windows NT clients can use their native security settings - dialog box to view and modify the underlying UNIX permissions.

Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set.

Note

- All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - the identity of the Windows user as it is presented by Samba at - the point of file access. This can best be determined from the - Samba log files. -

How to view file security on a Samba share

From an NT4/2000/XP client, single-click with the right - mouse button on any file or directory in a Samba mounted - drive letter or UNC path. When the menu pops-up, click - on the Properties entry at the bottom of - the menu. This brings up the file properties dialog - box. Click on the tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

Viewing file ownership

Clicking on the "Ownership" button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :

"SERVER\user (Long name)"

Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the Close - button to remove this dialog.

If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone".

The Take Ownership button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the root - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.

There is an NT chown command that will work with Samba - and allow a user with Administrator privilege connected - to a Samba server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the Seclib - NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.

Viewing file or directory permissions

The third button is the "Permissions" - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :

"SERVER\user (Long name)"

Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.

File Permissions

The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group Everyone, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - user icon and an NT local - group icon respectively followed by the list - of permissions allowed for the UNIX user and group.

As many UNIX permission sets don't map into common - NT names such as "read", - "change" or "full control" then - usually the permissions will be prefixed by the words - "Special Access" in the NT display list.

But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below.

Directory Permissions

Directories on an NT NTFS file system have two - different sets of permissions. The first set of permissions - is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.

The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the - "inherited" permissions that any file created within - this directory would inherit.

Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.

Modifying file or directory permissions

Modifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the OK button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.

If the parameter nt acl support - is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

The first thing to note is that the "Add" - button will not return a list of users in Samba (it will give - an error message of "The remote procedure call failed - and did not execute"). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.

If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the "OK" button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component.

As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.

When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the "Replace - permissions on existing files" checkbox in the NT - dialog before clicking "OK".

If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the "Remove" button, - or set the component to only have the special "Take - Ownership" permission (displayed as "O" - ) highlighted.

Interaction with the standard Samba create mask - parameters

There are four parameters - to control interaction with the standard Samba create mask parameters. - These are :

security mask

force security mode

directory security mask

force directory security mode

Once a user clicks "OK" to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions.

Essentially, zero bits in the security mask - mask may be treated as a set of bits the user is not - allowed to change, and one bits are those the user is allowed to change. -

If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter - to 0777.

Next Samba checks the changed permissions for a file against - the bits set in the - force security mode parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.

Essentially, bits set in the force security mode - parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.

If not set explicitly this parameter is set to the same value - as the force - create mode parameter. - To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

The security mask and force - security mode parameters are applied to the change - request in that order.

For a directory Samba will perform the same operations as - described above for a file except using the parameter - directory security mask instead of security - mask, and force directory security mode - parameter instead of force security mode - .

The directory security mask parameter - by default is set to the same value as the directory mask - parameter and the force directory security - mode parameter by default is set to the same value as - the force directory mode parameter.

In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.

If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the smb.conf file in that share specific section :

security mask = 0777

force security mode = 0

directory security mask = 0777

force directory security mode = 0

Interaction with the standard Samba file attribute - mapping

Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can - be a conflict between the permission bits set via the security - dialog and the permission bits set by the file attribute mapping. -

One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.

What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - "OK" to get back to the standard attributes tab - dialog, and then clicks "OK" on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking "OK" to get back to the - attributes dialog you should always hit "Cancel" - rather than "OK" to ensure that your changes - are not overridden.

Prev Up Next
Chapter 10. User information database Home Chapter 12. Configuring Group Mapping
diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html deleted file mode 100644 index fcaca133fe..0000000000 --- a/docs/htmldocs/vfs.html +++ /dev/null @@ -1,490 +0,0 @@ - -Stackable VFS modules
SAMBA Project Documentation
PrevNext

Chapter 21. Stackable VFS modules

Table of Contents
21.1. Introduction and configuration
21.2. Included modules
21.2.1. audit
21.2.2. extd_audit
21.2.3. recycle
21.2.4. netatalk
21.3. VFS modules available elsewhere
21.3.1. DatabaseFS
21.3.2. vscan

21.1. Introduction and configuration

Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. -Samba passes each request to access the unix file system thru the loaded VFS modules. -This chapter covers all the modules that come with the samba source and references to -some external modules.

You may have problems to compile these modules, as shared libraries are -compiled and linked in different ways on different systems. -They currently have been tested against GNU/linux and IRIX.

To use the VFS modules, create a share similar to the one below. The -important parameter is the vfs object parameter which must point to -the exact pathname of the shared library objects. For example, to log all access -to files and use a recycle bin: - -

       [audit]
-                comment = Audited /data directory
-                path = /data
-                vfs object = /path/to/audit.so /path/to/recycle.so
-                writeable = yes
-                browseable = yes

The modules are used in the order they are specified.

Further documentation on writing VFS modules for Samba can be found in -the Samba Developers Guide.

21.2. Included modules

21.2.1. audit

A simple module to audit file access to the syslog -facility. The following operations are logged: -

share
connect/disconnect
directory opens/create/remove
file open/close/rename/unlink/chmod

21.2.2. extd_audit

This module is identical with the audit module above except -that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. At loglevel = 0, only file -and directory deletions and directory and file creations are logged. At loglevel = 1 -file opens are renames and permission changes are logged , while at loglevel = 2 file -open and close calls are logged also.

21.2.3. recycle

A recycle-bin like modules. When used any unlink call -will be intercepted and files moved to the recycle -directory instead of beeing deleted.

Supported options: -

vfs_recycle_bin:repository

FIXME

vfs_recycle_bin:keeptree

FIXME

vfs_recycle_bin:versions

FIXME

vfs_recycle_bin:touch

FIXME

vfs_recycle_bin:maxsize

FIXME

vfs_recycle_bin:exclude

FIXME

vfs_recycle_bin:exclude_dir

FIXME

vfs_recycle_bin:noversions

FIXME

21.2.4. netatalk

A netatalk module, that will ease co-existence of samba and -netatalk file sharing services.

Advantages compared to the old netatalk module: -

it doesn't care about creating of .AppleDouble forks, just keeps ones in sync
if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

21.3. VFS modules available elsewhere

This section contains a listing of various other VFS modules that -have been posted but don't currently reside in the Samba CVS -tree for one reason ot another (e.g. it is easy for the maintainer -to have his or her own CVS tree).

No statemets about the stability or functionality any module -should be implied due to its presence here.

21.3.1. DatabaseFS

URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

By Eric Lorimer.

I have created a VFS module which implements a fairly complete read-only -filesystem. It presents information from a database as a filesystem in -a modular and generic way to allow different databases to be used -(originally designed for organizing MP3s under directories such as -"Artists," "Song Keywords," etc... I have since applied it to a student -roster database very easily). The directory structure is stored in the -database itself and the module makes no assumptions about the database -structure beyond the table it requires to run.

Any feedback would be appreciated: comments, suggestions, patches, -etc... If nothing else, hopefully it might prove useful for someone -else who wishes to create a virtual filesystem.

21.3.2. vscan

URL: http://www.openantivirus.org/

samba-vscan is a proof-of-concept module for Samba, which -uses the VFS (virtual file system) features of Samba 2.2.x/3.0 -alphaX. Of couse, Samba has to be compiled with VFS support. -samba-vscan supports various virus scanners and is maintained -by Rainer Link.

PrevHomeNext
PAM Configuration for Centrally Managed AuthenticationUpHosting a Microsoft Distributed File System tree on Samba
\ No newline at end of file diff --git a/docs/textdocs/README.NOW b/docs/textdocs/README.NOW deleted file mode 100644 index dda607097b..0000000000 --- a/docs/textdocs/README.NOW +++ /dev/null @@ -1,6 +0,0 @@ -All old text documents have been converted to docbook. -To create ASCII versions of the official documentation -run the following command in ../docbook/: - - $ make txt - diff --git a/docs/textdocs/README.jis b/docs/textdocs/README.jis deleted file mode 100644 index 50ff0cced7..0000000000 --- a/docs/textdocs/README.jis +++ /dev/null @@ -1,149 +0,0 @@ -$B!|(B samba $BF|K\8lBP1~$K$D$$$F(B - -1. $BL\E*(B - - $BF|K\8lBP1~$O!"(B - - (1) MS-Windows $B>e$G!"4A;z%U%!%$%kL>$r$I$&$7$F$b07$&I,MW$N$"$k%"%W%j%1!<%7%g%s$,$A$c(B - $B$s$HF0:n$9$k!#Nc$($P!"(BMS-WORD 5 $B$J$I$O!"%$%s%9%H!<%k;~$K4A;z$N%U%!%$%kL>$r>!l9g$K$A$c$s$HBP1~$G$-$k$h$&$K$9$k!#(B - - (2) UNIX $B$O!":G6a$G$O$[$H$s$I$N$b$N$,(B 8 bits $B$N%U%!%$%kL>$r%5%]!<%H$7$F$$$^$9$,!"(B - $BCf$K$O!"$3$l$r%5%]!<%H$7$F$$$J$$$b$N$b$"$j$^$9!#$3$N$h$&$J>l9g$G$b!"(B(1)$B$NL\E*(B - $B$,K~B-$G$-$k$h$&$K$9$k!#(B - - $B$rL\E*$H$7$F$$$^$9!#$=$N$?$a!"F|K\8lBP1~$O!"I,MW:G>.8B$7$+9T$J$C$F$*$j$^$;$s!#(B - - $BF|K\8lBP1~$7$?(B samba $B$rMxMQ$9$k$?$a$K$O!"%3%s%Q%$%k$9$k;~$K!"I,$:!"(BKANJI $B$NDj5A$rDI(B - $B2C$7$F$/$@$5$$!#$3$N%*%W%7%g%s$r;XDj$7$F$$$J$$>l9g$O!"F|K\8l$N%U%!%$%kL>$r@5$7$/07(B - $B$&$3$H$O$G$-$^$;$s!#!J%3%s%Q%$%k$K$D$$$F$O!"2<5-(B 3. $B$r;2>H$7$F2<$5$$!K(B - -2. $BMxMQJ}K!(B - -(1) $BDI2C$7$?%Q%i%a!<%?(B - - smb.conf $B%U%!%$%k$N(B global $B%;%/%7%g%s$K0J2<$N%Q%i%a!<%?$r@_Dj$G$-$k$h$&$K$7$^$7$?!#(B - - [global] - .... - coding system = <$B%3!<%I7O(B> - - $B$3$3$G;XDj$5$l$?%3!<%I7O$,(B UNIX $B>e$N%U%!%$%k%7%9%F%`$N%U%!%$%kL>$N%3!<%I$K$J$j$^$9!#(B - $B@_Dj$G$-$k$b$N$O!"A0$O!"(B':83:49:83:74:83:42:83:58' $B$N$h$&$K!"(B':' $B$N8e$K#27e(B - $B$N(B16$B?J?t$rB3$1$k7A<0$K$J$j$^$9!#(B - $B$3$3$G!"(B':' $B$rB>$NJ8;z$KJQ99$7$?$$>l9g$O!"(Bhex $B$N8e$m$K$=$NJ8;z$r;XDj$7$^$9!#(B - $BNc$($P!"(B@$B$rJQ$o$j$K;H$$$?$$>l9g$O!"(B'hex@'$B$N$h$&$K;XDj$7$^$9!#(B - cap: 7 bits $B$N(B ASCII $B%3!<%I0J30$N%3!<%I$r0J2<$N7A<0$GI=$9J}<0$H$$$&E@$G$O(B - hex$B$HF1MM$G$9$,!"(BCAP (The Columbia AppleTalk Package)$B$H8_49@-$r;}$DJQ49(B - $BJ}<0$H$J$C$F$$$^$9!#(Bhex$B$H$N0c$$$O(B0x80$B0J>e$N%3!<%I$N$_(B':80'$B$N$h$&$KJQ49(B - $B$5$l!"$=$NB>$O(BASCII$B%3!<%I$G8=$5$l$^$9!#(B - $BNc$($P!"(B'$B%*%U%#%9(B'$B$H$$$&L>A0$O!"(B':83I:83t:83B:83X'$B$H$J$j$^$9!#(B - - JIS $B%3!<%I$K$D$$$F$O!"0J2<$NI=$r;2>H$7$F2<$5$$!#(B - $B(#(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(!(!(!(!(!($(B - $B(";XDj(B $B("4A;z3+;O("4A;z=*N;("%+%J3+;O("%+%J=*N;("1Q?t3+;O("Hw9M(B $B("(B - $B('(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(!(!(!(!(!()(B - $B("(Bjis7 $B("(B\E$B $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(Bjis 7$BC10LId9f(B $B("(B - $B("(Bjunet $B("(B\E$B $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(B7bits $B%3!<%I(B $B("(B - $B("(Bjis8 $B("(B\E$B $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(Bjis 8$BC10LId9f(B $B("(B - $B("(Bj7bb $B("(B\E$B $B("(B\E(B $B("(B0x0e $B("(B0x0f $B("(B\E(B $B("(B $B("(B - $B("(Bj7bj $B("(B\E$B $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(Bjis7$B$HF1$8(B $B("(B - $B("(Bj7bh $B("(B\E$B $B("(B\E(H $B("(B0x0e $B("(B0x0f $B("(B\E(H $B("(B $B("(B - $B("(Bj7@b $B("(B\E$@ $B("(B\E(B $B("(B0x0e $B("(B0x0f $B("(B\E(B $B("(B $B("(B - $B("(Bj7@j $B("(B\E$@ $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(B $B("(B - $B("(Bj7@h $B("(B\E$@ $B("(B\E(H $B("(B0x0e $B("(B0x0f $B("(B\E(H $B("(B $B("(B - $B("(Bj8bb $B("(B\E$B $B("(B\E(B $B("(B-- $B("(B-- $B("(B\E(B $B("(B $B("(B - $B("(Bj8bj $B("(B\E$B $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(Bjis8$B$HF1$8(B $B("(B - $B("(Bj8bh $B("(B\E$B $B("(B\E(H $B("(B-- $B("(B-- $B("(B\E(H $B("(B $B("(B - $B("(Bj8@b $B("(B\E@@ $B("(B\E(B $B("(B-- $B("(B-- $B("(B\E(B $B("(B $B("(B - $B("(Bj8@j $B("(B\E$@ $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(B $B("(B - $B("(Bj8@h $B("(B\E$@ $B("(B\E(H $B("(B-- $B("(B-- $B("(B\E(H $B("(B $B("(B - $B("(Bjubb $B("(B\E$B $B("(B\E(B $B("(B\E(I $B("(B\E(B $B("(B\E(B $B("(B $B("(B - $B("(Bjubj $B("(B\E$B $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(Bjunet$B$HF1$8(B $B("(B - $B("(Bjubh $B("(B\E$B $B("(B\E(H $B("(B\E(I $B("(B\E(H $B("(B\E(H $B("(B $B("(B - $B("(Bju@b $B("(B\E$@ $B("(B\E(B $B("(B\E(I $B("(B\E(B $B("(B\E(B $B("(B $B("(B - $B("(Bju@j $B("(B\E$@ $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(B $B("(B - $B("(Bju@h $B("(B\E$@ $B("(B\E(H $B("(B\E(I $B("(B\E(H $B("(B\E(H $B("(B $B("(B - $B(&(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(!(!(!(!(!(%(B - - $B$$$:$l$N>l9g$b!"$9$G$KB8:_$7$F$$$kL>A0$KBP$7$F$O!"4A;z$N3+;O=*N;%7!<%1%s%9$O!"0J2<(B - $B$N$b$N$rG'<1$7$^$9!#(B - $B4A;z$N;O$^$j(B: \E$B $B$+(B \E$@ - $B4A;z$N=*$j(B: \E(J $B$+(B \E(B $B$+(B \E(H - -(2) smbclient $B$N%*%W%7%g%s(B - - $B%/%i%$%"%s%H%W%m%0%i%`$G$b!"4A;z$d2>L>$r4^$s$@%U%!%$%k$r07$($k$h$&$K!" - - $B$3$3$G!"(B<$B%?!<%_%J%k%3!<%I7O(B>$B$K;XDj$G$-$k$b$N$O!">e$N(B<$B%3!<%I7O(B>$B$HF1$8$b$N$G$9!#(B - -(3) $B%G%U%)%k%H(B - - $B%G%U%)%k%H$N%3!<%I7O$O!"%3%s%Q%$%k;~$K7h$^$j$^$9!#(B - -3. $B%3%s%Q%$%k;~$N@_Dj(B - - Makefile $B$K@_Dj$9$k9`L\$r0J2<$K<($7$^$9!#(B - -(1) KANJI $B%U%i%0(B - - $B%3%s%Q%$%k%*%W%7%g%s$K(B -DKANJI=\"$B%3!<%I7O(B\" $B$r;XDj$7$^$9!#$3$N%3!<%I7O$O(B 2. $B$G;X(B - $BDj$9$k$b$N$HF1$8$G$9!#Nc$($P!"(B-DKANJI=\"euc\" $B$r(BFLAGSM $B$K@_Dj$9$k$H(B UNIX $B>e$N%U%!(B - $B%$%kL>$O!"(BEUC $B%3!<%I$K$J$j$^$9!#$3$3$G;XDj$7$?%3!<%I7O$O!"%5!<%P5Z$S%/%i%$%"%s%H(B - $B%W%m%0%i%`$N%G%U%)%k%H$KCM$J$j$^$9!#(B - - $B>0!"%*%W%7%g%sCf$N(B \ $B$d(B " $B$bK:$l$:$K;XDj$7$F2<$5$$!#(B - -3. $B@)8B;v9`(B - -(1) $B4A;z%3!<%I(B - smbd $B$rF0:n$5$;$k%[%9%H$N(B UNIX $B$,%5%]!<%H$7$F$$$J$$4A;z%3!<%I$O!"MxMQ$G$-$J$$$3$H$,(B - $B$"$j$^$9!#JQ$JF0:n$r$9$k$h$&$J$i(B hex $B$N;XDj$r$9$k$N$,NI$$$G$7$g$&!#(B - -(2) smbclient $B%3%^%s%I(B - $B%7%U%H%3!<%I$J$I$N4X78$G!"4A;z$d2>L>$r4^$s$@%U%!%$%kL>$N(B ls $B$NI=<($,Mp$l$k$3$H$,$"$j(B - $B$^$9!#(B - -(3) $B%o%$%k%I%+!<%I$K$D$$$F(B - $B$A$c$s$H$7$?%9%Z%C%/$,$h$/$o$+$i$J$+$C$?$N$G$9$,!"0l1~!"(BDOS/V $B$NF0:n$HF1$8F0:n$r9T$J(B - $B$&$h$&$K$J$C$F$$$^$9!#(B - -(4) $B%m%s%0%U%!%$%kL>$K$D$$$F(B - Windows NT/95 $B$G$O!"%m%s%0%U%!%$%kL>$,07$($^$9!#%m%s%0%U%!%$%kL>$r(B 8.3 $B%U%)!<%^%C%H(B - $B$G07$&$?$a$K!"(Bmangling $B$7$F$$$^$9$,!"$3$NJ}K!$O!"(BNT $B$d(B 95 $B$,9T$J$C$F$$$k(B mangling $B$H(B - $B$O0[$J$j$^$9$N$GCm0U$7$F2<$5$$!#(B - -4. $B>c32Ey$N%l%]!<%H$K$D$$$F(B - - $BF|K\8l$N%U%!%$%kL>$K4X$7$F!"J8;z2=$1Ey$N>c32$,$"$l$P!";d$K%l%]!<%H$7$FD:$1$l$P9,$$$G(B -$B$9!#$?$@$7!"%*%j%8%J%k$+$i$NLdBjE@$d@\Ld$$9g$o$;$k(B -$B$+!"$b$7$/$O%a!<%j%s%0%j%9%H$J$I$X%l%]!<%H$9$k$h$&$K$7$F2<$5$$!#(B - -$B%l%]!<%H$5$l$k>l9g!"MxMQ$5$l$F$$$k4D6-(B(UNIX $B5Z$S(B PC $BB&$N(BOS$B$J$I(B)$B$H$G$-$^$7$?$i@_Dj%U%!(B -$B%$%k$d%m%0$J$I$rE:IU$7$FD:$1$k$H9,$$$G$9!#(B - -5. $B$=$NB>(B - - $B%3!<%IJQ49$O0J2<$NJ}!9$,:n$i$l$?%W%m%0%i%`$rMxMQ$7$F$$$^$9!#(B - - hex $B7A<0(B $BBgLZ!wBgDM!&C^GH(B $B;a(B - cap $B7A<0(B $BI%ED(B $BF;O:(B (michiro@po.iijnet.or.jp)(michiro@dms.toppan.co.jp)$B;a(B - - $B$=$NB>!"$?$/$5$s$NJ}!9$+$i$$$m$$$m$H8f65<($$$?$@$-$"$j$,$H$&$4$6$$$^$7$?!#:#8e$H$b$h(B -$B$m$7$/$*4j$$CW$7$^$9!#(B - -1994$BG/(B10$B7n(B28$BF|(B $BBh#1HG(B -1995$BG/(B 8$B7n(B16$BF|(B $BBh#2HG(B -1995$BG/(B11$B7n(B24$BF|(B $BBh#3HG(B -1996$BG/(B 5$B7n(B13$BF|(B $BBh#4HG(B - -$BF#ED(B $B?r(B fujita@ainix.isac.co.jp - -- cgit