From aniluniyal at xoinfotech.com Sun Sep 9 07:34:00 2001 From: aniluniyal at xoinfotech.com (Anil) Date: Fri Feb 13 23:41:23 2004 Subject: Trust Relationship Message-ID: <000a01c13901$cbaf5320$1301a8c0@cyber> Could anybody help me to create trust relationship between Samba Domain and NT Domain. Pl. provide detailed description Thanks in Advance Anil -------------- next part -------------- HTML attachment scrubbed and removed From gcarter at valinux.com Tue Sep 4 00:37:13 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:24 2004 Subject: Newbie vents frustration - smbpasswd case In-Reply-To: <003a01c13048$15743380$0100a8c0@frankspc.mabrey> Message-ID: On Tue, 28 Aug 2001, Frank E Mabrey wrote: > I spent a considerable about of time struggling with access to samba > on Linux from Win98 before determining that smbpasswd does not like > mixed case user names. I think this should be EMPHASIZED in the docs. Thanks for the comments. Mixed case usernames is a very rare case in my experience. See the 'username level' parameter for more details. We could look into making this lookup dependent upon the system getpwnam() call (whether or not the OS username lookups are case sensitive). cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From gcarter at valinux.com Tue Sep 4 00:38:01 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:24 2004 Subject: man pages on samba website In-Reply-To: <15242.47494.93630.945719@frungy.org> Message-ID: On Tue, 28 Aug 2001, Tim Potter wrote: > Rafal Szczesniak writes: > > > I've looked at man pages on samba web site. Obviously it's > > not up to date. Is there any possibility to link the mans to > > their cvs html equivalents ? > > Yeah, I've discovered this too. I suspect the man pages are the > ones from the latest released version of Samba. Since you have > contributed the polish man pages the web site will have to be > updated with a link to the latest docs from CVS. Tim, I think these are rsync'd out of HEAD. I'll update HEAD asap and that should fix it. cheers, jerry --------------------------------------------------------------------- www.valinux.com VA Linux Systems gcarter_at_valinux.com www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From Glenn.Deans at sea.siemens.com Mon Sep 10 20:32:57 2001 From: Glenn.Deans at sea.siemens.com (Deans, Glenn) Date: Fri Feb 13 23:41:24 2004 Subject: Xinetd doesn't work, not documented Message-ID: <3EF10BAF5211D5119BEE00805F575D192BB2A2@IBMS01> I just spent several days trying to get Samba up and running and finally found the problem. On my RH7 I had xinetd installed and for some reason was preventing Samba from working. Once I removed the rpm it started working fine. The RH blurb said xinetd was an improved version of inetd. Being a newbie I figured ping is ping and if it works better then its less trouble for me. -- Wrong. Wish someone would add this little tidbit to the docs. Glenn "Tis not too late to seek a newer world." - Alfred, Lord Tennyson From mimir at spin.ict.pwr.wroc.pl Thu Sep 13 15:03:21 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: Turkish translations for swat In-Reply-To: <02fd01c13959$3e2db520$0300a8c0@ergenekon> Message-ID: On Sun, 9 Sep 2001, Deniz Akkus Kanca wrote: > Hello, Hi. I'm sorry for the absence, but my mail server has been out of order for the last 3-4 days. > The make process needs to be changed to include these. That's no problem, I guess. > Also, not having the parameter names in the local language makes the program > pretty cryptic for a non-English user. What can we do to make it more > understandable for a non-English speaker? Yes. We were talking about this with monyo and after a short mail exchange it seems to be better to leave parameter names in english and, optionally, add a short explanation. But I guess you already know that. > I have not yet translated the numerous help pages. Where does one go for > translating these? (Where in the source tree I mean, I assume they are > generated from a single location) I noticed you've been informed about this too. Good luck with smb.conf(5) ! You'll surely need it :) cheers, Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From Paul.Green at stratus.com Mon Sep 17 20:32:43 2001 From: Paul.Green at stratus.com (Green, Paul) Date: Fri Feb 13 23:41:24 2004 Subject: Samba Troubleshooting Guide Message-ID: <95AE3CDB3543D511883A0020485B38B901252AD0@exna3.stratus.com> I have written a troubleshooting guide for the port of Samba to the Stratus VOS operating system. It contains information that I have learned while tracking down and solving a number of installation and operational issues. This guide is by no means complete or comprehensive, but I have attempted to be careful and methodical about each entry. It uses a "Symptom, Cause, Resolution" format, much like the Knowledge Base format used by a number of vendors. I intend to add to it as our customers run into new issues. I don't intend to make it a generic document, suitable for any operating system, or covering all of the Samba features. Like many people, I have a bookshelf of large technical books that claim to serve that role. But I am offering it to the Samba community in the hopes it will be useful. I've been working on the VOS port of Samba for only 6 months, so I'm sure there are mistakes in here; if you see any, and have the time to let me know about them, I'd be very grateful. Since Samba is covered by the GPL, I have decided to apply the GNU Documentation License to this material. I hope this is acceptable to everyone; if not, I'd like to know what issues this creates for people. Please see ftp://ftp.stratus.com/pub/vos/customers/samba/SAMBA_Troubleshooting.rtf. Oh, and when you see the term "VOS", think "Unix" or "POSIX-compliant OS". Since my target audience is VOS customers, I haven't attempted to be generic...and this info is for Samba 2.0.7, which is the current version we are using. Thanks PG -- Paul Green, Senior Technical Consultant, Stratus Technologies. Voice: +1 978-461-7557; FAX: +1 978-461-3610; Video on request. From mimir at spin.ict.pwr.wroc.pl Tue Sep 18 21:54:56 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: yet another winbindd.8.sgml fix ? Message-ID: Correct me if I'm wrong here, but shouldn't any notes about that winbindd is not a part of stable samba go away from this file ? Just confirm and I'll make a patch for what I've caught. Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From gcarter at valinux.com Tue Sep 18 21:59:29 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:24 2004 Subject: yet another winbindd.8.sgml fix ? In-Reply-To: Message-ID: On Tue, 18 Sep 2001, Rafal Szczesniak wrote: > > Correct me if I'm wrong here, but shouldn't any notes about that > winbindd is not a part of stable samba go away from this file ? > Just confirm and I'll make a patch for what I've caught. Yes. They should. I removed the notices in smb.conf.5.sgml but forgot to clean winbindd.8.sgml. Thanks. jerry > > > Rafal 'Mimir' Szczesniak | > *BSD, Linux and Samba / > ______________________________________________________/ > > -- --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From mimir at spin.ict.pwr.wroc.pl Tue Sep 18 22:52:05 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: yet another winbindd.8.sgml fix ? In-Reply-To: Message-ID: On Tue, 18 Sep 2001, Gerald Carter wrote: > On Tue, 18 Sep 2001, Rafal Szczesniak wrote: > > > > > Correct me if I'm wrong here, but shouldn't any notes about that > > winbindd is not a part of stable samba go away from this file ? > > Just confirm and I'll make a patch for what I've caught. > > Yes. They should. I removed the notices in smb.conf.5.sgml > but forgot to clean winbindd.8.sgml. Thanks. No problem, Jerry. Patches included. Also the small one fixing a typo I've noticed in nmbd.8.sgml. > jerry > > > Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ -------------- next part -------------- --- manpages/winbindd.8.sgml Tue Sep 18 13:13:16 2001 +++ manpages.fix/winbind.8.sgml Wed Sep 19 00:44:17 2001 @@ -25,9 +25,8 @@ DESCRIPTION - This tool is part of the - Samba suite version 3.0 and describes functionality not - yet implemented in the main version of Samba. + This program is part of the + Samba suite. winbindd is a daemon that provides a service for the Name Service Switch capability that is present @@ -353,7 +352,7 @@ - Notes + NOTES The following notes are useful when configuring and running winbindd: @@ -366,8 +365,8 @@ servers, it must be sent a SIGHUP signal. Client processes resolving names through the winbindd - nsswitch module read an environment variable named - $WINBINDD_DOMAIN. If this variable contains a comma separated + nsswitch module read an environment variable named + $WINBINDD_DOMAIN. If this variable contains a comma separated list of Windows NT domain names, then winbindd will only resolve users and groups within those Windows NT domains. @@ -386,7 +385,7 @@ - Signals + SIGNALS The following signals can be used to manipulate the winbindd daemon. @@ -415,7 +414,7 @@ - Files + FILES @@ -444,7 +443,7 @@ $LOCKDIR/winbindd_idmap.tdb Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially - compiled using the --with-lockdir option. + compiled using the --with-lockdir option. This directory is by default /usr/local/samba/var/locks . @@ -461,9 +460,8 @@ VERSION - This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - the stable release of Samba as of yet. + This man page is correct for version 2.2 of + the Samba suite. -------------- next part -------------- --- manpages/nmbd.8.sgml Tue Jul 31 23:01:22 2001 +++ manpages.fix/nmbd.8.sgml Wed Sep 19 00:48:25 2001 @@ -15,7 +15,7 @@ - smbd + nmbd -D -a -o From mimir at spin.ict.pwr.wroc.pl Tue Sep 18 23:38:24 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: ... again, another typo Message-ID: Hehe :) I've noticed another typo in wbinfo.1.sgml ;-) Will send proper patch... Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From mimir at spin.ict.pwr.wroc.pl Tue Sep 18 23:57:01 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: ... again, another typo In-Reply-To: Message-ID: On Wed, 19 Sep 2001, Rafal Szczesniak wrote: > Hehe :) I've noticed another typo in wbinfo.1.sgml ;-) > > Will send proper patch... I'm doing as I said. Patch included. Jerry, I've cc'ed to you because someone should apply it - I count on you here :) I'll probably catch more things to fix, stay tuned :-) Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ -------------- next part -------------- --- manpages/wbinfo.1.sgml Fri Jun 22 18:53:29 2001 +++ manpages.fix/wbinfo.1.sgml Wed Sep 19 01:48:43 2001 @@ -14,7 +14,7 @@ - nmblookup + wbinfo -u -g -n name @@ -158,8 +158,7 @@ VERSION This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - stable release of Samba as of yet. + the Samba suite. @@ -177,7 +176,7 @@ to the way the Linux kernel is developed. wbinfo and winbindd - were written by TIm Potter. + were written by Tim Potter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter From monyo at samba.gr.jp Thu Sep 20 19:55:48 2001 From: monyo at samba.gr.jp (TAKAHASHI Motonobu) Date: Fri Feb 13 23:41:24 2004 Subject: How to integrate i18n docs in HEAD branch Message-ID: <20010921045548F.monyo@home.monyo.com> Jerry, To support SWAT i18n, we can determine where to put i18n documents in the source archive. There are several kind of documents. 1. translation of swat/{help,images,included} At samba-technical, I proposed swat/$ln/{help,images,included}. Deniz Akkus Kanca wrote: >> In Samba Japanese Edition, we put them at >> swat/$ln/{help,images,include}. Is this OK? > >Yes, this directory structure looks OK. Another solution is to put swat/lang/$ln/{help,images,included}. The following is mentioned about where to install, not where to put in source archive, but it may be usefull to adjust the directory tree. Andrew Tridgell wrote: >One request though - I think we should have a "lang" subdirectory for >languages. For example the ja Samba currently uses /swat/ja/ for the >Japanese SWAT templates, whereas I think we should probably use >/swat/lang/ja. That will scale a little better when we eventually get >dozens of languages in there. 2. translation of docs/{html,text}docs and docs/manpages I know Jerry put the Polish SGML files under docbook dir, but for installation we need only html and man page (and some text) files. We need to have docs of these formats because I think we should not assume that DOCBOOK - html and man page converter is always installed on the platform. docs/$ln/{htmldocs,manpages,faq,textdocs} or docs/{htmldocs,manpages,faq,textdocs} are considerable? Of course there should be a discussion whether the Samba archive includes these i18n'ed documentations as I mentioned before, but we can discuss it later. ----- TAKAHASHI, Motonobu(monyo) monyo@samba.org Personal - http://home.monyo.com/ Samba Team - http://samba.org/ Samba-JP - http://www.samba.gr.jp/ JWNTUG - http://www.jwntug.or.jp/ Analog-JP - http://www.jp.analog.cx/ MCSE+I, SCNA, CCNA, Turbo-CI From mimir at spin.ict.pwr.wroc.pl Thu Sep 20 21:16:42 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:24 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010921045548F.monyo@home.monyo.com> Message-ID: On Fri, 21 Sep 2001, TAKAHASHI Motonobu wrote: > Jerry, > > To support SWAT i18n, we can determine where to put i18n documents in > the source archive. > > There are several kind of documents. > > 1. translation of swat/{help,images,included} > At samba-technical, I proposed swat/$ln/{help,images,included}. > > Deniz Akkus Kanca wrote: > >> In Samba Japanese Edition, we put them at > >> swat/$ln/{help,images,include}. Is this OK? > > > >Yes, this directory structure looks OK. > > Another solution is to put swat/lang/$ln/{help,images,included}. > The following is mentioned about where to install, not where to put > in source archive, but it may be usefull to adjust the directory > tree. What would be in swat/ apart from the lang/ directory ? It seems to me the dir tree like swat/$ln/{help,images,include} is quite good. (...) > 2. translation of docs/{html,text}docs and docs/manpages > > I know Jerry put the Polish SGML files under docbook dir, but for > installation we need only html and man page (and some text) files. > > We need to have docs of these formats because I think we should not > assume that DOCBOOK - html and man page converter is always > installed on the platform. While I agree with you here, I'm also working on docs/docbook/configure.in and docs/docbook/Makefile.in files to automate generating of the html and man files from docs/docbook/$ln (pl here) directory. > docs/$ln/{htmldocs,manpages,faq,textdocs} or > docs/{htmldocs,manpages,faq,textdocs} are considerable? > > Of course there should be a discussion whether the Samba archive > includes these i18n'ed documentations as I mentioned before, but > we can discuss it later. Well... (a) docs/$ln/{html,manpages,faq,textdocs} makes easier extracting i18n'ed documentation in future and splitting it out as separated "packages" (b) docs/html/$ln, docs/manpages/$ln, docs/faq/$ln fits easier in current source tree Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From monyo at samba.gr.jp Fri Sep 21 04:18:10 2001 From: monyo at samba.gr.jp (TAKAHASHI Motonobu) Date: Fri Feb 13 23:41:24 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: References: <20010921045548F.monyo@home.monyo.com> Message-ID: <20010921131810B.monyo@home.monyo.com> Rafal Szczesniak wrote: >> Another solution is to put swat/lang/$ln/{help,images,included}. >> The following is mentioned about where to install, not where to put >> in source archive, but it may be usefull to adjust the directory >> tree. > >What would be in swat/ apart from the lang/ directory ? It seems to me >the dir tree like swat/$ln/{help,images,include} is quite good. swat/lang/$ln/ is Andrew's opinion. For me, both are acceptable. I think to fix it ASAP is important. >> We need to have docs of these formats because I think we should not >> assume that DOCBOOK - html and man page converter is always >> installed on the platform. > >While I agree with you here, I'm also working on >docs/docbook/configure.in and docs/docbook/Makefile.in files to >automate generating of the html and man files from docs/docbook/$ln >(pl here) directory. Does this mean you are creating a converter using awk, sed and other standard stuffs? >> docs/$ln/{htmldocs,manpages,faq,textdocs} or >> docs/{htmldocs,manpages,faq,textdocs} are considerable? Sorry for severe typo. docs/$ln/{htmldocs,manpages,faq,textdocs} or docs/lang/$ln/{htmldocs,manpages,faq,textdocs} are considerable? ~~~~~~~~ Anyway, >(a) >docs/$ln/{html,manpages,faq,textdocs} makes easier extracting i18n'ed >documentation in future and splitting it out as separated "packages" > >(b) >docs/html/$ln, docs/manpages/$ln, docs/faq/$ln fits easier in current >source tree For (a) and (b), I think (a) is better than (b). And for (a), we can easily take a partial CVS commit right later. ----- TAKAHASHI, Motonobu(monyo) monyo@samba.org Personal - http://home.monyo.com/ Samba Team - http://samba.org/ Samba-JP - http://www.samba.gr.jp/ JWNTUG - http://www.jwntug.or.jp/ Analog-JP - http://www.jp.analog.cx/ MCSE+I, SCNA, CCNA, Turbo-CI From sfvila at bkb.com Fri Sep 21 21:47:25 2001 From: sfvila at bkb.com (Sebastian F. Vila) Date: Fri Feb 13 23:41:24 2004 Subject: hi Message-ID: <0008DE0A.C21432@bkb.com> I've a question, because i had installed Samba on solaris, but when i have drag & drop with the text file, on Unix i red ^M in EOF. Can you sendme the solutions Regards, Sebas From mimir at spin.ict.pwr.wroc.pl Fri Sep 21 22:09:03 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010921131810B.monyo@home.monyo.com> Message-ID: On Fri, 21 Sep 2001, TAKAHASHI Motonobu wrote: > swat/lang/$ln/ is Andrew's opinion. For me, both are acceptable. > I think to fix it ASAP is important. Well, it's not actually crucial, so we can think over it yet later. At least we don't have to decide in rush. > >While I agree with you here, I'm also working on > >docs/docbook/configure.in and docs/docbook/Makefile.in files to > >automate generating of the html and man files from docs/docbook/$ln > >(pl here) directory. > > Does this mean you are creating a converter using awk, sed and other > standard stuffs? Nooo... Mostly, converting is already ready-to-use. Generating html, ps and pdf files can be done using sgmltools. About manpages, a perl script called by sgmlspl (or sth like that, I might miss the actual name) _and_ nsgmls parser is used here. What I'm doing is modifying the configure.in and related stuff to accomodate it to sgml sources in language subdirectories too (docbook/docs/ja for instance). Well ... maybe some sed cosmetics too ;-) We'll see ... (...) > > Anyway, > > >(a) > >docs/$ln/{html,manpages,faq,textdocs} makes easier extracting i18n'ed > >documentation in future and splitting it out as separated "packages" > > > >(b) > >docs/html/$ln, docs/manpages/$ln, docs/faq/$ln fits easier in current > >source tree > > For (a) and (b), I think (a) is better than (b). > And for (a), we can easily take a partial CVS commit right later. Yes, that's right. It's the biggest advantage of this solution I think. Oh, btw, polish parameter's labels in swat po files are under construction :) cheers, Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From monyo at samba.gr.jp Sat Sep 22 10:07:45 2001 From: monyo at samba.gr.jp (TAKAHASHI Motonobu) Date: Fri Feb 13 23:41:25 2004 Subject: Steps againt Nimba Worm In-Reply-To: <20010921045548F.monyo@home.monyo.com> References: <20010921045548F.monyo@home.monyo.com> Message-ID: <20010922190745K.monyo@home.monyo.com> Hello, SUGJ(Samba Users Group Japan) offers such information at http://www.samba.gr.jp/project/kb/J0/1/09.html This is the English version of it, Is it usefull? ----- Steps againt Nimba Worm for Samba Last Updated: 2001/09/22 Author: HASEGAWA Yohsuke Translator: TAKAHASHI Motonobu The information in this article applies to Samba 2.0.x Samba 2.2.x Windows 95/98/Me/NT/2000 SYMPTOMS This article has described the measure against Nimba Worm for Samba server. DESCRIPTION Nimba Worm is infected through the shared disk on a network besides Microsoft IIS, Internet Explorer and mailer of Outlook series. At this time, the worm copies itself by the name *.nws and *.eml on the shared disk, moreover, by the name of Riched20.dll in the folder where *.doc file is included. To prevent infection through the shared disk offered by Samba, set up as follows: ----- [global] ... veto files = /*.eml/*.nws/riched20.dll/ ----- Setting up "veto files" parameter, the matched files on the Samba server are completely hidden from the clients and become impossible to access them at all. In addition to it, the following setting are also pointed out by the samba-jp:09448 thread: when the "readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on a Samba server, it is visible only with "readme.txt" and a dangerous code may be performed when this file is double-clicked. Setting the following, ----- veto files = /*.{*}/ ----- no files having CLSID in its file extension can be accessed from any clients. This technical article is created based on the discussion of samba-jp:09448 and samba-jp:10900 threads. ----- TAKAHASHI, Motonobu(monyo) monyo@samba.gr.jp Personal - http://home.monyo.com/ Samba Team - http://samba.org/ Samba-JP - http://www.samba.gr.jp/ JWNTUG - http://www.jwntug.or.jp/ Analog-JP - http://www.jp.analog.cx/ MCSE+I, SCNA, CCNA, Turbo-CI From mimir at spin.ict.pwr.wroc.pl Wed Sep 26 10:45:12 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:25 2004 Subject: generating docs from DocBook sources (fwd) Message-ID: I've forgot to send it to samba-docs too. ---------- Forwarded message ---------- Date: Wed, 26 Sep 2001 12:43:45 +0200 (CEST) From: Rafal Szczesniak To: samba-technical@lists.samba.org Subject: Re: generating docs from DocBook sources On Wed, 26 Sep 2001, Rafal Szczesniak wrote: > What do you think about this? It's about docs/docbook/manpages > actually, but anything else from docbook sources will be concerned > (sooner or later). > > (1) Is it better to check with the ./configure script what files do we > actually have in docbook/manpages (note, that these may change as more > i18n languages may be supported as time goes) and on that basis > generate proper Makefile by substituting variable in Makefile.in > > or > > (2) to leave it as is, hardcoding further i18n files in Makefile.in > (just like it's done now). This may unneccessarily enlarge Makefile.in > as, after some period of time, it may contain paths to the same file > actually, but in 5 (just for instance) languages ! It sounds like a > kind of redundancy even if these paths would differ with lang > subdirectory name. > > Plese, tell me what do you think, because this affects my decision on > which patch to send. OK. I see no response, so, in the meanwhile, I'll provide a patch for the former case. Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From gcarter at valinux.com Wed Sep 26 15:24:50 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: yet another winbindd.8.sgml fix ? In-Reply-To: Message-ID: On Wed, 19 Sep 2001, Rafal Szczesniak wrote: > No problem, Jerry. Patches included. Also the small one fixing a typo > I've noticed in nmbd.8.sgml. applied. cheers, jerry From gcarter at valinux.com Wed Sep 26 15:27:57 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: ... again, another typo In-Reply-To: Message-ID: On Wed, 19 Sep 2001, Rafal Szczesniak wrote: > On Wed, 19 Sep 2001, Rafal Szczesniak wrote: > > > Hehe :) I've noticed another typo in wbinfo.1.sgml ;-) > > > > Will send proper patch... > > I'm doing as I said. Patch included. Jerry, I've cc'ed to you > because someone should apply it - I count on you here :) applied. jerry From gcarter at valinux.com Wed Sep 26 15:46:09 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010921045548F.monyo@home.monyo.com> Message-ID: Monyo, Sorry so late. I know this has already been commited. Glad to see things going forward. I've been a little tied up with other deadlines. (almost done). On Fri, 21 Sep 2001, TAKAHASHI Motonobu wrote: > To support SWAT i18n, we can determine where to put i18n documents in > the source archive. > > There are several kind of documents. > > 1. translation of swat/{help,images,included} > At samba-technical, I proposed swat/$ln/{help,images,included}. Makes sense to me. > Andrew Tridgell wrote: > >One request though - I think we should have a "lang" subdirectory for > >languages. For example the ja Samba currently uses /swat/ja/ for the > >Japanese SWAT templates, whereas I think we should probably use > >/swat/lang/ja. That will scale a little better when we eventually get > >dozens of languages in there. I agree. I will defer to your judgement in this manner. You have discussed things thoroughly with Tridge so I'm sure all the bases are covered. > 2. translation of docs/{html,text}docs and docs/manpages > > I know Jerry put the Polish SGML files under docbook dir, but for > installation we need only html and man page (and some text) files. > > We need to have docs of these formats because I think we should not > assume that DOCBOOK - html and man page converter is always > installed on the platform. > > docs/$ln/{htmldocs,manpages,faq,textdocs} or > docs/{htmldocs,manpages,faq,textdocs} are considerable? > > Of course there should be a discussion whether the Samba archive > includes these i18n'ed documentations as I mentioned before, but > we can discuss it later. Most of the current documentation distribution is designed around our current release process. I think we should split the docs out into a separate package with a separate (but corresponding release schedule). It makes no sense to install polish, japanese, and other languages for most systems (and vice versa). Any thoughts on this (i'm having serious deja-vu here). chers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From gcarter at valinux.com Wed Sep 26 15:47:41 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: Message-ID: On Thu, 20 Sep 2001, Rafal Szczesniak wrote: > (a) > docs/$ln/{html,manpages,faq,textdocs} makes easier extracting i18n'ed > documentation in future and splitting it out as separated "packages" > > (b) > docs/html/$ln, docs/manpages/$ln, docs/faq/$ln fits easier in current > source tree We can create a separate cvs module for docs alone and start over. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From gcarter at valinux.com Wed Sep 26 15:49:01 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010921131810B.monyo@home.monyo.com> Message-ID: On Fri, 21 Sep 2001, TAKAHASHI Motonobu wrote: > >(a) > >docs/$ln/{html,manpages,faq,textdocs} makes easier extracting i18n'ed > >documentation in future and splitting it out as separated "packages" > > > >(b) > >docs/html/$ln, docs/manpages/$ln, docs/faq/$ln fits easier in current > >source tree > > For (a) and (b), I think (a) is better than (b). > And for (a), we can easily take a partial CVS commit right later. Personally, I like (a) better. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From gcarter at valinux.com Wed Sep 26 16:00:32 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: Samba Troubleshooting Guide In-Reply-To: <95AE3CDB3543D511883A0020485B38B901252AD0@exna3.stratus.com> Message-ID: On Mon, 17 Sep 2001, Green, Paul wrote: > Since Samba is covered by the GPL, I have decided to apply the GNU > Documentation License to this material. I hope this is acceptable to > everyone; if not, I'd like to know what issues this creates for > people. > > Please see > ftp://ftp.stratus.com/pub/vos/customers/samba/SAMBA_Troubleshooting.rtf. > > Oh, and when you see the term "VOS", think "Unix" or "POSIX-compliant > OS". Since my target audience is VOS customers, I haven't attempted to > be generic...and this info is for Samba 2.0.7, which is the current > version we are using. Paul, I'll review this, but it will be week or so before I can get to it. Since it is based on Samba 2.0.x, maybe it would be a better idea to link it from samba.org (under the documentation page), rather than including it in the 2.2 distribution. What do you think about this. Thanks for putting time into this. Every one's contributions help. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From Paul.Green at stratus.com Wed Sep 26 16:05:31 2001 From: Paul.Green at stratus.com (Green, Paul) Date: Fri Feb 13 23:41:25 2004 Subject: Samba Troubleshooting Guide Message-ID: <95AE3CDB3543D511883A0020485B38B901252B99@exna3.stratus.com> You are quite welcome. I agree with your suggestion re placement. That will give people some time to give me feedback too. I do hope to port 2.2 at some point, but we're not ready yet. PG -----Original Message----- From: Gerald Carter [mailto:gcarter@valinux.com] Sent: Wednesday, September 26, 2001 12:01 PM To: Green, Paul Cc: Samba Documentation (E-mail) Subject: Re: Samba Troubleshooting Guide On Mon, 17 Sep 2001, Green, Paul wrote: > Since Samba is covered by the GPL, I have decided to apply the GNU > Documentation License to this material. I hope this is acceptable to > everyone; if not, I'd like to know what issues this creates for > people. > > Please see > ftp://ftp.stratus.com/pub/vos/customers/samba/SAMBA_Troubleshooting.rtf. > > Oh, and when you see the term "VOS", think "Unix" or "POSIX-compliant > OS". Since my target audience is VOS customers, I haven't attempted to > be generic...and this info is for Samba 2.0.7, which is the current > version we are using. Paul, I'll review this, but it will be week or so before I can get to it. Since it is based on Samba 2.0.x, maybe it would be a better idea to link it from samba.org (under the documentation page), rather than including it in the 2.2 distribution. What do you think about this. Thanks for putting time into this. Every one's contributions help. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- From gcarter at valinux.com Wed Sep 26 16:14:46 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: Samba Troubleshooting Guide In-Reply-To: <95AE3CDB3543D511883A0020485B38B901252B99@exna3.stratus.com> Message-ID: On Wed, 26 Sep 2001, Green, Paul wrote: > You are quite welcome. > > I agree with your suggestion re placement. That will give people some > time to give me feedback too. I do hope to port 2.2 at some point, > but we're not ready yet. ok. I'll add a link to your ftp server. This will make it easier for you to update it as you need. What do you want me to say about it? Samba 2.0.x troubleshooting information provided by Paul Green, Stratus Systems? cheers, jerry From Paul.Green at stratus.com Wed Sep 26 16:18:48 2001 From: Paul.Green at stratus.com (Green, Paul) Date: Fri Feb 13 23:41:25 2004 Subject: Samba Troubleshooting Guide Message-ID: <95AE3CDB3543D511883A0020485B38B901252B9A@exna3.stratus.com> Uh, let's leave the company name off...just my name. If you need an email address, please use Paul_Green@alum.mit.edu. Thanks PG -----Original Message----- From: Gerald Carter [mailto:gcarter@valinux.com] Sent: Wednesday, September 26, 2001 12:15 PM To: Green, Paul Cc: Samba Documentation (E-mail) Subject: RE: Samba Troubleshooting Guide On Wed, 26 Sep 2001, Green, Paul wrote: > You are quite welcome. > > I agree with your suggestion re placement. That will give people some > time to give me feedback too. I do hope to port 2.2 at some point, > but we're not ready yet. ok. I'll add a link to your ftp server. This will make it easier for you to update it as you need. What do you want me to say about it? Samba 2.0.x troubleshooting information provided by Paul Green, Stratus Systems? cheers, jerry From gcarter at valinux.com Wed Sep 26 16:22:41 2001 From: gcarter at valinux.com (Gerald Carter) Date: Fri Feb 13 23:41:25 2004 Subject: Samba Troubleshooting Guide In-Reply-To: <95AE3CDB3543D511883A0020485B38B901252B9A@exna3.stratus.com> Message-ID: On Wed, 26 Sep 2001, Green, Paul wrote: > Uh, let's leave the company name off...just my name. If you need an email > address, please use Paul_Green@alum.mit.edu. That's why I asked :-) WIll add this today. jerry From Ryan.Potter at Colorado.EDU Wed Sep 26 17:06:44 2001 From: Ryan.Potter at Colorado.EDU (Ryan Potter) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: Message-ID: Gerald, Could you please tell me how to get off of the Samba list? Thank you. ryan From monyo at samba.org Wed Sep 26 18:32:36 2001 From: monyo at samba.org (TAKAHASHI Motonobu) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: References: <20010921045548F.monyo@home.monyo.com> Message-ID: <20010927033236U.monyo@home.monyo.com> Gerald Carter wrote: >Monyo, > >Sorry so late. No problem :-) >Most of the current documentation distribution is designed around >our current release process. I think we should split the docs >out into a separate package with a separate (but corresponding >release schedule). It makes no sense to install polish, japanese, >and other languages for most systems (and vice versa). > >Any thoughts on this I agree, >(i'm having serious deja-vu here). And it's time to decide:-) 1. we should split the docs out into a separate archive. English documents is not seperated. 2. if we can, create a separate cvs module for docs alone and start over. 3. if we want to install i18n documents, we extract the i18n documents archive and put into docs/$ln/{htmldocs,manpages, ...} 4. install script automatically discover the docs/$ln if exists and install under them. ---- and outstanding matter... I think we do not need to include docbook source itself in the Samba archive. Or how we have the documents into CVS? ----- TAKAHASHI, Motonobu(monyo) monyo@samba.org Personal - http://home.monyo.com/ Samba Team - http://samba.org/ Samba-JP - http://www.samba.gr.jp/ JWNTUG - http://www.jwntug.or.jp/ Analog-JP - http://www.jp.analog.cx/ MCSE+I, SCNA, CCNA, Turbo-CI From mimir at spin.ict.pwr.wroc.pl Thu Sep 27 23:58:50 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010927033236U.monyo@home.monyo.com> Message-ID: On Thu, 27 Sep 2001, TAKAHASHI Motonobu wrote: > >Any thoughts on this > > I agree, > > >(i'm having serious deja-vu here). > > And it's time to decide:-) > > 1. we should split the docs out into a separate archive. > English documents is not seperated. > > 2. if we can, create a separate cvs module for docs alone and start > over. > > 3. if we want to install i18n documents, > we extract the i18n documents archive and put into > docs/$ln/{htmldocs,manpages, ...} Would it be performed by using a configure script to detect where actually to extract the files to or rather by simply copying what's needed by hand ? > 4. install script automatically discover the docs/$ln if exists and > install under them. err... I'm working on something similiar. Once it's done it should be fairly easy to port it to detection of separate docs/$ln packages. > I think we do not need to include docbook source itself in the Samba > archive. I think we don't need to include all of documentation, except manpages, in the archive. All of documents (with mentioned exception) should be put in a separate package. That's my personal feeling, but I'm debian user. > Or how we have the documents into CVS? good question. > TAKAHASHI, Motonobu(monyo) monyo@samba.org Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From monyo at samba.gr.jp Fri Sep 28 03:30:43 2001 From: monyo at samba.gr.jp (TAKAHASHI Motonobu) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: References: <20010927033236U.monyo@home.monyo.com> Message-ID: <20010928123043X.monyo@loire.u.coe.nttdata.co.jp> Rafal Szczesniak wrote: >> 3. if we want to install i18n documents, >> we extract the i18n documents archive and put into >> docs/$ln/{htmldocs,manpages, ...} > >Would it be performed by using a configure script to detect where >actually to extract the files to >or >rather by simply copying what's needed by hand ? copying by hand is enough, my image is ... %tar xzvf some/where/samba-3.x.x.tar.gz %cd samba-3.x.x/docs/lang %tar xzvf some/where/samba-3.x.x-docs-ja.tar.gz %cd ../../source %./configure ... --with-manlangs="ja" I hope --with-manlangs controls what language resources are installed with SWAT as well as manpages if we spefify --with-i18n-swat. >I think we don't need to include all of documentation, except >manpages, in the archive. All of documents (with mentioned exception) >should be put in a separate package. That's my personal feeling, but >I'm debian user. I do not agree with you. English manpages, html files used by SWAT and other docs are needed to include the basic archive. I guess you prefer to use manpages and I also usually use manpages, but other people will prefer to use HTML files via SWAT. SGML files are not needed to include, because we do not need SGML files to install Samba. ----- TAKAHASHI, Motonobu(monyo) monyo@samba.org Personal - http://home.monyo.com/ Samba Team - http://samba.org/ Samba-JP - http://www.samba.gr.jp/ JWNTUG - http://www.jwntug.or.jp/ Analog-JP - http://www.jp.analog.cx/ MCSE+I, SCNA, CCNA, Turbo-CI From mimir at spin.ict.pwr.wroc.pl Fri Sep 28 09:10:11 2001 From: mimir at spin.ict.pwr.wroc.pl (Rafal Szczesniak) Date: Fri Feb 13 23:41:25 2004 Subject: How to integrate i18n docs in HEAD branch In-Reply-To: <20010928123043X.monyo@loire.u.coe.nttdata.co.jp> Message-ID: On Fri, 28 Sep 2001, TAKAHASHI Motonobu wrote: > Rafal Szczesniak wrote: > >> 3. if we want to install i18n documents, > >> we extract the i18n documents archive and put into > >> docs/$ln/{htmldocs,manpages, ...} > > > >Would it be performed by using a configure script to detect where > >actually to extract the files to > >or > >rather by simply copying what's needed by hand ? > > copying by hand is enough, > my image is ... > > %tar xzvf some/where/samba-3.x.x.tar.gz > %cd samba-3.x.x/docs/lang > %tar xzvf some/where/samba-3.x.x-docs-ja.tar.gz > %cd ../../source > %./configure ... --with-manlangs="ja" > > I hope --with-manlangs controls what language resources are installed > with SWAT as well as manpages if we spefify --with-i18n-swat. It will do. > >I think we don't need to include all of documentation, except > >manpages, in the archive. All of documents (with mentioned exception) > >should be put in a separate package. That's my personal feeling, but > >I'm debian user. > > I do not agree with you. > English manpages, html files used by SWAT and other docs are needed to > include the basic archive. > I guess you prefer to use manpages and I also usually use manpages, > but other people will prefer to use HTML files via SWAT. I meant manpages by content, not by format. HTML man pages are to be installed as well as [ng]roff] ones. We could easily leave off the Samba HOWTO Collection, various textdocs, etc. > SGML files are not needed to include, because we do not need SGML > files to install Samba. right. > TAKAHASHI, Motonobu(monyo) monyo@samba.org Rafal 'Mimir' Szczesniak | *BSD, Linux and Samba / ______________________________________________________/ From davecb at canada.sun.com Fri Sep 28 11:57:47 2001 From: davecb at canada.sun.com (David Collier-Brown) Date: Fri Feb 13 23:41:25 2004 Subject: Default encrypted passwords = yes? References: <200109272222.f8RMMsd12165@toltec.metran.cx> <3BB45E2C.258181A4@canada.sun.com> Message-ID: <3BB465BB.A6B3B924@canada.sun.com> I mildly recommend users starting with non-encrypted passwords, but with a plan in mind for migrating to encrypted ones, especially if they plan to live in a world with NT fileserver or clients. Jay may recognize this approach from my comments about updating Using Samba (;-)) I'm tempted to suggest a different change in the defaults: to "update encrypted = yes", and to install an empty smbpasswd file as part of the normal installation process. This would allow the new Samba user to start with smbclient and/or with guest=ok, get her server working, get a few clients working, and only then start the process of switching over to encrypted passwords if she planned to use NT domains. This begs for a HOW-TO... --dave -- David Collier-Brown, | Always do right. This will gratify Americas Customer Engineering, | some people and astonish the rest. SunPS Integration Services. | -- Mark Twain (905) 415-2849 | davecb@canada.sun.com From johnkleven at yahoo.com Fri Sep 28 21:37:05 2001 From: johnkleven at yahoo.com (John Kleven) Date: Fri Feb 13 23:41:25 2004 Subject: New CIFS document Message-ID: <20010928213705.6972.qmail@web11204.mail.yahoo.com> If anyone has the time (or interest), I wrote a ~20 page CIFS document which explains the basics of the protocol. I was hoping to get any feedback (good and bad), and also just let people know it is out there because I wrote it to be read! There are two links below to the same document, one for HTML, the other PDF. HTML http://www.codefx.com/CIFS_Explained.htm PDF http://www.codefx.com/CIFS_Explained.pdf Thanks much - John Kleven __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com From jerry at samba.org Fri Sep 28 22:02:38 2001 From: jerry at samba.org (Gerald (Jerry) Carter) Date: Fri Feb 13 23:41:25 2004 Subject: New CIFS document In-Reply-To: <20010928213705.6972.qmail@web11204.mail.yahoo.com> Message-ID: On Fri, 28 Sep 2001, John Kleven wrote: > If anyone has the time (or interest), I wrote a ~20 > page CIFS document which explains the basics of the > protocol. I was hoping to get any feedback (good and > bad), and also just let people know it is out there > because I wrote it to be read! > > There are two links below to the same document, one > for HTML, the other PDF. Already had the link forwarded to me by Simo (our buglist maintainer). Have a opcy here on my disk and am planning on looking at sometime over the weekend. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca--