http://www.linuxfromscratch.org/lfs/view/stable/chapter06/sy...
http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/s...
637 karma · joined August 28, 2018
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/sy...
http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/s...
The opening paragraph has one of their Psychologist angel investors saying exactly this.
~70-120mg look like drip brew numbers. Instant tends to run from 30-50mg.
25 cups of instant == ~750-1250mg
From a security/reliability standpoint it sounds like a nightmare combining the worst of things like NTFS alternate data streams and share library loading into one.
Should we measure CMOS and silicon's overall usefulness as a medium of CPU design based on the performance of a Z80?
Nacha ACH spec per BoA for example:
https://files.nc.gov/ncosc/documents/eCommerce/bank_of_ameri...
https://www.alchemistowl.org/pocorgtfo/
Yes. Not only is it possible but historically already an avenue of attack.
Look at how much slower CPUs are without those speculative execution tricks. I can buy gigabytes of RAM with a 20 I found in an old jacket. You can explore entire worlds consisting of gigabytes of high res textures and mesh data in near real-time, while downloading 4 new albums off the internet.
Broken?
https://marc.info/?l=openbsd-misc&m=139819485423701&w=2
No one that cares enough to use LibreSSL over OpenSSL would want FIPS as reintroducing it would make LibreSSL demonstrably worse. Anyone that requires FIPS doesn't know or care enough about security to have a dog in the fight.
Sure it happens, but it's mostly to string along suckers.
Step One: Create Doofenshmirtz Evil LLC.
Step Two: Register HugsAndTrustBanking.com to LLC
Step Three: Get the legal services of Dewy Cheetum & Howe to issue a letter stating Evil LLC is your legitimate business.
Step Three: Show CA "proof" of ownership for Doofenshmirtz Evil LLC and HugsAndTrustBanking.com.
Step Four: Get genuine EV cert for your shady scam operation.
Step Five: Profit.
EV certs are dumb, you can trust me on that[0].
https://github.com/intel/spark-mpi-adapter
Oh look, a paper; "For example, a recent case study found C with MPI is 4.6–10.2×faster than Spark on large matrix fac-torizations on an HPC cluster with 100 compute nodes"
Does it sound like large data analytics would have horribly stagnated?
When only important shit you really wanted to encrypt was encrypted and you get a cert warning you took notice. Now one in 10 sites with an "easy/free ssl cert" that expired has normalized cert warnings on pages with cat pictures and bank sites alike.
I doubt intel could keep up much better.
Twice in the last 20 years - more than any other time in US history combined - The Presidential election went to the candidate that LOST the popular vote; These generations just lack a proper understanding of civics!
The beatings will continue until moral improves.
Boot time: A possible 5-10 extra seconds from sysvinit is the problem here not the 5 minutes of BIOS/EFI POST time for those server boxen?
Logs: Where's the storage of the log data in journalctl and what tools can I use to read that data in a small PXE rescue environment? But hot damn I didn't have to ls /var/log so that's nice.
Sarcasm aside how does it make your life any easier? I got a stack of FIXMEs to work on to get our infrastructure working, lot alone stable, on systemd.
This isn't just some theory work in academic papers. It isn't even "new", lots of research dating back to the 1960s.
Yes, they do all that now but it's kludgy, easy to detect, and a much more obvious overreach of their presumed authority. See Comcast/Sandvine fiasco.
As to the implicit assumption of the Telco's powers under such a system. History is my biggest "proof". It's a reasonable assumption given economic and games theory. At best it wouldn't have been the Telco's directly that ended up with the control. Someone would have and the result would still be the same.
How about this: How many terrible government regulations about filtering and censorship that are technologically infeasible with the current internet been not only technically possible, but fully fledged features of an objectively better design?
Again I'm not arguing against research and better designs, just rationalizing what we got.
With the power of hind-sight; Imagine an internet where Comcast, AT&T, et al, have such granular control over access to your infrastructure. Ala Cart billing based on each addressable service you happen to run for example. DNS hijacking on steroids as another. The development of new protocols for all but biggest "participating" organizations would be stillborn. Capitalism would have strangled the Internet baby in the crib long ago if we had "done it right."
The road to hell is paved with good intentions and these are some of the best intentions.
But then what about almost-uri text. www.yourbank.com without the https://. Or lookalikes "https:\\" or... what about proxies? does https://l33th4x.com?proxy=www.bank.com count if the text is www.bank.com?
Filtering crap like this sounds reasonable but very quickly becomes an exercise in what I call "Giving a mouse a cookie." Now you have a huge complex chunk of code to parse and filter URLs/URIs and every look-alike you can think of; Did you remember that automatic deserialization that kicked in when your values were sent to a callback?
2 days of work later, your new build has fancy-pants a tag filtering that contains and unknown number of bugs and phishers just register and use new domains that look kinda legit and follow your new text/link rules. www.security-wellsfargo-audit.com/login looks legit to the mark, your mail client allowed it so it must be OK.
Also; Cygwin, XWin and a real copy of XTerm/Gnome-Terminal/etc can give you the entire capabilities of a native terminal. Including weird hacks like w3m's image previews.
https://blog.z3bra.org/2014/01/images-in-terminal.html
The "downside" is native windows console apps will have a bad time with these terminal emulators.
All that assumes they even admit the issue is their hardware not your code, which is a mighty big assumption itself.