Many programs in /usr/bin cannot act on all files if permissions do
not allow it. Dirvish is no different. Dirvish is useful to regular
users. They may want to backup something they own via SSH on another
machine. The one use case where the root user wants to back-up the
entire system to another di
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.09.11.1731 +0200]:
> > There simply are tools that are not for "everybody", ifconfig, lsof
> > comes to mind.
>
> ifconfig needs root access for most of it's operations, and lsof
> (which I happen to use a lot as non-root) just happens to be in
also sprach Paul Slootman <[EMAIL PROTECTED]> [2006.09.11.1240 +0200]:
> It can't, really; at least, not without losing some functionality
> (e.g. files not readable for the user running dirvish won't be
> backupped, and I wouldn't be surprised if the management of the
> vaults might go wrong).
If
tag 386954 wontfix
thanks
On Mon 11 Sep 2006, martin f krafft wrote:
>
> I understand that dirvish can be used to backup directories as
> non-root. Thus, it should live in /usr/bin, not /usr/sbin.
It can't, really; at least, not without losing some functionality
(e.g. files not readable for the
Package: dirvish
Version: 1.2.1-1
Severity: minor
I understand that dirvish can be used to backup directories as
non-root. Thus, it should live in /usr/bin, not /usr/sbin.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (750, 'unstable'), (500, 'testin
5 matches
Mail list logo
