mv / cp should support arbitrary path lengths when crossing filesystems
Currently, mv(1) and cp(1) (same code -- binary name controls whether mv or cp behavior is used) are limited by PATH_MAX when the source and destination paths reside on different filesystems (for mv(1), mv must copy+unlink to when crossing filesystems). This prevents using either command on hierarchies that exceed PATH_MAX. With zfs and/or zones, this is possible to encounter with no good alternative.
No data to display