Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2009-11-26 Thread Darren J Moffat
Mike Gerdts wrote: Is there still any interest in this? I've done a bit of hacking (then searched for this thread - I picked -P instead of -c)... $ zfs get -P compression,dedup /var NAMEPROPERTY VALUE SOURCE rpool/ROOT/zfstest compression on inherited

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2009-11-26 Thread Menno Lageman
On 11/25/09 22:19, Mike Gerdts wrote: Is there still any interest in this? I've done a bit of hacking (then searched for this thread - I picked -P instead of -c)... $ zfs get -P compression,dedup /var NAMEPROPERTY VALUE SOURCE rpool/ROOT/zfstest compression on

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2009-11-25 Thread Mike Gerdts
Is there still any interest in this? I've done a bit of hacking (then searched for this thread - I picked -P instead of -c)... $ zfs get -P compression,dedup /var NAMEPROPERTY VALUE SOURCE rpool/ROOT/zfstest compression on inherited from rpool/ROOT

[zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Darren J Moffat
I regularly create new zfs filesystems or snapshots and I find it annoying that I have to type the full dataset name in all of those cases. I propose we allow zfs(1) to infer the part of the dataset name upto the current working directory. For example: Today: $ zfs create

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mark Phalan
On Thu, 2008-07-10 at 11:42 +0100, Darren J Moffat wrote: I regularly create new zfs filesystems or snapshots and I find it annoying that I have to type the full dataset name in all of those cases. I propose we allow zfs(1) to infer the part of the dataset name upto the current working

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mark J Musante
On Thu, 10 Jul 2008, Mark Phalan wrote: I find this annoying as well. Another way that would help (but is fairly orthogonal to your suggestion) would be to write a completion module for zsh/bash/whatever that could tab-complete options to the z* commands including zfs filesystems. You

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mark Phalan
On Thu, 2008-07-10 at 07:12 -0400, Mark J Musante wrote: On Thu, 10 Jul 2008, Mark Phalan wrote: I find this annoying as well. Another way that would help (but is fairly orthogonal to your suggestion) would be to write a completion module for zsh/bash/whatever that could tab-complete

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mark J Musante
On Thu, 10 Jul 2008, Tim Foster wrote: Mark Musante (famous for recently beating the crap out of lu) Heh. Although at this point it's hard to tell who's the beat-er and who's the beat-ee... Regards, markm ___ zfs-discuss mailing list

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Carson Gaspar
Darren J Moffat wrote: Today: $ zfs create cube/builds/darrenm/bugs/6724478 With this proposal: $ pwd /cube/builds/darrenm/bugs $ zfs create 6724478 Both of these would result in a new dataset cube/builds/darrenm/6724478 ... Maybe the easiest way out of the ambiquity is to add a

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Moore, Joe
Carson Gaspar wrote: Darren J Moffat wrote: $ pwd /cube/builds/darrenm/bugs $ zfs create -c 6724478 Why -c ? -c for current directory -p partial is already taken to mean create all non existing parents and -r relative is already used consistently as recurse in other zfs(1)

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Darren J Moffat
Carson Gaspar wrote: Why not zfs create $PWD/6724478. Works today, traditional UNIX behaviour, no coding required. Unles you're in some bizarroland shell Did you actually try that ? braveheart# echo $PWD /tank/p2/2/1 braveheart# zfs create $PWD/44 cannot create '/tank/p2/2/1/44':

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mike Gerdts
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

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Darren J Moffat
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

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Mike Gerdts
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

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Darren J Moffat
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

Re: [zfs-discuss] proposal partial/relative paths for zfs(1)

2008-07-10 Thread Carson Gaspar
Moore, Joe wrote: Carson Gaspar wrote: Darren J Moffat wrote: $ pwd /cube/builds/darrenm/bugs $ zfs create -c 6724478 Why -c ? -c for current directory -p partial is already taken to mean create all non existing parents and -r relative is already used consistently as recurse in