In a message dated 10/24/2002 8:51:22 AM Mountain Daylight Time,
[EMAIL PROTECTED] writes:
> Dave,
>
> Some of the binaries get put into /usr/bin, and others in /usr/sbin. The
> ones in /usr/bin are ones that non-root users might have a reason to
> execute, such as smbclient, smbpasswd, etc. /usr/sbin will not be in their
> $PATH, and so won't be found. The ones that go into /usr/sbin would be
> things like nmbd, smbd, swat, etc.
>
> During the "make install" process, Samba will detect existing module names,
> and rename them to .old. So no, the fact that the binaries were already in
> one place would not be the reason they got installed in /usr/bin.
>
> Mark Post
>
Thanks for the explanation.
Looks like I have some more investigative work to do then,
because the smbd, swat and nmbd were installed into /usr/bin.
I used the SuSE specfile from 2.2.0. (see below)
Can you tell me how to view the spec for the latest SuSE rpm?
Do I have to have the rpm source to do this...or is there an rpm
command that can display this?
LIBS=-lnsl CFLAGS="-Wall -g -D_GNU_SOURCE -D_LARGEFILE64_SOURCE" \
./configure --prefix=/usr --libdir=/etc \
--with-privatedir=/etc --localstatedir=/var/lock/samba \
--with-codepagedir=/usr/lib/samba/codepages \
--sbindir=/usr/sbin --with-pam \
--with-smbmount --with-automount --with-vfs \
--with-quotas \
--with-profile --with-msdfs \
--mandir=/usr/share/man \
--with-swatdir=/usr/lib/samba/swat \
--with-sambabook=/usr/lib/samba/swat/using_samba
