If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Fedora 15 Lovelock Alpha Arrives

03-08-2011, 10:40 AM

Phoronix: Fedora 15 Lovelock Alpha Arrives

Dennis Gilmore has announced the official release of Fedora 15 Alpha. This next Fedora release, which is codenamed "Lovelock", brings a number of new features to this leading Linux distribution, including the GNOME 3.0 desktop...

Comment

The answer to your indirect question/doubt is alctualy in the first video you listed around 20:00.

That makes we wonder if you even saw them (and remembered what was in them).

So for example we have the seemingly notorious KDE 4 series and D-bus and D-bus craches. What happens is that D-bus brings down the entire system (from an end-user perspective). Haters better be aware that this is what caused the nasty crashes...

But now we have systemd. systemd basically represents a collection of fake sockets that tracks processes with cgroups. Now D-bus crashes, systemd notices this, takes over with its fake D-bus socket, restarts D-bus, freezes up KDE whenever it reads out a sync, pass the socket back to the actual D-bus and everything resumes without the user even noticing.

Comment

The answer to your indirect question/doubt is alctualy in the first video you listed around 20:00.

That makes we wonder if you even saw them (and remembered what was in them).

So for example we have the seemingly notorious KDE 4 series and D-bus and D-bus craches. What happens is that D-bus brings down the entire system (from an end-user perspective). Haters better be aware that this is what caused the nasty crashes...

But now we have systemd. systemd basically represents a collection of fake sockets that tracks processes with cgroups. Now D-bus crashes, systemd notices this, takes over with its fake D-bus socket, restarts D-bus, freezes up KDE whenever it reads out a sync, pass the socket back to the actual D-bus and everything resumes without the user even noticing.

Self-healing

Ok, actually yes in a certain sense it can work this way for dbus. I read your previous statement that systemd in some mysterious way stops applications from crashing, which of course is untrue.

You should just write that systemd can start service again. This only works for systemd services activated by socket.

Comment

The answer to your indirect question/doubt is alctualy in the first video you listed around 20:00.

That makes we wonder if you even saw them (and remembered what was in them).

So for example we have the seemingly notorious KDE 4 series and D-bus and D-bus craches. What happens is that D-bus brings down the entire system (from an end-user perspective). Haters better be aware that this is what caused the nasty crashes...

I have never seen D-bus crash on gnome so it's probably just the Qt D-bus bindings that are buggy.

But now we have systemd. systemd basically represents a collection of fake sockets that tracks processes with cgroups. Now D-bus crashes, systemd notices this, takes over with its fake D-bus socket, restarts D-bus, freezes up KDE whenever it reads out a sync, pass the socket back to the actual D-bus and everything resumes without the user even noticing.

Self-healing

And because things usually crash for a reason (i.e. bugs) chances are it will crash again and before you know it you are stuck in an infinite loop of crashing-healing-crashing-healing...

Comment

Maybe that could be possible to write services for desktop things like a task bar or other foo app to restart them if they crashes. Maybe it is, maybe not - I do not know. But I doubt that to happen anytime soon - so far there are systemd services only for a few apps - less than 10% services for Fedora.

Comment

Maybe that could be possible to write services for desktop things like a task bar or other foo app to restart them if they crashes. Maybe it is, maybe not - I do not know. But I doubt that to happen anytime soon - so far there are systemd services only for a few apps - less than 10% services for Fedora.

I meant the kernel. Crashing the graphics driver (you can gues where that is ) in Windows will simply restart the driver and the rest of NT6.x (which is what Vista and 7 is build upon) is modular with defined interfaces which also restart on crashing (unless you run into some very fundamental stuff).