After upgrading a test machine to Sernet's 3.4 package, it looks like
the net command is gone. This was definitely there in the
redhat-supplied 3.0 build and I thought it was there in sernet's 3.3
build too. I installed all the rpm's - samba3-client, samba3-utils,
samba3-cifsmount am I
On Fri, Jul 10, 2009 at 02:10:24PM -0700, Adam Cohen wrote:
After upgrading a test machine to Sernet's 3.4 package, it looks like
the net command is gone. This was definitely there in the
redhat-supplied 3.0 build and I thought it was there in sernet's 3.3
build too. I installed all
Hi,
Adam Cohen wrote:
After upgrading a test machine to Sernet's 3.4 package, it looks like
the net command is gone. This was definitely there in the
redhat-supplied 3.0 build and I thought it was there in sernet's 3.3
build too. I installed all the rpm's - samba3-client, samba3-utils,
# yum list | grep samba3
samba3.i3863.4.0-40.el5 installed
samba3.x86_64 3.4.0-40.el5 installed
samba3-client.i386 3.4.0-40.el5 installed
samba3-client.x86_64 3.4.0-40.el5 installed
samba3-utils.i386
# yum list | grep samba3
samba3.i3863.4.0-40.el5 installed
samba3.x86_64 3.4.0-40.el5 installed
samba3-client.i386 3.4.0-40.el5 installed
samba3-client.x86_64 3.4.0-40.el5 installed
samba3-utils.i386
After upgrading a test machine to Sernet's 3.4 package, it looks like
the net command is gone.
I am using that same Sernet package (i386 version) and the net command
is working perfectly here.
--
To unsubscribe from this list go to the following URL and read the
instructions:
True. It looks like something went wrong in my first install of
samba3-client. I ran a reinstall and the binary is there and working
correctly.
samba3-client conflicted with samba-common 3.0.33 provided by RHEL. I
removed that package first to resolve the conflict. It's possible that
is
