rob-olmos

It would be about $2053.03 if it's only the 23TB for that month from N.Virginia region.

It looks like this is only for the paid/enterprise versions of the open-source software, which is a nice start. However, AWS has had their marketplace as well with additional hourly charges.

I understand Google has had their own contributions to certain projects, but I wonder if Google will do anything to differentiate from that and AWS. For example, add MariaDB to their SQL product and contribute some of the income back the MariaDB Foundation.

It's nice to see #2 for package managers, something I've been thinking about recently. I haven't look much into this yet, but I wonder if IPNS could provide a step forward in supply chain protection since package signing isn't available yet in certain managers/repos or not commonly utilized.

What's the shipping costs on a Snowball or other appliances?

IIRC mysqldump had a similar issue back in the day before the --quoted-names option became enabled by default.

Does anyone know if an OR store can tack on a bottle deposit fee for selling a bottle that's only marked CA CRV?

I also tried to recycle it at the store's recycling machine and it says it's not accepted. Recently found this out but haven't looked into it yet.

"The CentOS managed base image uses `yum` and `rpm` for package management, and these pull RPM files only over HTTPS connections."

That's interesting. Is there a reason for that?

IIRC the stock CentOS doesn't use HTTPS for its yum/rpm repos and I figured it wasn't necessary to use HTTPS since the package signature is verified.

It's still interesting that AFAICT there's still little questioning from users to install an app of that nature which needs microphone permission.

SSRI withdrawal can present new symptoms not existing before, such as the feeling of "brain zaps" and body temperature increases, so a friend has described.

If anyone has tried G Suite Chat, it looks like they've added "threads" at some recent point but the UX has some ways to go.

Which new requirements are you referring to?

It would be nice if US health insurance was a bit more roam-friendly as well. Becoming out-of-network with a $14k deductible just for moving to another state is a bit annoying. Last time I got new insurance outside of open enrollment (via a special exception for moving) it took a few months after moving to process & approve the exception. Having to transfer medical records is another aspect.

Thanks!

Thanks! And for the VRF tip.

sshd(8): Add "expiry-time" option for authorized_keys files to allow for expiring keys. -- hooray!

Can someone help explain what the "routing domain" is?

I'm also suspicious of the amount of testing that's being done. More than once the app was posting a completely black pic for every snap, lasting at least a couple days. I stopped using it after this last time it started doing that again.

Interesting idea to use CloudWatch on a Lambda function. I believe the equivalent for Google Cloud would be using Stackdriver's uptime check on a Cloud Function?

Thanks for the insights. What kind of traditional "Enterprise Architecture" patterns do you mean?

I imagine the "Enterprise service bus" architecture is probably a good fit, but maybe I'm missing something.

I think that's a good result, yea? If so, I'm glad it helped! Typically I use the double quotes to search for specific code/error strings and then use non-quoted words in the query to help filter the results to specific context, like the app name or topic. Others suggested the "Verbatim" option.

I've found if I put the keyword in double-quotes then it makes the keyword required in the search

Like others have said typically the microcode update is applied by both the BIOS and kernel. Typically the kernel has the latest microcode.

However, there could be an issue where updating the microcode at kernel time can cause an issue due to a microcode version (or lack of) from the BIOS.

Only other thing I could think of is the microcode update that disables TSX, I believe, could only disable it if TSX wasn't used yet.

So I suppose it's also possible that the microcode has to be updated by the BIOS because some boot process prevents the kernel from being effective with its microcode update step.

I think the only more concrete way you're going to determine intentional vs. unintentional is some type of paper trail being exposed.

https://github.com/andrewgaul/s3proxy ? (no hyphen)

That's incredible! Thanks for the insight.

Any recommendations for detecting/correcting bitrot with RHEL 7.4 at the filesystem or lower levels?

Given a stock (or additional packages?) RHEL 7.4 install on non-clustered storage, what would be the best combination to detect & correct bitrot at the filesystem and lower level?

Yikes. That's unnerving to read. Were you able to create a bug report? Was there any other related issue like an underlying storage controller messing up?

Interesting only one comment made a clear call to backups. Strongly second the notion of backups as a high priority to learn and implement. Could make it more "devops-y" by also automating the verification of them with restores/testing.

One thing to be aware of is that latent hits, via the Queue Time "qt" paramter, have a maximum delta of 4 hours:

"Used to collect offline / latent hits. The value represents the time delta (in milliseconds) between when the hit being reported occurred and the time the hit was sent. The value must be greater than or equal to 0. Values greater than four hours may lead to hits not being processed."

Would be nice if that delta time could be greater than 24 hours, eg. a human approves that a low-volume contact form submission isn't spam and that hit is tied to a GA goal.

Red Hat's vulnerability page: https://access.redhat.com/security/vulnerabilities/stackguar...

Implemented the 1MiB guard page and glibc hardening.