I am running a 4M RAM/40M HDD i386 setup with DGL 2.1, and do not use
dselect because it segfaults way too much - using dpkg alone works just
fine if I don't try to do too much in one run.
(try adding this to your /etc/profile: alias dpkg='dpkg --smallmem').
Have you tried to get a handle on how much memory is being used by
dselect+dpkg?
Running the following on a different VC may help you see
what is happening:
while true; do vmstat; done
or while true; do free; done
or while true; do df; done
kill them with CTRL-c.
Top would also work, but I think it is less likely to catch transient
peaks that may be causing problems.
- Bruce
--
On Mon, 22 Mar 1999, Raymond A. Ingles wrote:
> On Fri, 19 Mar 1999, Hartmut Schmude wrote:
>
> > Recently I tried to install DEBIAN 2.0 -kernel 2.0.34 - on an
> > old 386 machine with the following configuration:
> >
> > mainbord 386 with CT 82C206 / 301 / 302 Chipset
> > no copro
> > ISA bus only
> > 8 Meg memory
> > Adaptec 1542 C
> > 2 SCSI Disks with 240 M and 4.3 G
> > VGA Tseng ET4000 (generic)
> > multi IO for lp and serial
> >
> > During the installation procedure - mainly when dpkg starts its
> > work after having installed the base system - dpkg ends up
> > with segmentation faults and the system is only partial usable.
>
> Hmmm. I've been able to successfully install Debian 2.0 on a 386 system
> with 6MB of RAM. (In fact, so far as I can tell it only sees 4.5MB of that
> 6MB.) Since it only has 2 40MB IDE drives, I can't fit a lot on it, but it
> did install.
>
> > I tried out a customized kernel built on an other machine
> > with only 386 support, copro emulation etc. with the same
> > results.
>
> I haven't yet been able to compile a kernel on another machine that will
> run on my 386. I haven't tried in a long time, but every time I do it
> fails badly.
>
> Sincerely,
>
> Ray Ingles (248) 377-7735 [EMAIL PROTECTED]
