It's not intuitive because when you know that -o sets options, an error message saying that it's not a valid property makes you think that it's not possible to do what you're trying.
Documented and intuitive are very different things. I do appreciate that the details are there in the manuals, but for items like this where it's very easy to pick the wrong one, it helps if the commands can work with you. The difference between -o and -O is pretty subtle, I just think that extra sentence in the error message could save a lot of frustration when people get mixed up. Ross On Wed, Feb 4, 2009 at 11:14 AM, Darren J Moffat <darr...@opensolaris.org> wrote: > Ross wrote: >> >> Good god. Talk about non intuitive. Thanks Darren! > > Why isn't that intuitive ? It is even documented in the man page. > > zpool create [-fn] [-o property=value] ... [-O file-system- > property=value] ... [-m mountpoint] [-R root] pool vdev ... > > >> Is it possible for me to suggest a quick change to the zpool error message >> in solaris? Should I file that as an RFE? I'm just wondering if the error >> message could be changed to something like: >> "property 'casesensitivity' is not a valid pool property. Did you mean to >> use -O?" >> >> It's just a simple change, but it makes it obvious that it can be done, >> instead of giving the impression that it's not possible. > > Feel free to log the RFE in defect.opensolaris.org. > > -- > Darren J Moffat > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
