[Bug 187154] Add kuser, ksystemlog, kinfocenter and ksysguard as kcm modules to be accessible via KDE4 system-settings

[pipaceliny]

https://bugs.kde.org/show_bug.cgi?id=187154





--- Comment #14 from pipaceliny <pipaceliny interia pl>  2009-03-14 23:51:14 ---
(In reply to comment #13)
Hello

I was waiting for such a question ;-) Let's rock

1111.

> > To set something good you have to monitor something to know what is
> > needed to be set and how.
>
> Examples?

a)  Ksystemlog. 

1.Kgrubeditor and kernel. You see in kgrubeditor wich kernel is active as a
booting one and then in ksystemlog you monitor it's logs because of your system
 hung or you want to check kernel logs and you can check in kgrubeditor witch
kernel is booted as you prefer.
2.Samba - you set samba shares trough system-settings, not working, view logs
trough ksyslog then repair samba.

b).Ksysguard. 

1.Sometimes your kde services runing in the kde4's background are crashing, you
can check in system-settings services manager which kde services are set to run
then run ksysguard to check are they are present or crashed.
2.Your system is slow, because of too many kwin effects - you chceck in
ksysguard properties and info about your system performance and then switches
off some kwin effects for better performance

c).Kinfocenter .

1.Your graphic card is not working, no kwin 3d effects, you can check in
kinfocenter opengl info - is it installed and present there. Then install
drivers and set kwin working after X restart.
2.Audio settings problem, you are newbie, you don't know how to get your sound
card info via command line, you open kinfocenter get there info about sound
card or graphic card, check out forum then install for example oss or fglrx
then configure it trough system-setting

You want more? 


2222.

> > The first thing is that one is connected to the other so I
> > think adding monitoring category in system-settings will not cause the
> > mess because every people using linux has to know how to read
>
> So you are saying that every new Linux user *has* to know about
> a) system logs
> b) system processes
> and then we complain "Linux is hard to use" just because we have three
> separate applications, each tied for a specific use? This won't work at
> all. Weekend users should not need ksysguard and ksystemlog at all; who
> really need to use any of them would not bother at all opening a separate
> application, that is *tied* to that, and not a "generic container" of
> whatever has "system" in its name.

a) Has to know how to read (READ WORDS) not has to know about system logs, but
if earlier the newbie will discover system logs - better for him, don't you
think so? 
b) Know about System processes - yes, alt control delete in windows and
intelligent people can do with windows taskmanager.exe tabs? So by the analogy
lets find something familiar to taskmanager.exe in linux the newbie thinks.

You are wrong ksysguard was one of the first application I started to find when
I first installed Mandrake 10.0 few years ago (my first was Red hat 9 with
gnome ;-) - I miss the hat by the way ;)

You are talking about weekend users. Weekend users use windows. They are
frightened when I call linux ;-). If you start with linux - you have two ways
fight with small system problems ;-) or give it away. If you stay with linux
sooner or later you will have to use ksysguard, then kinfocenter and then
ksyslog. Ksyslog I think at the end of the list, why at the end, because newbie
doesn't know that there is such a thing as ksyslog. If ksyslog will be visible
in system-settings the newbie may start to be interested with this, discovering
after some time how useful tool it is, even without options to set settings!
;-)


> Assuming partitionmanager is a kcm: while you do real partition work (eg
> resizing, creation, etc), you cannot do any other configuration from the
> same application. IMHO this should really bad.

I meant in my post that there is no system-settings entry for partitionmanager.
It is installed on my system. 

Thanks
Darek

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.