On Tue, Feb 19, 2013 at 8:11 AM, Nick Holland
<n...@holland-consulting.net> wrote:
> I use ZFS, and have a few ZFS systems in production, and what it does is
> pretty amazing, but mostly in the sense of the gigabytes of RAM it
> consumes for basic operation (and unexplained file system wedging).
> I've usually seen it used as a way to avoid good system design. Yes,
> huge file systems can be useful, but usually in papering over basic
> design flaws.
funnily enough, that "avoid[ing] good system design" is exactly what
makes it useful for desktop over server. i don't want to spend any
time figuring out how much gigs for /usr/{src,xenocara}. i also don't
want to partition /usr/ports only to find out later on that there's an
"object" or "tmp" sub-directory that i want on a different fs but i
can't because i've hit the 16 partition limit
if i ever install an application for experimental reasons, because
it's not a production machine, i don't want to rethink everything to
fit inside the disklabel constraints either. "good system design"
doesn't apply because it's a case where, gasp, the admin couldn't
possibly plan ahead
