Sometimes these things turn into just another layer of non-information.
I understand your concern.
The first of the three goals of OpenZFS is to raise awareness of the quality, utility, and availability of open source implementations of ZFS. As an end user, very much into awareness-raising of ZFS, I'll occasionally edit (and/or discuss in IRC) wherever I feel that the value of something thats in the wiki is not immediately clear. But I'm neither a developer nor a typical end user, so there'll be large areas that are beyond me. Maximising the value of contributions to the wiki should be very much a collaborative effort...
Whilst over the years computers have grown more compact, and display sizes are varied without argument, there remains widespread majority preference for one aspect: the 'normal' proportions of a keyboard.
The squashed keyboards/keypads on mobile/handheld devices and on Eee PC may be useful, but they're not as useful, easy or widely-appreciated as a normal-sized keyboard.
For devices with squashed or no keyboards: there exist, as peripherals, plenty of normal-size projected or peripheral foldaway/fabric keyboards.
For devices with normal keyboards: I know no-one who prefers to use a sqaushed peripheral alternative (though there are probably very rare cases when people do so).
Why use an inferior tool (squashed keyboard) for learning --which is what the XO and OLPC are all about -- if it's near-inevitable that sooner or later, you'll require additional learning -- to use a device that truly fits one's fingers whilst typing)? As you learn through doing so I can't view Eee PC as an ideal device for learners.
Don't misunderstand me: I'm not disrespecting the Eee PC in itself. A colleague has one, and he loves it, and I realise its usefulness, but the keyboard is peculiarly small and I can't view Eee PC hardware as a recommended substitute for XO.
For myself, and for colleagues who have NeoOffice or OpenOffice.org installed (that's nearly everyone in our Centre):
* always, ODF.
When choices become limited to DOC or PDF (typically, in a web/instutitional context):
* PDF
When there's no other option (rarely):
* DOC
The most recent Microsoft Office 2004 for Mac OS can't handle Microsoft's most recent formats without converting to RTF. There may be numerous excuses and technical reasons for these delays but ultimately, it's unacceptable. What are Microsoft doing with their millions/billions? Haven't they had over twenty years to get things right with MS Office?
Slashdot Mirror
hope that this nice umbrella will evolve into a single point of access
If you find time, I recommend listening to bsdtalk227 (listed under Publications ).
https://twitter.com/grahamperrin/status/380395699734466560 quoting plus hashtag from a Delphix blog: " To some degree, #OpenZFS is just putting a name to what we have already been doing as a community ".
Sometimes these things turn into just another layer of non-information.
I understand your concern.
The first of the three goals of OpenZFS is to raise awareness of the quality, utility, and availability of open source implementations of ZFS. As an end user, very much into awareness-raising of ZFS, I'll occasionally edit (and/or discuss in IRC) wherever I feel that the value of something thats in the wiki is not immediately clear. But I'm neither a developer nor a typical end user, so there'll be large areas that are beyond me. Maximising the value of contributions to the wiki should be very much a collaborative effort...
https://github.com/zfsrogue/zfs-crypto
In the ZFSonLinux area at https://github.com/zfsonlinux/zfs/issues/494#issuecomment-23652335 it's noted that the zfsrogue code is encumbered and so, will not be used.
There's an earlier comment https://github.com/zfsonlinux/zfs/issues/494#issuecomment-7158618 and a corresponding note in the OpenZFS wiki: The early ZFS encryption code published in the zfs-crypto repository of OpenSolaris.org could be a starting point
Three items that may be of interest:
* A short history of btrfs [LWN.net] (2009) (highlights)
* How ZFS continues to be better than btrfs — Rudd-O.com in English (2012) (highlights)
* Btrfs & ZFS, the good, the bad, and some differences. | www | grep storage (2013)
http://open-zfs.org/wiki/Developer_resources#Implementation_documentation notes that the ZFS On-Disk Format document is "a good overview, but sorely outdated". Of possible interest: Max Bruning's weblog: ZFS Raidz Data Walk (2009)
Correct. http://groups.diigo.com/search?group_name=collaboration&what=Inkscape for some comments.
Whilst over the years computers have grown more compact, and display sizes are varied without argument, there remains widespread majority preference for one aspect: the 'normal' proportions of a keyboard.
The squashed keyboards/keypads on mobile/handheld devices and on Eee PC may be useful, but they're not as useful, easy or widely-appreciated as a normal-sized keyboard.
For devices with squashed or no keyboards: there exist, as peripherals, plenty of normal-size projected or peripheral foldaway/fabric keyboards.
For devices with normal keyboards: I know no-one who prefers to use a sqaushed peripheral alternative (though there are probably very rare cases when people do so).
I guess that normal-sized keyboards are ergonomcally good and it does seem that XO fits.
Why use an inferior tool (squashed keyboard) for learning --which is what the XO and OLPC are all about -- if it's near-inevitable that sooner or later, you'll require additional learning -- to use a device that truly fits one's fingers whilst typing)? As you learn through doing so I can't view Eee PC as an ideal device for learners.
Don't misunderstand me: I'm not disrespecting the Eee PC in itself. A colleague has one, and he loves it, and I realise its usefulness, but the keyboard is peculiarly small and I can't view Eee PC hardware as a recommended substitute for XO.
Best,
Graham
For myself, and for colleagues who have NeoOffice or OpenOffice.org installed (that's nearly everyone in our Centre):
* always, ODF.
When choices become limited to DOC or PDF (typically, in a web/instutitional context):
* PDF
When there's no other option (rarely):
* DOC
The most recent Microsoft Office 2004 for Mac OS can't handle Microsoft's most recent formats without converting to RTF. There may be numerous excuses and technical reasons for these delays but ultimately, it's unacceptable. What are Microsoft doing with their millions/billions? Haven't they had over twenty years to get things right with MS Office?