From kde-devel Tue Aug 31 14:53:27 2004 From: Luke Kenneth Casson Leighton Date: Tue, 31 Aug 2004 14:53:27 +0000 To: kde-devel Subject: how do i get rid of kdeinit dominating program names - entirely get Message-Id: <20040831150423.GJ11456 () lkcl ! net> X-MARC-Message: https://marc.info/?l=kde-devel&m=109396400731118 kdeinit is great, i am sure: it allows a speed-up of kde programs. there are alternative methods of doing speed-up, such as prelink. kdeinit is therefore more of a problem than it is a solution. 1) under SE/Linux, rules are created on a per-program basis. if kdeinit is _the_ only program, it is impossible to create proper policy files defining what program can run what, if they are all called kdeinit. therefore, kdeinit must die. 2) under FireFlier, it is possible to create per-program firewall rules. if kdeinit is _the_ only program, it is impossible to create proper per-program firewall rules if they are all called kdeinit. therefore, kdeinit must die. defining KDE_IS_PRELINKED is insufficient. KDE_IS_PRELINKED gets rid of _some_ uses of kdeinit. however it doesn't get rid of kdeinit kip_imap4. it doesn't get rid of kdeinit kio_file. i cannot do a firewall rule for kmail under FireFlier to allow only kmail (or kontact) to only be allowed SMTP outgoing traffic because this stupid kdeinit program runs the SMTP traffic, not kmail. so i have to grant kdeinit access to ports 80 and 443 for konqueror-usage, ports 25, 110 and 143 for kmail usage, and that's just not good enough. so. how do i kill kdeinit? how do i put a bullet in kdeinit's head? what ./configure compile-time options do i use to twist its neck and sever its head from the rest of the kde desktop? l. -- -- Truth, honesty and respect are rare commodities that all spring from the same well: Love. If you love yourself and everyone and everything around you, funnily and coincidentally enough, life gets a lot better. -- lkcl.net
lkcl@lkcl.net
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<