On that RAM... slackware with fluxbox/window maker ... you will be surprised at how nicely it works ..

Honestly, I'm not sure anymore, it's been a long time since I cared about memory usage. I used to use tik on a solaris box with something like 64 MB of RAM, and if I remember correctly, that supports AIM, ICQ, and MSN. On low-memory Windows systems, I use Opera as a substitute for Firefox; on linux, I suppose your best bet might be to use Firefox 3, which has thus far impressed me with the reduced memory leaks.

Apparently Opera is available for linux:
http://www.opera.com/download/?platform=linux

But I've never tested it, so I can't vouch for its memory usage or lack thereof. Worth a try, though.

You mention not knowing if you secure. Try getting Rootkit Hunter and/or Chkrootkit: there's nothing like being really sure.

Yes! Especially if you look at the system requirements given by various distributors for their current versions, Slackware is the only option you have with only 64MB of RAM. Besides of this, Windows 2000 also needs a minimum of 128MB - and it's a lot faster than any linux distro you could grab (due to the fact that it's as old as your hardware and there is no 8-year old linux distro still supported and still running current days applications).

Slackware would be the best choice for you anyway, I think, because you seem wanting to learn how it is done the linux way.

ok...one word Slackware.

You'll learn how to install without a gui and config without one too, unless to add gui software to do it.

Also, Ubuntu server edition does not install a gui by default so you need to learn cli to use it.

I've got a Toshiba 4180xcdt running a whopping 400 mhz and with 128mb ram (maxxed) I have Debian Etch (gonna put Lenny on this weekend). It had KDE on it though it is a little sluggish. But I also have IceWm for performance. Not really bad. Only thing is you'll have to do some leg work to get wireless working (from what I've heard. I don't use it myself)

I understand what you say about Ubuntu. It is not bad, but the idea of hiding everything which may look technical and the weird sudo approach which let you do anything while you are not really the root made me turn away from Ubuntu.

OK, I am a convinced Debian user myself, so I am biased, but I can recommend Debian to anyone else who is willing to spend some time reading thru the Debian installation manual and Debian reference manual. Debian package management is superb, and so are the tools for kernel and module compilation.

I prefer KDE over Gnome, but KDE won't run on 64 MB. Choose a lightweight WM like IceWM or Fluxbox. Salvaging ancient hardware is one of my favorite pastimes as well, but by all means, try to get some classical SDRAM strips and you'll be much happier. Processor speed doesn't matter. It is the [memory] size that matters. (Pun intended given you thread title)

OTOH, if you are building a server, you don't need any GUI at all, and you can happily start with 64 MB. I am running my main server at home on a PII-300 / 192 MB.

jlinkels

Ark mentions 64MB as it's minimum requirement, or did you forget to check that?

As for Win2K running faster than any Linux distro, ARE YOU CRAZY? I used Windoze for all my life before Linux (including Win2K), and no Windoze is as fast as Ark and Yoper (though Yoper will probably not run on 64MB because it's optimized for newer CPUs).

I use TinyFlux (PCLOS) on my archaich 330Mhz box. It's GUI is Fluxbox based. The LAMP instal from the Control Panel is there with an easy Firewall with PSAD, and you can add users, and even virtual hosts. Being a Mandriva Linux fork the commands are generic linux when you get the urge to open the terminal! Howtoforge.com has a lot samples to get you going.

Yo, folks! Read it again. He's not planning on doing this on the laptop with 64 meg, he's doing it on the salvaged P-III with 512 meg. Shouldn't be a problem.

SauceForge, consider using a GUI distro and gradually learning the command line stuff as you go. Get your system up and running with the GUI, then start examining the config files and comfortable with editing them in a console. Wean yourself off the GUI. When you are ready, shut down the GUI and enjoy!

Yeah, reading the thread starting post is never a bad idea!

However, real men start with command line use. GUI is for dummies!

Don't take this last statement too serious, the intention is to make a joke, not to start a flame war.

jlinkels

Command line! HA! REAL men simply WILL the computer to respond by force of their magnetic personalities! And if the computer doesn't respond, they type all their commands in assembler language!

Arrrhhg, matey!





But for those of us in the real world, starting with baby steps ain't necessarily a bad idea.