Hot answers tagged tar
Tape devices under Unix are a bit unique in that they are record-oriented rather than being a stream of bytes. So each record written to tape must be a round multiple of some block size, usually 512 bytes, and must be done in a single write call. Each tape device will have lower and upper bounds for the record size. Similarly, you have to read a record in a ...
GNU tar's --index-file option works well: tar cvf - ./foo 2>foo.err --index-file=foo.out | squish > foo.tar.S
My first time here. I wonder whether you can list the files without attempting a restore just yet. You could try doing that with tar -tvf /dev/rmt0 And also, is it possible that you could capture the output to a file rather than to STDOUT (your screen)? tar -tvf /dev/rmt0 1>/tmp/rest.out 2>/tmp/rest.err A couple of other areas to look at. Is it ...
The other answers on here are great, but I wanted to create a completely automated installation script. I hope this helps someone. #!/bin/bash sudo apt-get install -y cmake yasm libjpeg-dev libsdl-image1.2-dev libsdl1.2-dev pushd /tmp wget -O libpng-1.6.21.tar.xz ...
Simplest answer: Add --exclude-vcs --exclude-vcs This excludes all version control system directories Personally I use tar -zcvf foo.tar.gz ./FOLDER_NAME --exclude-vcs so all you need to do is add the --exclude-vcs at the end of the command.
This is pretty interesting: a wrong block size using the dd command also generates an out of memory error. Using 'dd' (disk dump) to verify Tivoli Storage Manager tape volume labels To view or change the block size on a tape drive, you could use: lsattr -El rmt0 -a block_size And to change it, for example to variable, chdev -l rmt0 -a block_size=0 ...
In this situation you should use the tar --numeric-owner option. The files in the archive were created using the user IDs from the /etc/passwd file that's in the archive. It's possible that users and groups exist in the archive with different numeric IDs than on the Live DVD image. Even if you ran the same Live DVD each time, there can still be different ...
This the command you will need: find . -type d -print0 | tar cf folderstructure.tar --null --files-from - --no-recursion it generates the file folderstructure.tar with the folder structure without the files.
If You are using MAC OS It turns out this is just an issue with tar files created on Mac OS X. Mac OS X uses BSD tar and creates some extra info that is not recognized by GNU tar. Solution: Don’t Worry About It What should you do about this? You don’t need to do anything. Your files will be extracted correctly, so you can safely ignore these warnings or ...
Only top voted, non community-wiki answers of a minimum length are eligible