Hi all, we have CentOS 3.3 running here on our Samba server. Problem is, that we need to mount samba shares on our Win2003 server. Is there a way to install (new) samba-3.1 rpms for CentOS 3.3? tia!
On 8/7/05, Support support@ev-theol.uni-bonn.de wrote:
Hi all, we have CentOS 3.3 running here on our Samba server. Problem is, that we need to mount samba shares on our Win2003 server. Is there a way to install (new) samba-3.1 rpms for CentOS 3.3? tia!
First I'd recommend upgrading to CentOS 3.5, as it has a number of security fixes not in 3.3. Second, and mostly for clarification, the samba 3.0.9 included with centos 3.5 works like a champ with win2003server. Is there any specific reason you need 3.1?
Lastly, yes you can install samba 3.1 rpms on the system, but this will break from RHEL3 compatibility and you won't get security updates for the 3.1 rpms unless you install those yourself also.
-- Jim Perrin System Administrator - UIT Ft Gordon & US Army Signal Center
On 7/8/05 16:52, Jim Perrin wrote:
First I'd recommend upgrading to CentOS 3.5, as it has a number of security fixes not in 3.3.
Does it? What's the difference between an up-to-date 3.3 installation and an up-to-date 3.5 installation? 3.3 is just a symlink to 3.5 on the mirrors, from what I can see.
Mike.
This message has been scanned for viruses by MailController - www.MailController.altohiway.com
Mike Zanker wrote:
On 7/8/05 16:52, Jim Perrin wrote:
First I'd recommend upgrading to CentOS 3.5, as it has a number of security fixes not in 3.3.
Does it? What's the difference between an up-to-date 3.3 installation and an up-to-date 3.5 installation? 3.3 is just a symlink to 3.5 on the mirrors, from what I can see.
It is two "minor releases" further. If /etc/redhat-release tells you, that you still have CentOS 3.3, then you haven't updated your system for close to 6 months - so a "fully patched" 3.3 cannot be "fully patched" - as it will become a 3.5 system just by running "yum update".
Besides the security updates RedHat sometimes also pushes functioniality upgrades with the minor releases.
Ralph
On Mon, 2005-08-08 at 10:12 +0200, Ralph Angenendt wrote:
Mike Zanker wrote:
On 7/8/05 16:52, Jim Perrin wrote:
First I'd recommend upgrading to CentOS 3.5, as it has a number of security fixes not in 3.3.
Does it? What's the difference between an up-to-date 3.3 installation and an up-to-date 3.5 installation? 3.3 is just a symlink to 3.5 on the mirrors, from what I can see.
That is correct ... the 3.1, 3.3, 3.4 all are pointing to 3.5 ... SO, if you maintain your system updated, you are at 3.5.
If you don't update your system, then there are many changes between 3.3 and 3.5.
It is two "minor releases" further. If /etc/redhat-release tells you, that you still have CentOS 3.3, then you haven't updated your system for close to 6 months - so a "fully patched" 3.3 cannot be "fully patched" - as it will become a 3.5 system just by running "yum update".
Right ... you can tell your version with the command:
cat /etc/redhat-release
Besides the security updates RedHat sometimes also pushes functioniality upgrades with the minor releases.
Ralph
This is another good time to point out that the real release is EL 3 (for the upstream provider) and CentOS 3 ... and that updates (if done) automatically move you to EL 3 Update 5 for the upstream provider and to CentOS-3.5.
Please see this FAQ answer concerning the version cycle for CentOS:
[ This is an indirect answer to your question that might be OT, but I feel I must make it. ]
On Sun, 2005-08-07 at 17:06 +0200, Support wrote:
Hi all, we have CentOS 3.3 running here on our Samba server. Problem is, that we need to mount samba shares on our Win2003 server. Is there a way to install (new) samba-3.1 rpms for CentOS 3.3? tia!
That opens a can of worms.
1. SMB mounts per-user, not per-system
SMB does not mount per-system, it mounts per-user. So anything you mount is tied to the user that mounted it.
2. SMB is Windows client native, not UNIX-like
The smbfs VFS "hack" in Linux (and virtually _no_ other UNIX) is not a pretty sight. Especially given the fact that mounting is a _kernel_ level operation. You do not want to put the stability of a server at the mercy of a non-native mount.
If at all possible, only use the "smbclient" function to transfer files from SMB shares, especially native SMB (at least Samba has some UNIX services).
- Consider Services for UNIX (SFU)
Alternatively, consider installing Services for UNIX (SFU) on your Windows Server 2003 system. That will give you: A. An NFS Service so you can mount "system-wide" (all users) B. An NIS Service to synchronize and map users/groups
The SFU NFS service will be far more native to your Linux client and allow multiple users to access files as themselves. It will also give a more formal way to synchronize Windows and UNIX users/groups.
- Automounter Recommended
BTW, I'd use the kernel automounter ("autofs" command, /etc/auto.* files) when mounting any other servers on a server system. That way the mounts are only made when the data is actually accessed (and disconnected after 30-300 seconds of inactivity).
-
Bryan J. Smith -
Jim Perrin -
Johnny Hughes -
Mike Zanker -
Ralph Angenendt -
Support