rule-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Rule-list] Modifying the current anaconda--progress update


From: Taylor, ForrestX
Subject: RE: [Rule-list] Modifying the current anaconda--progress update
Date: Fri, 8 Feb 2002 15:40:38 -0800

> -----Original Message-----
> From: Chuck Moss [mailto:address@hidden
> 
> The base section in the comps file.

Good idea.  I tried just the base section by using a ks.cfg file that had
nothing under the %packages section.  Here's what happened:

Using ks mem=16M:

The install took about 20 minutes, and it installed 132 packages and 262MB
(according to the installer--once rebooted, df showed 203MB were actually
used).  I set swap at 64MB, and during the install, it use no more than
47MB.

Using ks mem=12M:

The install took about 35 minutes, and installed the same packages.  The
install used no more than 38MB swap.

Using ks mem=8M:

I actually had to rebuild anaconda and the discs, because the installer only
had 6344K of RAM.  I changed anaconda to check for 6000K RAM instead of
8000K.  Although it didn't complain about the RAM, it took a long time to
start.  I let it go for a couple of hours on the 'Running anaconda...please
wait' screen, and it never got past that.

Using linux mem=8M:

Same as above.  I thought that I'd try this just in case kickstart was
taking up more memory than it should be.  I would guess that this would
eventually work, but I didn't have the patience to wait that long.


 
> Thanks for the info.  If you posted the patch to enigma list 
> I saved the
> thread.  If not it would be great if you could email me the 
> patch directly.
> (maybe to the list so it would be in the archive???)
> 
> 
> Chuck

Here is the patch that I used.  Notice that I changed the MIN_RAM to 6000K
in case someone had an extra week or two to try it on an 8MB system ;o)

--- anaconda-7.2.orig/isys/isys.h       Tue Apr 17 09:05:39 2001
+++ anaconda-7.2/isys/isys.h    Mon Feb  4 16:18:50 2002
@@ -3,7 +3,7 @@
 
 #define MIN_ROOTPART_SIZE_MB   250
 
-#define MIN_RAM                        17000       /* 20M or so */
+#define MIN_RAM                        6000        /* 8M or so */
 #define MIN_GUI_RAM            35000
 #define EARLY_SWAP_RAM         34000
 

Now, the problem remains as to how to implement this.  I just tried using a
floppy with the new anaconda, and using the original discs, but it looks
like the stage2.img on the original disc is the culprit.  I have been using
totally rebuilt discs.  Thus, it looks like we have to somehow change the
stage2.img, or rebuild the disc(s).  Any ideas on this subject?

Forrest




reply via email to

[Prev in Thread] Current Thread [Next in Thread]