Blocklist-Update.sh is a script that I wrote to manage blocklists from bluetack etc to be used in conjunction with Transmission torrent downloader in Linux/MacOS. The script can be taylored to work with Qbittorrent as well, but the placement of the blocklists means you'd have to redirect the blocklist to go somewhere locally manageable as Transmission uses its own blocklist directory in .config. I believe there are about 10 lists there now. It works well for my needs. It can be ran weekly using crontab in standard user profile. To download: blocklist-update.sh To download the others: Github
For
those who are running older systems, and I’m talking systems with
ancient AMD chips and Nvidia graphics. You might have updated kernels
in Linux lately and got the following message; Spectre mitigation V2
LFENCE not serializing. What this most likely means is that AMD is
pretty hardy and it turns out that most AMD processors were not as
vulnerable as the Intel processors were. Thus, your processor is
probably not vulnerable to certain variants. I’m speaking of
variants 1 & 2. Variant 3, however… Any who, if this message
shows itself at boot, it appears that it is so far, just words. I
wouldn’t worry too much about it unless you later notice that
something about your hardware configuration is acting strange. What
it is doing is going back to a generic retpoline. If you didn’t catch
anything at boot and are worried about the potential incompatibility,
you can usually just revert back in Linux by hitting the shift key
before the kernel loads itself. In most distributions you will get a
screen full of choices to boot into an older kernel or do maintenance
on the system in the case of Ubuntu. If you want to see kernel
panics after the boot up process, there are two possible ways. On
newer Ubuntu distributions, the ones based on 16.04, you can run
journalctl –list-boots and
then run journalctl -p err -b <#NumberofLatestBoot> command
in a terminal window. If that is too complicated, a
more simple command that I
use is sudo dmesg -l err or
sudo dmesg -l warn. These will show the latest kernel panic
complaints from the last boot/latest kernel. There
have been Windows machines that have had trouble rebooting after the
said patches, however, on Linux, the impact of these patches seem to
be nominal, meaning you should probably continue patching. I just
thought that people running AMD hardware or hardware as old as mine
are more or less safe :).
Link to see if you're still vulnerable:
https://github.com/speed47/spectre-meltdown-checker/blob/master/spectre-meltdown-checker.sh
Link to see if you're still vulnerable:
https://github.com/speed47/spectre-meltdown-checker/blob/master/spectre-meltdown-checker.sh
Comments
Post a Comment