Language Selection

English French German Italian Portuguese Spanish

M$ To Clone Open Source

Filed under
Microsoft

If imitation is the sincerest form of flattery, developer of the open source fire transfer tool rsync, Andrew 'Tridge' Tridgell has every reason to smile as Microsoft announced a similar utility will feature in the next Windows server release.

Speaking at this year's TechEd conference on the Gold Coast on Wednesday, Redmond-based Windows Server group director Iain McDonald said the next update of Windows Server 2003, dubbed "R2", will reduce bandwidth for file transfers for organizations with many branch offices.

"There is new functionality we wanted to be able to provide to you in R2," McDonald said. "First of all there is a bunch of stuff for branches. In the US there are new regulations about what [organizations] have to do on branches, what they have to keep around over longer terms. We had a look at that and in discussions we knew one of the big things was 'let's minimize the amount of bandwidth that stuff takes to get into a central location'."

To achieve this, Microsoft will introduce DFSR, or Distributed File System Replication, with R2, which is due for release later this year.

Full Story.

More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more