Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

KDE 4 problems highlight shift from community users to consumers

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News KDE 4 problems highlight shift from community users to consumers
# 1  
Old 07-16-2008
KDE 4 problems highlight shift from community users to consumers
07-16-2008 11:00 AM
The reasons for the user revolt against KDE 4, which we reported on yesterday, are still being sorted out. They appear to be a complex mixture that includes the assumptions that KDE used in its planning, the rush by distributions to include a release that was not ready for general use, and sensationalism in free software blogs and journalism. One reason that has yet to be discussed is one of the potentially most significant -- the apparent shift in the FOSS user base. Judging from the quickness and thoroughness with which KDE 4 was rejected, the audience for free software seems to have shifted from a small group of knowledgeable users that treasures innovation to a larger one that values convention and familiarity and is actively suspicious of change.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Problems in analysing SSH LOG users & time

Attached is the log file that I have generated through the following script: last | head -2 |sed '2q;d' |awk '{ print $1"\t"$2"\t"$3"\t\t"$4"\t"$5"\t"$6"\t"$7"\t"$8"\t" $9"\t"$10"\t"$11}'>>/var/log/logadmin/logtest.txt But now I'm unable to run the following operations on it: 1. Count... (1 Reply)
Discussion started by: Lionking93
1 Replies

2. HP-UX

Users problems

Hi everybody! We have created a user, like another one that works well. But this "bad" user cannot loggin into an application that is running on informix bbdd. When the user try to loggin, it appears an error message: "killed" and logout. Do you know what can we do? where can we find the... (2 Replies)
Discussion started by: faca317
2 Replies

3. SuSE

SUSE 9.1 - Problems with Adding new users plz help

Hi every one, I recently installed Suse 9.1 and added two users during installation with out problems. I have tried to add another user using the following cmd: 'useradd pite' and 'passwd xxxx' and got a message new user and password added. But when i tried to create a directory using... (3 Replies)
Discussion started by: sybella1
3 Replies
Login or Register to Ask a Question

LEARN ABOUT CENTOS

kdeinit4

KDEINIT4(8)							 KDE User's Manual						       KDEINIT4(8)

NAME

       kdeinit4 - KDE process launcher.

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[1] to report them.

AUTHORS

       Waldo Bastian <bastian@kde.org>
	   Author.

       Mario Weilguni <mweilguni@sime.com>
	   Author.

       Lubos Lunak <l.lunak@kde.org>
	   Author.

NOTES

	1. bugs.kde.org
	   http://bugs.kde.org

0.01.01 							    2008-10-03							       KDEINIT4(8)