This works with lspci and if it's outdated may not give you the exact manufacturer and device model.
For example take these 3 different RX 580's:
1a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 67df (rev e7)
1b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 67df (rev e7)
1d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 67df (rev e7)
This is an important feature a failed read can genuinely occur if a temporary file has been removed or if you try backing up a sysetm file in /proc /sys (which you shouldn't really anyway).
The way to fix this is the following switch:
sudo tar --ignore-failed-read -czvf mycomputer-backup.tar.gz --exclude=/home/otheruser/* --exclude=/proc/* --e........
I believe from what I've read that this card's driver doesn't support the features after trying all known troubleshooting methods.
ffmpeg -i uservideoRendered.mp4 -filter:v hwupload_cuda,scale_npp=w=1920:h=1080:format=nv12:interp_algo=lanczos,hwdownload -c:v hevc_nvenc -profile main -preset slow -rc vbr_hq -c:a copy uservideoRendered.mp4-test
ffmpeg -i uservideoRendered.mp4 -filter:v hwupload_cuda,scale_npp=w=1920:h=1080:format=nv12:interp_algo=lanczos,hwdownload........
For the first two entries comment out #mirrorlist and uncomment #baseurl and then it worked
openvz yum problem Centos 6.5 cannot find file on mirror:
Loaded plugins: fastestmirror
Determining fastest mirrors
* openvz-kernel-rhel6: mirrors.ustc.edu.cn
* openvz-utils: mirrors.ustc.edu.cn
tar -czf yourfile.tar.gz .
The . dot is the crucial part, normally many will use * and that will exclude hidden files by default which is very undesirable as many hidden files are important such as .htaccess and conf files in your home directory etc.. It seems the default behavior of tar should be the opposite but these are all very old tools.........
The folder I was trying to archive is about 72GB, but much like rsync at about 17GB it chokes because of the filesize. What's with so many common and essential Linux tools having such limitations? I guess it is likely that the authors never wrote their code with the idea that files would be so large but it's still very annoying. It's important to stay on top of these limitations on production servers because I didn't realize what happened until I checked the file with "........
Tar & Encrypt in the same command![code:1:f2c600dbb6]tar -cz --file=tarfile.tar `gpg -e -r email@address file.name`[/code:1:f2c600dbb6]
Notice the back ticks in the place where the filename would normally be. This will let us encrypt and tar any files/directories!........