You have to store data somewhere. We have two choices - memory or mass storage (tape, disk, etc). You just eliminated one, so we are left with memory. That means a program has to receive the data
When tar outputs, not just data comes out, also metadata. So you get to filter it out, I don't know how to do that a priori.
Your program has to read from stdin, pitch metadata, and then keep real data. I wonder what you do with it then if you don't put some of it to disk or the tty.
The only point I would make is this is an odd request as tar is inherently slower than disk I/O, so why would you do all this? No spare disk space?
Hey guys complete n00b here so I'll try my best at explaining.
I'm creating a backup and restore utility and decided to use tar. I create a backup folder in each user's account and when backing up (say word processing files), I use the following:
tar cvf /home/user/backup/wpbackup.tar... (2 Replies)
hi,
I am in a weird situation. I have a parent tarball which contains 2 sub tarballs.
The structure is such :
Parent.tar.gz ---- > child1.tar.gz and child2.tar.gz
I need to get the size of the parent tarball without untaring it
I know that the command is gunzip -c parent.tar.gz | wc -c ... (1 Reply)
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)
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)
Hi All,
I would like to know couple of ways to list the content available in tar and gzipped file without extracting.
i.e., I would like to display the contents of test.tar.gz without extracting.
Note :: please suggest a command other that tar -ztvf (9 Replies)
#cat a
BAC064DAL
BAC063DAL
BAC056PHX
BAC066DAL
BAC062PHX
BAC062DAL
BAC060DAL
BAC058PHX
BAC054PHX
BAC051PHX
# for i in `cat a`
> do
> tar xvf $a/$a*.tar*
> done
tar: /*.tar*: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: /*.tar*: Cannot... (3 Replies)
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)
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)
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)
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
LEARN ABOUT FREEBSD
fdwrite
FDWRITE(1) BSD General Commands Manual FDWRITE(1)NAME
fdwrite -- format and write floppy disks
SYNOPSIS
fdwrite [-v] [-y] [-f inputfile] [-d device]
DESCRIPTION
The fdwrite utility formats and writes one and more floppy disks. Any floppy disk device capable of formatting can be used.
The fdwrite utility will ask the user (on /dev/tty) to insert a new floppy and press return. The device will then be opened, and queried for
its parameters, then each track will be formatted, written with data from the inputfile, read back and compared. When the floppy disk is
filled, the process is repeated, with the next disk. This continues until the program is interrupted or EOF is encountered on the inputfile.
The options are as follows:
-v Toggle verbosity on stdout. Default is ``on''. After device is opened first time the format will be printed. During
operation progress will be reported with the number of tracks remaining on the current floppy disk, and the letters I, Z,
F, W, R and C, which indicates completion of Input, Zero-fill, Format Write, Read and Compare of current track respec-
tively.
-y Do not ask for presence of a floppy disk in the drive. This non-interactive flag is useful for shell scripts.
-f inputfile
Input file to read. If none is given, stdin is assumed.
-d device The name of the floppy device to write to. Default is /dev/fd0.
The fdwrite utility actually closes the device while it waits for the user to press return, it is thus quite possible to use the drive for
other purposes at this time and later resume writing with the next floppy.
The parameters returned from device are used for formatting. If custom formatting is needed, please use fdformat(1) instead.
EXAMPLES
The fdwrite utility was planned as a tool to make life easier when writing a set of floppies, one such use could be to write a tar-archive:
tar cf -. | gzip -9 | fdwrite -d /dev/fd0.1720 -v
The main difference from using tar(1)'s multivolume facility is of course the formatting of the floppies, which here is done on the fly, thus
reducing the amount of work for the floppy-jockey.
SEE ALSO fdformat(1)HISTORY
The fdwrite utility was written while waiting for ``make world'' to complete. Some of the code was taken from fdformat(1).
AUTHORS
The program has been contributed by Poul-Henning Kamp <phk@FreeBSD.org>.
BUGS
Diagnostics are less than complete at present.
If a floppy is sick, and the inputfile is seekable, it should ask the user to frisbee the disk, insert another, and rewind to the right spot
and continue.
This concept could be extended to cover non-seekable input also by employing a temporary file.
An option (defaulting to zero) should allow the user to ask for retries in case of failure.
At present a suitable tool for reading back a multivolume set of floppies is missing. Programs like tar(1) for instance, will do the job, if
the data has not been compressed. One can always trust dd(1) to help out in this situation of course.
BSD September 16, 1993 BSD