I would really like to know why does linux access the >disk so much (in GUI mode) to fire-up even a small application like terminals
windows? What is it that it reads/writes so much? This is
irrespective of >m/c configuration.
veejay
My swap is 4 times the RAM still i also face the same problem...
(wading in late, excuse)
What is the distribution ? What machine config ? More importantly do you have anything running in the background ? Excessive logging ? You have some inefficient program running in the background which updates a few KB file on disk every few seconds ? There could be many reasons. Your problem seems not to be a generally observed phenomenon.
man! i am not complaining about the hdd access my system does.... mine is a RHL8.0 on a P3-933 mhz, with 128MB SD RAM, the hard disk also runs at 5400 something RPM... swap alloted is half GB,
i've seen hdd access right from the days i had RHL6.0, then 7.1 and now 8.0... I've always chosen to do a full installation off the CDs, just to taste everything that's inside...
Agreed i have many services running, I just turn it on to work with it... telnetting into smtp/ftp/telnet servers...
I think the people here are comparing the hdd access of M$ windows with gnu/linux... Windows loads all the configuration settings (Registry) into the RAM at startup, whereas gnu/linux apps have to read the config files the first time they start (am just speculating a reason)...also many services report their errors to the root's mailbox... These might be one of the many reasons of unexpected hdd access... Is my justification correct???
-
xterm