With Android Oreo, Google is introducing Linux kernel requirements

Re:With Android Oreo, Google is introducing Linux kernel req... by majewsky on Monday September 04, 2017 @01:43PM (#15169706)

> 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.

(Not going to argue about journald's weird binary log format though. I don't get that. But at least it doesn't get in the way for me.)

[ Parent | on HN ]

Re:With Android Oreo, Google is introducing Linux kernel req... by kevingadd on Monday September 04, 2017 @03:04PM (#15170215)

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.

[ Parent | on HN ]

Re:With Android Oreo, Google is introducing Linux kernel req... by majewsky on Tuesday September 05, 2017 @06:30AM (#15173882)

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.

[ Parent | on HN ]