SAMBA Anyone

[Bond007s]

I noticed in a small google mail that there was a message in the ROS-DEV mailing list that said there was a SAMBA TNG Win32 Port. It can be found here...

http://www.reactos.org/archives/public/ ... 01445.html

Now, Filip said that it was running when posted, this was in January of 2005, where could this port be found. I understand that it most likely is pretty primitive, however I would like to look at the sources and see if I can give any hand in that area. Could someone direct me to the right area, or atleast point me to a port in progress. Thank you ahead of time...

This message appears to answer many questions, however I would like to know if there is any progress in this area?

http://www.reactos.org/archives/public/ ... 01446.html


Anyway, again any help or updates in this area would be useful...Perhaps this would warrant others joining in...

[Jaix]

Well, I am not the best person to answer this but I too am very interested in this subject, here follows some info I have found concerning this.

http://leenux.org.uk/lpackham/smbclient/ This is a samba client for win32

and here is some info from ReactOS.org:
http://www.reactos.org/mlsearch/show.ph ... gmail.com>
http://www.reactos.org/mlsearch/show.ph ... @lkcl.net>
http://www.reactos.org/mlsearch/show.ph ... 0@phx.gbl>
http://www.reactos.org/mlsearch/show.ph ... 0@putte2k>
http://www.reactos.org/mlsearch/show.ph ... @volny.cz>
http://www.reactos.org/mlsearch/show.ph ... 0@phx.gbl>

My guess is that when 0.3 is released and the network layer is working the developers will probably direct some resources to SAMBA, it would be a natrural continuation of a network layer.
Another thing I think I have read is that we have got a partner in the SAMBA TNG team who will port it for us, someone could perhaps confirm/deny this info.

[BrandonTurner]

Elrond from IRC is working on SAMBA-TNG win32 port. Luke did a lot of work for a while and then disappeared.

[GreatLord]

Elron appper time to time in irc at #reactos channel and report to us how it goes, they have come pretty far. I can not go into detail. They got alot of part working fine in reactos and windows.

[MadRat]

Basic SAMBA support in ROS would be most excellent considering it would allow ROS to be the server side. Its easy to grab files from a Linux machine using SAMBA but I found it wasn't as easy grabbing files the opposite way - that is using the Linux machine to grab from a Windows share.

[Lucractius]

aboslutely. Samba with windows can be picky :/

my XP Pro box cant be accessed by the XP home box on my network, and samba on my FreeBSD box worked with it, but not RW, i could copy from XP Pro but not put files onto the Pro box and i dont think the XP Pro box can actualy deal with the FreeBSD samba serer either, havent used it in ages so cant remember... have to check after i update.

But samba is definatly something reactos needs implemented. If i remember correctly the Samba-TNG was only a new implementation of the domain controler though???

I would have figured that samba file & print sharing would be a more "useful" feature... but i can see the logic in aiming high with the domain controler first, seeing as the kinds of windows machines liscencing behind machines runing those is usualy fairly heavy.

[Ged]

Samba works very well with Windows, but it does need to be set up correctly. Any slight hickup in the config scripts can result in a strange outcome.

[Jaix]

Samba works very well with Windows, but it does need to be set up correctly. Any slight hickup in the setup config scripts can result is a strange outcome.

Well, we maybe should explain that Samba for for example

• AIX
  Debian
  Fedora
  IRIX
  Mandriva
  RedHat
  SuSE
  hp
  mvs
  novell
  solaris
  timestamp
  vms

is working good, but Samba for win32 does just exist as a development project under SAMBA-TNG and has no explorer plugin or fs driver yet, so we have to wait for it for a while. It will probably happen a lot in this area after ROS 0.3.0 is released.

[Floyd]

ooh! ReactOS domain controllers
(drool)

[MadRat]

Why emulate the AD beast when domains was so much simpler to comprehend?

[Mike]

Active Directory is excellent in large networks. However, domains are much easier in smaller networks

[MadRat]

It might sound blasphemous, but I'd rather manage NDS/eDirectory over AD any day of the week.

[Jaix]

It might sound blasphemous, but I'd rather manage NDS/eDirectory over AD any day of the week.

He is blaspheming, stone him! STONE HIM! stone him!
Always look at the bright side of life!

Well, anyway, we could use both, and in time we will probably have it. Or if it's possible to get from the SAMBA-TNG right away. Anyway, this will be so very cool!

[Headstrong]

It might sound blasphemous, but I'd rather manage NDS/eDirectory over AD any day of the week.

have you or anyone tryed installing the novell client on ROS ?

I know it would not work, but worth playing with if you have time


http://download.novell.com/SummaryFree. ... PKBIq2DPVI~

[Floyd]

Why emulate the AD beast when domains was so much simpler to comprehend?

either ADS (an implementation of LDAP) or NT4/SaMBa domains would work.

NT4 domain controllers work just fine even in an all XP environment, but i don't know if the SaMBa implementation would have the 40,000 items limit like NT4 did.

which in large networks would be hit rather quickly as that item limit was for user accounts, computer accounts and known printers; and it's not an artificial limit, it's basically around that number because when the SAM/registry gets to a certain size point NT becomes unstable. which is why MS "best practices" for NT4 said that it was a good idea for business to have 2 domains. one for users and machines, ie the "normal" domain and a domain for resources such as printers and other devices that had a one way trust to the "main" domain.

i actually prefer the simpler NT4 approach but ADS has its strong points too. however, whichever one React chooses to implement would be inconsquential with interoperability as long as MS maintains NT4 legacy emulation in their software.