06-25-2010
Thanks vgersh99!
so, this "listOfFilesFile" should be a directory I should have already created and where the new files will be dumped to?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All.
im a noob to scripting. could somone help me with a script please.
what i want to do is.
1. run a cmd in the script - qmqtool -s
this will give me an output similar to this.
Messages in local queue: 790
Messages in remote queue: 306
Messages in todo queue: 23
i then want... (1 Reply)
Discussion started by: aron
1 Replies
2. UNIX for Dummies Questions & Answers
Hello. Complete newbie over here, and I'm hoping you can help me out with this problem.
The script copies a file to a directory within my home dir.
Permissions are ok and the source file exists. If I execute the cp command from the command line or hardcode the path/file name, it works.
... (6 Replies)
Discussion started by: verdugan
6 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I'm trying to create the shell script that:
copy (or transfer) the directory from the unix server to my external hard drive (or hard drive)
I've been serching this kind of thread here, but no luck so far. anyone can help me? Thank you. (2 Replies)
Discussion started by: myjwjw
2 Replies
4. Shell Programming and Scripting
Writing a bash script for use with Geektool, pulls the battery info, and shuffles images around so that an Image geeklet can display the correct expression as the desktop background. (Eventually I intend to make it more intricate, based on more variables, and add more expressions)
I'm extremely... (1 Reply)
Discussion started by: The_Ardly374
1 Replies
5. Shell Programming and Scripting
Hello everyone
I am completely new to shell scripting in linux. I wan to write a script to search for a certain string from a .txt file and copy the string which apears just after tat searched string.
Eg: in a file- try.txt , we have a line saying: "roses are red, so what do i do"
I... (4 Replies)
Discussion started by: Kishore920
4 Replies
6. Shell Programming and Scripting
Hello,
I'm new to this forum and like to first of all say hello to everyone.
I've got a really annoying problem at the moment.
I'm trying to rsync some files (about 200MB with one file of 120MB) from a Raspberry PI with raspbian to a debian server via rsync.
This procedure is stored in a... (3 Replies)
Discussion started by: wex_storm
3 Replies
7. Shell Programming and Scripting
Dear All,
I have a situation where I want to copy some files of type .txt.
These files are o/p from one program. Some of the files are named as
fileName .txt instead of fileName.txt
after fileName by mistake I have specified "space". Now I want to move these files as follows.
mv fileName*... (13 Replies)
Discussion started by: linuxUser_
13 Replies
8. Shell Programming and Scripting
Hello,
I'm trying to write a script in Dialog for configuring a router. I basically need the user to select from a list of say 4 options, confirm the option and then copy the configuration files, depending on the choice to the HDD and then reboot (I'm hoping to boot from a USB stick).
The... (0 Replies)
Discussion started by: pm77
0 Replies
9. Shell Programming and Scripting
Hello All,
I have a file of ip addresses called activeips.txt
What I'm trying to do is run a simple bash script that has a loop in it. The loop is a cat of the IP addresses in the file.
The goal is to run 2 nmap commands to give me outputs where each address in the list has an OS... (11 Replies)
Discussion started by: Dirk_Pitt
11 Replies
10. UNIX for Beginners Questions & Answers
The bash stores each uniqueid in an array and then passes them to %q to get the unique path. That seems to work what I am having trouble with is renaming each .png with the unique value in %q. I thought it was working but upon closer inspection, a .png file is being sent to scp.... but only 1 and... (21 Replies)
Discussion started by: cmccabe
21 Replies
TAR(5) File Formats Manual TAR(5)
NAME
tar - tape archive file format
DESCRIPTION
Tar, (the tape archive command) dumps several files into one, in a medium suitable for transportation.
A ``tar tape'' or file is a series of blocks. Each block is of size TBLOCK. A file on the tape is represented by a header block which
describes the file, followed by zero or more blocks which give the contents of the file. At the end of the tape are two blocks filled with
binary zeros, as an end-of-file indicator.
The blocks are grouped for physical I/O operations. Each group of n blocks (where n is set by the b keyletter on the tar(1) command line
-- default is 20 blocks) is written with a single system call; on nine-track tapes, the result of this write is a single tape record. The
last group is always written at the full size, so blocks after the two zero blocks contain random data. On reading, the specified or
default group size is used for the first read, but if that read returns less than a full tape block, the reduced block size is used for
further reads.
The header block looks like:
#define TBLOCK 512
#define NAMSIZ 100
union hblock {
char dummy[TBLOCK];
struct header {
char name[NAMSIZ];
char mode[8];
char uid[8];
char gid[8];
char size[12];
char mtime[12];
char chksum[8];
char linkflag;
char linkname[NAMSIZ];
} dbuf;
};
Name is a null-terminated string. The other fields are zero-filled octal numbers in ASCII. Each field (of width w) contains w-2 digits, a
space, and a null, except size and mtime, which do not contain the trailing null and chksum which has a null followed by a space. Name is
the name of the file, as specified on the tar command line. Files dumped because they were in a directory which was named in the command
line have the directory name as prefix and /filename as suffix. Mode is the file mode, with the top bit masked off. Uid and gid are the
user and group numbers which own the file. Size is the size of the file in bytes. Links and symbolic links are dumped with this field
specified as zero. Mtime is the modification time of the file at the time it was dumped. Chksum is an octal ASCII value which represents
the sum of all the bytes in the header block. When calculating the checksum, the chksum field is treated as if it were all blanks. Link-
flag is NULL if the file is ``normal'' or a special file, ASCII `1' if it is an hard link, and ASCII `2' if it is a symbolic link. The
name linked-to, if any, is in linkname, with a trailing null. Unused fields of the header are binary zeros (and are included in the check-
sum).
The first time a given i-node number is dumped, it is dumped as a regular file. The second and subsequent times, it is dumped as a link
instead. Upon retrieval, if a link entry is retrieved, but not the file it was linked to, an error message is printed and the tape must be
manually re-scanned to retrieve the linked-to file.
The encoding of the header is designed to be portable across machines.
SEE ALSO
tar(1)
BUGS
Names or linknames longer than NAMSIZ produce error reports and cannot be dumped.
4.2 Berkeley Distribution November 7, 1985 TAR(5)