For me the archwiki is for getting started with a program. I use the gentoo one when I want to customize the experience
For me the archwiki is for getting started with a program. I use the gentoo one when I want to customize the experience
I’ve searched for it and xz also doesn’t use multithreading by default, you can change the program tar uses to compress by passing the -I
option. For xz using all possible CPU threads:
tar -cv -I 'xz -6 -T0' -f archive.tar.xz [list of directories]
The number indicates the compression ratio, the higher the number, the more compressed the archive will be but it will cost more in terms of memory and processing time
Does something similar happen using xz
?
I think the -j
also compresses with bzip2 but I’m not sure if this is defined behavior or just a shortcut
This script will unmount the problematic drive and try to mount it to another place /tmp/myprecious
, a temporary place.
Then, as it says, will attempt to read and then write to the drive.
Finally, it removes the file it wrote to test writeability, unmounts the drive again and removes the temporary mount place.
The scripts needs root access to mount and unmount and possibly to write and read.
Please don’t run a script you found on the internet with root access without knowing what it does.
The pasting of random commands is something wikis should avoid. The best option is saying the command and then explining what everything does but this is something that happens pretty rarely
Sometimes there is so much configuration options a GUI would scare most users. Or as you said, a GUI may not be feasible or useful
We’ll wait until 7.7.7 so all of the religious folk switch to linux