| |||||||||||||
Releasing Samba 4Releasing Samba 4Posted Dec 2, 2011 0:43 UTC (Fri) by ras (subscriber, #33059)In reply to: Releasing Samba 4 by abartlet Parent article: Releasing Samba 4
> 16MB of flash or RAM is still very small.
16Mb of flash and 64Mb of RAM is typical. There is always more RAM than flash a new image can be downloaded to RAM, then burnt into flash. Embedded systems of this size running CIFS and Windows printer servers are very common. In fact vendors are now starting to drop their home brew solutions and base their stock firmware on OpenWrt, which is very pleasing to see. It means manufacturers like Broadcom and Atheros are being dragged into the open source world.
Anyway, my point is there are now substantial revenue streams dependent on Samba running on these devices. That means regardless of what the Samba development team decides, one of two things will happen: either Samba v4.0 runs on these devices or Samba will be be forked into v4 and v3 streams.
(Log in to post comments)
Releasing Samba 4 Posted Dec 2, 2011 1:04 UTC (Fri) by abartlet (subscriber, #3928) [Link]
> Anyway, my point is there are now substantial revenue streams dependent on Samba running on these devices. That means regardless of what the Samba development team decides, one of two things will happen: either Samba v4.0 runs on these devices or Samba will be be forked into v4 and v3 streams.
If Samba operates on these devices now, then it will continue to operate. Even the previous build system is being kept for now. However, when we are able to make a release with the new 'waf' build system, the job of fitting Samba into embedded devices will get much easier, due to internal shared libraries.
The AD support is surprisingly small, but there will also be the ability to not to install it
|
|||||||||||||