On 3/4/25 12:13 AM, Christiano Anderson wrote:
On 04/03/2025 04:08, ToddAndMargo via users wrote:
It looks like if I wanted to exclude "folder3" and
all its sub folders, the run line would look like:
/home/ftp/mysite/folder3
cd /home/ftp
tar -czvf mysite.tar.gz mysite --excl
On 04/03/2025 04:08, ToddAndMargo via users wrote:
It looks like if I wanted to exclude "folder3" and
all its sub folders, the run line would look like:
/home/ftp/mysite/folder3
cd /home/ftp
tar -czvf mysite.tar.gz mysite --exclude='file3' --exclude='folder3'
On 3/3/25 5:40 PM, Jeffrey Walton wrote:
On Mon, Mar 3, 2025 at 8:17 PM ToddAndMargo via users
wrote:
Is there a way to exclude a directory when creating a tar ball?
Let me Google that for you:
<https://www.google.com/search?q=tar+how+to+exclude+directory>.
Jeff
It looks like if I
On Mon, Mar 3, 2025 at 8:17 PM ToddAndMargo via users
wrote:
>
> Is there a way to exclude a directory when creating a tar ball?
Let me Google that for you:
<https://www.google.com/search?q=tar+how+to+exclude+directory>.
Jeff
--
___
u
Hi All,
Is there a way to exclude a directory when creating a tar ball?
-T
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
On Thu, 2023-02-02 at 16:19 -0600, Chris Adams wrote:
> Once upon a time, Patrick O'Callaghan said:
> > So Fedora can supply the executable (and source) but not the
> > documentation? Is there something wrong with this picture?
>
> The executable/source doesn't come from POSIX, it comes from glib
Once upon a time, Patrick O'Callaghan said:
> So Fedora can supply the executable (and source) but not the
> documentation? Is there something wrong with this picture?
The executable/source doesn't come from POSIX, it comes from glibc. It
just implements the interface defined by POSIX (which is
On Thu, 2023-02-02 at 16:10 -0500, Jon LaBadie wrote:
> > > $ getconf -a | wc -l
> > > 320
> >
> > $ getconf -a
> > LINK_MAX 127
> > ...
> >
> > $ getconf LINK_MAX
> > Usage: getconf [-v specification] variable_name [pathname]
> > getconf -a [pathname]
> >
> > So
On Thu, 2023-02-02 at 15:28 -0600, Chris Adams wrote:
> Once upon a time, Jon LaBadie said:
> > I'd also like to see some docs on the meanings of the
> > variables. For example, is ARG_MAX the maximum NUMBER of
> > args or the maximum total length? I assume the former.
>
> It's the max total le
Once upon a time, Jon LaBadie said:
> I'd also like to see some docs on the meanings of the
> variables. For example, is ARG_MAX the maximum NUMBER of
> args or the maximum total length? I assume the former.
It's the max total length (and includes the environment variable size).
The difference
On Thu, Feb 02, 2023 at 08:19:18PM +, Patrick O'Callaghan wrote:
On Thu, 2023-02-02 at 14:28 -0500, Jon LaBadie wrote:
On Thu, Feb 02, 2023 at 05:11:55PM +, Patrick O'Callaghan wrote:
> On Thu, 2023-02-02 at 07:54 -0600, Robert Nichols wrote:
...
>
> > Your "multiple groups" warning belo
On Thu, 2023-02-02 at 14:28 -0500, Jon LaBadie wrote:
> On Thu, Feb 02, 2023 at 05:11:55PM +, Patrick O'Callaghan wrote:
> > On Thu, 2023-02-02 at 07:54 -0600, Robert Nichols wrote:
> ...
> >
> > > Your "multiple groups" warning below still applies, but on modern
> > > systems this is quite a
On Thu, Feb 02, 2023 at 05:11:55PM +, Patrick O'Callaghan wrote:
On Thu, 2023-02-02 at 07:54 -0600, Robert Nichols wrote:
...
Your "multiple groups" warning below still applies, but on modern
systems this is quite a large limit. Run "getconf ARG_MAX" to see the
limit on your system.
Tha
On Thu, 2023-02-02 at 07:54 -0600, Robert Nichols wrote:
> On 2/1/23 4:28 PM, Cameron Simpson wrote:
> > On 01Feb2023 13:07, Jerry James wrote:
> > > If you can make your list with find, you can also do something
> > > like this:
> > >
> > > find [
On 2/1/23 4:28 PM, Cameron Simpson wrote:
On 01Feb2023 13:07, Jerry James wrote:
If you can make your list with find, you can also do something like this:
find [top directory] [find criteria here] -exec tar -cvzf arch.tgz {} +
This recreates the tar file once per file, ending up with a tar
On 2/1/23 11:24, Patrick Dupre wrote:
To create a tar file, I used to create a list and to make
tar -cvzf arch.tgz $list
However, if there are file names with a space, this space is
interpreted as file name separator.
How can I fix this,
either when I tar, or when I create the list?
You
Patrick Dupre composed on 2023-02-01 20:24 (UTC+0100):
> To create a tar file, I used to create a list and to make
> tar -cvzf arch.tgz $list
> However, if there are file names with a space, this space is
> interpreted as file name separator.
> How can I fix this,
> either whe
Hello Patrick,
On Wed, 1 Feb 2023 20:24:22 +0100 Patrick Dupre wrote:
> To create a tar file, I used to create a list and to make
> tar -cvzf arch.tgz $list
>
> However, if there are file names with a space, this space is
> interpreted as file name separator.
>
> How can
On 2/1/23 11:24, Patrick Dupre wrote:
Hello,
To create a tar file, I used to create a list and to make
tar -cvzf arch.tgz $list
However, if there are file names with a space, this space is
interpreted as file name separator.
How can I fix this,
either when I tar, or when I create the list
On 01Feb2023 20:24, Patrick Dupre wrote:
To create a tar file, I used to create a list and to make
tar -cvzf arch.tgz $list
However, if there are file names with a space, this space is
interpreted as file name separator.
If you can match the files with a glob (shell pattern):
tar cvzf
On 01Feb2023 13:07, Jerry James wrote:
If you can make your list with find, you can also do something like
this:
find [top directory] [find criteria here] -exec tar -cvzf arch.tgz {} +
This recreates the tar file once per file, ending up with a tar file
containing only the last file found
On Wed, Feb 1, 2023 at 12:41 PM Go Canes wrote:
> On Wed, Feb 1, 2023 at 2:24 PM Patrick Dupre wrote:
> > To create a tar file, I used to create a list and to make
> > tar -cvzf arch.tgz $list
> >
> > However, if there are file names with a space, this space is
&
On Wed, Feb 1, 2023 at 2:24 PM Patrick Dupre wrote:
>
> Hello,
>
> To create a tar file, I used to create a list and to make
> tar -cvzf arch.tgz $list
>
> However, if there are file names with a space, this space is
> interpreted as file name separator.
>
> How c
Hello,
To create a tar file, I used to create a list and to make
tar -cvzf arch.tgz $list
However, if there are file names with a space, this space is
interpreted as file name separator.
How can I fix this,
either when I tar, or when I create the list?
Thank
On 2020-10-10 07:15, C Linus Hicks wrote:
On Fri, 2020-10-09 at 15:08 -0700, ToddAndMargo via users wrote:
On 2020-10-07 14:17, Cameron Simpson wrote:
On 06Oct2020 16:32, ToddAndMargo wrote:
I am noticing that
tar czvf x
is only using one of my cores (and pretty much all of
the
On Fri, 2020-10-09 at 15:08 -0700, ToddAndMargo via users wrote:
> On 2020-10-07 14:17, Cameron Simpson wrote:
> > On 06Oct2020 16:32, ToddAndMargo wrote:
> > > I am noticing that
> > >
> > >tar czvf x
> > >
> > > is only using
On 2020-10-07 14:17, Cameron Simpson
wrote:
On 06Oct2020 16:32, ToddAndMargo wrote:
I am noticing that
tar czvf x
is only using one of my cores (and pretty much all of
the core).
Is there a way to get it to use more than one core
On 06Oct2020 22:10, Samuel Sieb wrote:
>On 10/6/20 10:02 PM, ToddAndMargo via users wrote:
>>How would I use this in place of `tar czvf xxx`?
>
>Add "-I pigz" to the command.
>tar cvf myfile.tgz -I pigz files to pack
Well, today I've learnt a new
On 06Oct2020 16:32, ToddAndMargo wrote:
>I am noticing that
>
>tar czvf x
>
>is only using one of my cores (and pretty much all of
>the core).
>
>Is there a way to get it to use more than one core?
It is writing data serailly. In what way do you think using anothe
ToddAndMargo via users kirjoitti 7.10.2020 klo 8.22:
And will they untar with `tar xzvf `?
While it's less useful for decompression, you can use pigz for that as well:
tar -xf -I unpigz
--
Terveisin / Regards,
Matti Pulkkinen
___
On 2020-10-06 22:38, Ed Greshko wrote:
On 2020-10-07 13:22, ToddAndMargo via users wrote:
On 2020-10-06 22:10, Samuel Sieb wrote:
On 10/6/20 10:02 PM, ToddAndMargo via users wrote:
How would I use this in place of `tar czvf xxx`?
Add "-I pigz" to the command.
tar cvf myfile.t
On 2020-10-07 13:22, ToddAndMargo via users wrote:
> On 2020-10-06 22:10, Samuel Sieb wrote:
>> On 10/6/20 10:02 PM, ToddAndMargo via users wrote:
>>> How would I use this in place of `tar czvf xxx`?
>>
>> Add "-I pigz" to the command.
>> tar cvf
On 2020-10-06 22:10, Samuel Sieb wrote:
On 10/6/20 10:02 PM, ToddAndMargo via users wrote:
How would I use this in place of `tar czvf xxx`?
Add "-I pigz" to the command.
tar cvf myfile.tgz -I pigz files to pack
Thank you!
And will they untar with `tar
On 10/6/20 10:02 PM, ToddAndMargo via users wrote:
How would I use this in place of `tar czvf xxx`?
Add "-I pigz" to the command.
tar cvf myfile.tgz -I pigz files to pack
___
users mailing list -- users@lists.fedoraproject.org
To unsubscri
On 2020-10-06 21:45, Ed Greshko wrote:
On 2020-10-07 12:31, ITwrx wrote:
On 10/6/20 6:32 PM, ToddAndMargo via users wrote:
Hi All,
I am noticing that
tar czvf x
is only using one of my cores (and pretty much all of
the core).
Is there a way to get it to use more than one core
On 2020-10-07 12:31, ITwrx wrote:
> On 10/6/20 6:32 PM, ToddAndMargo via users wrote:
>> Hi All,
>>
>> I am noticing that
>>
>> tar czvf x
>>
>> is only using one of my cores (and pretty much all of
>> the core).
>>
>> Is the
On 10/6/20 6:32 PM, ToddAndMargo via users wrote:
> Hi All,
>
> I am noticing that
>
> tar czvf x
>
> is only using one of my cores (and pretty much all of
> the core).
>
> Is there a way to get it to use more than o
No. Tar and compress are single threaded. Depending on what you are
wanting to do, mksquashfs will build a filesystem img that you can
mount, and it will use all cores when it compresses, and the way it
compresses it is easier to mount it and pull out parts.
On Tue, Oct 6, 2020 at 6:33 PM
Hi All,
I am noticing that
tar czvf x
is only using one of my cores (and pretty much all of
the core).
Is there a way to get it to use more than one core?
Many thanks,
-T
___
users mailing list -- users@lists.fedoraproject.org
To
On 9/9/19 7:20 PM, Tim via users wrote:
On Wed, 2019-09-04 at 23:58 -0700, ToddAndMargo via users wrote:
If Windows read Ext4, I'd convert all my flash drives over to it.
Apparently it can be done.
Indeed. And the results are tragic. Here are my notes on it:
Paragon EXTFS for Windows:
On Wed, 2019-09-04 at 23:58 -0700, ToddAndMargo via users wrote:
> If Windows read Ext4, I'd convert all my flash drives over to it.
Apparently it can be done.
--
uname -rsvp
Linux 3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64
Boilerplate: All unexpected mail to my m
On 9/6/19 9:43 PM, ToddAndMargo via users wrote:
On 9/6/19 9:36 PM, Cameron Simpson wrote:
On 06Sep2019 20:16, ToddAndMargo wrote:
On 9/6/19 7:45 PM, Cameron Simpson wrote:
# dd status=progress bs=4096 if=/dev/sdb | gzip >
DeadStick.FC30.2019-09-06
34489798656 bytes (34 GB, 32 GiB) copied, 4
On 9/6/19 9:36 PM, Cameron Simpson wrote:
On 06Sep2019 20:16, ToddAndMargo wrote:
On 9/6/19 7:45 PM, Cameron Simpson wrote:
# dd status=progress bs=4096 if=/dev/sdb | gzip >
DeadStick.FC30.2019-09-06
34489798656 bytes (34 GB, 32 GiB) copied, 404 s, 85.4 MB/s
dd: error reading '/dev/sdb': Inpu
On 06Sep2019 20:16, ToddAndMargo wrote:
On 9/6/19 7:45 PM, Cameron Simpson wrote:
# dd status=progress bs=4096 if=/dev/sdb | gzip >
DeadStick.FC30.2019-09-06
34489798656 bytes (34 GB, 32 GiB) copied, 404 s, 85.4 MB/s
dd: error reading '/dev/sdb': Input/output error
8425692+0 records in
8425692
On 9/5/19 3:44 AM, Samuel Sieb wrote:
However, the other suggestion to pipe straight
through gzip (or other compression program) is better anyway.
Thank you!
Backup:
1) shutdown: zero out unused space
Figure out which partitions / and /boot are loated on. Gparted
work
On 9/6/19 7:45 PM, Cameron Simpson wrote:
On 06Sep2019 19:34, ToddAndMargo wrote:
I am going to test the straight pipe today on my USB3 ports
and see if the overhead slows down the dd enough to stop
crashing dd. [...]
"crashing" ?
[...]
Ahh poop! (Not my "exact" word.)
# dd status=progres
On 06Sep2019 19:34, ToddAndMargo wrote:
I am going to test the straight pipe today on my USB3 ports
and see if the overhead slows down the dd enough to stop
crashing dd. [...]
"crashing" ?
[...]
Ahh poop! (Not my "exact" word.)
# dd status=progress bs=4096 if=/dev/sdb | gzip > DeadStick.FC
On 9/6/19 3:21 PM, ToddAndMargo via users wrote:
On 9/5/19 3:44 AM, Samuel Sieb wrote:
On 9/4/19 10:55 PM, ToddAndMargo via users wrote:
# gzip DeadStick.[date] # creates DeadStick.[date].gz
# rm DeadStick.[date]
The rm will fail because gzip removes the original file whe
On 9/5/19 3:44 AM, Samuel Sieb wrote:
On 9/4/19 10:55 PM, ToddAndMargo via users wrote:
# gzip DeadStick.[date] # creates DeadStick.[date].gz
# rm DeadStick.[date]
The rm will fail because gzip removes the original file when it's
finished compressing. However, the other
On 9/4/19 10:55 PM, ToddAndMargo via users wrote:
# gzip DeadStick.[date] # creates DeadStick.[date].gz
# rm DeadStick.[date]
The rm will fail because gzip removes the original file when it's
finished compressing. However, the other suggestion to pipe straight
through gz
On 9/4/19 11:24 PM, francis.montag...@inria.fr wrote:
Hi.
On Wed, 04 Sep 2019 22:55:56 -0700 ToddAndMargo via users wrote:
This is what I finally wound up doing to back up this stick.
Dead Stick is a play on words off of Live USB:
Backup:
1) shutdown: zero out unused space
...
Hi.
On Wed, 04 Sep 2019 22:55:56 -0700 ToddAndMargo via users wrote:
> This is what I finally wound up doing to back up this stick.
> Dead Stick is a play on words off of Live USB:
> Backup:
> 1) shutdown: zero out unused space
...
> # zerofree -v /dev/sd..
Beware that zerofree
On 9/3/19 10:03 PM, ToddAndMargo via users wrote:
Hi All,
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
Many thanks,
-T
Followup.
This is what I finally wound up doing to back
On 9/3/19 11:32 PM, Eyal Lebedinsky wrote:
dd if=/dev/zero of=/path/to/mountPoint/zero
rm /path/to/mountPoint/zero
Oh, I finally understand! I was thinking /mnt/flash/big-file-o-zeros
was on the local drive, not the flash drive. Duh!
Thank you!
On Wed, 2019-09-04 at 12:44 -0700, Gordon Messmer wrote:
> On 9/4/19 8:20 AM, Patrick O'Callaghan wrote:
> > For a USB drive it probably doesn't make much difference. Output will
> > be buffered and speed is limited by the USB interface.
>
> If you aren't specifying a block size, the default block
On 9/4/19 1:48 PM, Ted Roche wrote:
scrub, in the Fedora repos, has a fillzero option and a freespace
specifier that should do the trick. MAKE A BACKUP FIRST, as scrub's
primary job is to erase any trace of everything on a device, so you'd
hate to get the options wrong!
Thank you!
Ya, backup
scrub, in the Fedora repos, has a fillzero option and a freespace specifier
that should do the trick. MAKE A BACKUP FIRST, as scrub's primary job is to
erase any trace of everything on a device, so you'd hate to get the options
wrong!
On Wed, Sep 4, 2019 at 4:41 PM ToddAndMargo via users <
user
On 9/4/19 1:25 PM, ToddAndMargo via users wrote:
On 9/4/19 2:44 AM, Patrick O'Callaghan wrote:
The point of Eyal's method is to ensure that all the free space on the
drive is filled with zeroes, thus improving the compression. Otherwise
you are just uselessly compressing junk.
poc
Is there a
On 9/4/19 6:16 AM, Dave Ihnat wrote:
On 4 Sep at 01:12, Ed Greshko wrote:
Of course a dd copy may be rather time consuming and space consuming
with no apparent advantage.
A lot less time consuming if you use the "bs=" option. Haven't seen anyone
mention that; I believe the default is still
On 9/4/19 2:44 AM, Patrick O'Callaghan wrote:
The point of Eyal's method is to ensure that all the free space on the
drive is filled with zeroes, thus improving the compression. Otherwise
you are just uselessly compressing junk.
poc
Is there a way to tell the stick itself to zero out
all unuse
On 9/4/19 8:20 AM, Patrick O'Callaghan wrote:
For a USB drive it probably doesn't make much difference. Output will
be buffered and speed is limited by the USB interface.
If you aren't specifying a block size, the default block size tends to
involve more round-trips through the kernel and thr
On Wed, Sep 04, 2019 at 04:20:14PM +0100, Patrick O'Callaghan wrote:
> On Wed, 2019-09-04 at 21:55 +0800, Ed Greshko wrote:
> > On 9/4/19 9:16 PM, Dave Ihnat wrote:
> > > On 4 Sep at 01:12, Ed Greshko wrote:
> > > > Of course a dd copy may be rather time consuming and space consuming
> > > > with
SORRY! That message was not intended for you.
-Original Message-
From:
Sent: Wed, 04 Sep 2019 16:20:14 +0100
To: 3603060...@txt.att.net
Subject: Re: tar a flash drive
>On Wed, 2019-09-04 at 21:55 +0800, Ed Greshko wrote:
>> On 9/4/19 9:16 PM, Dave Ihnat wrote:
>>
FOLLOW @gnome
-Original Message-
From:
Sent: Wed, 04 Sep 2019 16:20:14 +0100
To: 3603060...@txt.att.net
Subject: Re: tar a flash drive
>On Wed, 2019-09-04 at 21:55 +0800, Ed Greshko wrote:
>> On 9/4/19 9:16 PM, Dave Ihnat wrote:
>> > On 4 Sep at 01:12,
On Wed, 2019-09-04 at 21:55 +0800, Ed Greshko wrote:
> On 9/4/19 9:16 PM, Dave Ihnat wrote:
> > On 4 Sep at 01:12, Ed Greshko wrote:
> > > Of course a dd copy may be rather time consuming and space consuming
> > > with no apparent advantage.
> > A lot less time consuming if you use the "bs=" opti
On 9/4/19 9:16 PM, Dave Ihnat wrote:
> On 4 Sep at 01:12, Ed Greshko wrote:
>> Of course a dd copy may be rather time consuming and space consuming
>> with no apparent advantage.
> A lot less time consuming if you use the "bs=" option. Haven't seen anyone
> mention that; I believe the default is
On 4 Sep at 01:12, Ed Greshko wrote:
> Of course a dd copy may be rather time consuming and space consuming
> with no apparent advantage.
A lot less time consuming if you use the "bs=" option. Haven't seen anyone
mention that; I believe the default is still the old Unix 512b, painful.
Cheers,
On 9/4/19 5:00 PM, ToddAndMargo via users wrote:
> On 9/3/19 11:12 PM, Ed Greshko wrote:
>> The question would then arise as to how you would extract files/data from
>> that dd created
>
> No extraction. I just want to do a mass overwrite when
> the stick gets corrupted
OK.
Pro-Tip: Spelling o
On Wed, 2019-09-04 at 01:59 -0700, ToddAndMargo via users wrote:
> On 9/3/19 11:32 PM, Eyal Lebedinsky wrote:
> > What is the purpose of this exercise?
>
>
> I have a bootable Fedora 64 GB flash drive. I use it
> to troubleshoot customers' computers -- mostly Windows.
> Windows loved to eat thes
On 9/4/19 12:06 AM, Cameron Simpson wrote:
Shrug. "cat" is easier to invoke:
cat /dev/sdBLAH >sdBLAH.img
Cheers,
Cameron Simpson
I am use to dd. Kind of like I am use to vi when
EVERY other editor it the world is easier to use.
:-)
___
users ma
On 9/3/19 11:12 PM, Ed Greshko wrote:
The question would then arise as to how you would extract files/data from that
dd created
No extraction. I just want to do a mass overwrite when
the stick gets corrupted
___
users mailing list -- users@lists.fed
On 9/3/19 11:32 PM, Eyal Lebedinsky wrote:
What is the purpose of this exercise?
I have a bootable Fedora 64 GB flash drive. I use it
to troubleshoot customers' computers -- mostly Windows.
Windows loved to eat these sticks. (I have had great
luck switching to a Samsung stick.)
I have prev
On 03Sep2019 23:12, ToddAndMargo wrote:
On 9/3/19 10:56 PM, Cameron Simpson wrote:
On 03Sep2019 22:03, ToddAndMargo wrote:
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
Depends
On 04/09/2019 16.12, ToddAndMargo via users wrote:
On 9/3/19 10:59 PM, John Harris wrote:
On Tuesday, September 3, 2019 10:03:21 PM MST ToddAndMargo via users wrote:
Hi All,
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring
On 9/4/19 1:59 PM, John Harris wrote:
> On Tuesday, September 3, 2019 10:03:21 PM MST ToddAndMargo via users wrote:
>> Hi All,
>>
>> I have a flash drive with about four partitions on is.
>> Lets call it /dev/sdc.
>>
>> Can I tar sdc or am I stuck with tarrin
On 9/3/19 10:56 PM, Cameron Simpson wrote:
On 03Sep2019 22:03, ToddAndMargo wrote:
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
Depends what you want from it. If the partitions
On 9/3/19 10:59 PM, John Harris wrote:
On Tuesday, September 3, 2019 10:03:21 PM MST ToddAndMargo via users wrote:
Hi All,
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
If you
On Tuesday, September 3, 2019 10:03:21 PM MST ToddAndMargo via users wrote:
> Hi All,
>
> I have a flash drive with about four partitions on is.
> Lets call it /dev/sdc.
>
> Can I tar sdc or am I stuck with tarring the partitions?
>
> Any drawback to this?
If you we
On 03Sep2019 22:03, ToddAndMargo wrote:
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
Depends what you want from it. If the partitions have real filesystems
in them then mount
Hi All,
I have a flash drive with about four partitions on is.
Lets call it /dev/sdc.
Can I tar sdc or am I stuck with tarring the partitions?
Any drawback to this?
Many thanks,
-T
--
~
When we ask for advice, we are usually
On 8/8/19 3:06 PM, Patrick Dupre wrote:
> Hello,
>
> I do not understand,
> The command:
> tar -cf /mnt/backup/home.tlz --lzma pdupre --exclude-caches-all
> --exclude='pdupre/Nextcloud' --exclude='pdupre/.mozilla'
> returns:
>
> tar: --exclude-ca
Hello,
I do not understand,
The command:
tar -cf /mnt/backup/home.tlz --lzma pdupre --exclude-caches-all
--exclude='pdupre/Nextcloud' --exclude='pdupre/.mozilla'
returns:
tar: --exclude-caches-all has no effect
tar: --exclude ‘pdupre/Nextcloud’ has no effect
tar: --excl
On 07/17/2017 12:55 PM, Rick Stevens wrote:
Tar does an alphabetical sort of the top level of the directory you're
tarring up.
No, tar does not do any sorting. It just process the directory entries in the
order that readdir(3) returns them. For some filesystems, that will be a sorted
> Tar does an alphabetical sort of the top level of the directory you're
> tarring up. When it hits a directory, it descends down that tree and
> repeats the process (alphabetical sort, descend directory, etc.) until
> all files/directories are completed in that branch, then g
he file
> are taken from the directory,
> Not alphabetic ordering
> not date ordering.
>
> Then, I cannot guess what is missing.
> It is an emergency archive, because the disk is failing.
Tar does an alphabetical sort of the top level of the directory you're
tarring up. When
alphabetic ordering
not date ordering.
Then, I cannot guess what is missing.
It is an emergency archive, because the disk is failing.
Because tar files are assebled by appending things, you can "tar tvf
your-tar-file" to see what is in it. Sort that. Diff against sorted listing
fro
y 16, 2017 at 7:55 PM
> From: "Samuel Sieb"
> To: users@lists.fedoraproject.org
> Subject: Re: tar failure
>
> On 07/16/2017 10:52 AM, Patrick Dupre wrote:
> > I got: tar: Exiting with failure status due to previous errors
> > How can I finish the process?
>
On 07/16/2017 10:52 AM, Patrick Dupre wrote:
I got: tar: Exiting with failure status due to previous errors
How can I finish the process?
I do not want to restart the tar, I only would like to tar the rest
(directory).
It usually doesn't stop at the error, that's why it says "p
Hello,
I got: tar: Exiting with failure status due to previous errors
How can I finish the process?
I do not want to restart the tar, I only would like to tar the rest
(directory).
I do not see the logic that tar uses to create the archive
Can I guess this logic? and only tar the missing ?
Thank
On Thu, Oct 6, 2016 at 5:57 PM, Richard W.M. Jones
wrote:
> On Thu, Oct 06, 2016 at 03:08:53PM -, jerome.ya...@gmail.com wrote:
> > Is there a way to change the folder structure inside a tar file without
> extracting it to disk first?
> >
> > For example, I have t
On Thu, Oct 06, 2016 at 03:08:53PM -, jerome.ya...@gmail.com wrote:
> Is there a way to change the folder structure inside a tar file without
> extracting it to disk first?
>
> For example, I have the following file/folder structure in a tar file,
> test.tar.
>
> dir1
Is there a way to change the folder structure inside a tar file without
extracting it to disk first?
For example, I have the following file/folder structure in a tar file, test.tar.
dir1/
dir1/file1
dir1/file2
I would like the contents to be modified to.
dir2/dir1/
dir2/dir1/file1
dir2/dir1
;s SPECIFICALLY looked for by tar:
[snip of great info]
As a bonus question; do you know why md5sum is showing a different
value, as in...
echo ".IsCacheDirectory" | md5sum -
6929f806dd11bc634be8205d11af24d6 -
I used "John the Ripper" to prove that 8a477f597d28d172789f0
On 12/21/2015 05:37 PM, Doug H. wrote:
On Mon, 2015-12-21 at 16:19 -0800, Rick Stevens wrote:
On 12/21/2015 02:41 PM, Patrick Dupre wrote:
Thank you
By the way, the signature is the MD5 hash of the string
".IsCacheDirectory" and it's SPECIFICALLY looked for by tar:
[snip of
On Mon, 2015-12-21 at 16:19 -0800, Rick Stevens wrote:
> On 12/21/2015 02:41 PM, Patrick Dupre wrote:
> > Thank you
>
> By the way, the signature is the MD5 hash of the string
> ".IsCacheDirectory" and it's SPECIFICALLY looked for by tar:
[snip of great info]
On 12/21/2015 02:41 PM, Patrick Dupre wrote:
Thank you
By the way, the signature is the MD5 hash of the string
".IsCacheDirectory" and it's SPECIFICALLY looked for by tar:
[root@prophead tmp]# strings /bin/tar | grep
8a477f597d28d172789f06886806bc55
s.fedoraproject.org
> Subject: Re: tar exclude cache
>
> On Mon, 2015-12-21 at 21:29 +0100, Patrick Dupre wrote:
> > Hello,
> >
> > I am trying to exclude the .cache directories when I tar a home
> > directory
> > by using:
> > tar -cjf /mnt/backup/home.tb
On Mon, 2015-12-21 at 21:29 +0100, Patrick Dupre wrote:
> Hello,
>
> I am trying to exclude the .cache directories when I tar a home
> directory
> by using:
> tar -cjf /mnt/backup/home.tbz2 --exclude-caches-all /home/pdupre
> but it does not work.
> What am I doing wron
Hello,
I am trying to exclude the .cache directories when I tar a home directory
by using:
tar -cjf /mnt/backup/home.tbz2 --exclude-caches-all /home/pdupre
but it does not work.
What am I doing wrong ?
Thank for your help
On 02/08/2015 12:53 AM, Manish Jain wrote:
Hi,
I am having problems trying to understand why does tar archive
differently with the following 2 commands, presuming xyz is a
sub-directory :
tar -c -f - ./xyz | gzip > xyz.tar.gz//xyz nested one level under .
and ..
tar -c -f - xyz | g
1 - 100 of 171 matches
Mail list logo
