I'll wager there were emails requesting that customers at least be exhorted to "use only Samsung manufactured and approved chargers" - and since we've all known certain Android apps to eat battery like candy, I'll wager there were more than a few internal emails warning that certain apps could be dangerous as well.
The Bene Gesserit understand the correct response. The courts need to tell Samsung: "You will pay."
* dwiw() - Do What I Want (null function - a return code should be unnecessary)
I note that nowadays, ISIS refers to something else. I wonder what ever happened to Samsung's ISIS?
But you know, just when I thought it was safe to go back in the internet, Comcast flashed my router. Suddenly, even with wifi explicitly turned "off", there was the XFINITY free hotspot, just advertising that any wardrivers with a valid or hacked Comcast account should park near my place.
Anybody ever see what the built-in (internal) antenna on an Arris cable modem/router looks like? It's just a little green piece of circuit board, and the connector just comes right off without any excess tugging or pulling. I do think Comcast misses me, though - they seem to send hits downstream to my cable modem/router several times a day. It's vaguely frustrating to hit these forty to fifty second network outages from them because they just can't believe nobody is using my free wifi SSID.
But I regulated Comcast.
(Says one prairie dog to the other): "I think the lawnmower's gone. I'm gonna stick my head up and check."
The Cygwin layer has a long track record of success in providing a POSIX layer with some notable exceptions. There no native software management layer (forcing reliance upon the downloaded installer for software management). Further, while it is possible to build and install software locally from source, the process to do so is at best far from bulletproof - I personally was never able to get ClusterSSH running correctly under Cywin under multiple versions of Windows. However, it does provide a fairly robust software selection "out of the box" and does receive regular patches and updates. Being implemented as a set of API calls and libraries it tends to live within and get along more-or-less well with the underlying MS-Windows system.
They Bash on Ubuntu on Windows stack provides a binary-ready environment pre-loaded with a somewhat modified version of Ubuntu (GNU, but not technically Linux IMHO). Software management is performed using APT, and with very few exceptions software runs identically to the Linux counterpart. The entire environment appears to be created as an abstraction layer in memory on demand, although once running the subsystem does not spawn separate processes as more shells are created. Note that the environment is destroyed when the last user shell is logged out. This is permissible because there is no (significant) boot time associated with the environment - it is created and destroyed instantly without user intervention of any kind. This arrangement neatly precludes the likelihood that system services will be run in an environment which the MS-Windows system cannot control, but does lead to some coexistence issues in regards to filesystem metadata - specifically security-related metadata. The two systems (MS-Windows and Linux) are fundamentally incompatible by design at that level and so implementation/execution of GNU Linux binaries will turn up some quirks caused by this basic incompatibility. Incidentally, I've only been using the Ubuntu subsystem for a month now, and while I've installed and tested Xming and I've been able to install ClusterSSH with one command, I can't get the thing to work correctly in this environment yet either.
Yes, we will be going to OSI, Mars, and Pluto, but not necessarily in that order. -- Jeffrey Honig