| Author |
Message |
rusty
*nix forums beginner
Joined: 31 Jul 2005
Posts: 5
|
 Posted: Sun Jul 31, 2005 7:22 pm Post subject:
unrar sytax
|
|
|
I'm attempting to unrar an archive that was e-mailed to me in several
volumes. Starting with mandrake 10.1, I installed plf unrar, changed
permissons to all executable (chmod 0755). Changed directory to location
of the 12 volume archive . Then using
bash unrar e /email/fun/temp/tripcancun1.rar
I get
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...>
<@listfiles...> <path_to_extract\>
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
Rusty |
|
| Back to top |
|
 |
Robert McKee
*nix forums Guru Wannabe
Joined: 13 Apr 2005
Posts: 106
|
| Posted: Sun Jul 31, 2005 9:24 pm Post subject:
Re: unrar sytax
|
|
|
rusty wrote:
| Quote: | I'm attempting to unrar an archive that was e-mailed to me in several
volumes. Starting with mandrake 10.1, I installed plf unrar, changed
permissons to all executable (chmod 0755). Changed directory to location
of the 12 volume archive . Then using
bash unrar e /email/fun/temp/tripcancun1.rar
I get
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...
@listfiles...> <path_to_extract\
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
Rusty
|
Rusty,
I am able to do this easily from within Ark. I have plf unrar installed. I
select the first archive choose the 'all' option within Ark, then unzip
into the directory of choice. It seems to find the other .rar archives
fine if they are in the same directory.
Robert |
|
| Back to top |
|
|
Stanislaw Flatto
*nix forums Guru Wannabe
Joined: 23 Feb 2005
Posts: 232
|
| Posted: Sun Jul 31, 2005 10:19 pm Post subject:
Re: unrar sytax
|
|
|
rusty wrote:
| Quote: | bash unrar e /email/fun/temp/tripcancun1.rar
I get
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...
@listfiles...> <path_to_extract\
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
|
You gave a command in CLI and bash responded by giving you the "help"
sentence as the command had parts (switches) missing.
So the best would be to go to "man rar" or "man unrar" (no quotes) and
get all the wisdom from there.
HTH
Stanislaw
Slack user from Ulladulla. |
|
| Back to top |
|
|
phlux0r
*nix forums Guru Wannabe
Joined: 28 Apr 2005
Posts: 105
|
| Posted: Sun Jul 31, 2005 11:59 pm Post subject:
Re: unrar sytax
|
|
|
rusty wrote:
| Quote: | bash unrar e /email/fun/temp/tripcancun1.rar
|
Did you actually type 'bash'? If so, you don't need it. At the command
prompt just type:
unrar e /email/fun/temp/tripcancun1.rar
That should work fine.
--
"While I thought that I was learning to live,
I have been learning how to die."
Leonardo DaVinci |
|
| Back to top |
|
|
rusty
*nix forums beginner
Joined: 31 Jul 2005
Posts: 5
|
| Posted: Mon Aug 01, 2005 2:49 am Post subject:
Re: unrar sytax
|
|
|
| Quote: | Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...
@listfiles...> <path_to_extract\
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
You gave a command in CLI and bash responded by giving you the "help"
sentence as the command had parts (switches) missing.
So the best would be to go to "man rar" or "man unrar" (no quotes) and
get all the wisdom from there.
HTH
Stanislaw
Slack user from Ulladulla.
|
I checked "man","help", and "info" first . the above is from "info" my
problem is where to put spaces and where not to; what is seperated by
commas or hypens or semicolons. Is one of the 4 commands manditory or is
there some basic default ? Same with switches. If your working dirrectory
is where all the volumes are, do you need to list a path to the archive?
How do you seperate the path of sources from path to extracked?
It seems as if each Unix command has a slightly different grammer and
syntax. Althought they follow a pattern there are minor differences,
trying to blindly duplicate paterns without understanding or having a
definitive reference is very frustrating. Sometimes my first attempt
works, sometimes I play with the command while reading "man" and I get
it right. Other times I just cannot get it to do what I want it to no
matter what.
Is there on the web or in print a true definitive guide ? My best
reference by far is Rute yet even it does not cover these details that can
make or break a simple one line command.
Thank you for your time,
Rusty |
|
| Back to top |
|
|
rusty
*nix forums beginner
Joined: 31 Jul 2005
Posts: 5
|
| Posted: Mon Aug 01, 2005 2:51 am Post subject:
Re: unrar sytax
|
|
|
On Sun, 31 Jul 2005 16:24:13 -0700, r.mckee wrote:
| Quote: | rusty wrote:
I'm attempting to unrar an archive that was e-mailed to me in several
volumes. Starting with mandrake 10.1, I installed plf unrar, changed
permissons to all executable (chmod 0755). Changed directory to location
of the 12 volume archive . Then using
bash unrar e /email/fun/temp/tripcancun1.rar
I get
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...
@listfiles...> <path_to_extract\
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
Rusty
Rusty,
I am able to do this easily from within Ark. I have plf unrar installed. I
select the first archive choose the 'all' option within Ark, then unzip
into the directory of choice. It seems to find the other .rar archives
fine if they are in the same directory.
Robert
|
Thanks Robert, ARK worked for me also.
Rusty |
|
| Back to top |
|
|
PRose
*nix forums addict
Joined: 09 Apr 2005
Posts: 51
|
| Posted: Mon Aug 01, 2005 3:31 am Post subject:
Re: unrar sytax
|
|
|
On Sun, 31 Jul 2005 21:22:07 +0000, rusty wrote:
| Quote: | I'm attempting to unrar an archive that was e-mailed to me in several
volumes. Starting with mandrake 10.1, I installed plf unrar, changed
permissons to all executable (chmod 0755). Changed directory to location
of the 12 volume archive . Then using
bash unrar e /email/fun/temp/tripcancun1.rar
I get
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...
@listfiles...> <path_to_extract\
I used the "e" command to extract to the current working directory
/email/fun/temp/
could somebody please explain how to read the "info" description to get
the proper syntax. thank you
Rusty
|
What's "bash"? If I were in your situation, I'd type "unrar e
tripcancun1.rar" Notice, there's only one space between the unrar, the e,
and the file name (if you're in the directory, you don't need to type the
absolute path). Actually, instead of typing out "tripcancun1.rar," I
would have typed "t<tab>1<tab>" -- helps to prevent typos.
HTH,
PRose |
|
| Back to top |
|
|
Stanislaw Flatto
*nix forums Guru Wannabe
Joined: 23 Feb 2005
Posts: 232
|
| Posted: Mon Aug 01, 2005 8:33 am Post subject:
Re: unrar sytax
|
|
|
rusty wrote:
| Quote: | I checked "man","help", and "info" first . the above is from "info" my
problem is where to put spaces and where not to; what is seperated by
commas or hypens or semicolons. Is one of the 4 commands manditory or is
there some basic default ? Same with switches. If your working dirrectory
is where all the volumes are, do you need to list a path to the archive?
How do you seperate the path of sources from path to extracked?
|
OK, let me dissapoint you (no offence intended).
In unix there are NO "commands", those are "requests" from simple
applications to perform some acts. What to do is _precisely_ defined by
the person issuing the request. And each app responds to a variety of
"switches", sometimes the same letter assignment doing different results
depending on particular app.
So if you have a particular application which you want to use daily
invest some time to get to know it, it may involve some "Damn!, Hell!
Stupid!" remarks but then the "coin drops" and everything is "so easy".
| Quote: |
It seems as if each Unix command has a slightly different grammer and
syntax. Althought they follow a pattern there are minor differences,
trying to blindly duplicate paterns without understanding or having a
definitive reference is very frustrating. Sometimes my first attempt
works, sometimes I play with the command while reading "man" and I get
it right. Other times I just cannot get it to do what I want it to no
matter what.
|
What can be done, Unix has a history of over 50 years, and the
underlying theme was/is "Develope an application that does _ONE_ thing,
but does it perfectly!" so we are saddled with a lot of little perfect
apps developed all over the world.
We are lucky that the "man" pages were and still are part of this design.
| Quote: |
Is there on the web or in print a true definitive guide ? My best
reference by far is Rute yet even it does not cover these details that can
make or break a simple one line command.
Thank you for your time,
Rusty
|
And where would you look, at last count there are more than 50 variants
of Unix, most of them commercial, plus its derivative Linux.
So when you have an app under one in this crowd learn just this one, it
maybe the same one in every one of them or it maybe different.
Have fun
Stanislaw
Slack user from Ulladulla. |
|
| Back to top |
|
|
Chris F.A. Johnson
*nix forums Guru
Joined: 20 Feb 2005
Posts: 2268
|
| Posted: Tue Aug 02, 2005 1:10 am Post subject:
Re: unrar sytax
|
|
|
On 2005-08-01, Stanislaw Flatto wrote:
| Quote: | rusty wrote:
I checked "man","help", and "info" first . the above is from "info" my
problem is where to put spaces and where not to; what is seperated by
commas or hypens or semicolons. Is one of the 4 commands manditory or is
there some basic default ? Same with switches. If your working dirrectory
is where all the volumes are, do you need to list a path to the archive?
How do you seperate the path of sources from path to extracked?
OK, let me dissapoint you (no offence intended).
In unix there are NO "commands", those are "requests" from simple
applications to perform some acts.
|
Really? I use dozens, if not hundreds, of commands.
Who posted:
| Quote: | You gave a command in CLI and bash responded by giving you the
"help" sentence as the command had parts (switches) missing.
|
(In that case, bash didn't respond, the unrar command did.)
| Quote: | What to do is _precisely_ defined by
the person issuing the request. And each app responds to a variety of
"switches", sometimes the same letter assignment doing different results
depending on particular app.
|
Switches? That DOS talk; you mean 'options'.
| Quote: | So if you have a particular application which you want to use daily
invest some time to get to know it, it may involve some "Damn!, Hell!
Stupid!" remarks but then the "coin drops" and everything is "so easy".
It seems as if each Unix command has a slightly different grammer and
syntax. Althought they follow a pattern there are minor differences,
trying to blindly duplicate paterns without understanding or having a
definitive reference is very frustrating. Sometimes my first attempt
works, sometimes I play with the command while reading "man" and I get
it right. Other times I just cannot get it to do what I want it to no
matter what.
What can be done, Unix has a history of over 50 years, and the
|
Only 35 or so. It started in 1969, and developed into a real OS
over the next five to ten years.
| Quote: | underlying theme was/is "Develope an application that does _ONE_ thing,
but does it perfectly!" so we are saddled with a lot of little perfect
apps developed all over the world.
We are lucky that the "man" pages were and still are part of this design.
|
Unfortunately, the Free Software Foundation doesn't like man
pages and often provides full documentation only in the clunky
info format.
| Quote: | Is there on the web or in print a true definitive guide ?
|
There is no "definitive" Unix. The closest there is is the Single
Unix Specification, which GNU/Linux and other *nix variants
follow with varying degrees of compliance.
| Quote: | My best reference by far is Rute yet even it does not cover these
details that can make or break a simple one line command.
|
There are far more details than can be covered in a single book.
For use of Unix commands, you can learn a lot from the archives
of the comp.unix.shell newsgroup.
| Quote: | And where would you look, at last count there are more than 50 variants
of Unix, most of them commercial, plus its derivative Linux.
So when you have an app under one in this crowd learn just this one, it
maybe the same one in every one of them or it maybe different.
|
The best place to look is the Single Unix Specification. With a
few exceptions, you can't go far wrong using the standard syntax:
<http://www.opengroup.org/onlinepubs/009695399/utilities/contents.html>
--
Chris F.A. Johnson <http://cfaj.freeshell.org>
==================================================================
Shell Scripting Recipes: A Problem-Solution Approach, 2005, Apress
<http://www.torfree.net/~chris/books/cfaj/ssr.html> |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
*nix
»
Linux
»
Distributions
»
Mandrake
