ReactOS Forum

vicmarcal wrote:

hbelusca wrote:Nope. And nobody so far works on it...

Ein?Nobody works in 0.4?
Gigaherz is pushing explorer-new...
ThFabba is fixing the CC...
Zefklop is fixing the MM...
GonzoMd is preparing the new Community design...
I see at least 4 working for the 0.4...

I meant, working on SAMBA

Where's the source (for windows/reactos) for smb-tng, and should it be brought into the reactos svn repo now?

As far as I can tell, there's been very little action on the projects side for a few years, so I think we might need to become the principal maintainers (and if it's in the codebase, fs drivers are more likely to be hacked upon... by me).

I was thinking along similar lines myself. Samba-TNG seems to not have any work done on it in several years. And, near as I can tell, it needs to be brought in pretty close to the OS core to enable functionality like mapped drives, active directory authentication, etc. Seems like folding it in (after the initial headache) would be the most reasonable course of action. If possible, it could still be maintained as a more-or-less standalone library as well...?

Not that I'm one who would be working on it, but figured I'd throw my 2 cents in.

And, near as I can tell, it needs to be brought in pretty close to the OS core to enable functionality like mapped drives, active directory authentication, etc.

ReactOS really does network drive functionality.

Huh?!

karlexceed wrote:Huh?!

I assume he means "needs"

I assume he means "needs"

You right! I was typing this in a hurry.

karlexceed wrote:I was thinking along similar lines myself. Samba-TNG seems to not have any work done on it in several years. And, near as I can tell, it needs to be brought in pretty close to the OS core to enable functionality like mapped drives, active directory authentication, etc. Seems like folding it in (after the initial headache) would be the most reasonable course of action. If possible, it could still be maintained as a more-or-less standalone library as well...?

Not that I'm one who would be working on it, but figured I'd throw my 2 cents in.

"folding in" this particular Samba derivative doesn't seem to make sense as it's so old. It would be better to adapt a more current version of Samba, both server and client components. It'll be a mammoth task, both on the ReactOS side and the Samba side.

karlexceed wrote: And, near as I can tell, it needs to be brought in pretty close to the OS core to enable functionality like mapped drives, active directory authentication, etc

mapped drives (IFS) are not supported in Reactos at the moment,
but samba-TNG contain all the API to access to network drivers including authentication.

At this time sambaTNG is a collection of command line tools but there are'nt tecnical problem to write a gui for the client.

And when the new explorer arrive trasform this to virtual folder plug-in is not really difficult.

So integrating smb in this way will not provide support for mapped drive,
and is'nt the right way to integrate it but can be use to access network disks from explorer.

It's not really an integration, it does'nt provide the possibility to share files from reactos,
but it will be very useful to access other machine and install software on real hardware (or VM)
without burn cds or attach the hard disk to another pc.

hbelusca wrote:Nope. And nobody so far works on it...

EDIT (after vicmarcal's comment): "nobody so far works on SAMBA integration"
EDIT 2: About ROS 0.4 release: when devs will be happy with its stability, after explorer_new merging and other things vicmarcal mentioned in his answer.

Better use quotes next time.