I have been accused of 'solo action' recently, so I'll announce the
change I want to make to the desktop spin here.
If there are good reasons why the desktop spin should be a nfs or nis
client, speak up; otherwise I'll commit this:
diff --git a/fedora-livecd-desktop.ks b/fedora-livecd-desktop.ks
index 52c1d0a..4dcf011 100644
@@ -67,6 +67,10 @@ festvox-slt-arctic-hts
# drop some system-config things
I don't know what is the idea of those yellow bubbles and I don't want to know.
This is an operation system running on a computer. My naivistic notion is that if s.th. is cyber let it look like cyber at full power, not like 'a yellow submarine'.
Why don't you try s.th. in Leo Villareal style, for example.
See the movie:
With the move to more mobile devices (laptops, etc.), we're more likely to
have very long-running sessions that are just suspended and resumed, as
opposed to a workstation that is logged out every day.
This means that for me on rawhide, my session is often much longer-lived than my
software set, as I'll have a two-week session that is running older code
that I've long since upgraded past. Even for those on an actual release,
this can be an issue given our update stream.
For system-level services, we have the idea of try-restart on upgrades; if
the service is running, we automatically restart it on upgrade. How can
we implement this sanely for session/desktop services? For example, in
my session I see:
any number of status icons (volume control, gpk, g-p-m, etc.)
... and more I'm forgetting ...
Since very few of these have state, can't we implement a framework where
they automatically get restarted on upgrade?