public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Hart Larry <chime@hubert-humphrey.com>
To: Blinux Discussion List <blinux-list@redhat.com>
Subject: Lots of Trouble Extracting .rar Files?
Date: Sat, 19 Jun 2004 09:28:07 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.60.0406190919580.62331@server2.shellworld.net> (raw)

I must have posted this earlier to the subscription address instead?  For some 
years I have been collecting rar encoded binaries from usenet.  I either grab 
messages in pine and run uudeview to decode, or grab files directly from an 
easynews web site.  Most of these rars find nothing to extract.  I can still 
extract older rars with .mod music files from years ago.
I am running unrar and rar in linux, with a Dec-PC, Speakup Fedora 1.
Also, many are posting par2 files incase we miss any of the rars.  We grabbed a 
linux program to handle these, however, I cannot find any command-line options 
to put everything together.
Are their any smarter rar extracting programs which any of you can please 
suggest which also handle wild cards?  Thanks so much in advance
Hart


                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.BSF.4.60.0406190919580.62331@server2.shellworld.net \
    --to=chime@hubert-humphrey.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).