Re: high memory usage in KDE?

On Thu, Aug 08, 2002 at 05:11:16PM -0500, nick phillips wrote: > loaded into memory and so on. i'm a little concerned about KDE's memory > usage at the moment. when i boot into KDE, with no applications running, and > issue the 'top' command, it shows about 95MB used, with 35 MB available. > one l

XF86Config for a DECpc 450SLC/e?

I tried to get X up and running on an old DECpc 450SLC/e 486sx laptop, running woody last night. I installed the xserver-vga16 package: I also installed wdm and then tried s

Re: high memory usage in KDE?

Hi Nick, nick phillips <[EMAIL PROTECTED]> wrote: > so, my question is: is this an ordinary amount of memory for KDE to > use? are there any ways to decrease memory usage so i can minimize > using swap space? or should i think about switching to GNOME or > another window manager? i like KDE a lot

Are you coming to Marbella?

Title: Tures Andalucia 2002 - Residential Tourism Fair   Dear Sir or Madam: We are pleased to invite you to an exclusive event to enjoy Marbella, one of the most charming places in Andalusia, in the South of Spain. TURES Andalucia® 2002, the

unsubscribe

unsubscribe

unsubscribe

unsubscribe

Head & Rotor VE 08/09

Dear Sir, *¡°ÖзͨÅä¼þ³§¡±×¨ÒµÉú²úVE±ÃÍ·(VE·ÖÅä±Ã±ÃÍ·×ܳÉ),Ö÷ÒªÐͺÅÓÐ ÎåÊ®Áå4JB1,¿µÃ÷˹6BT,ÒÀά¿ÂµÍÅÅ·Å,ÎåÊ®ÁäƤ¿¨. * ÖзͨÅä¼þ³§ÓжàÄêÉú²úVE±ÃÍ·µÄ¾­Ñé, ×÷Ϊ½ÏÔç½øÈëÓͱÃÓÍ×ìÐÐ ÒµµÄרҵ³§,ÎÒÃÇʱ¿Ì¸ú×Ù¹ú¼Ê¸÷µØÆäËü²ñÓÍȼÓÍÅçÉäϵͳµÄÖÆ ÔìÉ̵ÄÉú²ú¹¤ÒÕ,²¢ÇÒ²»¶ÏÎüÊÕ

Can't boot from hd after upgrade to woody

Platform: DECpc 450SLC/e (laptop w/486, 8MB RAM, 250MB HD) This machine got potato installed from floppies last year. Yesterday I started it, and it booted nicely from hd with the kernel-image-2.2.19pre17-compact kernel from a potato floppy install. I tried upgrading it to woody by editing /etc/

unsubscribe

unsubscribe

Re: Can't boot from hd after upgrade to woody

> Steinar Bang <[EMAIL PROTECTED]>: > Platform: DECpc 450SLC/e (laptop w/486, 8MB RAM, 250MB HD) [snip! boot worked with potato, but not after dist-upgrade to woody] > Is this caused by a LILO upgrade and incompatibilities with old > hardware? It seems to have been caused by the LILO upgrad

unubscribe