From: Jeremy Jackson <jeremy.jackson@sympatico.ca>
To: Scott Long <smlong@teleport.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux OS boilerplate
Date: Sun, 18 Feb 2001 15:32:25 -0500 [thread overview]
Message-ID: <3A903159.3D190848@sympatico.ca> (raw)
In-Reply-To: <3A902F77.8BF6AB52@teleport.com>
Scott Long wrote:
> Does there exist an outline (detailed or not) of the boot process from
> the point of BIOS bootsector load to when the kernel proper begins
> execution? If not would anyone be willing to help me understand
> bootsect.S and setup.S enough so that I might write such an outline?
I have been over it, and would be willing to help. You should first read all
of the LILO documentation, and check out some of the LinuxBIOS
project at www.linuxbios.org.
next prev parent reply other threads:[~2001-02-18 20:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 20:24 Linux OS boilerplate Scott Long
2001-02-18 20:32 ` Jeremy Jackson [this message]
2001-02-18 21:46 ` TeknoDragon
2001-02-19 1:47 ` Alan Cox
2001-02-19 10:07 ` Eric W. Biederman
2001-02-22 1:24 ` Tim Wright
2001-02-19 9:03 ` Paul Gortmaker
2001-02-20 4:29 ` H. Peter Anvin
2001-05-18 6:14 ` H. Peter Anvin
2001-05-18 7:24 ` Linux scalability? Sasi Peter
2001-05-18 8:12 ` reiser.angus
2001-05-18 8:30 ` Ronald Bultje
2001-05-18 8:30 ` reiser.angus
2001-05-18 9:05 ` Ronald Bultje
2001-05-18 19:28 ` [OT] " J Sloan
2001-05-18 19:38 ` David S. Miller
2001-05-18 19:46 ` Peter Rival
2001-05-18 19:57 ` David S. Miller
2001-05-18 20:06 ` Peter Rival
2001-05-18 20:13 ` David S. Miller
2001-05-18 21:36 ` J Sloan
2001-05-19 8:26 ` Sasi Peter
2001-05-18 8:17 ` Sean Hunter
2001-05-18 21:18 ` Rodger Donaldson
2001-05-19 8:31 ` Sasi Peter
2001-05-21 10:42 ` Sean Hunter
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 21:13 Linux OS boilerplate Rick Hohensee
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=3A903159.3D190848@sympatico.ca \
--to=jeremy.jackson@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=smlong@teleport.com \
/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