(Edit:Actually, that subject line should say samba-latest.tar.bz2)

Ok, I recently installed SuSE 8.2 Professional.

I did this:
linux:/etc # rpm -q samba
samba-2.2.7a-58
linux:/etc # rpm -e samba
error: removing these packages would break dependencies:
samba = 2.2.7a is needed by samba-vscan-0.3.2a-20
linux:/etc # rpm -e samba-vscan
linux:/etc # rpm -e samba
(note: i just happened to be in /etc. That has no bearing on the issue here.)

Then I:
linux:/etc # cd /home/bss1/download
linux:/home/bss1/download # tar xjvf samba-latest.tar.bz2
linux:/home/bss1/download # cd samba-3.0.0/source
linux:/home/bss1/download/samba-3.0.0/source # ./configure
linux:/home/bss1/download/samba-3.0.0/source # make
(Note: output omitted)
linux:/home/bss1/download/samba-3.0.0/source # make install
Using FLAGS = -g -O2 -Iinclude -I/home/bss1/download/samba-3.0.0/source/include -I/home/bss1/download/samba-3.0.0/source/ubiqx -I/home/bss1/download/samba-3.0.0/source/smbwrapper -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/home/bss1/download/samba-3.0.0/source
LIBS = -lcrypt -lresolv -lnsl -ldl
LDSHFLAGS = -shared
LDFLAGS =
Installing bin/smbd as /usr/local/samba/sbin/smbd
Installing bin/nmbd as /usr/local/samba/sbin/nmbd
Installing bin/swat as /usr/local/samba/sbin/swat
Installing bin/winbindd as /usr/local/samba/sbin/winbindd
======================================================================
The binaries are installed. You may restore the old binaries (if there
were any) using the command "make revert". You may uninstall the binaries
using the command "make uninstallbin" or "make uninstall" to uninstall
binaries, man pages and shell scripts.
======================================================================
Installing bin/smbclient as /usr/local/samba/bin/smbclient
Installing bin/net as /usr/local/samba/bin/net
Installing bin/smbspool as /usr/local/samba/bin/smbspool
Installing bin/testparm as /usr/local/samba/bin/testparm
Installing bin/testprns as /usr/local/samba/bin/testprns
Installing bin/smbstatus as /usr/local/samba/bin/smbstatus
Installing bin/smbcontrol as /usr/local/samba/bin/smbcontrol
Installing bin/smbtree as /usr/local/samba/bin/smbtree
Installing bin/tdbbackup as /usr/local/samba/bin/tdbbackup
Installing bin/nmblookup as /usr/local/samba/bin/nmblookup
Installing bin/pdbedit as /usr/local/samba/bin/pdbedit
Installing bin/smbpasswd as /usr/local/samba/bin/smbpasswd
etc...
(Note: remaining output omitted)

NOW... I saw in another thread where someone said samba was simple with SuSE, just go into YaST and select samba.
Well, before I did 'rpm -e samba', there was no samba selection anywhere in YaST2 that I could find.

-- And now that I've installed samba-3.0, how can I get access to it into YaST2?
-- How do I start smbd and nmbd? rcsmb and rcnmb are commands that are not found, even as 'su -'.
-- The command '/usr/local/samba/sbin/nmbd start && /usr/local/samba/sbin/smbd start' seemed to work (no errors) but I'm seeing NO indication that either is a process now.

Still searching .

Thanks...

"And now that I've installed samba-3.0, how can I get access to it into YaST2?"

YaST2 only works with rpm packages. Since you installed samba from a tarball then YaST2 never heard of it. I always convert my tarballs to rpm packages before I install them so that the package will be recorded in the rpm data base. I convert tarballs to rpm packages with checkinstall. The procedure is:
./configure
make
checkinstall
then install the resulting rpm package with rpm, kpackage, or YaST2 (which is the least convenient of the 3 ).

http://checkinstall.izto.org/

You can still convert samba into a rpm package and install it over top of the tarball samba. Then samba will be noticed by YaST2.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thanks for the info.

OK, so then checkinstall is not a part of SuSE, but is an app that needs to be downloaded and installed and put in the PATH. (Sorry, just thinking out loud.)

Is it an app that just about anybody with SuSE would need to get and use for the occasions where another app is not in an rpm format for SuSE?
In other words, is it in widespread use like, say, apt-get, is?
(I'm not comparing it to apt-get. I'm just wondering how popular it is.)

Thanks again...

"Is it an app that just about anybody with SuSE would need to get and use for the occasions where another app is not in an rpm format for SuSE?"

Many packages are distributed as tarballs. When you install a package from a tarball it is not recorded in the rpm data base. If you want to record the application in the rpm data base then you need to use checkinstall to change the tarball to a rpm. Fedora, Mandrake, Red Hat, and SuSE all use rpm. So with these distributions checkinstall is useful but not required to install tarballs.

"I'm just wondering how popular it is."

I don't know. checkinstall is popular enough that it is not going to die of neglect.

"an app that needs to be downloaded and installed and put in the PATH. "
Yes to needs to be downloaded and installed but it is installed in /usr/local/bin which is on your PATH. Try:
echo $PATH

Actually checkinstall is peculiar in that the best way to install it is to install it twice. First you have to install it as a tarball at which point checkinstall is fully functional. Then to record checkinstall in the rpm data base you install it a second time using checkinstall to create a checkinstall rpm package.

You can also use checkinstall to get rid of tarballs that you have installed with make install and now want to remove. The checkinstall web page explains how to do this.

checkinstall also advertises that it can create Debian and Slackware packages but I have never tried creating them with checkinstall.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites