ok, here's the scoop, google has similar, but nothing that quite fits the bill. here is what I'm up against:
i have a linux system that is running both kde 3.x and gnome 2.x, selectable via gdm.
the kde 3.x app menu is heavily modified and i'm looking for a way to import that over to the... (0 Replies)
I've just done a brand new full clean install of OPenSUSE 10 and thought I'd take a look at Gnome. Having spent a day playing with it I've decided I prefer the familiarity I have with KDE.
How do I now install KDE? I've tried logging off to log back on with a different envionnment but KDE... (1 Reply)
i have been reading some atticles but i still do not understand the diferrence btw KDE & Gnome. Someone once told me he prefers Gnome to KDE 'coz of it's audio support & Redhat says ver 7.3 has KDE 3.0 & Gnome 1.4. So could someone explain? (2 Replies)
Hey all :)
I finally got around to installing FreeBSD 4.4, which considering it's my first attempt with *nix, didn't go too badly. I've managed to configure X and everything else, but I've got a bit of a problem, lol.
I installed KDE and GNOME. I had a rough idea as to what they were, but I... (5 Replies)
KDEINIT4(8) KDE User's Manual KDEINIT4(8)NAME
kdeinit4 - Start all other KDE programs and kdeinit loadable modules (KLMs).
SYNOPSIS
kdeinit4 [--help] [--no-fork | --no-kded | --suicide] [+programs | programs]
DESCRIPTION
kdeinit4 is a process launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable
modules (KLMs) starting them more efficiently.
Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption by
a substantial amount.
kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster
because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses need
to be linked.
DISADVANTAGES
The process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application
name as shown by ps. However, applications like killall will only see kdeinit4 as the process name. To workaround this, use kdekillall
(from kdesdk/scripts) for applications started via kdeinit4.
OPTIONS --help Show help about options
--no-fork
Do not fork, i.e. do not exit until all the executed programs ends
--no-kded
Do not start kded
--suicide
Terminate when no KDE applications are left running
+programs
runs the programs handling requests
programs
runs the programs without handling requests
USAGE
A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program
FILES
/tmp/kde-$USER/kdeinit4_$INSTANCE
...
ENVIRONMENT VARIABLES
$HOME Specifies the home directory of the current user
$KDE_HOME_READONLY
Specifies if the home directory of the current user is read only
$KDE_IS_PRELINKED
If set, tells kdeinit4 that the KDE programs are pre-linked.
(Prelinking is a process that allows you to speed up the process of dynamic linking.)
$KDE_DISPLAY
If set, tells kdeinit4 that it is running on a KDE desktop.
SEE ALSO
kded, kdekillall
BUGS
There are probably tons of bugs. Use bugs.kde.org: http://bugs.kde.org to report them.
AUTHORS
Waldo Bastian <bastian@kde.org>, Mario Weilguni <mweilguni@sime.com>, Lubos Lunak <l.lunak@kde.org>.
2008-10-03 KDEINIT4(8)