Since you can't legally share a lot of patient information with "unknown third parties", a consequence is that bills are going to be decidedly lacking in specific information. Even if you want to ascribe that to malice, it isn't necessarily the hospital that you should point the finger at first.
That's my browser selection.... and right now FF is doing its damnedest to NOT be it. The current version has a horrid lag, where typing into an input field is akin to a 300 baud dial-up line with noise on it. It gets worse if I allow spell checking.
And I'm STILL trying to figure out how to get some of the plugins to work like they did under v23. I think it is part of their "be like Chrome" strategy, where anything really helpful isn't supported.
But, then again, the others aren't doing much to become the browser I use most, because they don't do what FireFox USED to do...
I wonder how much CO2 those wicked agricultural crops scrubbed from the polluted California atmosphere...
This is a story about going after telemarketers that made calls from 2012. It's 2015, and my phone is still ringing with robocallers. At this rate, the people calling me now will be fined in 2018...
... to ask these same managers how their hiring goals of 2014 were met during 2014. That is, if they planned on hiring someone with skill X within 6 months, did they hire someone with skill X? Did they actively LOOK for someone with skill X? Or was it, "If someone with skill X comes in, they get 2 extra Brownie Points"?
It's all well and good to say you plan on hiring certain skill sets in a given period, but if you haven't been fulfilling your goals in the past, what does that bode for the future?
I don't even get a black box... There is a white hole allocated for the video, but no noise or other annoyances.
I wonder if the other companies that use ooyala.com for useful purposes appreciate the damage
(actually, that's *.ooyala.com... too many Ls)
The auto-play waits for the whole page to load. Well, it did, until I told my system that *.ooylala.com should be mapped to 127.0.0.1
I used to be able to create a bootable drive, configure it the way I wanted, then clone it to allow redundant hardware; only the IP and host name varied between machines. Several machines were built with two boot drives, imaged after the configuration was complete, then the "spare" powered down.
That stopped working a few years ago. Distributions now made partitions that included the serial numbers of the disks in their GUIDs. If the MAC address on net card didn't match, a "new interface!" was discovered, so routing tables needed to change. Now, it takes less time to build the install from scratch than to patch the mirror image to replace a failed boot drive.
Between this story about the need to secure on board systems against hacking, and Friday's story about the NEED to hack farm equipment....
... if the farm equipment ran iOS. You'd just have to submit a bug report, and it would be fixed in the next update!
Oh, wait... That would be when iFarm 12.4 gets released.... and that's not scheduled until the iPlow 9S is announced...
A number of U.S. based companies have already purchase, merged with, and become subsidiaries of Irish companies. That makes profits made in the U.S. "foreign income", and everything outside the U.S. untouchable, because it will never be "repatriated".
The price of companies incorporated in Ireland is going to skyrocket even higher than it has.
And yet summary says 6...
The way around the requirement that a violation of LAW requiring an OFFICER to issue the ticket is that the cameras document violations of ORDINANCES with a CIVIL penalty.
Blow a red light in front of a cop, you're issued a ticket that affects your license. Blow it in front of a camera, your license is safe, but your wallet is in jeopardy!
"With RHEL based sysysstems, at least, the simplest way to block it is to put "NM_CONTROLLED=no" in the "/etc/sysconfig/network. That helps ensure it stays disabled, until, and unless you specifically select it for any network port.."
If NM is installed, even telling it to not control a network interface is insufficient to keep it from interfering with that interface. Just a week ago, I installed a new NIC in a server, configured it manually with NM told to leave it alone. 12 hours later, the server disappeared from the network. It didn't crash, it just disconnected, because NM decided to take over control of the NIC.
Why? Because I had not put the MAC address into the configuration. Seems NM will ignore NM_CONTROLLED=no if you don't tell it the MAC address. So my fixed-IP server suddenly became a dynamic-IP workstation, with DNS pointing to the wrong network and a different gateway.
So, no, I'm not going to leave NM installed on any machine that is NOT moving around the country using WiFi.