*** ilovezfs_ sets a ban on 16:41] *** ChanServ takes channel operator privileges from ilovezfs_. *** ChanServ gives channel operator privileges to ilovezfs_. I was hoping to get a little bit more appreciation for introducing a wider audience to the ZFS effort. Users who are interested in a -devel port are IMHO much more likely to know the potential risks of running without that additional safety net (= in a pre-SIP configuration). I don't think this kind of port will mean much to most users who are better off with SIP. In other words, that concerns only 10.11, and it should be perfectly possible to find a way around this, like reaping the kexts off an upstream DMG in the non-devel port, or a co-maintainer with the possibility to sign the kexts (on the 10.11+ buildbots).Įdit 2 : OSXFuse also snatches the to-be-signed bits from an official installer. Question: is there a phase where one could check if either of the kexts is loaded, and raise an error if that is the case (pre-deactivate would be perfect)?Įxplanation for this request from a single upstream dev who may or may not be voicing the majority opinion: SIP. As a result it should PROBABLY NOT be deactivated, uninstalled or reinstalled without taking the following precautions:ġ) unmount (export) all ZFS datasets and pools This port installs kernel extensions which get loaded automatically when using ZFS. On the other hand, the MacPorts version should be less intrusive/invasive and easier to uninstall. In fact, I'd (almost) suggest to use an official installer from the project's website instead of using port:zfs, because that should give better system integration "out of the box".There's a port:zfs but I would strongly suggest to test port:zfs-devel. This is a project that's seeing active development and continuous improvement.amount used by ARC (not related to ObjC's ARC )) On systems with <8Gb it might be wise to read up on reducing the max. ZFS does tend to like having sufficient memory.I suspect it might be necessary to put the kernel stuff into /Library when SIP is not disabled (?) I'd be very interested in feedback from users on more recent versions of OS X, notably 10.11. That works fine on OS X 10.9 (with a single warning when loading eacho of the kexts the 1st time). The current implementation installs everything properly into $, kernel extensions included. I already tested an earlier release from an officialy installer on Bradley's (pixilla) VM about a year ago, using it to put a whole MacPorts install in a dataset mounted on /opt/local, with compression, case sensitivity and redundancy for important parts like the registry. *) even when using a single partition because it can write each file in multiple copies - a feature that prevented me from losing no more than a single trivial file from my Linux rig when a disk started dropping sectors on me at a rate I never saw before a few days ago. It also offers optional on-the-fly compression including using the lz4 scheme which is fast enough to improve I/O to slow media (time spent de/compressing is less than the increase in data transfer times). It provides very high data reliability (*), is extremely flexible & scalable and has a potential for very good performance (though not necessarily trivial and probably not yet in the OS X implementation). I don't think I have to introduce ZFS here, but for those who really don't know what it is: It's the filesystem that Apple once considered as an officially supported FS, if not the default for OS X. I've finally gotten around to making a port for the OS X implementation of the ZFS filesystem, now that it seems to have reached a sufficient maturity (read: it no longer causes system instability after having done a few simple tests).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |