------ CONTEST, WIN A HOLOGRAM -------
For real cracks here comes a real challenge...
I'm trying to setup Linux in a 386 with 2 Mbytes of memory. I have a
distribution of slackware on my HDD that works on a 4Mb machine.
Booting from harddisk didn't work, Probably the generic kernel is too
big. So I made a new bootdisk with a newly compiled kernel.
Booting now succeeds until the login prompt. Except for the fsck.
Fsck quits because it's not able to allocate memory for a inode table.
After logging in, I can run most built in shell commands. But external
commands - which are executed by fork - gave the error :
Here are a few data and figures:
AMIBIOS 1990 (Colorized BIOS SetupScreen)
AMD 386dx 40,
2 MB main memory
including 384 kB shadow Ram.
Kernelsize: 502 kB (expanded)
"1020kB (free) 2048kB (total) 502kB(kernelsize) 384kB (reserved)
Switching between shadow ram on and off doesn't seem to matter. In
both cases the linux boot screen shows 384 kB reserved Ram.
- What is the configuration for the smallest kernel (e.g. Can I leave
out the networking code (like TCP/IP etc.))
- Is there a CMOS-setting which really disables Shadow Ram?
- Is the shadowram the cause of memory problems?
The most succesfull contribution which leads to running linux on this
machine, wins a reflection full color rainbow HOLOGRAM (12 cm x 9 cm).
- THIS IS NO JOKE, you'll get it -