
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
600877ad4eb7ec5032f170eced51c5dd startkde.faster
45e5ebe2bbf7914deaef995332dd905c startkde.fastest
This script is now outdated as it does little to improve preformance in kde 3.0.2 and up. But I will leave it up for people with older versions of kde.
UPDATE: There are now 2 scripts. One is named 'startkde.faster' witch is basicaly
the same as version .05 but with some bug fixes. The other is 'startkde.fastest',
witch is MUCH faster, but does not include font overiding and may not work on
all systems the way you'd like it to. So try 'startkde.fastest' and if something
doesn't work switch to 'startkde.faster'. So just take the one you want and rename
it startkde, set the path in the first three lines of the script, and put it in your
path.
================================================================================
This is a drop in replacement for your startkde script. It disables ksplash
(It is so fast you don't need it!).
It works by basically pre-launching kdesktop, kicker, and kwin and launches kde
in the normal way. So you have a ready system wail the rest of kde loads. Then
when the kdeinit discovers that the window manager desktop and panel are already
running it just doesn't start another copy. (So you can start programs etc. and
you probably won't notice other stuff because it doesn't seam to be CPU or disk
intensive)
To use it just rename your existing startkde script and put this one in it's
place.
To clarify, the script is by default configured to work with kde3 located in
/opt/kde3. If you have kde2 or are not located in /opt/kde3 you should edit the
first 3 lines or it will not work properly.
=================================================================================
Quirks:
Ktip and the sound are still controlled by the normal startup so they may come
in later than you want. If you still want to have ktip, or a timely startup sound
then tell ktip not to start on login by unchecking it's box when it loads, and
uncomment the line about ktip in the script. (or with sound, just add artsd to
the list of pre-launch apps)
Next if you have the feature to have the cursor blink when you start an application,
that may happen after you login. (If this bothers you have to disable it.)
Finally it may be very slow logging off. If you experience this try using he
button on the panel or the one in the right click menu instead of the one in
the K menu. (This does not help under some versions of kde though)
If you have any other problems just e-mail me.
18 years ago
.09 -- Big speed improvements (best with kde3) and forking of script.
.06 -- Bug fixes
.05 -- include more of the default startkde stuff (font overriding etc.)
.04 -- Fixes/work with red-hat 7.3 (hopefully) and objprelink
.03 -- Rewrite to merge kde3/kde2 scripts
.02 -- Works with kde 2.2
.01 -- Initial release
18 years ago
.09 -- Big speed improvements (best with kde3) and forking of script.
.06 -- Bug fixes
.05 -- include more of the default startkde stuff (font overriding etc.)
.04 -- Fixes/work with red-hat 7.3 (hopefully) and objprelink
.03 -- Rewrite to merge kde3/kde2 scripts
.02 -- Works with kde 2.2
.01 -- Initial release
PARENA
18 years ago
Report
KzT
18 years ago
startkde.fastest:
Time from login to kicker: 26.04s
Time from logoff to login screen: 30.18s
System Services: Apprx 10-20s
startkde[without fonts]
Time from login to kicker: 49.45s
Time from logout to login screen: 12.34s
System Services: Already done
In my not so expert opinion, the only people who should use this are the people running KDE on OLD machines. Otherwise, just takeout the fonts, and make other optimizations. However, it was a good idea - nice try. Maybe additional work could iron out these problems ;-)
Report
Seli
18 years ago
The patch is wrong, because it breaks the proper startup order, and your KDE may therefore not work correctly. There are also people for whom it actually doesn't cause any startup time decrease.
In case somebody will carefully compare this modified startkde script and the original one and will find out what's causing the big difference for some people, please report it.
Report
pippi
18 years ago
now that i had a closer look to the scripts is clear that i am an idiot. SuSE8 defaults to ".kde", these scripts to ".kde3" so it was clear that my configuration was ignored when using theses scripts instead of SuSE`s.
Having changed the definitions in your script-header from ".kde3" to ".kde" works everything very fine.
Thank you for your work!
Bye
-Pippi L.
Report
Rafaga2k
18 years ago
Report
uk3y4
18 years ago
rotfl
Report
pippi
18 years ago
Report
davidsansome
18 years ago
I know I can have multiple X sessions, but it's just not the same :-)
Report
Ptero4
16 years ago
Report
asifalirizwaan
18 years ago
Thank you, I appreciate it.
Report
emissary
18 years ago
just tryed it with kde 2.2.2
wow! thats fast !! ;)
nice work !!
what about submitting it to the kde
people for possible inclusion ?
Report
pacal
18 years ago
Report
ZIOlele
18 years ago
Report
tkaitchuck
18 years ago
If you don't have kde3 you may want to wait a few days for a kde 2.2 version. Or you could try inserting those 3 "Preload" lines into your startkde script and see what happens.
Report
ian
18 years ago
I love it! Thanks for your great work!
ian
Report
voz
18 years ago
Report
nomis80
18 years ago
Report
mksoft
18 years ago
If you'll look into /etc/rc3.d (or whatever directory your distro using and your default run level) you see something like SXXcups SXXsamba.
XX determines the order of services started (lower means started first). Arrange them to your liking.
Report
nomis80
18 years ago
Report
tkaitchuck
18 years ago
Because it loads the Desktop/panel/window manager first, then does the usual kde stuff.
So then when the kdeinit discovers that the window manager desktop and panel are already running it just doesn't start another copy.
So after about 20 sec (usual kde load time) it is exactly the same as it would be with the default script.
All the problems I mentioned are either come directly from these thins not being session managed in the usual way. (So I don't think there will be any other problems)
About the fonts though, If you want to use font overriding, just copy that section from your existing startkde3 script. (I just removed it because it took time and it is not something most people need)
If you have any other problems just e-mail me.
Report