From: Henry Yen <blinux-mail@AegisInfoSys.com>
To: blinux-list@redhat.com
Subject: Re: joining a bunch of files
Date: Sat, 1 Dec 2001 00:34:55 -0500 [thread overview]
Message-ID: <20011201003455.B29873@nntp.AegisInfoSys.com> (raw)
In-Reply-To: <3.0.6.32.20011130184529.0087abe0@mail.doorpi.net>; from Brent Harding on Fri, Nov 30, 2001 at 06:45:29AM -0600
according to 'man bash', pathname expansion results in "an alphabetically
sorted list". with that, i should think:
cat file_prefix_* > final_file
should be sufficient.
BTW linux has a much longer command line length limit, though i don't know what
it is; i imagine 4K, at least.
On Fri, Nov 30, 2001 at 06:45:29AM -0600, Brent Harding wrote:
> I didn't use xargs, but I did cat `ls | sort` >file.
> At 04:33 PM 11/30/01 -0500, Nicolas wrote:
> > ls file_prefix_* | sort | xargs cat > final_file
> >> I've heard of this, but it doesn't appear to be the thing, dos would do it
> >> if I copied and typed in all the names, would run out of command line
> >> anyway, 255 character limit.
[ snip ]
> >> How do
> >> >> > I put the files together to make one huge file without having to type all
> >> >> > the echo <file.a01 >> file
> >> >> > echo <file.a02 >> file
> >> >> > and so on up to 99?
> >> >> > There must be a copy a range, like echo <file.a01-a99 >> file, or something
> >> >> > on that order. Using * won't necessarily copy them in numeric order though.
--
Henry Yen Aegis Information Systems, Inc.
Senior Systems Programmer Hicksville, New York
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Brent Harding
` Luke Davis
` Mike Gorse
` dreamwvr
` Luke Davis
[not found] ` <Pine.BSF.4.43.0111301549410.66683-100000@server1.shellworl d.net>
` Brent Harding
` Luke Davis
` Nicolas Pitre
` Luke Davis
` Brent Harding
` Henry Yen [this message]
[not found] ` <Pine.BSF.4.43.0111301627330.66683-100000@server1.shellworl d.net>
` Brent Harding
` dreamwvr
` Jude DaShiell
` Luke Davis
[not found] ` <Pine.BSF.4.43.0112070250210.85814-100000@server1.shellworl d.net>
` Brent Harding
` John G. Heim (26 2-9887)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011201003455.B29873@nntp.AegisInfoSys.com \
--to=blinux-mail@aegisinfosys.com \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).