The Grumpy Editor's Fedora 18 experience

Posted Jan 16, 2013 0:16 UTC (Wed) by nirik (subscriber, #71)
In reply to: The Grumpy Editor's Fedora 18 experience by quintesse
Parent article: The Grumpy Editor's Fedora 18 experience

It's now handled (by default) by systemd.

Either:

a) edit /etc/systemd/logind.conf and tell it to not do that.

b) run systemd-inhibit to prevent it from doing so when you don't want it to.
(something like: 'systemd-inhibit --what=handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch sleep NNNNN'

to post comments

The Grumpy Editor's Fedora 18 experience

Posted Jan 16, 2013 0:38 UTC (Wed) by quintesse (guest, #14569) [Link] (12 responses)

I tried editing the logind.conf but it didn't seem to do anything, is there some service that has to be restarted first?

(I also tried systemd-inhibit, but all the examples I find seem to be missing some important part because the command always complains)

The Grumpy Editor's Fedora 18 experience

Posted Jan 16, 2013 4:48 UTC (Wed) by mezcalero (subscriber, #45103) [Link] (11 responses)

yes, restart systemd-logind

The Grumpy Editor's Fedora 18 experience

Posted Jan 16, 2013 10:44 UTC (Wed) by jospoortvliet (guest, #33164) [Link] (10 responses)

Should this even have gone in without a way to disable it (preferably the same way it used to be possible to disable)? I think it's a good feature and a reasonable place to put this feature - but some degree of user control shouldn't be optional. I'm rather unhappy not to be able to easily control power management.

Are there hooks for the UI to control this, Lennart?

(I use the feature to disable power management in the battery applet frequently, it's a smart and useful feature which I'd rather not see broken)

I'll surely test this feature for the upcoming openSUSE 12.3 release to make sure I raise a bug if this is an issue there too. I'd rather not have us ship it this way.

The Grumpy Editor's Fedora 18 experience

Posted Jan 16, 2013 22:50 UTC (Wed) by mezcalero (subscriber, #45103) [Link] (9 responses)

DEs can control the stuff on their own if they wish. logind only does that if no DE is around or if the DE is too simply to do lid switch handling of its own.

With other words: KDE can do whatever it wants, it can tell logind to stay away from the lid switch, or it can leave logind in control, and can even dynamically do that at any time.

GNOME for example tells logind to stay away from the lid switch if an external monitor is plugged in, but otherwise let's logind handle everything.

Joke alert

Posted Jan 17, 2013 18:16 UTC (Thu) by man_ls (guest, #15091) [Link] (8 responses)

What!? You mean to say that systemd doesn't have its own embedded desktop environment yet? Really hope you are working on it! (Disableable of course. Is that a word? Apparently not.)

Joke alert

Posted Jan 18, 2013 10:41 UTC (Fri) by dgm (subscriber, #49227) [Link] (7 responses)

A desktop environment? Why?

I hereby propose that systemd gets merged with Emacs. Think of the possibilities! It would become sentient in less than 24 hours...

:-P

Joke alert

Posted Jan 18, 2013 16:12 UTC (Fri) by man_ls (guest, #15091) [Link] (1 responses)

I hereby propose your message as "LWN comment of the week".

Joke alert

Posted Jan 22, 2013 23:59 UTC (Tue) by DonDiego (guest, #24141) [Link]

That's at least the comment of the month and let's see if anybody gets close in 2013 ;-p

Joke alert

Posted Jan 18, 2013 22:49 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

But whose personality would it have? Stallman's? Lennart's? It's going to have a lot of enemies to start out either way…

Joke alert

Posted Jan 19, 2013 15:52 UTC (Sat) by nix (subscriber, #2304) [Link] (3 responses)

You can already run Emacs as /sbin/init, so *obviously* the solution is to reimplement systemd in Emacs Lisp. (We might need to wait for the concurrency branch to mature, so as not to block for too long.)

My normal arguments about init being critical software and thus being software that should not change too fast (because if it dies the system is useless and instantly panics) is moot here, because if your Emacs dies your system is useless in any case. I mean, what else is an OS for?

Joke alert

Posted Jan 19, 2013 16:44 UTC (Sat) by apoelstra (subscriber, #75205) [Link] (2 responses)

>You can already run Emacs as /sbin/init,

This isn't true, is it? Do people do that?

I'm scared to try because I don't know Emacs well enough to undo it.

Joke alert

Posted Jan 19, 2013 20:10 UTC (Sat) by tom.prince (guest, #70680) [Link] (1 responses)

> I'm scared to try because I don't know Emacs well enough to undo it.

If you just pass init=/usr/bin/emacs on the kernel command line, you shouldn't need to do anything to undo it.

Joke alert

Posted Jan 20, 2013 8:04 UTC (Sun) by apoelstra (subscriber, #75205) [Link]

> If you just pass init=/usr/bin/emacs on the kernel command line, you shouldn't need to do anything to undo it.

That didn't work. Maybe this is a bug in Fedora's initram, because it worked the last time I tried it (several years ago, and with an actual init program).

For those curious, I did manage to do it though, by popping open my initramfs and adding an explicit INIT=/bin/emacs after the code which sets the INIT variable. The result was emacs saying "cannot open /dev/tty" and bailing, and then the kernel panicked.

If only udev had been merged into emacs..