On Wed, Mar 17, 2004 at 07:09:08PM +0100, Lubos Lunak wrote:
> - where to do this caching. KDM (hello Ossi) and init.d script seem
> the two places where this could be done, it takes some time to log in
> using kdm, and there are definitely placed during init.d startup when
> the HDD must be pretty bored. Ossi, could you please provide some
> thoughts on this? I don't know how that works, and there could be two
> places where to have this caching running, while typing in kdm, and
> also while initializing X (at least it seem to be that while
> initializing the graphics mode or whatever it's just waiting for about
> two seconds and nothing is really happening).
> 
http://bugs.kde.org/show_bug.cgi?id=63789 :)
the disadvantage of my envisaged approach is, that the preloading won't
start before the greeter is up, and that will be only after the X server
did "nothing" for a few seconds (and loading the greeter will be
somewhat slower without the preload as well). it wouldn't be impossible
to change that, though - only that some really "frontend-style" things
(the user preselection) would have to move to the backend.

the alternative is preloading kde unconditionally; this approach would
make sense for kde-only systems/distributions. for that, a separate
init.d script would be the cleanest solution, i think.
i think this solution is more effective (and "simpler" for me (read: a
no-op :)), but it looks even more like a hack (hard-wiring something is
usually no good ... in any case it must be a yast/debconf/... option).

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
_______________________________________________
Kde-optimize mailing list
Kde-optimize@kde.org
https://mail.kde.org/mailman/listinfo/kde-optimize