On Tue, Sep 04, 2012 at 02:09:30AM -0300, Cristian Rodríguez wrote:
setups in 12.1 were a little rough, but systemd has just plain worked with 12.2.
That's just not the case for everyone:
https://bugzilla.novell.com/show_bug.cgi?id=768788 ... This is not a bug.. Unless there is an standard that demands stuff to work the way you want..
And this is *exectly* that kind of attitude that got systemd the bad name it
still has in many of it's oponents eyes: It changes things that have been
fixed for "ages" and then declares it either the user's or the program's
author's problem but not systemd's problem. Actually, what got it its bad
name was that this was the percieved attitude of its inventor's previous
high profile project pulseaudio. For me personally systemd has not lived up
to my prejudice in a very positive way (I always liked systemd's concept).
And now to why I think that users (admins) have a right to expect thing to
happen reproduceably:
If you have two monitors connected to your computer and don't change the
setup then you should have a right to expect that the same applications
always appear on the same monitor. Everthing else is a bug. When I run
xdm restart (which of course tells me how to do this with systemctl instead)
and X changes from alt-f7 to alt-f8 in the process, then this isn't cool
or acceptable. You probably wouldn't find it acceptable if the keyboard
mapping changed two keys due to some race condition from time to time.
I don't know how long you have been using oS or it's predecessors: Has
there been a time when the default has not been: tty1...tty6 X:0 X:1 ?
So what happens right now is that with the new systemd, this behavior
changes. The assignment is no longer fix but depends on "raceconditions"
instead. So what is needed is a way to have a fixed mapping of tty to
virtual console - and that the same X session always ends up on the
same virtual screen.
I thus have put the above paragraph into the bug above.
Ciao
Jörg
--
Joerg Mayer