"shouldn't be necessary" ?

Kirk A Wolff kirk at braemarinc.com
Tue Apr 18 21:00:49 GMT 2000


See Line number 42 through 45.  This is from samba/source/README

----- Original Message -----
From: "Luke Kenneth Casson Leighton" <lkcl at samba.org>
To: "Multiple recipients of list SAMBA-NTDOM" <samba-ntdom at samba.org>
Sent: Monday, April 17, 2000 10:38 PM
Subject: Re: Works!


> On Mon, 17 Apr 2000, Kirk A Wolff wrote:
>
> > Thanks for all of the hard work!  I will reap all of the benefits with
much
> > joy!) j/k
> >
> > Like I said earlier, I am using this for my home network with
connectivity
> > via Amateur Radio (http://n0tia-uhf.ampr.org).  Now I can serve file
space
> > and internet access to the windows workstations roommates and neighbors!
> >
> > I have one suggestion though:  In your FAQ at
> > http://www.kneschke.de/projekte/samba_tng/faq/configuration.php3, tell
> > people to give the server a trust account also!  That way they won't
miss
> > that little statement in the samba/source/README!  I think that was why
I
> > couldn't get it to work all along (for the past week).
>
> shouldn't be necessary.
>


1:    Samba, The Next Generation.
2:    Sun Jan 2nd 2000.
3:    lkcl, samba team.
4:
5:    if you got this far, you probably obtained samba using cvs.  well
done.
6:    in order to maintain it, you will need to use cvs update, but
occasionally
7:    this will fail, and you will need to delete your cvs tree and start
again.
8:    instructions, in case it was a while since you last did that, are at
9:    http://samba.org/cvs.html.  remember to use SAMBA_TNG as the tag name.
10:
11:   there is also a FAQ, maintained by Lars Kneschke <lars at kneschke.de>,
at
12:   http://www.kneschke.de/projekte/samba_tng.
13:
14:    basic compilation and usage instructions.  the following are executed
at
15:    the unix prompt, if you hadn't already guessed.
16:
17:    ./configure
18:    make
19:    [make install]
20:
21:    to run samba, you will need:
22:
23:    bin/smbd
24:    bin/nmbd
25:
26:    if you are using any nt clients, running the following will change
the
27:    behaviour of the nt clients towards samba, which will improve the nt
28:    clients' reliability and performance:
29:
30:    bin/srvsvcd
31:    bin/wkssvcd
32:
33:    if you intend to operate samba with "encrypt passwords = yes",
34:    "update encrypted = yes" or "migrate passwords = yes", you will
35:    also need:
36:
37:    bin/lsarpcd
38:    bin/samrd
39:    bin/netlogond
40:    bin/winregd
41:
42:    you will also need to add your own samba server as a trust account.
43:    one way to do this, in the usual manner, is:
44:
45:    bin/smbpasswd -a -m your_samba_server_name
46:
47:    if you need NT-style printing:
48:
49:    bin/spoolssd
50:
51:    if you want to be able to start/stop services remotely (yes, dammit,
52:    you can only do this as root, you think i'm stupid????), you will
need,
53:    as well as your own rc.services script in /usr/local/samba/bin:
54:
55:    bin/svcctld
56:
57:
58:    i _really_ like this daemon architecture stuff.  if ever there's a
problem,
59:    or you want to upgrade one component, just kill the relevant daemon,
60:    NOT smbd and NOT any of the other services, and restart it.  i think
61:    that's just great :)
62:
63:
64:    Sun Jan 2nd 2000 (later on)
65:
66:    i liked the daemon architecture so much i decided to add it to cvs
main,
67:    or what is affectionately known as the SAMBA-3 tree.  what i added
was
68:    code that, instead of _always_ redirecting to the daemon architecture
69:    like in SAMBA_TNG, samba cvs main _attempts_ to redirect to the
daemon
70:    architecture.  if this fails, it will fall back to using the internal
71:    msrpc code.
72:
73:    so, if you want to use smbd file-services in cvs main, which are much
better,
74:    then simply run cvs main's smbd daemon instead of SAMBA_TNG's.




-------------- next part --------------
HTML attachment scrubbed and removed


More information about the samba-ntdom mailing list