FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=zfs-0.5.1 2010-09-08T19:38:56Z 2010-09-08T19:38:56Z Brian Behlendorf behlendorf1@llnl.gov 2010-09-04T20:26:23Z urn:sha1:6283f55ea1b91e680386388c17d14b89e344fa8d One of the neat tricks an autoconf style project is capable of is allow configurion/building in a directory other than the source directory. The major advantage to this is that you can build the project various different ways while making changes in a single source tree. For example, this project is designed to work on various different Linux distributions each of which work slightly differently. This means that changes need to verified on each of those supported distributions perferably before the change is committed to the public git repo. Using nfs and custom build directories makes this much easier. I now have a single source tree in nfs mounted on several different systems each running a supported distribution. When I make a change to the source base I suspect may break things I can concurrently build from the same source on all the systems each in their own subdirectory. wget -c http://github.com/downloads/behlendorf/zfs/zfs-x.y.z.tar.gz tar -xzf zfs-x.y.z.tar.gz cd zfs-x-y-z ------------------------- run concurrently ---------------------- <ubuntu system> <fedora system> <debian system> <rhel6 system> mkdir ubuntu mkdir fedora mkdir debian mkdir rhel6 cd ubuntu cd fedora cd debian cd rhel6 ../configure ../configure ../configure ../configure make make make make make check make check make check make check This change also moves many of the include headers from individual incude/sys directories under the modules directory in to a single top level include directory. This has the advantage of making the build rules cleaner and logically it makes a bit more sense. 2010-08-31T20:42:02Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T19:28:14Z urn:sha1:e70e591c51177d202396b1b0c5de04a7664d45cf Add the initial products from autogen.sh. These products will be updated incrementally after this point as development occurs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:42:01Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:57:29Z urn:sha1:9b020fd97a3dc449a94baec028b30b1fe3c2d5bc This topic branch contains required changes to the user space utilities to allow them to integrate cleanly with Linux. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:42:00Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:56:53Z urn:sha1:d603ed6c278f9c25b17ba8e75e9bce6e5d715ac0 This topic branch contains all the changes needed to integrate the user side zfs tools with Linux style devices. Primarily this includes fixing up the Solaris libefi library to be Linux friendly, and integrating with the libblkid library which is provided by e2fsprogs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:42:00Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:55:32Z urn:sha1:f1fb119f6bb0c3185ec88912e4488fdd9ec08ab2 Track various large hunks which have been dropped simply because they are not relevant to this port. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:42:00Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:55:19Z urn:sha1:6b003d7cda153c58bb5faab62c5e5a7aab780715 Solaris recently introduced the idea of drive topology because where a drive is located does matter. I have already handled this with udev/blkid integration under Linux so I'm hopeful this case can simply be removed but for now I've just stubbed out what is needed in libspl and commented out the rest here. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:41:59Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:54:51Z urn:sha1:054bc00b4c0c257f6baf6d7145b270c7283fe51e Resolve minor Linux compatibility issues. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:41:59Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:52:05Z urn:sha1:9c905c550bb9cb095a5d9707bc7cf72d3f2562af The upstream ZFS code has correctly moved to a faster native sha2 implementation. Unfortunately, under Linux that's going to be a little problematic so we revert the code to the more portable version contained in earlier ZFS releases. Using the native sha2 implementation in Linux is possible but the API is slightly different in kernel version user space depending on which libraries are used. Ideally, we need a fast implementation of SHA256 which builds as part of ZFS this shouldn't be that hard to do but it will take some effort. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:41:50Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:44:39Z urn:sha1:325f023544bbec6a478882c442e15304ee379759 This branch contains the majority of the changes required to cleanly intergrate with Linux style special devices (/dev/zfs). Mainly this means dropping all the Solaris style callbacks and replacing them with the Linux equivilants. This patch also adds the onexit infrastructure needed to track some minimal state between ioctls. Under Linux it would be easy to do this simply using the file->private_data. But under Solaris they apparent need to pass the file descriptor as part of the ioctl data and then perform a lookup in the kernel. Once again to keep code change to a minimum I've implemented the Solaris solution. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> 2010-08-31T20:41:50Z Brian Behlendorf behlendorf1@llnl.gov 2010-08-26T18:43:58Z urn:sha1:2eadf037f5ae2735bcbc61e3bb2974c6d3235b8e Use mount entry if HAVE_SETMNTENT defined Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>