Linked by Rahul on Fri 31st Oct 2008 16:12 UTC
Linux InternetNews talks to developers and vendors about the rise of Btrfs as a successor to Ext4. Though Ext4 adds extents, Chris Mason, Btrfs developer noted that BTRFS adds a number of other features beyond that. Among those features are items like snapshotting, online file consistency checks and the ability to perform fast incremental backups. BTRFS (pronounced better FS) is currently under development in an effort led by Oracle engineer Chris Mason. With the support of Intel, Red Hat, HP, IBM, BTRFS could become the engine that brings next generation filesystem capabilities to Linux.
Thread beginning with comment 335948
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: ZFS
by PlatformAgnostic on Sat 1st Nov 2008 10:35 UTC in reply to "RE: ZFS"
PlatformAgnostic
Member since:
2006-01-02

Just a note on Windows TCP/IP: It's not related to any BSD or other networking stack out there. There has never been any BSD code in the networking stack in any eternally released and commonly used versions of Windows.

Reply Parent Score: 2

RE[3]: ZFS
by Detlef Niehof on Sat 1st Nov 2008 11:34 in reply to "RE[2]: ZFS"
Detlef Niehof Member since:
2006-05-02

(...) There has never been any BSD code in the networking stack in any eternally released and commonly used versions of Windows.


Interesting information. I believe you mean "externally" instead of "eternally", right? Any idea how this myth (that Windows contained BSD networking code) came about?

Reply Parent Score: 1

RE[4]: ZFS
by ba1l on Sat 1st Nov 2008 12:33 in reply to "RE[3]: ZFS"
ba1l Member since:
2007-09-08

Most of the command-line network tools that come with Windows were derived from BSD versions. So utilities like ping, traceroute, nslookup, telnet, and so forth. That's the only trace of any BSD code in the network stack of current Windows versions.

Apparently, these were originally provided by a company called Spider Systems, and were ported by Microsoft to use the Winsock API instead of the BSD sockets API.

That same company also provided the initial TCP/IP stack used in Windows NT 3.0. Apparently, this stack was basically parts of the BSD TCP/IP stack, ported to run on top of an abstraction layer. Microsoft incorporated that into NT 3.0, because they decided to include TCP/IP support far too late to develop their own.

They did develop their own before NT 3.5 was released, and that one was in use up to Windows XP. Windows Vista contains yet another new TCP/IP stack.

It's not really a myth - one version of Windows NT certainly did contain BSD network code, but it's since been replaced. Twice. There might be some remnants of it, since there's little point in throwing out working, well-tested code, but there's no way to know without looking at the source code.

Reply Parent Score: 3

RE[4]: ZFS
by PlatformAgnostic on Sat 1st Nov 2008 14:29 in reply to "RE[3]: ZFS"
PlatformAgnostic Member since:
2006-01-02

Yeah.. there's a pretty detailed description of it at http://www.kuro5hin.org/?op=displaystory;sid=2001/6/19/05641/7357.

The basic gist is that in pre-release versions of NT, some BSD code may have been used in boot-strapping the networking effort. This code was accessed through a wrapper which is now long-disused (and probably not even present anymore) and was entirely replaced in NT 3.5, the first externally (eternally, even) released NT, by a significantly different Microsoft stack.

Some of the userland network tools are ported bsd code (command line ftp being an example), so maybe that's the source of this rumor.

Reply Parent Score: 2