04-16-2002
Check the man page!!
Found in the man page for tar -
x Extract or restore. The named files are extracted from
the tarfile and written to the directory specified in
the tarfile, relative to the current directory. Use
the relative path names of files and directories to be
extracted. If a named file matches a directory whose
contents has been written to the tarfile, this direc-
tory is recursively extracted. The owner, modification
time, and mode are restored (if possible); otherwise,
to restore owner, you must be the super-user.
Character-special and block-special devices (created by
mknod(1M)) can only be extracted by the super-user. If
no file argument is given, the entire content of the
tarfile is extracted. If the tarfile contains several
files with the same name, each file is written to the
appropriate directory, overwriting the previous one.
Filename substitution wildcards cannot be used for
extracting files from the archive; rather, use a com-
mand of the form:
tar xvf... /dev/rmt/0 `tar tf... /dev/rmt/0 |grep 'pattern'`
This works great - you just set the pattern to ".pds"
To do a directory in UNIX - ls *.pds (UNIX does not have the same restrictions as VMS - files do not need extensions - you will find it will free the mind. The only thing I have found that works better in VMS is search (ie. grep).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi. I have been having problems with restoring from a tape backup. I use the following cpio command:
find / -print | cpio -ouvB > /dev/rStp0
After running this cpio command, the screen will display all files, but when I try to read or restore the tape I get the following error:
Tape input... (1 Reply)
Discussion started by: cstovall
1 Replies
2. Filesystems, Disks and Memory
I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now.
The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ".
This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies
3. HP-UX
I am trying to do a restore on a backup tape (DDS2) and am having a little trouble. For one, I dont know how the tape was made, whether is was tar, cpio, dump..etc. Anyone know how to restore a tape without knowing the format of the backup? (5 Replies)
Discussion started by: bake255
5 Replies
4. AIX
Hello everyone
I have a tape with some information that I got
to restore, the tape was made with the fbackup
command in a hp box.
My question is that I have to restore in a Ibm
box, how can I do this ?
Thanks in advance (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
5. SCO
Here is the scenario. We have an billing system that ran on SCO 5.0.6. The HP Netserver went dwon, along with SCSI disks. They are unretrievable. I installed an IDE HDD, and reinstalled SCO. I am not too familiar w/ SCO or UNIX, and need to know how to install Tape drive, and how to restore from... (11 Replies)
Discussion started by: jlewis808
11 Replies
6. SCO
I am a mewbie to UNIX. I am using SCO Open Server 5 to run a legacy medical billing program "MDX" I have backup tapes made on HP DataStore8 which have the application and data files. Recently unable to login as individual user but can log into root. Previous commands that had restored the system... (5 Replies)
Discussion started by: canbe842
5 Replies
7. Solaris
I have a T2000 server that is JumpStarted with Solaris 10 from the JumpStart server. Host name and IP address is changed after that. Then we backup the server using FLAR to tape:
root.damas# date; flarcreate -c -t -n "Sol10_cairo_image" -a "engineering@starsolutions.com" -R / /dev/rmt/0n ;... (2 Replies)
Discussion started by: StarSol
2 Replies
8. Solaris
Hope someone can help me here...
I've got to restore an E450 with 300MHz cpus which was running Solaris 2.6 from tape. Regrettably the boot drive has failed.
I've access to the first release of Solaris 2.6 CD's and to a set of Solaris 9 CD's.
I remember that different E450 CPUs needed different... (1 Reply)
Discussion started by: pamplemousse
1 Replies
9. Emergency UNIX and Linux Support
Hi
I recently deleted my /etc but I had a backup on tape. I was able to boot the server with a cd-rom and mounted the /c1t0d0s0 which is where the root directory resides. However when I tried to restore the backup with tar xvf /dev/rmt/0n I wasn't successful even though I was able to use the tar... (2 Replies)
Discussion started by: rahmantanko
2 Replies
10. AIX
Hi,
I have taken a backup of a directory on my tape in using below command
cd /backup
find * -print|backup -ivf '/dev/rmt0' '-U' |tee -a /syslogs/backup.log and output appear in below format.
a 0 rman-before-08032014
a 58403323904... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies
LEARN ABOUT FREEBSD
deb-old
deb-old(5) dpkg suite deb-old(5)
NAME
deb-old - old style Debian binary package format
SYNOPSIS
filename.deb
DESCRIPTION
The .deb format is the Debian binary package file format. This manual page describes the old format, used before Debian 0.93. Please see
deb(5) for details of the new format.
FORMAT
The file is two lines of format information as ASCII text, followed by two concatenated gzipped ustar files.
The first line is the format version number padded to 8 digits, and is 0.939000 for all old-format archives.
The second line is a decimal string (without leading zeroes) giving the length of the first gzipped tarfile.
Each of these lines is terminated with a single newline character.
The first tarfile contains the control information, as a series of ordinary files. The file control must be present, as it contains the
core control information.
In some very old archives, the files in the control tarfile may optionally be in a DEBIAN subdirectory. In that case, the DEBIAN
subdirectory will be in the control tarfile too, and the control tarfile will have only files in that directory. Optionally the control
tarfile may contain an entry for '.', that is, the current directory.
The second gzipped tarfile is the filesystem archive, containing pathnames relative to the root directory of the system to be installed on.
The pathnames do not have leading slashes.
SEE ALSO
deb(5), dpkg-deb(1), deb-control(5).
1.19.0.5 2018-04-16 deb-old(5)