![]() Its use of a standard ZFS on-disk format is therefore binary compatible with ZFS on other platforms that support version 28 or greater. GreenBytes ZEVO Community Edition 1.1.1 is based on ZFS pool version 28 and ZFS file system (zpl) version 5. Yes, if you specify a pool version at the time of creation of the pool: Versions less than 5000 can not use feature flags.Īre storage pools created by OpenZFS compatible with ZEVO and with Oracle® Solaris? Just one pool version is associated with feature flags: version 5000. To maintain compatibility, new feature flags are usually ported to all operating systems very quickly. This may be appropriate if you expect to use the pool with a different implementation that does not support the feature. You can disable a feature flag for a pool when the pool is created. Pools can be moved freely between different implementations of OpenZFS wherever the implementations support the same feature flags. Learning other processes and interacting with multiple communities would be a hurdle to development.Ĭompatibility Are storage pools created by OpenZFS portable between operating systems? Most developers are only familiar with the integration process for their operating system of choice. ![]() For example OpenZFS on illumos must follow the illumos integration process because it is part of the larger illumos operating system repository. Each implementation has its own process for integrating changes, some of which cannot be changed.Most developers are only familiar with kernel development on their operating system of choice, so this would be a huge hurdle to development. Every developer would have the burden of testing changes for four different operating systems.There are several reasons we do not want a single repository to support all operating systems: Every implementation would port changes from this central repository instead of searching the commit history of the other implementations. Developers from any implementation could then easily install and test platform-independent changes in that central repository. ![]() We want to simplify the sharing of code between implementations by having a platform-independent central repository that runs as a userland process on any operating system. One of the goals of OpenZFS is to simplify this porting process.Īre there plans to merge the different repositories? Each implementation regularly ports platform-independent changes from the other implementations. Even though the core of OpenZFS is platform-independent, there are a significant number of platform-specific changes need to be maintained for the parts of ZFS which interact with the rest of the operating system (VFS, memory management, disk i/o, etc.).Īre new features and improvements shared between the different repositories? OpenZFS brings together developers from multiple open-source forks of the original ZFS project from OpenSolaris to help ensure the compatibility and quality of all of our implementations.ĭevelopment Model Why are there four different repositories?Įach repository supports a different operating system. Yes, the OpenZFS community has a code of conduct. General Does OpenZFS have a Code of Conduct?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |