From: <lakicsv@ntlworld.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] My take on prelink
Date: Tue, 7 Jan 2003 13:10:21 +0000 [thread overview]
Message-ID: <20030107131021.ZUUR22267.mta01-svc.ntlworld.com@[10.137.100.61]> (raw)
Dear Devs,
I was very excited about prelink, since on my Athlon 1800 XP machine with 512 DDR, KDE startup times still bother me...(I guess the faster machine you have the more you expect:-))
So I looked at the (otherwise clear and well written) prelink guide. I was very unhappy with what I found there:
In the era of fast PC-s, one only need to have a couple of programs prelinked: to me this is kde (konqi mainly but others as well), wine, winex and probably (if prelink would help it) openoffice...(I do not run gnome). All the rest of my programs startup like flash, so there is no practical advantage to prelink them time to time...
Those of you familiar with the prelinking guide already figured where I am getting at:
- wine and winex cannot be prelinked (yet)
- since I have nvidia graphics, all my kde stuff is linked to that so I cannot prelink any KDE apps...
Yes, I could switch to nv driver, but then I would loose my TV-out for watching dvds, and I cannot start any movie in fullscreen with xvideo under mplayer (trust me I tried hard) not to mention games...
Is there any hope to remedy these problems? How other distros handle the nvidia probs? Red hat and mandrake supposedly prelinked, and they use nvidia rpms...
What about wine? Even running calc.exe can take a good ten seconds to start up...
It is not supposed to be a flame just wrote this in the hope that someone might be able to help...
Cheers: Viktor
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-01-07 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 13:10 lakicsv [this message]
2003-01-07 13:32 ` [gentoo-dev] My take on prelink Stefan Jones
2003-01-07 21:19 ` Viktor Lakics
2003-01-09 15:12 ` Paul de Vrieze
2003-01-10 6:07 ` [gentoo-dev] " Jeff Stuart
2003-01-10 22:35 ` Stefan Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20030107131021.ZUUR22267.mta01-svc.ntlworld.com@[10.137.100.61]' \
--to=lakicsv@ntlworld.com \
--cc=gentoo-dev@gentoo.org \
--cc=viktor@lakics.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox