On Thursday 26 February 2004 11:14 pm, David Gethings wrote:
> On Thu, 2004-02-26 at 22:03, Zabil Maliackal wrote:
> > Tried the above, took an awful lot of time in doing what it did.
> > Did not notice big improvements in the application start up though.
>
> I use prelink -afhmR. -m tries to use less memory (I don't have much).
>
> use 'man prelink' to find out what the other option do. They might make
> a difference. Then again they might not. I'm no prelink expert.
>
> Also make sure that all libs are found. If you get an error message
> saying that a lib could not be found then that executable is not
> prelinked, AFAIK.
Ran prefdm with the the options that were mentioned above.
A bit of improvement , but i guess it might not be noticeable, here and there.
Here is what is there in my prelink.conf. I hope the directories are taken
recursively. There is no specific entry for the Kde dir's
-l /bin
-l /usr/bin
-l /sbin
-l /usr/sbin
-l /usr/X11R6/bin
-l /usr/kerberos/bin
-l /usr/games
-l /usr/libexec
-l /var/ftp/bin
-l /lib
-l /usr/lib
-l /usr/X11R6/lib
-l /usr/kerberos/lib
-l /usr/X11R6/LessTif
-l /var/ftp/lib
-l /lib64
-l /usr/lib64
-l /usr/X11R6/lib64
-l /usr/kerberos/lib64
-l /var/ftp/lib64
___________________________________________________
.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
