-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Samad writes:
> On Wed, Nov 04, 2009 at 08:53:04AM +, John Allen wrote:
>> Merciadri Luca wrote:
>> >-BEGIN PGP SIGNED MESSAGE-
>> >Hash: SHA1
>> >
> [snip]
>> >
>> >Any ideas?
>> >
>> Well one idea is to stop using tar, and use a ge
On Wed, Nov 04, 2009 at 08:53:04AM +, John Allen wrote:
> Merciadri Luca wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
[snip]
> >
> >Any ideas?
> >
> Well one idea is to stop using tar, and use a generational rsync
> backup tool instead.
>
> One such tool is http://rsnapshot.o
Merciadri Luca wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello folks,
I use tar to make (not necessarily incremental) backups of my /etc/*,
/home/*, and other important folders. I am encountering a problem:
reading a file in a .tgz takes a really long time. I use the
Archive Manager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexey Salmin writes:
> Since tgz is .tar.gz (a tar file compressed via gzip) there is no
> surprise that it's slow to get a single file from it. The whole
> tarball will be decompressed first and it's definitely expensive.
> If you have enough space
Since tgz is .tar.gz (a tar file compressed via gzip) there is no
surprise that it's slow to get a single file from it. The whole
tarball will be decompressed first and it's definitely expensive.
If you have enough space on your hdd you can store a plain tarball
instead of compressed file - that sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello folks,
I use tar to make (not necessarily incremental) backups of my /etc/*,
/home/*, and other important folders. I am encountering a problem:
reading a file in a .tgz takes a really long time. I use the
Archive Manager GUI (of GNOME) to go thr
6 matches
Mail list logo
