1:24 p.m.
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
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
===========================================================================
1:40 p.m.
On Wed, Feb 1, 2023 at 2:24 PM Patrick Dupre <pdupre(a)gmx.com> 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?
Instead of putting the filenames in a variable, put them in a file
(one filename per line) and tell tar to get the filenames from the
file with "--verbatim-files-from" and "-T, --files-from=FILE".
I.e., put filenames in /tmp/list-for-tar, and then "tar -cvzf arch.tgz
--verbatim-files-from -T /tmp/list-for-tar". See if that works for
you.
2:07 p.m.
On Wed, Feb 1, 2023 at 12:41 PM Go Canes <letsgonhlcanes0(a)gmail.com> wrote:
On Wed, Feb 1, 2023 at 2:24 PM Patrick Dupre <pdupre(a)gmx.com>
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?
Instead of putting the filenames in a variable, put them in a file
(one filename per line) and tell tar to get the filenames from the
file with "--verbatim-files-from" and "-T, --files-from=FILE".
I.e., put filenames in /tmp/list-for-tar, and then "tar -cvzf arch.tgz
--verbatim-files-from -T /tmp/list-for-tar". See if that works for
you.
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 {} +
Or, if you can generate the list with null characters instead of
spaces as the filename separators, you could do something like this:
[generate the list with nulls] | xargs -0 tar -cvzf arch.tgz
--
Jerry James
http://www.jamezone.org/
4:28 p.m.
On 01Feb2023 13:07, Jerry James <loganjerry(a)gmail.com> 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.
Or, if you can generate the list with null characters instead of
spaces as the filename separators, you could do something like this:
[generate the list with nulls] | xargs -0 tar -cvzf arch.tgz
Unless there are enough files for xargs to break the files into multiple
groups, in which case... again a tar file containing only the last
group.
Cheers,
Cameron Simpson <cs(a)cskk.id.au>
7:54 a.m.
On 2/1/23 4:28 PM, Cameron Simpson wrote:
On 01Feb2023 13:07, Jerry James <loganjerry(a)gmail.com> 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.
No, it does not. Note the "+" at the end, which tells the "find"
command to pass as many arguments as will fit within the maximum length of a command line.
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.
> Or, if you can generate the list with null characters instead of
> spaces as the filename separators, you could do something like this:
>
> [generate the list with nulls] | xargs -0 tar -cvzf arch.tgz
Unless there are enough files for xargs to break the files into multiple groups, in which
case... again a tar file containing only the last group.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
11:11 a.m.
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 <loganjerry(a)gmail.com> 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.
No, it does not. Note the "+" at the end, which tells the "find"
command to pass as many arguments as will fit within the maximum
length of a command line.
I didn't know that. Interesting.
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.
That does work, but I can find no reference to getconf in the Fedora
docs even though the command is part of glibc-common. It would be nice
to know what other parameters it can tell me about.
poc
1:28 p.m.
On Thu, Feb 02, 2023 at 05:11:55PM +0000, 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.
That does work, but I can find no reference to getconf in the Fedora
docs even though the command is part of glibc-common. It would be nice
to know what other parameters it can tell me about.
poc
No man page either. And "getconf --help" is incomplete.
Try running getconf with np args.
$ getconf
Usage: getconf [-v specification] variable_name [pathname]
getconf -a [pathname]
Assuming that "-a" is "all",
$ getconf -a | wc -l
320
Lots of parameters available to inspect.
--
Jon H. LaBadie jonfu(a)jgcomp.com
2:19 p.m.
On Thu, 2023-02-02 at 14:28 -0500, Jon LaBadie wrote:
On Thu, Feb 02, 2023 at 05:11:55PM +0000, 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.
>
> That does work, but I can find no reference to getconf in the
> Fedora
> docs even though the command is part of glibc-common. It would be
> nice
> to know what other parameters it can tell me about.
>
> poc
No man page either. And "getconf --help" is incomplete.
Try running getconf with np args.
$ getconf
Usage: getconf [-v specification] variable_name [pathname]
getconf -a [pathname]
Assuming that "-a" is "all",
$ getconf -a | wc -l
320
$ getconf -a
LINK_MAX 127
...
$ getconf LINK_MAX
Usage: getconf [-v specification] variable_name [pathname]
getconf -a [pathname]
So documentation is not only missing but necessary.
poc
3:10 p.m.
On Thu, Feb 02, 2023 at 08:19:18PM +0000, 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 +0000, 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.
> >
> > That does work, but I can find no reference to getconf in the
> > Fedora
> > docs even though the command is part of glibc-common. It would be
> > nice
> > to know what other parameters it can tell me about.
> >
> > poc
>
> No man page either. And "getconf --help" is incomplete.
> Try running getconf with np args.
>
> $ getconf
> Usage: getconf [-v specification] variable_name [pathname]
> getconf -a [pathname]
>
> Assuming that "-a" is "all",
>
> $ getconf -a | wc -l
> 320
$ getconf -a
LINK_MAX 127
...
$ getconf LINK_MAX
Usage: getconf [-v specification] variable_name [pathname]
getconf -a [pathname]
So documentation is not only missing but necessary.
For sure. I do have getconf man pages on CentOS 7 and
Ubuntu 22.04. Very different pages!
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.
Probably need to read some source header files to be sure.
--
Jon H. LaBadie jonfu(a)jgcomp.com
3:28 p.m.
Once upon a time, Jon LaBadie <jonfu(a)jgcomp.com> 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 in man page availability is due to this coming from the
POSIX spec, which is in the man-pages-posix package. However, The Open
Group changed the license to something not compatible with Fedora, so
that package was moved to RPM Fusion.
You can also see the POSIX/Single Unix Specification here:
https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/
ARG_MAX is defined in the limits.h header (click on Headers at the
bottom left to find it).
--
Chris Adams <linux(a)cmadams.net>
4:04 p.m.
On Thu, 2023-02-02 at 15:28 -0600, Chris Adams wrote:
Once upon a time, Jon LaBadie <jonfu(a)jgcomp.com> 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 in man page availability is due to this coming from
the
POSIX spec, which is in the man-pages-posix package. However, The
Open
Group changed the license to something not compatible with Fedora, so
that package was moved to RPM Fusion.
You can also see the POSIX/Single Unix Specification here:
https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/
So Fedora can supply the executable (and source) but not the
documentation? Is there something wrong with this picture?
Why can't Fedora provide at least a skeleton man page that points to
the POSIX doc?
poc
4:19 p.m.
Once upon a time, Patrick O'Callaghan <pocallaghan(a)gmail.com> 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 freely
reimplementable).
--
Chris Adams <linux(a)cmadams.net>
4:46 p.m.
On Thu, 2023-02-02 at 16:19 -0600, Chris Adams wrote:
Once upon a time, Patrick O'Callaghan
<pocallaghan(a)gmail.com> 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 freely
reimplementable).
No doubt. However it still makes no logical (rather than legal) sense
to me. To repeat: if the canonical documentation is legally restricted,
Fedora should at minimum give a pointer to it in the man pages.
I actually looked at the POSIX reference and found it IMHO pretty
useless to be honest, so Fedora could certainly improve on it with an
independent implementation (of the docs).
poc
4:11 p.m.
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 documentation is not only missing but necessary.
For sure. I do have getconf man pages on CentOS 7 and
Ubuntu 22.04. Very different pages!
I wasn't clear enough. Docs are necessary because the command doesn't
behave the way it claims. It lists a variable under '-a' which it
doesn't recognise when given directly. This is either a bug or I'm
misunderstanding how it's supposed to work, but with no docs it's
impossible to tell.
poc
4:32 p.m.
On 01Feb2023 20:24, Patrick Dupre <pdupre(a)gmx.com> 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 arch.tgz *.ext
Obviously replacing *.ext appropriately. And of course you can give that
many times.
If the files are the entire content of a directory, merely mentioning
the directory is enough:
tar cvzf arch.tgz directoryname
Of course you can give multiple directories or globs.
And in modern shells there's a "**" pattern means a recursive walk. So:
tar cvzf arch.tgz subdir/**/*.py
to name all the .py files in subdir. And so forth.
All of these are space (and other weird characters) safe.
If you must make the tar file in a few goes/batches, do the first with
"c" (create) and the rest with "r" (replace), which does an append.
Cheers,
Cameron Simpson <cs(a)cskk.id.au>
5:35 p.m.
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?
Thank
I wild guess:
Escape the space(s) with a backslash(s)
Who Am I
Who\ Am\ I
5:56 p.m.
Hello Patrick,
On Wed, 1 Feb 2023 20:24:22 +0100 Patrick Dupre <pdupre(a)gmx.com> 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?
Somebody suggested that you use --files-from=FILE and
--verbatim-files-from, this is IMO the right way.
If you really need to use $list, it all depends how you store the file
list in it, and how you expand the variable in the command-line.
Playing with the IFS env. var. can also help.
See:
# supposing that "a b" and "c d" exist:
$ list=`find . -name "a b" -o -name "c d"`
or
$ list=`ls -1 "a b" "c d"`
$ echo $list
a b c d
$ echo "$list"
a b
c d
$ tar cvzf arch.tgz "$list"
a b
c d
Isn't what you wanted?
Regards,
--
wwp
https://useplaintext.email/
6:26 p.m.
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 when I tar, or when I create the list?
Rename the files to exclude spaces.
Filenames with spaces are administrative headaches.
mothersRecipesForPancakes01.txt is understandable enough that spaces aren't
necessary.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
7:10 p.m.
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 aren't providing enough information for a good answer.
How are you creating the list?
What is the format of the data in that variable?
Generally, it's not a good idea to store a lot of data in an environment
variable, so how many files are involved?
493
days inactive
494
days old
18 comments
12 participants
participants (12)
-
Cameron Simpson -
Chris Adams -
Felix Miata -
Go Canes -
Jerry James -
Jon LaBadie -
Patrick Dupre -
Patrick O'Callaghan -
Robert Nichols -
Samuel Sieb -
ToddAndMargo -
wwp