Re: How to write a Kernel Q2

To: Andrej Presern <andrejp@luz.fe.uni-lj.si>
Subject: Re: How to write a Kernel Q2
From: Leigh Stoller <stoller@fast.cs.utah.edu>
Date: Tue, 02 Mar 1999 07:34:06 -0500
Cc: "oskit-users@fast.cs.utah.edu" <oskit-users@fast.cs.utah.edu>
Sender: owner-oskit-users@fast.cs.utah.edu

> From: Andrej Presern <andrejp@luz.fe.uni-lj.si>
> Subject: Re: How to write a Kernel Q2
>
> Where can I see what exactly has been called prior to entering
> main() and how things were initialized so that I can reproduce it
> myself without all of it being hidden.

Look at multiboot_main() in kern/x86/pc/base_multiboot_main.c.

I find the easiest way to navigate around the source code is to
glimpsify it:

	echo CVS >.glimpse_exclude
	echo doc >>.glimpse_exclude
	echo html >>.glimpse_exclude
	echo '.~*' >>.glimpse_exclude
	echo '.glimpse_*' >>.glimpse_exclude
	glimpseindex -B -M 8 -H . .
	chmod 664 .glimpse_*

then you can use glimpse to find stuff.

	glimpse -H . base_cpu_setup

I think there is an emacs interface to glimpse too, but I don't
remember anything about it.

Lbs


=================================
To subscribe or unsubscribe, send mail with "subscribe" or "unsubscribe"
to oskit-users-request@flux.cs.utah.edu.  The oskit-announce list is low
volume - if you want to subscribe, mail oskit-announce-request@flux.cs.utah.edu

Follow-Ups:

Re: How to write a Kernel Q2

From: Lorenzo Bettini <lorenzo.bettini@penelope.penteres.it>