According to Bogdan Taru: While burning my CPU.
> 
> 
>       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!

You should have let the install procedure make and setup the swap
partition.

> 
>  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.

Yup been there done that, but you (like i) will remember that we HAD to make
a swap partition before we could install the "then small" operating system
on machines with low memory, that has not changed. One thing which has
changed since then is the amount of documentation there is telling you about
the pit falls of taking short cuts etc.

> 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???

Looks like we did not Read the F!!!ing manuel before we installed, after all
folks who install Windows systems have the same problems, the big differance
between the 2 is, Micket$oft "makes" you do it there way, Linux
(distributions) as a whole let you choose what "you" want.

I'm not saying your complaneing, however Linux is free, you dont look a gift
horse in the mouth and boy what a GIFT it is.

> 
> Have fun,
> bogdan
> 
> 
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Reply via email to