Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187204

Re: Restore backup to KVM

From solitone <solitone@mail.com>
Newsgroups linux.debian.user
Subject Re: Restore backup to KVM
Date 2017-09-25 21:10 +0200
Message-ID <utGVs-27d-19@gated-at.bofh.it> (permalink)
References (1 earlier) <uspjX-2Dw-13@gated-at.bofh.it> <usBEt-1vD-1@gated-at.bofh.it> <usBXS-1C1-25@gated-at.bofh.it> <utaVA-6wY-15@gated-at.bofh.it> <utbRE-76z-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 24/09/17 11:51, Reco wrote:
> ACLs are easy. Even tar(1) knows them.
> It's things like these that give you headache:
> 
> $ /sbin/getcap /bin/ping
> /bin/ping = cap_net_raw+ep
> 
> # lsattr /etc/resolv.conf
> ----i---------e---- /etc/resolv.conf
> 
> # getfattr -d /var/log/messages
> # file: var/log/messages
> user.name="main system log"
> 
> # ls -alZ .bashrc
> -rw-r--r--. root root system_u:object_r:admin_home_t:s0 .bashrc
> 
> If you have any of these in your source system, but don't have in target
> one - your backup is invalid, consider changing tool you're using.
> Note that these are just the examples, there can be other files like
> this.

Is there anything like this in the standard debian configuration? I 
haven't set any.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 06:50 +0200
  Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 08:10 +0200
    Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 21:20 +0200
      Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 21:40 +0200
        Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-24 11:00 +0200
          Re: Restore backup to KVM <tomas@tuxteam.de> - 2017-09-24 11:20 +0200
          Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-24 12:00 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:10 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:20 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:20 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 17:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:20 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 09:00 +0200
                Re: Restore backup to KVM "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-27 09:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 10:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 14:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 19:00 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-28 09:00 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-29 06:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-29 08:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-30 15:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 17:00 +0200

csiph-web