2,258 karma · joined June 5, 2015
https://github.com/mbakke
I suspect the vast majority of OpenBSD users never hit a "scaling wall". What do you mean by product?
In a previous life I installed two OpenBSD routers with a 10GbE card each. With carp(4) they could push nearly 20Gbps total. This was back in 2015 or so.
"Scaling" would just be matter of adding more nodes, or replace with 40GbE cards (which would require a more powerful CPU).
Perhaps running a high traffic relayd on them would have reduced the throughput. But that smells like poor architecture: let routers be routers and load balancers be load balancers :)
https://man.openbsd.org/man8/relayd.8
https://man.openbsd.org/man8/relayctl.8
https://man.openbsd.org/man5/relayd.conf.5
Side note, I haven't heard failover used in the context of kicking unhealthy backends before. Failover is typically something that would be implemented with carp(4) (aka VRRP, but with support for active/active setups) on two different machines running relayd.
https://man.openbsd.org/man4/carp.4
Nothing beats the sheer elegance of OpenBSD for networking tasks. :-)
I was thinking the exact same thing while pondering the parents assertion.
Qualia is just the notion of being something. The classic example is a bat: what is the qualitative experience of being nearly blind, but having wings and a highly accurate echolocation system?
Plants too have qualia. What is it like to be a tree. To feel the nurture of the sun, the change in seasons, and to heal a broken branch.
The qualia of a stone is less exciting, but we can still imagine being a dense pack of minerals. Perhaps rolling down a mountain and losing some weight. Suddenly finding ourselves on the ocean floor, drifting aimlessly, while providing cover and nutrition to all sorts of life. After staying stationary for thousands of years.
That rock has seen things, man!
Down at the atom level things get more excited. What is the qualitative experience of interacting with other atoms? Or a photon? Of being entangled? State transitions?
Anyway. It's clear to me that this robot absolutely has qualia. I can imagine what it's like to be be a circuit board, with an operating system, a bunch of sensors, a neural processing engine, and a hard shell. How it feels.
It makes me appreciate being human more. But also evokes empathy for that adorable lump of silicon, metals, and plastics. Don't let the GP comment bring you down, little one. You are perfect just as you are.
https://joyofsource.com/the-full-source-bootstrap-building-f...
And will gradually become a non issue as distros incorporate it (or more likely: reproducible binaries generated from it) in their bootstrap.
IME, if a process grows out of control, Linux won't notice until the whole system is thrashing, at which point it's too late and it tries killing random things like browser tabs way before the offending process.
In rare cases Linux might recover, but only because I hammered C-c the right place 30 minutes ago. In most cases a hard reboot is required (I left it overnight once, fans spinning at max, hoping the kernel would eventually accept my plea for help, but she had other priorities).
I hope kids today find the weird world of user-friendly operating systems (license- and tinkering-wise) just as interesting as we once did.
It just blows my mind as someone with a somewhat perfectionist approach to rebasing (to the extent I sometimes intentionally break up or reorder commits to make the changes more intentional or natural, even when it causes nasty local merge conflicts) :P
The main drawback is that contributors have to learn a proper mail user agent (Gmail is notoriously bad with patches).
Relatedly, does GitHub merge understand !squash and !fixup commands? I kind of gave up on those and just accepted a few trailing bugfix commits on PRs to not mess up peoples reviews (some projects also invalidate review on force push).
We as users should demand insight into the software running on hardware we own. Otherwise we only partially own it, and if the device is connected to the internet, we can lose ownership any time.
Software is malleable, and Tesla (or hackers) can change it under your feet. You should be able to inspect it and have a say in what it does or whether to accept the next update.
See the recent Philips Hue debacle for an example of when software that's been running well for years suddenly turns on the user.
That does not answer your question though. It goes both ways: if the doctor recognises that a firmware tweak may save your life, then she should be able to do so.
Your parser is no longer 300 lines, and eventually you might snap and throw it all away for a full-blown interpreter which makes dealing with user provided input difficult.
I'm actually investigating using S-expressions for describing jobs and systems, but haven't figured out how to safely evaluate them short of running in isolated VMs.
Edit: thinking more about this, it is possible to represent all those things without evaluation. It's just awkward to create them... but that can be solved on a different level.
Or are they directly executing CPU instructions?
(Android is almost there, software wise, but closed vendor firmwares are still rampant).
That's a good point that I never made sense of. The most likely explanation is simply an oversealouz toll agent. It just left a bad taste in my mouth so I didn't want to play with them...
I had largely forgotten about it until the Google Pixel got stuck.
* When I ordered the first generation Raspberry Pi, they were stuck in the toll a long time, and when they arrived all the warranty seals were broken. Consequently I never really used them.
* When I ordered the first generation Google Pixel, before it was generally available in my country, it was stuck in domestic mail for almost a week. The person who imported them sold and sent two phones the same day: the other one arrived after just two days and travelled a lot further. I used it regardless as I already considered phones a lost cause... (and could not with good conscience sell a possibly compromised device).
At this point I don't trust anything sent by mail.
Apologies to anyone who had to endure my display of contempt.
I agree with the parent comment that FSF (and friends) needs to step up their game to have any influence on the tech scene of the future.
https://guix.gnu.org/blog/2018/bootstrapping-rust/
I was thinking about the fact that building Rust requires cURL, Python, CMake, and more, which makes the "bootstrapping graph"[0] very complicated if coreutils is rewritten in Rust.
0: https://guix.gnu.org/en/manual/devel/en/guix.html#Full_002dS...
Individual GNU projects are doing fairly well on the technical side (toolchain, Emacs, Guix, Mes), but there is little to no coordination across GNU, much less with the FSFs.
FSF Asia seems to have fallen off the earth, even though India appears to have a fairly active free software movement.
I don't think rewrite in Rust is a solution to "modernize" GNU tools. Maybe another memory safe language, but Rust has severe bootstrapping issues which is a hard sell for distros that care about source to binary transparency.
I don't doubt you but would like to read it and try to confirm my bias anyway!
My experience is mainly with completely crap grinders vs high-end burrs which is very distinguishable. Probably low/mid end burrs do okay as long as there aren't too many fines. Grind size variability may even be advantageous :)
Above the $200 range really only matter for espresso. Manual brews don't need that fine grind precision, just consistency (no fines, no rocks) at medium grind levels.
Devices must remain open for the kernel programmers and hardware hackers of tomorrow to follow their curiosity and develop their potential.
Anyway I decided to try Caddy to quickly get up and running and had a good setup in minutes including certificates for multiple domains. Even added wildcard certificates which I never figured out with Lets Encrypt, just because I could.
Thanks for this amazing software :-)