06-15-2015
Can you please elaborate what exactly is your requirement here
10 More Discussions You Might Find Interesting
1. BSD
Hello,
I have a little problem with backup & restoring files from tape drive.
I am adding 3 directories to my tape, and it is OK:
hades# tar -cvf /dev/nsa0 test test1 restore
a test
a test/level1
a test/myharddisk.img
a test1
a test1/level1
a test1/myharddisk.img
a test1/test.img
a... (1 Reply)
Discussion started by: d3m00n
1 Replies
2. Solaris
Hello all.
I have a tar file that contains a number of files that are stored in different directories.
If I extract this tar file with -xvf , the directories get created.
Is there a way to extract all of the files into one directory without creating the directories stored in the tar file. (9 Replies)
Discussion started by: gkb
9 Replies
3. Shell Programming and Scripting
Hi,
I'm using a tar command
tar -xOvf /home/mytar.tar
My intention is to extract data in files which are inside various directories,
without extracting files to the disk.
Is this the best way to achieve it?
Thanks,
Chetan (3 Replies)
Discussion started by: chetan.c
3 Replies
4. Shell Programming and Scripting
Hi,
I have tar filw which has multiple directories which contain files.
When i extract using tar -xf the directory structure also get extracted.
I require only files and not directory structures as there will be overhead of moving the files again.
So i searched here and got a solution but... (4 Replies)
Discussion started by: chetan.c
4 Replies
5. UNIX for Advanced & Expert Users
Hi
Somebody must have done this before, but I can't seem to find any answer on my problem.
On HP-UX 11i v3 I have a relatively large tar ball (~120 GB), and I want to create the directory structure only from the archive.
There is no option to make a new archive with only the directory... (3 Replies)
Discussion started by: hpvm_adm
3 Replies
6. Shell Programming and Scripting
i extract it through script, is there any way to script or automate to tar extract a tarfiles in multiple directories at once?
Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
for dir in `ls -d /tarfiles/*/ | sed 's/.$//'`
do
rm -f $dir/*.tar
mv -f... (1 Reply)
Discussion started by: kenshinhimura
1 Replies
7. Shell Programming and Scripting
Hi,
uname -a
SunOS mymac 5.11 11.2 sun4u sparc SUNW,SPARC-Enterprise
I need to tar a folder /tmp/moht but do not want these three folders to be included in the tar file -> savejpg, bmpsave and imgsave
I tried --exclude, -path, -not options but it says bad option
Can you help me with... (3 Replies)
Discussion started by: mohtashims
3 Replies
8. Shell Programming and Scripting
I have a tar file hello.tar which is 95 GB.
hello.tar has many files and folders including some tar files as well.
I wish to create a new tar ball which should maintain only the folder structure of hello.tar and the tar ball within the hello.tar
So basically the idea is to untar... (2 Replies)
Discussion started by: mohtashims
2 Replies
9. Shell Programming and Scripting
Hi all. I'm hitting a problem creating a tar archive in one directory from files located in a different directory. It fails when I replace the absolute paths with variables in the script but works if I just run tar on the cmdln. E.g.
#!/bin/ksh
BASE=$PWD
STAGE=$BASE/stage
LOG=$BASE/log... (4 Replies)
Discussion started by: user052009
4 Replies
10. Shell Programming and Scripting
Hi Team,
Following unix command is throwing error. Can anyone please help me to fix the issue?
tar -cvf /aa/bb/cc/tarball1.tar /x/y/z1/abc.ksh /x/y/z2/pqr.txt /x/y/z3/lmn.tmp
Error message thrown:
tar: Removing leading `/' from member names
OS: uname -a
Linux xyz... (1 Reply)
Discussion started by: kmanivan82
1 Replies
CSREQ(1) BSD General Commands Manual CSREQ(1)
NAME
csreq -- Expert tool for manipulating Code Signing Requirement data
SYNOPSIS
csreq [-v] -r requirement-input -t
csreq [-v] -r requirement-input -b outputfile
DESCRIPTION
The csreq command manipulates Code Signing Requirement data. It reads one requirement from a file or command arguments, converts it into
internal form, checks it, and then optionally outputs it in a different form.
The options are as follows:
-b path
Requests that the requirement read be written in binary form to the path given.
-r requirement-input
Specifies the input requirement. See "specifying requirements" below. This is exactly the same format as is accepted by the -r and -R
options of the codesign(1) command.
-t Requests that the requirement read be written as text to standard output.
-v Increases the verbosity of output. Multiple instances of -v produce increasing levels of commentary output.
In the first synopsis form, csreq reads a Code Requirement and writes it to standard output as canonical source text. Note that with text
input, this actually compiles the requirement into internal form and then converts it back to text, giving you the system's view of the
requirement code.
In the second synopsis form, csreq reads a Code Requirement and writes its binary representation to a file. This is the same form produced by
the SecRequirementCopyData API, and is readily acceptable as input to Code Signing verification APIs. It can also be used as input to subse-
quent invocations of csreq by passing the filename to the -r option.
SPECIFYING REQUIREMENTS
The requirement argument (-r) can be given in various forms. A plain text argument is taken to be a path to a file containing the require-
ment. This program will accept both binary files containing properly compiled requirements code, and source files that are automatically com-
piled for use. An argument of "-" requests that the requirement(s) are read from standard input. Again, standard input can contain either
binary form or text. Finally, an argument that begins with an equal sign "=" is taken as a literal requirements source text, and is compiled
accordingly for use.
EXAMPLES
To compile an explicit requirement program and write its binary form to file "output":
csreq -r="identifier com.foo.test" -b output.csreq
To display the requirement program embedded at offset 1234 of file "foo":
tail -b 1234 foo | csreq -r- -t
FILES
DIAGNOSTICS
The csreq program exits 0 on success or 1 on failure. Errors in arguments yield exit code 2.
SEE ALSO
codesign(1)
HISTORY
The csreq command first appeared in Mac OS 10.5.0 .
BSD
June 1, 2006 BSD