That's dangerous thinking. Any un-patched service can turn into a pivot point. If the same folks who managed more critical pieces of infrastructure log in there, it can almost certainly be used to pivot onto their other systems.
Not really. It's technically possible with Ksplice, but almost no distro actually supports it.
Beyond the kernel, you have various libs and binaries that will be replaced during upgrades. All can usually/mostly be restarted without a reboot, but just upgrading packages alone won't guarantee all running processes have been updated.
The consumer gear was trash. The server lines were an entirely different story. Also worth noting that by the mid 2000s, Compaq was just a branding on the consumer side. The hardware was all the same old HP consumer junk.
There are plenty of System X HPC installs. They just no longer come from IBM. Even when IBM still owned the line, it was being outsourced. The University of California SRCS system from ~10 years ago was an iDataPlex sold to us by IBM. Most of the boards had Asus marked on them.
Also remember the System X line was sold way after the Think lines.
This is exactly whay I was getting at before. Please stop fixating on the deferred form of deep links. The play store need not even be involved for deep linking to an already installed app.
The mobile_guide instructions are where most people bail out.
"Yeah, no. This is too complicated." is the response when they see
"Install an app, then click on a check box that changes the UI, then enter https://foo.bar:8448, then register".
That's a massive turn off before your app is even installed. A flow of "Install this app, then return to this web page" is significantly easier. Or if/when branded builds of Riot are possible, it becomes "Install this app."
I'm not sure -- I haven't messed with a Pixelbook. On Chromebooks, the trust root lives in the bootloader's flash with no security beyond the write protect screw.
A quick googling led to a reddit post that indicates it's possible with the Pixelbook, but likely a PITA:
> Chromebooks use both, coreboot on x86, and u-boot for the rest.
This isn't entirely true. Coreboot is used on a number of ARM Chromebooks, including rk3288 and rk3399 based devices. It seems like u-boot is used less and less in the space. Libreboot has builds for a few devices that kill the annoying "untrusted os" message, and even allow you to set your own trust root.