Stop Microsoft

Operating Systems => Linux and UNIX => Topic started by: DukePuke on 5 April 2004, 19:26

Title: KDE is slow
Post by: DukePuke on 5 April 2004, 19:26
Actualy yes, I have 3.1 version of KDE , and that windows managing, browsing files/internet is actualy not fast, i have to wait about 1-1.5 seconds to wait until directory opens, etc. Can you give some tips , how to configure enviroment for faster work? Actualy I realy have problems (slow) then 10 web pages is opened, it damn slows down much.

My komp is AMD duron 850@900MHZ
128 MB RAM
8MB integrated video

I keep turned all animations off, but cool tweak advices would be acceptable  (http://tongue.gif)
Title: KDE is slow
Post by: Refalm on 5 April 2004, 19:32
The slowness is due to the QT core.

If you have that much VGA memory, just use XFCE instead. You'll be able to use all your favourite KDE programs, but it runs faster.
Title: KDE is slow
Post by: DukePuke on 5 April 2004, 19:36
man, I typed xfce in console, it added another panel in top of window, man I need to tweak, not to make my system on knees
Title: KDE is slow
Post by: Refalm on 5 April 2004, 20:48
quote:
Originally posted by DukePuke:
man, I typed xfce in console, it added another panel in top of window, man I need to tweak, not to make my system on knees


Hahaha, no  (http://tongue.gif)

Do this:
Instead of logging in to your system at the console and typing the startx command to start the X Window System, you can configure your system so that you can log in directly to X.

You must edit one file, /etc/inittab, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you will have a graphical login prompt.

Open a shell prompt. If you're in your user account, su to root by typing

su

Now, type vi /etc/inittab to edit the file with vi. The file /etc/inittab will open. Hit the INSERT button. Within the first screen, you will see a section of the file which looks like this:

# Default runlevel. The runlevels used by RHS are:
#   0 - halt (Do NOT set initdefault to this)
#   1 - Single user mode
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - unused
#   5 - X11
#   6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:

To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5.

After you're done, hit the Escape button and type
Code: [Select]
press Enter and type
Code: [Select]
and press Enter.

Reboot, and you'll see a nice login screen from which you can boot KDE, Gnome or XFCE  (http://smile.gif)
Title: KDE is slow
Post by: WMD on 5 April 2004, 22:41
Just to point out - the X11 mode in Slackware is runlevel 4, not 5 as in most distros.

As for KDE, you can speed it up by updrading to 3.2.1, or getting a 2.6 series kernel.  However, you may not be ready for that.

And try Gnome first if you want to ditch KDE.
Title: KDE is slow
Post by: DukePuke on 5 April 2004, 23:39
Actualy Refalm, thanks, but I like way choosing/launching X style with wmconfig and startx.
btw about vi redaktor, I havent understood how it works yet  (http://tongue.gif)  (I prefer more... uh forgot its name, beggining with "p")

WMD:
and about new KDE and Kernel... Do upgrading them realy increase my performance much? I dont want to compile this shit all night just for 2-5% performance increase.

BTW thanks!
Title: KDE is slow
Post by: Refalm on 6 April 2004, 00:20
Vi is easy. It begins in non-edit mode. To switch to edit mode, hit the INSERT key.

To save a file, you've got to leave edit mode. Press the ESC key to enter non-edit mode.

Type :w to save, type :q to quit. If you can master vi, you'd never have to worry about "hey, is pico going to be installed on that system?" ever again  ;)
Title: KDE is slow
Post by: skyman8081 on 6 April 2004, 10:17
try nano or pico, FAR mor intuitive than vi for doing text editing.

just these people think that poor UI design is a good thing.
Title: KDE is slow
Post by: WMD on 6 April 2004, 10:50
quote:
Originally posted by DukePuke:
WMD:
and about new KDE and Kernel... Do upgrading them realy increase my performance much? I dont want to compile this shit all night just for 2-5% performance increase.

BTW thanks!



For KDE 3.2, you can upgrade by running pkgtool at the console, removing all the KDE packages, and then downloading the new ones from ftp.slackware.com/pub/slackware/slackware-cuurent.  (Or use a mirror that's faster.)  Then use pkgtool to install those.
I'm not sure how much faster 3.2 is, but its faster.

As for kernel 2.6, you'll have to configure and compile that (but it takes 30-45 min., not all night).  The instructions come with the tar.gz file.  Then you (unfortunately) have to reformat your swap after booting the new kernel: mkfs.swap /dev/hda3 or whatever your swap is.  The 2.6 kernel will help more than the KDE upgrade, but its a bit tougher.

EDIT: Use pico, it's easier than vi.  Actually, vi  is only easy to Vi fanboys.  (http://tongue.gif)   ;)

[ April 06, 2004: Message edited by: WMD ]

Title: KDE is slow
Post by: WMD on 6 April 2004, 10:59
Alright, for upgrading KDE:

1.  Exit KDE and set wmconfig to something else.

2.  Uninstall the packages listed here:
ftp://ftp.slackware.com/pub/slackware/slackware-9.0/slackware/kde/ (http://ftp://ftp.slackware.com/pub/slackware/slackware-9.0/slackware/kde/)

3.  Download/install the packages available here:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/kde/ (http://ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/kde/)

4.  Re-choose KDE in wmconfig.  Start it.
Title: KDE is slow
Post by: DukePuke on 6 April 2004, 17:38
i dont know. i just fear. I will mess everything up and stick with gnome of other graphical enivronment (checked some alternatives and they all so sucked, lol). No no maybe in weekend,my ISP dont count data transfer during this.

Btw vi is stupid, file editing is total mess, you press insert, ok, but you go one line above and all edited stuff dissapears, lol. Finaly i got bored of this shit, end hit Esc, and I typed :q
Vi shitprompted me that file modified, not saved, and do it every time i wanted to quit.
":q" means quit right?
Title: KDE is slow
Post by: Refalm on 6 April 2004, 17:45
Damnit, vi rules  :(
Title: KDE is slow
Post by: insomnia on 6 April 2004, 18:06
quote:
Originally posted by DukePuke:
i dont know. i just fear. I will mess everything up and stick with gnome of other graphical enivronment (checked some alternatives and they all so sucked, lol). No no maybe in weekend,my ISP dont count data transfer during this.

Btw vi is stupid, file editing is total mess, you press insert, ok, but you go one line above and all edited stuff dissapears, lol. Finaly i got bored of this shit, end hit Esc, and I typed :q
Vi shitprompted me that file modified, not saved, and do it every time i wanted to quit.
":q" means quit right?



Vi and Emacs are the only good editors.
People who don't know this simply can't use them.
Their's no sain reason for calling Vi bad.

On your system KDE shoudn't be slow.
 
Don't use an other kernel(2.6) yet.
First make 2.4 working like it shoud.
Compiling a kernel mostly means disabling stuff you don't need.
If you don't do this your kernel will use alot more mem. than needed.
This is what makes your system run slow, not KDE.
Title: KDE is slow
Post by: insomnia on 6 April 2004, 18:25
quote:
Originally posted by Sauron: GenSTEP Fanboy:
try nano or pico, FAR mor intuitive than vi for doing text editing.

just these people think that poor UI design is a good thing.



They don't.
They only don't care about people who fail to understand that simplicity is much more important.

[ April 06, 2004: Message edited by: insomnia ]

Title: KDE is slow
Post by: DukePuke on 6 April 2004, 20:32
about editor vi, ppl who uses them and proud of it i can understand. Its psichologicaly explainable

"I can use vi, and you try to learn it and still dont understant, lol, i am above you, you are n00b".

Actualy we need to look at this situation from third person view. What usefull jobs you do with text editor? Actualy dont know, but probably editing some files, some configuration, or even take a look at some scripts, or misc ascii filetypes just to see structure of them. Actualy this is NOT big deal. Editing files with text editor its very small , little-taking work for most users (probably 1-15 minutes in sum per day).So why should i learn vi, read manuals and damage my eyes, then i can use pico, which is very easy to use and almost dont require learning how to use it.

And btw topic related stuff : I thinked about my situation, and i've made decisions, i am not ready to update kde / kernel. lol I am using linux only 1 week allready

thanks
Title: KDE is slow
Post by: Refalm on 6 April 2004, 20:42
quote:
DukePuke: "I can use vi, and you try to learn it and still dont understant, lol, i am above you, you are n00b"


Not really. I just want you to use vi too, it saves time, and it's REALLY simple. It just doesn't use shortcut keys.

Really, it's this simple:
Edit mode (you can edit text now): Insert key
Non-edit mode (you can't edit text now, you must enter commands): Esc key
Useful commands to use in non-edit mode:
:w Save the file.
:q Quit vi.

There, that's the easiest explanation I can give you.
Title: KDE is slow
Post by: DukePuke on 6 April 2004, 21:24
thats ok, understood. It works, but it is still complex. If you edited file, wrote some shit, etc, and you wanna quit without saving. I press Esc to enter "non-edit mode" and :q, but lol it prompts its not saved. Ok, i dont need to save it! i do it again, the same prompt appears. I press CTRL-C even this dont work. So : to make exit from vi, you MUST to save work. No matter what you written in there, you must save before exit

btw i understand this situation, i believe vi is old unix tool, and I am just familiar with windoze notepad (lol) so I just preparing for nix systems

Thanks
Title: KDE is slow
Post by: KernelPanic on 6 April 2004, 21:36
:q! Exit without Saving.
Title: KDE is slow
Post by: savet on 6 April 2004, 22:08
another overlooked one is :w! for overwriting read-only files.  vi can be tricky to learn, but IMO there's nothing comparable for editing purposes...

[ April 06, 2004: Message edited by: Rio ]

Title: KDE is slow
Post by: DukePuke on 6 April 2004, 22:34
well, this makes me to think about vi. Somebody mentioned vi and emacs is best editors, curious to know what emacs can offer on editors table. btw name looks apple'ish
Title: KDE is slow
Post by: DukePuke on 6 April 2004, 22:36
hehe I like that it shows your position of percentage value in file, but lol how to quit it? btw every nix editor has its own way how to quit to the system.
Title: KDE is slow
Post by: insomnia on 7 April 2004, 03:34
quote:
Originally posted by DukePuke:
btw name looks apple'ish

 
It's not.
Emacs is one of GNU's biggest projects and mostly developed by R. Stallman himself.
Title: KDE is slow
Post by: skyman8081 on 7 April 2004, 03:49
don't think that emacs can get away so easiliyit is just as non-intuitive as vi.

they are both equally bad.

EMACS (Escape Meta Alt Control Shift) is just plain bloated, and requires a bunch of zany keyboard shortcuts to use.

I honestly prefer GEdit on a linux system and nano/pico if I am on a console only system.

it is a better editor, and more intuitive, seeing as applications should be built with the end user in mind, and not the machine.
Title: KDE is slow
Post by: hm_murdock on 7 April 2004, 03:50
quote:
simplicity is much more important.


INCORRECT

I could make an app that has one command to do one thing, but uses a simple prompt

Or I could make an app that lets you choose between two commands. The first one is the same command as the first app, the other command is "quit".

The second is better. Why? Discoverability.

If vi is so "simple", then why can't people just sit down and use it? Why do I find myself always reaching for emacs if I'm in the terminal, or TextEdit if I'm not?

In the end, it's all preference. I abhor uglyfied cli-based pseudo apps like that. Shortcut keys are better. GUI is better still.

CLI works for simple command-like apps. Things like the destitutely bad PlayFair that I downloaded today.

Get this... you download it and build it on Mac OS X... the home platform of iTunes... AND IT CAN'T GET YOUR iTUNES KEY TO DECODE AACS. You have to have an iPod.

the only platform this *NIX app works right on is... Windows.

WHAT.

THE.

FUCK.
Title: KDE is slow
Post by: WMD on 7 April 2004, 04:47
I like pico for console, KEdit/GEdit for simple GUI and Kate for coding.
Title: KDE is slow
Post by: insomnia on 7 April 2004, 05:41
quote:
Originally posted by JimmyJames: GenSTEP Founder:


INCORRECT

I could make an app that has one command to do one thing, but uses a simple prompt

Or I could make an app that lets you choose between two commands. The first one is the same command as the first app, the other command is "quit".

The second is better. Why? Discoverability.

If vi is so "simple", then why can't people just sit down and use it? Why do I find myself always reaching for emacs if I'm in the terminal, or TextEdit if I'm not?

In the end, it's all preference. I abhor uglyfied cli-based pseudo apps like that. Shortcut keys are better. GUI is better still.

CLI works for simple command-like apps. Things like the destitutely bad PlayFair that I downloaded today.

Get this... you download it and build it on Mac OS X... the home platform of iTunes... AND IT CAN'T GET YOUR iTUNES KEY TO DECODE AACS. You have to have an iPod.

the only platform this *NIX app works right on is... Windows.

WHAT.

THE.

FUCK.




Sorry Jimmy, But you a 100% wrong about emacs and vi.
An editor simply has to do a certain job.
Only Emacs an Vim can do everything.
That is more important than it's UI.

PS: Their's nothing wrong with their look anyway...
Title: KDE is slow
Post by: hm_murdock on 7 April 2004, 06:25
their look?? I thought they looked like some words

Code: [Select]

Code: [Select]

Form is equal to function. Never above or below in priority.
Title: KDE is slow
Post by: insomnia on 7 April 2004, 06:32
quote:
Originally posted by JimmyJames: GenSTEP Founder:
their look?? I thought they looked like some words

Code: [Select]

Code: [Select]

Form is equal to function. Never above or below in priority.[/b]



Yes.
So what's wrong with it?
...it is about file editing...
Title: KDE is slow
Post by: hm_murdock on 7 April 2004, 06:45
(http://jimmyjames.sytes.net/media/realedit.png)

Real Men use Real Editors.
Title: KDE is slow
Post by: hm_murdock on 7 April 2004, 06:55
I just remembered another real text editor

(http://jimmyjames.sytes.net/media/stillreal.png)
Title: KDE is slow
Post by: WMD on 7 April 2004, 07:12
Ah, good old SimpleText  (http://smile.gif)

BTW, this thread is WAY off topic.  DukePuke, sure you have been using Linux only a week, but upgrading KDE and compiling a kernel are not hard at all.  The kernel directions come in the download, and for KDE just do what I said in my post back on page 1.
Title: KDE is slow
Post by: DukePuke on 7 April 2004, 13:36
At last we returned on-topic
Actualy I will think about KDE, but idea about compiling/installing kernel makes me considering much, because:

1. i compiled lots of apps during this week. Only few of them worked after compiling. Much of them spited errors during ./configure, much of them during make.

2. My komp is slow, it kompiles 10 meg data about half of hour. Dunno how about kernel, he is bigger i think. I believe my comp realy will stuck with him.

3. reformat swap.. oh man , this sounds scary. Actualy yes, i fear, and most important i forgot hda# for swap..

btw thanks
Title: KDE is slow
Post by: hm_murdock on 7 April 2004, 15:08
hey, buddy.

if half the stuff won't compile for you, why don't you try a different method of installing? binaries, perhaps?

grab Mandrake or SuSE and run them for now. When GenSTEP comes out, get it. It'll kill all of 'em.

Then, when you've got more experience under your belt, then give Slack another try.
Title: KDE is slow
Post by: DukePuke on 7 April 2004, 16:45
heard somethere that new kernels has serious problems with old shitty motherfuckerboards ch!psets, like my via one (manufuckturer dfi)

[ April 07, 2004: Message edited by: DukePuke ]

Title: KDE is slow
Post by: Refalm on 7 April 2004, 19:07
vim is powerful. Both in Konsole/xterm/runmode3 and X.

Just open an html file with vim (in X), it's COOL  (http://smile.gif)
Title: KDE is slow
Post by: Commander on 10 April 2004, 01:03
i know people that hate vi or vim with all their power.  i, personally, dont mind it.  it's fast and mostly simple (although i hate the fact that the backspace doesnt work and i still haven't figured out how to delete unwanted newlines).  it good for quick edits since it;s faster to type 'vi' then nano, pico or emacs!  :D
Title: KDE is slow
Post by: DukePuke on 10 April 2004, 02:05
You can rename pico in yout bin direktory to one stupid letter : "p", and you will race around all vi's with speed
Title: KDE is slow
Post by: savet on 13 April 2004, 08:49
quote:
Originally posted by Commander - useSuse:
i know people that hate vi or vim with all their power.  i, personally, dont mind it.  it's fast and mostly simple (although i hate the fact that the backspace doesnt work and i still haven't figured out how to delete unwanted newlines).  it good for quick edits since it;s faster to type 'vi' then nano, pico or emacs!   :D  


To delete a line, position the cursor over the line you want to remove. Type the command "dd" and it'll cut the entire line.

*side note* you can undo your cut with the "u" command, or you can paste the line somewhere else using the "p" command.
Title: KDE is slow
Post by: flap on 13 April 2004, 15:33
quote:
If vi is so "simple", then why can't people just sit down and use it? Why do I find myself always reaching for emacs if I'm in the terminal, or TextEdit if I'm not?


You're making the mistake of confusing user friendliness with usability. Vi isn't "simple" to use and it's certainly not user friendly, but it's highly usable and very powerful, which is why people use it. You always seem to assume that everything should be user-friendly. Not everyone who uses a computer is a novice.