tylerjd
Joined 10 years ago
Karma
50
Submissions
22
Member since
Sep 15
Recent submissions
Comment · 4 years ago
The major Linux providers already offer 1st party supported Linux on AWS. Both RHEL and Ubuntu instances offer support contracts from their respective companies, as well as Amazon Linux from AWS themselves. It is already here and a big force there. You can provision ElastiCache and RDS Graviton instances too.
Comment · 5 years ago
Blizzard might not be targeted at the younger demographic, but teenagers still play CoD, which is made by Activision. ActiBlizz also owns King, which makes games like Candy Crush, which kids also play.
Comment · 7 years ago
To be fair, it comes with your World of Warcraft retail subscription, and you don't have to purchase the original game again nor the latest retail expansion (Battle for Azeroth) to play it.
Comment · 9 years ago
With Parity, afaik they had a uninitialized contract owner, which could be and was initialized and subsequently caused the contract to suicide. This has a better writeup: https://medium.com/crypt-bytes-tech/parity-wallet-security-a...
Comment · 9 years ago
If you can't find it or it is too scratched, they also sell the full edition of RCT2 on GoG for cheap https://www.gog.com/game/rollercoaster_tycoon_2
Comment · 9 years ago
Probably something along the lines of secure erase. Most modern SSDs/NVMe drives are encrypted by default in firmware. All the firmware needs to do is throw away the old keys and generate new ones. It's better than zeroing the drive as there is no wear to the write cycles and guarantees that the slack space in the SSD is also cleared, which DD'ing to /dev/nvme0 wont be certain of. The nvme-format tool can be used for this: http://manpages.ubuntu.com/manpages/zesty/man1/nvme-format.1...
Comment · 9 years ago
I agree with most of what you said, but Kaby Lake had issues with Hyperthreading, and Haswell had to fully disable the TXT extensions, both modified (fixed/disabled) through microcode updates. You could say Intel hasn't had great press either.
That being said, I still agree AMD still needs to prove their new platform in the server space.
Comment · 9 years ago
Newer steppings of Ryzen have a fix applied, and AMD is allowing people to RMA those processors affected. Threadripper is unaffected by the bug.
Source: https://www.phoronix.com/scan.php?page=article&item=new-ryze...
Comment · 9 years ago
Are you trying to say that BTRFS is supposed to compete feature-to-feature with ZFS? It's not.
https://lwn.net/Articles/342892/
>I had a unique opportunity to take a detailed look at the features missing from Linux, and felt that Btrfs was the best way to solve them.
>From other points of view, they are wildly different: file system architecture, development model, maturity, license, and host operating system, among other things
-------------------------------
>Btrfs snapshots are read-write by default, which in some ways defeats the point of a point-in-time snapshot.
Yes, and have the option of being read only for your temporal "in place" snapshots. But if I want to clone a container for instant use (as LXC or Docker does), then the RW snapshots make sense. Btrfs doesn't make a distinction between a Clone and Snapshot, they are one and the same with a flag.
> but in practice is much less flexible
Tell me more how I can mix disks of differing size in RAID on ZFS
> There's no way to confuse the origin of a snapshot because it's tied to a parent dataset
There's no confusing to the origin of my sanpshots. `btrfs subvolume list -q` shows the ancestral parent as well as the subvolume it's located in, example:
ID 6442 gen 50527 top level 751 parent_uuid 0f4442f8-6363-6944-be8d-e2b45d809352 path .snapshots/321/snapshot
See user_subvol_rm_allowed mount option, available since Kernel 3.0
It's like comparing a car and a truck, they both have four wheels, transport passengers and cargo, and have an engine. Just because a truck runs on diesel does not make the fact that the car running on gas "wrong". Due to its fundamentally different implementation, the way the filesystem works is also different.
Yes ZFS has many more features, has been in development longer, and probably more "production ready" than BTRFS. But ZFS is not GPL compatible. And BTRFS doesn't require it's own separate cache that is apart from the normal filesystem cache.
Comment · 9 years ago
> deprecated and unsupported LXC
Where did you hear this? This is news to me. https://linuxcontainers.org/ and https://github.com/lxc/lxc both seem active and supported by Canonical to me. The only deprecated project by them is listed to be CGManager.
Comment · 9 years ago
It was a euphemism, though I don't know how much RedHat would like you swinging around a binary build of RHEL, but IANAL
Comment · 9 years ago
It depends on your threat model. Are you just wanting to get around your ISP selling your personal data and (in the future) slowing down your internet to certain sites? Host a VPS at DO or Linode or AWS (though you'll look a lot like a bot). This way is also useful for hosting things at your house, but have them look and act as if they are hosted in your provider's DC.
Are you trying to partially anonymize yourself on the internet and download Linux ISOs? Use a provider like PIA. The benefit of those is you're going to (probably) be connected to a node with dozens of others, certain entities would be dissuaded from tracking you, and cease and desist letters stop at PIA and never make it to you, as they don't maintain logs.
If you really want to be anonymous and not be able to be tracked by even governments, TOR is really your only option.
Comment · 9 years ago
Essentially, the Captains word is law while on the plane. He is responsible for the safety of everyone on board. According to FAA FAR 91.3,
a. The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft.
The pilot-in-command of an aircraft shall have final authority as to the disposition of the aircraft while in command.
Comment · 9 years ago
That's exactly what they did. Someone up the chain made a mistake. Other airlines board must-ride passengers (i.e. crew deadheading to the next destination) before passengers, but this did not happen.
Due to FAA regulations, the movement and sleep requirements of crew is enforced big time. In this case, they had a higher priority than a full-fare passenger (Must Ride), and even though it's morally wrong, it is well within the airline's right to remove any passenger at any time for any reason.