Mike Gerdts wrote: > On Thu, Jul 10, 2008 at 11:31 AM, Darren J Moffat <[EMAIL PROTECTED]> wrote: >> Mike Gerdts wrote: >>> On Thu, Jul 10, 2008 at 5:42 AM, Darren J Moffat <[EMAIL PROTECTED]> >>> wrote: >>>> Thoughts ? Is this useful for anyone else ? My above examples are some >>>> of the shorter dataset names I use, ones in my home directory can be >>>> even deeper. >>> Quite usable and should be done. >>> >>> The key problem I see is how to deal with ambiguity. >>> >>> # zpool create pool >>> # zfs create pool/home >>> # zfs set mountpoint=/home pool/home >>> # zfs create pool/home/adams (for Dilbert's master) >>> ... >>> # zfs create pool/home/gerdts (for Me) >>> ... >>> # zfs create pool/home/pool (for Ms. Pool) >>> ... >>> # cd /home >>> # zfs snapshot [EMAIL PROTECTED] >>> >>> What just got snapshotted? >> The dataset named "pool" only. I don't see how that could be ambiguous now >> or with what I proposed. >> >> If you said zfs snapshot -r [EMAIL PROTECTED] then all of them. > > Which dataset named pool? The one at /pool (the root of the zpool, if > you will) or the one at /home/pool (Ms. Pool's home directory) which > happens to be `pwd`/pool.
Ah sorry I missed that your third dataset ended in pool. The answer is still the same though if the proposal to use a new flag for partial paths is taken. Which is why I suggested that, it is ambiguous in the example you gave if zfs(1) commands other than create can take relative paths too [ which would be useful ]. -- Darren J Moffat _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
