tar exits on “Cannot stat: No such file of directory”, why?
Clash Royale CLAN TAG#URR8PPP
I'm trying to create tar.gz file using the following command:
sudo tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
It then start to create files (many files in folder), but then I get the following error:
tar: dvr_rdk_v1.tar.gz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
I don't see any description of this error, what does it mean?
tar
add a comment |
I'm trying to create tar.gz file using the following command:
sudo tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
It then start to create files (many files in folder), but then I get the following error:
tar: dvr_rdk_v1.tar.gz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
I don't see any description of this error, what does it mean?
tar
add a comment |
I'm trying to create tar.gz file using the following command:
sudo tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
It then start to create files (many files in folder), but then I get the following error:
tar: dvr_rdk_v1.tar.gz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
I don't see any description of this error, what does it mean?
tar
I'm trying to create tar.gz file using the following command:
sudo tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
It then start to create files (many files in folder), but then I get the following error:
tar: dvr_rdk_v1.tar.gz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
I don't see any description of this error, what does it mean?
tar
tar
edited Mar 4 at 20:17
Kusalananda♦
139k17259430
139k17259430
asked Aug 10 '14 at 7:34
ranshransh
431259
431259
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
Remove -
from vcfz
options. tar
does not need hyphen for options.
With a hyphen, the argument for the -f
option is z
. So the command is in effect trying to archive dvr_rdk_v1.tar.gz
and dvr_rdk
into an archive called z
. Without the hyphen, the semantics of the options changes, so that the next argument on the command line, i.e. your archive's filename, becomes the argument to the f
flag.
Also check your write permission to the directory from which you are executing the command.
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
@MichaelMrozek Actually, removing the-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a-
, so the argument tof
is the next argument totar
, and sotar vcfz dvr_rdk_v1.tar.gz
is equivalent totar -v -c -f dvr_rdk_v1.tar.gz -z
.
– Gilles
Aug 10 '14 at 22:19
1
I also realized if I remove thez
orj
the archive compression is successful even with-
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I getj
orz
as an archived file if I use this option-cvfz
or-cvfj
.
– JohnnyQ
Sep 14 '16 at 2:11
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
add a comment |
The -f
option should directly precede the filename. So, use tar -vczf filename.tar.gz
instead of -vcfz
Ah this explains why the command I'm using tries to create a compressed archive file calledj
orz
with these commands-cvfj
and-cvfz
respectively.
– JohnnyQ
Sep 14 '16 at 2:14
add a comment |
The tar command historically has been one of the few commands that doesn't follow the Unix utility syntax guidelines.
The standards page for tar says:
f
Use the first file operand (or the second, if b has already been specified) as the name of the archive instead of the system-dependent default
While the syntax guidelines include this:
Guideline 5:
One or more options without option-arguments, followed by at most one option that takes an option-argument, should be accepted when grouped behind one '-' delimiter.
So while the command you typed, tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
, would be fine on older versions of tar, certain versions of tar that are written to strictly follow the utility syntax guidelines will parse this to mean "use z
as the file argument to -f
". So you should use the following to be portable:
tar -cvzf dvr_rdk_v1.tar.gz dvr_rdk/
add a comment |
To create the archive
$ tar -cvf music.tar Music/
This shows the list of file & folders
$ tar -tvf music.tar
And to extract again
$ tar -xvf music.tar
This does not really explain his error, right? This is just explaining the usage oftar
.
– Bernhard
Aug 10 '14 at 8:23
1
@Bernhard Well, his error was that he was usingtar
wrong, although it's nice to at least mention what the key difference is (moving-f
to the end)
– Michael Mrozek♦
Aug 10 '14 at 19:01
2
@MichaelMrozek Well, he rather left out thez
than putf
in the end, hence my comment.
– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
add a comment |
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f149494%2ftar-exits-on-cannot-stat-no-such-file-of-directory-why%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Remove -
from vcfz
options. tar
does not need hyphen for options.
With a hyphen, the argument for the -f
option is z
. So the command is in effect trying to archive dvr_rdk_v1.tar.gz
and dvr_rdk
into an archive called z
. Without the hyphen, the semantics of the options changes, so that the next argument on the command line, i.e. your archive's filename, becomes the argument to the f
flag.
Also check your write permission to the directory from which you are executing the command.
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
@MichaelMrozek Actually, removing the-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a-
, so the argument tof
is the next argument totar
, and sotar vcfz dvr_rdk_v1.tar.gz
is equivalent totar -v -c -f dvr_rdk_v1.tar.gz -z
.
– Gilles
Aug 10 '14 at 22:19
1
I also realized if I remove thez
orj
the archive compression is successful even with-
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I getj
orz
as an archived file if I use this option-cvfz
or-cvfj
.
– JohnnyQ
Sep 14 '16 at 2:11
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
add a comment |
Remove -
from vcfz
options. tar
does not need hyphen for options.
With a hyphen, the argument for the -f
option is z
. So the command is in effect trying to archive dvr_rdk_v1.tar.gz
and dvr_rdk
into an archive called z
. Without the hyphen, the semantics of the options changes, so that the next argument on the command line, i.e. your archive's filename, becomes the argument to the f
flag.
Also check your write permission to the directory from which you are executing the command.
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
@MichaelMrozek Actually, removing the-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a-
, so the argument tof
is the next argument totar
, and sotar vcfz dvr_rdk_v1.tar.gz
is equivalent totar -v -c -f dvr_rdk_v1.tar.gz -z
.
– Gilles
Aug 10 '14 at 22:19
1
I also realized if I remove thez
orj
the archive compression is successful even with-
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I getj
orz
as an archived file if I use this option-cvfz
or-cvfj
.
– JohnnyQ
Sep 14 '16 at 2:11
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
add a comment |
Remove -
from vcfz
options. tar
does not need hyphen for options.
With a hyphen, the argument for the -f
option is z
. So the command is in effect trying to archive dvr_rdk_v1.tar.gz
and dvr_rdk
into an archive called z
. Without the hyphen, the semantics of the options changes, so that the next argument on the command line, i.e. your archive's filename, becomes the argument to the f
flag.
Also check your write permission to the directory from which you are executing the command.
Remove -
from vcfz
options. tar
does not need hyphen for options.
With a hyphen, the argument for the -f
option is z
. So the command is in effect trying to archive dvr_rdk_v1.tar.gz
and dvr_rdk
into an archive called z
. Without the hyphen, the semantics of the options changes, so that the next argument on the command line, i.e. your archive's filename, becomes the argument to the f
flag.
Also check your write permission to the directory from which you are executing the command.
edited Mar 4 at 20:15
Kusalananda♦
139k17259430
139k17259430
answered Aug 10 '14 at 7:42
VelnixVelnix
61463
61463
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
@MichaelMrozek Actually, removing the-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a-
, so the argument tof
is the next argument totar
, and sotar vcfz dvr_rdk_v1.tar.gz
is equivalent totar -v -c -f dvr_rdk_v1.tar.gz -z
.
– Gilles
Aug 10 '14 at 22:19
1
I also realized if I remove thez
orj
the archive compression is successful even with-
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I getj
orz
as an archived file if I use this option-cvfz
or-cvfj
.
– JohnnyQ
Sep 14 '16 at 2:11
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
add a comment |
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
@MichaelMrozek Actually, removing the-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a-
, so the argument tof
is the next argument totar
, and sotar vcfz dvr_rdk_v1.tar.gz
is equivalent totar -v -c -f dvr_rdk_v1.tar.gz -z
.
– Gilles
Aug 10 '14 at 22:19
1
I also realized if I remove thez
orj
the archive compression is successful even with-
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I getj
orz
as an archived file if I use this option-cvfz
or-cvfj
.
– JohnnyQ
Sep 14 '16 at 2:11
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
6
6
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
It doesn't need hyphens, but they shouldn't be a problem, they're just optional
– Michael Mrozek♦
Aug 10 '14 at 19:00
16
16
@MichaelMrozek Actually, removing the
-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a -
, so the argument to f
is the next argument to tar
, and so tar vcfz dvr_rdk_v1.tar.gz
is equivalent to tar -v -c -f dvr_rdk_v1.tar.gz -z
.– Gilles
Aug 10 '14 at 22:19
@MichaelMrozek Actually, removing the
-
does make a difference, because GNU tar is quirky. Option arguments can't be bundled in the first argument when it doesn't start with a -
, so the argument to f
is the next argument to tar
, and so tar vcfz dvr_rdk_v1.tar.gz
is equivalent to tar -v -c -f dvr_rdk_v1.tar.gz -z
.– Gilles
Aug 10 '14 at 22:19
1
1
I also realized if I remove the
z
or j
the archive compression is successful even with -
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I get j
or z
as an archived file if I use this option -cvfz
or -cvfj
.– JohnnyQ
Sep 14 '16 at 2:11
I also realized if I remove the
z
or j
the archive compression is successful even with -
involved. When I add the hyphen is included it treats the last character in the option as a "file". So as a result I get j
or z
as an archived file if I use this option -cvfz
or -cvfj
.– JohnnyQ
Sep 14 '16 at 2:11
7
7
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
Summary: if 'f' occurs as an option anywhere other as than the last option, then the command will not do what was intended. I don't see how Gnu couldn't add a warning when they detect such a serious and easily-detectable issue. I just spent 40min trying to debug this weirdness. This one must have wasted hundreds of thousands of man-hours of productivity.
– smci
Oct 25 '17 at 1:14
add a comment |
The -f
option should directly precede the filename. So, use tar -vczf filename.tar.gz
instead of -vcfz
Ah this explains why the command I'm using tries to create a compressed archive file calledj
orz
with these commands-cvfj
and-cvfz
respectively.
– JohnnyQ
Sep 14 '16 at 2:14
add a comment |
The -f
option should directly precede the filename. So, use tar -vczf filename.tar.gz
instead of -vcfz
Ah this explains why the command I'm using tries to create a compressed archive file calledj
orz
with these commands-cvfj
and-cvfz
respectively.
– JohnnyQ
Sep 14 '16 at 2:14
add a comment |
The -f
option should directly precede the filename. So, use tar -vczf filename.tar.gz
instead of -vcfz
The -f
option should directly precede the filename. So, use tar -vczf filename.tar.gz
instead of -vcfz
edited Aug 10 '14 at 8:26
Bernhard
7,82034368
7,82034368
answered Aug 10 '14 at 7:56
twan163twan163
2,5203915
2,5203915
Ah this explains why the command I'm using tries to create a compressed archive file calledj
orz
with these commands-cvfj
and-cvfz
respectively.
– JohnnyQ
Sep 14 '16 at 2:14
add a comment |
Ah this explains why the command I'm using tries to create a compressed archive file calledj
orz
with these commands-cvfj
and-cvfz
respectively.
– JohnnyQ
Sep 14 '16 at 2:14
Ah this explains why the command I'm using tries to create a compressed archive file called
j
or z
with these commands -cvfj
and -cvfz
respectively.– JohnnyQ
Sep 14 '16 at 2:14
Ah this explains why the command I'm using tries to create a compressed archive file called
j
or z
with these commands -cvfj
and -cvfz
respectively.– JohnnyQ
Sep 14 '16 at 2:14
add a comment |
The tar command historically has been one of the few commands that doesn't follow the Unix utility syntax guidelines.
The standards page for tar says:
f
Use the first file operand (or the second, if b has already been specified) as the name of the archive instead of the system-dependent default
While the syntax guidelines include this:
Guideline 5:
One or more options without option-arguments, followed by at most one option that takes an option-argument, should be accepted when grouped behind one '-' delimiter.
So while the command you typed, tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
, would be fine on older versions of tar, certain versions of tar that are written to strictly follow the utility syntax guidelines will parse this to mean "use z
as the file argument to -f
". So you should use the following to be portable:
tar -cvzf dvr_rdk_v1.tar.gz dvr_rdk/
add a comment |
The tar command historically has been one of the few commands that doesn't follow the Unix utility syntax guidelines.
The standards page for tar says:
f
Use the first file operand (or the second, if b has already been specified) as the name of the archive instead of the system-dependent default
While the syntax guidelines include this:
Guideline 5:
One or more options without option-arguments, followed by at most one option that takes an option-argument, should be accepted when grouped behind one '-' delimiter.
So while the command you typed, tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
, would be fine on older versions of tar, certain versions of tar that are written to strictly follow the utility syntax guidelines will parse this to mean "use z
as the file argument to -f
". So you should use the following to be portable:
tar -cvzf dvr_rdk_v1.tar.gz dvr_rdk/
add a comment |
The tar command historically has been one of the few commands that doesn't follow the Unix utility syntax guidelines.
The standards page for tar says:
f
Use the first file operand (or the second, if b has already been specified) as the name of the archive instead of the system-dependent default
While the syntax guidelines include this:
Guideline 5:
One or more options without option-arguments, followed by at most one option that takes an option-argument, should be accepted when grouped behind one '-' delimiter.
So while the command you typed, tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
, would be fine on older versions of tar, certain versions of tar that are written to strictly follow the utility syntax guidelines will parse this to mean "use z
as the file argument to -f
". So you should use the following to be portable:
tar -cvzf dvr_rdk_v1.tar.gz dvr_rdk/
The tar command historically has been one of the few commands that doesn't follow the Unix utility syntax guidelines.
The standards page for tar says:
f
Use the first file operand (or the second, if b has already been specified) as the name of the archive instead of the system-dependent default
While the syntax guidelines include this:
Guideline 5:
One or more options without option-arguments, followed by at most one option that takes an option-argument, should be accepted when grouped behind one '-' delimiter.
So while the command you typed, tar -vcfz dvr_rdk_v1.tar.gz dvr_rdk/
, would be fine on older versions of tar, certain versions of tar that are written to strictly follow the utility syntax guidelines will parse this to mean "use z
as the file argument to -f
". So you should use the following to be portable:
tar -cvzf dvr_rdk_v1.tar.gz dvr_rdk/
answered Aug 10 '14 at 8:33
Mark PlotnickMark Plotnick
18.7k24068
18.7k24068
add a comment |
add a comment |
To create the archive
$ tar -cvf music.tar Music/
This shows the list of file & folders
$ tar -tvf music.tar
And to extract again
$ tar -xvf music.tar
This does not really explain his error, right? This is just explaining the usage oftar
.
– Bernhard
Aug 10 '14 at 8:23
1
@Bernhard Well, his error was that he was usingtar
wrong, although it's nice to at least mention what the key difference is (moving-f
to the end)
– Michael Mrozek♦
Aug 10 '14 at 19:01
2
@MichaelMrozek Well, he rather left out thez
than putf
in the end, hence my comment.
– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
add a comment |
To create the archive
$ tar -cvf music.tar Music/
This shows the list of file & folders
$ tar -tvf music.tar
And to extract again
$ tar -xvf music.tar
This does not really explain his error, right? This is just explaining the usage oftar
.
– Bernhard
Aug 10 '14 at 8:23
1
@Bernhard Well, his error was that he was usingtar
wrong, although it's nice to at least mention what the key difference is (moving-f
to the end)
– Michael Mrozek♦
Aug 10 '14 at 19:01
2
@MichaelMrozek Well, he rather left out thez
than putf
in the end, hence my comment.
– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
add a comment |
To create the archive
$ tar -cvf music.tar Music/
This shows the list of file & folders
$ tar -tvf music.tar
And to extract again
$ tar -xvf music.tar
To create the archive
$ tar -cvf music.tar Music/
This shows the list of file & folders
$ tar -tvf music.tar
And to extract again
$ tar -xvf music.tar
edited Aug 10 '14 at 8:22
Bernhard
7,82034368
7,82034368
answered Aug 10 '14 at 7:56
dhamudhamu
2416
2416
This does not really explain his error, right? This is just explaining the usage oftar
.
– Bernhard
Aug 10 '14 at 8:23
1
@Bernhard Well, his error was that he was usingtar
wrong, although it's nice to at least mention what the key difference is (moving-f
to the end)
– Michael Mrozek♦
Aug 10 '14 at 19:01
2
@MichaelMrozek Well, he rather left out thez
than putf
in the end, hence my comment.
– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
add a comment |
This does not really explain his error, right? This is just explaining the usage oftar
.
– Bernhard
Aug 10 '14 at 8:23
1
@Bernhard Well, his error was that he was usingtar
wrong, although it's nice to at least mention what the key difference is (moving-f
to the end)
– Michael Mrozek♦
Aug 10 '14 at 19:01
2
@MichaelMrozek Well, he rather left out thez
than putf
in the end, hence my comment.
– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
This does not really explain his error, right? This is just explaining the usage of
tar
.– Bernhard
Aug 10 '14 at 8:23
This does not really explain his error, right? This is just explaining the usage of
tar
.– Bernhard
Aug 10 '14 at 8:23
1
1
@Bernhard Well, his error was that he was using
tar
wrong, although it's nice to at least mention what the key difference is (moving -f
to the end)– Michael Mrozek♦
Aug 10 '14 at 19:01
@Bernhard Well, his error was that he was using
tar
wrong, although it's nice to at least mention what the key difference is (moving -f
to the end)– Michael Mrozek♦
Aug 10 '14 at 19:01
2
2
@MichaelMrozek Well, he rather left out the
z
than put f
in the end, hence my comment.– Bernhard
Aug 10 '14 at 19:06
@MichaelMrozek Well, he rather left out the
z
than put f
in the end, hence my comment.– Bernhard
Aug 10 '14 at 19:06
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
This command working for ubuntu, It will success
– dhamu
Sep 6 '14 at 13:23
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
OK! sorry, I am not listening you question, but the command working for ubuntu.
– dhamu
Sep 6 '14 at 13:32
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f149494%2ftar-exits-on-cannot-stat-no-such-file-of-directory-why%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown