Yup, this is our case. There's also a common misconception that with oracle you can just open port 1521 and everything works, but per oracle, that's only part of it. SQL*NET is weird software.

The actual training did "get into" why it works that way. See the above referenced article explaining how SQL*NET works. 1521 doesn't handle the actual sql query, it forks a new oracle process for that particular request which has a new socket associated with it.

FYI, oracle requires ports from 1024-65535 to be open for any client. 1521 is only used for initial setup dialog. This also forks a new oracle process, which gets its own socket. Afterwards, as stated above, this information is sent back to the client which reconnects on the new socket. This oracle doc explains what I am talking about: https://asktom.oracle.com/pls/...

I disagree. When we have 15 million customers on a 3rd party's platform, we can't suddenly turn around to that vendor and say "yeah, no, you're using SELinux no matter what." We either build things to their spec, or we lose support. Their spec stipulates disabling SELinux and iptables, so they get disabled. Case closed. So, while I agree in principle, I have to disagree that it's always possible.

After 4 weeks of oracle training, the advice from the oracle trainer was that oracle simply doesn't play well with firewalls. I'm not a DBA (thankfully), but that's from their actual instruction.

It's actually quite useful if you have something which monitors those files. No open CM ticket for a server, but you suddenly see someone logged in and making changes? Sound an alarm. .history shows you everything a user types as soon as they type it (even modifying the shell to keep 0 history would show up initially). We use splunk to monitor it, and also monitor /etc for any changes to system files. It's lightweight and has helped us find a number of issues before.

This is true, however some databases simply aren't compatible with local firewalls. Oracle for instance requires your server to be more or less wide open (request comes in on one port, a response is sent back indicating the port to actually communicate on, then the client resends the query to that new port - so, more or less all ports have to be unblocked). This is where stuff like centralized authentication, nagios, monitoring of the /home/*/.history files, etc comes in useful. Sometimes local firewalls simply aren't an option.

From the sounds of it, you're discussing disabling a software firewall, not an actual hardware firewall. There's a lot of applications which require local firewalls to be disabled - for instance, we disable local firewalls when we're deploying telephony application servers because of vendor requirements. Likewise, some applications require SELinux to be disabled as well. All of our servers are still collectively behind a firewall, and beyond that we have a number of ACLs and centralized authentication controlling them. As for not running a firewall being lazy - firewalls are tools. Sometimes they're the right one, and sometimes they aren't. The only way to tell is experience on when to use each tool (and budget too). The more time you spend with networking, the more you'll come to realize that. But since you're learning, stick to what you've been told until you master it. As Picasso said, "learn the rules like a pro, so you can break them like an artist."

You are dumb if you think that a single word has enough power to indicate someone's cowardice. Cunt, cunt, cuntity cuntcunt.

You don't have to be wildly strabby or exotropic to get some (potential) benefits: if your eyes are struggling to maintain fusion, you may read more slowly and suffer more eyestrain than if you had vision therapy, without knowing that you're fighting your own eye muscles. Simple use is lousy training, it turns out, much like just walking lots doesn't help people with screwed-up knees.
It might not do anything for you, but a consult with an optometrist who knows a bit about vision therapy may be worthwhile.

When I took a geography class focussing on the western US, one of the things the teacher mentioned (which I haven't verified independently, but it was his job) was that the Colorado River water rights were allocated based on how much the Colorado River was running in roughly 1920, which happened to be an unusually high flow rate period, so ever since then there hasn't been enough water to satisfy everyone. (Water rights are allocated by time priority: first person who used it gets to take the entire amount that person is entitled to, then second person, and so forth.) So it's 100% spoken for, forever. The shortfall is made up for by pumping out groundwater, and when they allocated the colorado river water rights, they also decided that they were going to make a 100 year plan for water usage, meaning that after 100 years they would have used up pretty much all the available aquifers. Since then we've discovered some more aquifers, and are willing to drill deeper and run more expensive pumps, but that's only somewhat covering the shortage. We're pretty much collecting exactly what we planned 95 years ago. There are still semi-serious proposals to divert and pump chunks of the Columbia River over into the upper Colorado River basin... which is sort of funny, as much of the original water projects in the upper Colorado River basin were, and are, pumping water from it through the Continental Divide over to the eastern slope to fulfill Colorado, Kansas, Wyoming, and Oklahoma water needs.

The same instructor also noted that depending on how you define your terms, the category of western state water rights was by quite a bit the most common lawsuit that ended up in the US Supreme Court, showing up every couple of years in one form or another.

Consider talking to a vision therapist about if this is something that can be corrected. They can do pretty amazing things to train and strengthen your eyes to track, fuse images, and reduce eyestrain while doing so. A lot of people aren't aware that they're straining constantly to keep images fused, and as a result dislike reading or using computers. Sometimes, some physical therapy for your eye muscles can fix it. My wife regularly gets kids whose eyes are pointing in entirely different directions and have never had 3d vision in their lives and after five months (five very expensive months, it should be mentioned) they have and retain 3d vision. It's life-changing for a lot of them.

SPOOOOOOOOOOOOON!!!

I have not RTFA, however, one thing that should be noted is Iron Dome is also built specifically to not intercept a large number of incoming projectiles. It monitors incoming trajectories and calculates approximately where they will land. If it is somewhere such as a field, it is ignored. If it will land in an urban center, it intercepts.

Hey, do you happen to have any info on that Russian NOTAM? I can't seem to find it anywhere, and I have no idea what the russian equivalent of "NOTAM" is... googling NOTAM just brings up the FAA warnings.