Revisiting this...

I notice there is both samba 3.5 and 4.0rc4 available.

My ClearOS server is running samba-3.6.22, and I have not updated it in months, so I don't know what they are up to, but appearently this works for me.

Centos6 (i386) provides samba-3.6.9, where as RSEL6 has samba-3.5.6; both have the 4.0rc4.

so.....

Do I stay with Samba 3, but drop down to 3.5 or plead that this gets updated?

Or do I give samba4 a shot?

I run an NT domain controller and only have XP clients right now. At some point I am going to have to start supporting Win7, and don't know what that will take. Will I be forced to move to AD?

I won't be doing much for a few weeks; no hurry, but I do want to do this. I will save 2KWH/day by going with arm over intel.

It might be that going with samba4 will work for what I have now, and I can experiment with what it will take to upgrade for Win7 support?

BTW, I looked over at sernet, but they do not have a Centos6 arm repo :)



On 08/25/2014 04:28 PM, Gordan Bobic wrote:
On 2014-08-25 03:36, Robert Moskowitz wrote:
I am running my home Windows server on ClearOS, with minimal apps.
Currently all 3 of my clients are XP, but I should be looking at Win7
replacements (though I could just do the POS setting change and stay
with XP for a number of years, given how little we do anything with
the Windows systems).

I have roaming profiles for XP.  It works.

What I am thinking is that I SHOULD just be able to lift the samba
config files onto Redsleeve and have a working server without all of
the ClearOS tools.  This should hold me for a couple years more (I
built the ClearOS server 2 years ago) until more things develop both
with MS and with arm Centos.

Advice?

The same samba configs you currently use should work just fine.

Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users


_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to