vmp
It really helped me make some decent budget builds.
Tried to publish it to the chrome extension store as well but they removed it. Honestly just use Firefox, google is garbage.
The covid crisis made my issues boil over to the point of losing relationships, friendships and attempting to take my own life twice (before I found the therapist).
I don't know if I'm extremely unlucky or if the choices I make are really that bad;
- I've hit a bug with amavisd and bitdefender[1]
- Recently, Ubuntu pushed for 'netplan' instead of ifupdown and that didn't work with an empty bridge for LXC[2][3]
- They broke a (convenience) script for remotely unlocking a LUKS rootfs[4]
- postconf segfaulting every 5 minutes[5], nothing bad but it just looks ugly in the server logs
That's the major annoyances that I've experienced in the last 3 years. Never had anything like it on Debian. :/
[1] https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1...
[2] https://bugs.launchpad.net/netplan/+bug/1736975
[3] https://bugs.launchpad.net/netplan/+bug/1773997
[4] https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/16518...
[5] https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/17534...
[1] https://github.com/ckolivas/lrzip
# 151M linux-4.14-rc6.tar.gz
# GZIP decompression
~$ time gzip -dk linux-4.14-rc6.tar.gz
real 0m4.518s
user 0m3.328s
sys 0m13.422s
# 787M linux-4.14-rc6.tar
# LRZIP compression
~$ time lrzip -v linux-4.14-rc6.tar
[...]
linux-4.14-rc6.tar - Compression Ratio: 7.718. Average Compression Speed: 13.789MB/s.
Total time: 00:00:56.37
real 0m56.533s
user 5m35.484s
sys 0m9.422s
# 137M linux-4.14-rc6.tar.lrz
# LRZIP decompression
~$ time lrzip -dv linux-4.14-rc6.tar.lrz
[...]
100% 786.16 / 786.16 MB
Average DeCompression Speed: 131.000MB/s
Output filename is: linux-4.14-rc6.tar: [OK] - 824350720 bytes
Total time: 00:00:06.35
real 0m6.524s
user 0m8.031s
sys 0m1.766s
# Results
~$ du -hs linux* | sort -h
137M linux-4.14-rc6.tar.lrz
151M linux-4.14-rc6.tar.gz
787M linux-4.14-rc6.tar
tested on WSL (Ubuntu BASH for Windows 10)edit:
~$ time xz -vk linux-4.14-rc6.tar
linux-4.14-rc6.tar (1/1)
100 % 98.9 MiB / 786.2 MiB = 0.126 3.0 MiB/s 4:25
real 4m25.189s
user 4m23.828s
sys 0m1.094s
~$ du -hs linux* | sort -h
99M linux-4.14-rc6.tar.xz
137M linux-4.14-rc6.tar.lrz
151M linux-4.14-rc6.tar.gz
787M linux-4.14-rc6.tar
It looks like XZ still has the best compression ratio but also took the longest (real)time.> Given that ifupdown is no longer installed by default, its commands will not be present: ifup and ifdown are thus unavailable, replaced by ip link set $device up and ip link set $device down.
Sad to see this go; I always use ifup, ifdown and ifconfig. Yes, they're old and clunky tools but in a way they are the staple of a proper Linux installation to me.
Not to mention that it's quite a handful to write out "ip link set $device up".
Sounds like only to G-Suit customers, maybe they expand to everyone at a later date.
I just checked my free (grandfathered) GSuite account and there is no option for it (yet?).
Why is it more difficult to get back in to my 20 year old ICQ than it is to reset any other password I have, even "high security" sites like Bitcoin exchanges or Domain Name providers.
A lot of the (non-technical) internet users probably don't know how easy it can be to link an online identity to your person, be it through handle (nickname) re-use or simply having a pattern of likes and dislikes or hanging out with the wrong crowd. Once the connection is made you have nothing left to shield yourself with and will have to, like the person in this article, deal with it on a daily basis.
I've since grown up a little, grown a thicker hide and conquered my paranoia to a degree thanks to therapy, and have started to comment and share online again but the fear of coming across the wrong person with too much time on their hands still feels chilling to me.
Garry Newman (the guy behind "Garrys Mod" and "Rust" (game)) published[1] a rather interesting chain of emails, a peek in to the mind of his stalker.
Recently I tried running a simple BTRFS SSD Mirror for only a single KVM virtual machine, I thought compression would be neat since they are just two cheap 120GB SSDs and I wanted to have a spare if one of them gave up the ghost.
At first everything was great but after I ran a btrfs scrub, and it found ~4000 uncorrectable errors, my VM was broken beyond repair and had to be restored from backup. The SSDs SMART data was fine, there weren't any loose cables, everything worked great, no reported (ECC) memory errors... I have no proof but it seems that BTRFS just decided to destroy itself.
I have since moved my SSDs to a ZoL mirror and (after running scrubs every two days for two weeks) had no further corruption, silent or otherwise. To me, this means that btrfs just isn't stable enough for production use - while ZoL is.
The weirdest thing I noticed in the past was, that IPv6 via Tunnelbroker.net actually worked better than ISP-provided-native-v6, though I haven't tried using a tunnel in a long time.
To be fair, there is only one level of indentation. Kind of difficult to screw that up.
It's not pretty but it works well enough. :)
Flashbench [1] should be able to tell you what the erase-block and page size is.