Forgot your password?
typodupeerror

Comment: Re:It freakin' works fine (Score 1) 928

by AdamWill (#48290079) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?

well, ultimately the init system launches *everything* if you take a broad enough view of things, but that doesn't mean the init system is somehow responsible for your desktop environment's display configuration.

I mean, if you're really determined to, you can 'configure' things by modifying their init scripts, sure, but it's usually not the right way to do it. X has a perfectly good configuration system already. So does GNOME. If you want to change the DPI at one or other of those levels, go configure it through their configuration systems. That's how it's supposed to work.

Comment: Re:Parallel booting (Score 1) 928

by AdamWill (#48288987) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?

That's far too reductionist. For a start, there are many sysv-compatible init implementations that do parallel boot; upstart does it, Mandriva's pinit does it. There's a whole subset of LSB that exists exclusively to provide a way for sysv initscripts to represent dependencies *precisely in order to enable parallel init* - see https://wiki.debian.org/LSBIni... for a good write-up of that.

Secondly, insofar as systemd is intended to improve boot speeds, it wasn't actually just about implementing simple parallelization of sysv-style services using dependencies. If you read http://0pointer.de/blog/projec... it talks a lot about parallelization but it's actually talking about making *more* parallelization possible, not just *implementing* parallelization: the big idea Lennart had back then was the idea that you don't actually have to completely start up a service in order to start up another service that 'requires' it, if you can create the socket it listens on before it's ready, then queue up any requests and pass them on to the service once it's actually done starting up. Lennart was clearly really excited about this idea at the time, but if you look at systemd these days, it's a really pretty small corner of all the things it does.

All the way through the first part of that first post, Lennart is really talking about making more parallelization possible, he's not simply talking about implementing inter-service dependencies.

These days systemd does an awful lot more, and it really isn't just about making boot faster any more. Even in the very first post, once you get past the first half, it starts talking about improved capabilities. I find startup speed the least interesting thing about systemd, really, I'm much more interested in the improved capabilities for units and especially in the improved logging journald provides.

Comment: Re:Why dislike something you know nothing about? (Score 1) 928

by AdamWill (#48288923) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?

"Since RedHat's obviously the largest major proponent"

For the record, there's absolutely nothing 'obvious' about that. People tend to assume that since Lennart was @redhat.com when he wrote systemd it's 'obviously' a Red Hat project, but it really isn't, and never was. It's a Lennart project: he came up with the idea and he wrote it. Red Hat didn't ask for it, didn't actually have any idea it was coming.

The very first instance of all these battles that get fought every six weeks in some distro or on /. or on Phoronix happened in Fedora, when Lennart first proposed switching to systemd. Around the same time / a bit later, all the same battles happened within Red Hat. Just as with every other distro, systemd's proponents brought the idea and argued for it. systemd wasn't planned from the top down by 'Red Hat authorities' as 'our new init system', Lennart came up with it on his own, and convinced the plurality of significant folks/bodies within Fedora and RHEL that it was a good idea.

Comment: Re:It freakin' works fine (Score 1) 928

by AdamWill (#48288895) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?

Um. What? Display DPI is nothing the system init daemon cares about and never *has* been.

It can be set at the X level or at the desktop environment level. Some desktops respect X's setting, some ignore it.

In GNOME you can set both text scaling and full display scaling (the new thing used for hi-dpi screens) in GNOME Tweak Tool. Text scaling is in Fonts, it's the 'Scaling Factor' - if you think about things in DPI terms, just consider the 'scaling factor' to be a multiple of 96, e.g. if you want to set 110 DPI, set it to 1.14.

If you mean GNOME's decided your display is hidpi and starting scaling *everything*, that's the 'Window scaling' setting on the Windows tab, set it to 1 (which is no scaling).

Again, none of this has the slightest thing to do with init.

Comment: Re:She's.. (Score 2) 235

by AdamWill (#48245993) Attached to: Ex-CBS Reporter Claims Government Agency Bugged Her Computer

The article continues:

"It was described to me by the computer experts I consulted with afterwards that that was purely an attempt to let me know that they could do that, that they were watching, that they were in my computer."

Not saying that interpretation is correct, but it does seem reasonable to point out that she does in fact have a response to your objection.

Comment: Re:Please stop this madness! (Score 3, Informative) 774

by AdamWill (#48098807) Attached to: Systemd Adding Its Own Console To Linux Systems

It's been running under 'real-world conditions' for years already - do you think no-one runs real-world systems on Fedora, or that Red Hat doesn't run releases in production internally before they go out, or that RH has no customers who test pre-releases?

"Seems to me that's the largest reason it's being pushed"

Nope. I think this impression originally came from Lennart's original post on systemd, years and years ago - http://0pointer.de/blog/projec... - because it starts out talking about boot speed. But even that very first post moves on, in the sections "Keeping Track of Processes" and later, to talk about the really interesting bits of systemd - better service management, and more capable service configuration. As systemd development continued, it's become much more about the latter and much less about boot times - I think that's where Lennart *started* thinking about systemd, but it's really not what systemd is for any more. Red Hat certainly wasn't interested in systemd because it might make servers boot three seconds faster, RH was interested because it can make service management on servers much better.

Comment: Re:Why do people care so much? (Score 3, Interesting) 774

by AdamWill (#48094227) Attached to: Systemd Adding Its Own Console To Linux Systems

"Oh hey, just what I wanted BINARY LOGS THAT BREAK ALL MY EXISTING AUTOMATION."

systemd is designed to make it trivially simple to have text logs if you want that. RHEL 7 is configured by default to do permanent logging in plain text format via rsyslog; the native journald logs aren't even permanently stored by default (this is the config that was in Fedora for a while before journald's native format became the default/primary).

https://access.redhat.com/docu...

I am starting to suspect you're a troll and haven't actually used RHEL 7 at all.

"Never give in. Never give in. Never. Never. Never." -- Winston Churchill

Working...