Dear Suraj,
Thanks for the wonderful explantion on CPU loading with terminal and GUI
applications.
Regards
T.KaruppuSwamy
Suraj Kumar wrote:
T.KaruppuSwamy (T & B) wrote:
,----
| I am working on terminal and other GUI applications simultaneously
`----
Just because something is a GUI app doesn't mean it would suck
CPU/memory/disk. It all depends on the app. A gcc running on the
terminal is more CPU hungry than, say, an XMMS running hi-fi plugins.
,----
| 1. What way the application I am installing is related to the kernel?
| i.e Whether the applications depends tightly on kernel version? why I
| am asking is this, many applications are labelled for distro, not for
| kernel version. IN SHORT I WANT TO KNOW THE DEPENDENCY OF KERNEL
| VERSION, DISTRO VERSION, DESKTOP (KDE, GNOME..) AND APPLICATION WITH
| EACH OTHER?
`----
What do you mean by "many applications are labeled for the distro"? I
cannot think of distro specific apps (unless its some
core-distro-related app like a package manager (apt-get for debian,
rpm for redhat, etc.,.).
In short, The kernel is not really an issue as long as the app is only
using standard libc, other library calls. For example, you can well
compile the same "hello world" code on FreeBSD, Linux, HURD, DOS,
etc.,. It depends on the application and what it is trying to do. For
example, if you wrote an application that keeps polling for a
particular file in /proc/sys/wherever/wherever... your app is procfs
dependant. So if either you are on a kernel which does not have
/proc/sys OR if you have disabled procfs, your app wont work.
,----
| latest kernel, Can I keep my Redhat 8 distro undisturbed with only
| kernel update of 2.6.8.1. If I do so what are all the pros and cons on
| it?
`----
"undisturbed" is the way to go. Dont disturb it unless you are asking
for adventure.
cheers,
-Suraj