From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Samuel Subject: Re: HP opensourced advfs from tru64 and what it means for btrfs Date: Tue, 24 Jun 2008 23:50:17 +1000 Message-ID: <200806242350.19802.chris@csamuel.org> References: <20080623145026.GA13310@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1388351.RbNGPbO485"; protocol="application/pgp-signature"; micalg=pgp-sha1 To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: <20080623145026.GA13310@2ka.mipt.ru> List-ID: --nextPart1388351.RbNGPbO485 Content-Type: text/plain; charset="ansi_x3.4-1968" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 24 Jun 2008, Evgeniy Polyakov wrote: > Sure it is interesting as studing anything new, but there is nothing in > advfs which can prevent btrfs from success. Virtually nothing. As Bdale commented on the LWN article: http://lwn.net/Articles/287108/ # While it would be fine with HP if someone wants to "port" AdvFS to Linux # or any other operating system with a GPLv2 compatible license, this # contribution is not intended to "compete" with other existing file system # projects underway in and around the kernel.org development community. = =20 #=20 # Rather, our hope is that the algorithms, design documentation, and test # suite now available at the AdvFS site... and the active participation of # HP engineers in various open-source file system projects who have lots of # AdvFS experience... will help to accelerate the inclusion of AdvFS-like # enterprise features and capabilities in next-generation file systems for # Linux. =20 NB: Asides from briefly using AdvFS under OSF/1 back in the mid-90's I've=20 no other link to it or HP. =2D-=20 Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. =46or more info see: http://en.wikipedia.org/wiki/OpenPGP --nextPart1388351.RbNGPbO485 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUASGD7m41yjaOTJg85AQL5hwf+PUnHL9UA62ztg/LOlyBS8tev9qmk5n8G iDe9mmq1ZwOuXsYAyM9CL22VjH+I2C4b0hEEOejFrjlzKWkNDQx/FE+w9vQ3AqRy mGSY9KApLZ+QbTjmIM9OblV/D/9AoKDkJSrRdpq4Jna62bBeJ36hyoIe7ucVO2hM D4ORQu/VGcUTXoksXVWvK9tgt2cGt3k1SsrFwBJrKm5Kitb2SpEtwhklRZBr+jVu JmI1jEcXx07wmPROEjkbo3ONi9VUXY05ksU6c4n3yzWDsmppR19+43R5D8IADGI1 z7bKSS+twBZy8CEpyZ3iIO7RCixBSYJxJdxGw9DSsYu0POVrCypMTQ== =3K+k -----END PGP SIGNATURE----- --nextPart1388351.RbNGPbO485--