From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: joining a bunch of files
Date: Fri, 30 Nov 2001 15:26:49 -0600 [thread overview]
Message-ID: <3.0.6.32.20011130152649.0087da70@mail.doorpi.net> (raw)
In-Reply-To: <Pine.BSF.4.43.0111301549410.66683-100000@server1.shellworl d.net>
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.
At 03:51 PM 11/30/01 -0500, you wrote:
>Join, meaning the relational database utility?
>
>Even if that can do this, and I'm not convinsed that it can, that is a lot
>of learning for a simple problem--from one readthrough of the man page, I
>have no clear picture of what this is even supposed to acomplish, let
>alone how to make it do things for which it does not appear to be
>intended.
>
>
>On Fri, 30 Nov 2001, dreamwvr@dreamwvr.com wrote:
>
>> man join
>> On Fri, Nov 30, 2001 at 01:57:15PM -0600, 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
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>
>
>
>_______________________________________________
>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
` dreamwvr
` Luke Davis
[not found] ` <Pine.BSF.4.43.0111301549410.66683-100000@server1.shellworl d.net>
` Brent Harding [this message]
` 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=3.0.6.32.20011130152649.0087da70@mail.doorpi.net \
--to=bharding@doorpi.net \
--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).