mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: fattymikefx@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: installing .01
Date: Thu, 16 Aug 2001 23:58:12 -0400 (EDT)	[thread overview]
Message-ID: <200108170358.f7H3wCY36744@saturn.cs.uml.edu> (raw)
In-Reply-To: <20010817031904.3DFEF501D7@localhost.localdomain> from "tristan" at Aug 16, 2001 11:19:04 PM

tristan writes:

> I want to install the linux kernel 0.01 on my 386 machine, and im
> lost on how to do it.

Go up a few versions, to 0.02 maybe, if you have any hopes of
running a compiler on this system. You will need at least 4 MB of
RAM for compiling, since the early kernels didn't support swap.

Minix-386 is a hacked up Minix. Minix is an educational OS for
the 8088 that was just recently made free. There once was a
collection of patches that would add 386 feature support.
So you could get Minix running, patch it, then build Linux.

Try this:

The Minix filesystem can be 64 MB at most. Make a partition for
that, one for swap, and one for a newer Linux distribution.
This pre-Slackware thing would be a good choice:
http://www.ibiblio.org/pub/Linux/distributions/MCC/2.0+/

Um, you really don't want to be building gcc on a 386.
You might have to build intermediate versions, since the
old gcc might not compile with the most recent gcc.
Perhaps you have or can borrow a modern machine for builds.

Finding the extras, like libc and a shell, will be hard.

You might need a boot loader called "shoelace". You should
be able to run this from LILO.



  parent reply	other threads:[~2001-08-17  3:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  3:19 tristan
2001-08-17  3:50 ` David A. Frantz
2001-08-17  3:58 ` Albert D. Cahalan [this message]
2001-08-17  7:02   ` Nicholas Knight

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200108170358.f7H3wCY36744@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=fattymikefx@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®