From: Mike Gorse <mgorse@mgorse.dhs.org>
To: blinux-list@redhat.com
Subject: Re: joining a bunch of files
Date: Fri, 30 Nov 2001 15:29:59 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.40.0111301529170.26406-100000@mgorse.dhs.org> (raw)
In-Reply-To: <3.0.6.32.20011130135715.007dbd20@mail.doorpi.net>
Try something like
ls file.* |sort >file
--Michael Gorse / ICQ:22583968 / http://mgorse.home.dhs.org
On Fri, 30 Nov 2001, Brent Harding wrote:
> I encrypted a zip archive I had with pgp. Now, I have files with
> extensions of a01 to a99 that have to be joined in order from 01 to 99 so I
> can decrypt the whole thing. Decrypting only the first doesn't return
> everything, so it must be split, used the a option, and rezipped the 99
> files to another archive so I wouldn't have 99 files laying around. 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.
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
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 [this message]
` 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
[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=Pine.LNX.4.40.0111301529170.26406-100000@mgorse.dhs.org \
--to=mgorse@mgorse.dhs.org \
--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).