Well, that does kinda suck, doesn't it?

But, on the bright side of things, my Slackware 3.4 runs like a dream on
my 486DX/33 with 8megs, so maybe its just Slackware trying to be big and
bad...  And of course, at least Linux doesn't require a 12 million dollar
super computer to load up and just crash your system anyhow (ahem,
Windows, ahem).  :-)

-Evan-

On Fri, 9 Oct 1998, Bogdan Taru wrote:

> 
>       Hi all,
>  I hope I'm not going to be very boring, but I really had a bad experience
> with Linux yesterday...
> 
>  I had a 486DX2 machine with 8MB of Ram and 200MB of HDD, and tryied to
> install Slackware 3.5 on it. Booted, rooted, and when I've runned 'Set
> swap partitions' or 'Set target partitions', I got 'SetSwap can't fork'
> and 'SetTarget can't fork'. After hours of struggling, I finally read the
> message welcoming you: Yes, I've got to activate the swap partitions
> before running 'setup' on a 8MB of Ram machine!
> 
>  I mean, Linux started as a 'small' operating system, with high
> performances and low requirements (2MB of Ram???). I remember installing
> Linux 1.2.13 on a 486SX, with 4MB of Ram, and compiling kernel, and all 
> the other stuff without problems. And here I am, one year later, trying to 
> install the latest Slack on a machine with double memory, processing speed 
> and having problems from the very beginning... I know that a OS should 
> develop, and that means growing, but is there anyone out there who's still
> interested in optimizing???
> 
> Have fun,
> bogdan
> 
> 
> 

Reply via email to