Re: Linux Loaded on 486...what now

> From: "Patrick Huss" <patrick@...>
>
> I have succesfully loaded Linux onto my 486, but I ended up using a custom
> install. Consequently, I am not able to test Tim Goldstein's modified
> script. Whats more, I get a statement during startup, that I have 64k

Shadow

> RAM (I have 32M altogether). I am confused (more like bewildered) as to

how

> that affects my memory settings in EMC. Any ideas, Arne?
> I am also perplexed by my conflicting interpretations of some points of
> advice I've read in previous threads, not the least of which being the
> updates for the Kernel I need before I apply the RTpatch. Are the updates

on

> the redhat site what I want, or did I hear that I can use the RedHat CD?
> Also, can I use the Jun16 EMC or do I correctly understand that this was
> just a Beta for Tim's use?
> I am sorry to ask for repitious advice, but Im having a very difficult

time

> wading through the many hundreds of messages in the archives.
>
> Patrick Huss

Patrick,

The Jun 16 EMC build works fine. It is the July 16 version that was a beta
and can cause run aways with steppers under the right condition.

Regarding the rpm files you need for the kernel, I always use the ones from
the CD. The RedHat site has newer versions, but you then have to be careful
to make sure you also update the existing kernel files as the patch and
compile will not work if your versions are in conflict.

With a custom install you have to be sure you have all of the packages
required installed. Make, Patch, and many of the libraries and development
programs are not installed by default with custom install. I don't think
anyone has ever determined what the absolute minimum package installation
is. The best I have done is to determine that all the packages that are
default with a workstation install + the 4 my script loads will get the job
done. You may want to sit down with the "official" installation guide book
and see if you have all the workstation packages loaded. After that you
could still try the script I have if you edit the lilo.con file on the
diskette to use the drive and partition info that is in your current
/etc/lilo.conf file.

Tim
[Denver, CO]