With Android Oreo, Google is introducing Linux kernel requirements • Hacker News Board

Re: With Android Oreo, Google is introducing Linux kernel requirements

#71

Post by pjmlp » Tue, Sep 05, 2017, 6:12 AM UTC

remir wrote: post #56

sverige wrote: post #29

Some have speculated that Fuchsia will eventually replace Android. I remember back in May that some prototype UI was introduced by Google. Anyone know of any recent developments on this front?

Magenta (their new microkernel) is being renamed Zircon as they reorganize the OS into layers named on gemstones. As for the UI, their new compositor requires a GPU with Vulkan support to make it run. Unfortunately QEMU doesn't support Vulkan at the moment, so I wasn't able to test it.

Interesting, so they are ruling out everyone that has computers older than two years.

And given that Android 7 (where Vulkan is anyway optional), is about 13%, I wonder what the target users would be, if this ever gets out of the lab.

Re: With Android Oreo, Google is introducing Linux kernel requirements

#72

Post by sitepodmatt » Tue, Sep 05, 2017, 6:33 AM UTC

pen2l wrote: post #53

newforice wrote: post #27

Earlier quoted context omitted.

It is frustrating how far Ubuntu has diverged from Debian. It used to be easy to set up a remote desktop, I can't even get it to work in Ubuntu 16 now, just tried the other day too.

What if you use Teamviewer? It seems to support both Ubuntu/Debian and Fedora/CentOS, etc.

Nasty piece of software that requires running a server daemon even for the client. Bad secuity history and non open. Simply horrid.

Re: With Android Oreo, Google is introducing Linux kernel requirements

#73

Post by bitwize » Tue, Sep 05, 2017, 9:03 AM UTC

bitmapbrother wrote: post #44

bitwize wrote: post #14

Looks like they want to have certain security features enabled so Android can maybe catch up to where iOS was a year ago.

What security features would those be?

I don't know, but my guess would be process namespaces, cgroups, and TPM support.

Re: With Android Oreo, Google is introducing Linux kernel requirements

#74

Post by majewsky » Tue, Sep 05, 2017, 10:30 AM UTC

kevingadd wrote: post #55

majewsky wrote: post #42

Earlier quoted context omitted.

> made everything harder to debug It's not harder, it's just different. As a counterpoint, I never figured out how sysvinit works and got by with guesswork and Stack Overflow answers. And I hated how logs were scattered all over the place. Nowadays you have systemctl(1) and journalctl(1) which are exceptionally well-documented in their manpages, and now services and logs work the same all the time across all distros.…

I believe you, but design decisions like 'the systemd utilities for controlling services exit silently with no output even when they fail to start a service' definitely make it hard to learn the new systems.

Eh, what? I've seen them fail non-silently. What you're thinking of is probably when a service comes up fine, but then fails a few seconds after it has started up.