garethsaxby

I remember a long time ago in the UK, around 2003 or so, there was a similar problem with Fruit Machines (Slot machines found in UK bars and pubs).

Through dumping the ROMs and emulating the machines, it was found that the machines were effectively forcing losses at certain points in gameplay; from the same memory state, you bet high and the machine goes low, or you bet low and the machine goes high, giving you zero chance of winning.

There was a campaign called Fairplay that I believe resulted in a fairly small print label being placed on the machines stating that they would at times give no chance of winning; not a great win, but at least it was being said somewhere - http://worldofstuart.excellentcontent.com/fairplay/fruit/bre...

The FairPlay site by Stuart Campbell is actually still up, although I remember first reading about it back in PC Zone personally. There's details on there about replicating the findings, but unfortunately the links are broken; http://www.worldofstuart.excellentcontent.com/fairplay/fruit...

At present if you get the direct download you have to write to an EPROM, install into your AMIGA and then write out and use the Kickstart floppy. Actually having the kit to do the programming, the correct EPROM chips and doing it right is a little more involved, from what I've read; I haven't touched an Amiga in some time myself.

The news post on Hyperion's website states that you'll be able to buy ROMs and floppy disks that have already had the updated code written to them "shortly".

Just an FYI, it is a touch screen, according to the presentation at the 41m50s mark - https://www.youtube.com/watch?v=uuC4YLLkqME&feature=youtu.be...

g2 are the EC2 instances designed for graphics usage; they're typically aimed at GPU encoding rather than machine learning, like what the blog poster is aiming for.

Not to say they couldn't cover either, but the GPU classes used between the two instance types are very different; g2 is GRID based, p2 is using Tesla. I don't think that the GRID GPUs have RDMA, although not being into machine learning I don't know how important that would be.

The real problem is that the documentation you've linked to (The EC2 FAQ) actually shows that the p2 instances should have a spot limit of 1, but when I check my account, it's actually 0 for all sizes of p2 instances.

It doesn't seem to matter what region I choose, it just doesn't match the FAQ; p2 is on request only.

I found that this talk (selinux for mere mortals) was good for me to start off - https://www.youtube.com/watch?v=cNoVgDqqJmM

After that, Red Hat's documentation was probably the next most useful thing for getting started; https://access.redhat.com/documentation/en-US/Red_Hat_Enterp...

But mostly it was a lot of proding and poking whilst setting various things up that helped a lot, and remembering that when something doesn't work, to check selinux first.

The 'settroubleshoot-server' package for the Red Hat based distributions is also good whilst you're getting started in dev, as it takes the avc logs and 'guesses' what the likely cause of the problems you've had are, giving percentage likelihoods of the policies and booleans that might be causing problems.

That's good to know too, yes, but using the nginx binary itself to test is always available, whilst a service command normally involves an init script, systemd config file or similar to be available, and they can vary between packages and distributions.

The issue with that, in Windows at least, is that host lookups become a lot slower with a larger hosts file; a local caching DNS server with a block list is possibly a better solution, and one I think is already adopted by some.