From owner-freebsd-doc Sat Jun 8 3:59:17 2002 Delivered-To: freebsd-doc@freebsd.org Received: from web21104.mail.yahoo.com (web21104.mail.yahoo.com [216.136.227.106]) by hub.freebsd.org (Postfix) with SMTP id 630A537B403 for ; Sat, 8 Jun 2002 03:59:14 -0700 (PDT) Message-ID: <20020608105914.76306.qmail@web21104.mail.yahoo.com> Received: from [62.254.0.5] by web21104.mail.yahoo.com via HTTP; Sat, 08 Jun 2002 03:59:14 PDT Date: Sat, 8 Jun 2002 03:59:14 -0700 (PDT) From: Hiten Pandya Reply-To: hiten@uk.FreeBSD.org Subject: Re: An addition to developers-handbook To: Sergey Lyubka , freebsd-doc@freebsd.org In-Reply-To: <20020607134647.A1803@oasis.uptsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --- Sergey Lyubka wrote: Hi Sergey. > I've found that handbook lacks one important part there a lot of stuff > described well, but nowhere shown how it all works together. > I've started to write an additional chapter, called "System > initialization", where the initialization will be described in-deep, > starting from bootstrapping, trough the loader code, to kernel > initialization. I'm doing that for x86 arch. Cool. We are looking forward to it; but my advice is, if you are planning to get very specific about the x86 architecutre, than this would better fit in as an article. > Question: > does it makes sense to add this to dev-handbook ? > If so, I'll post a hyperlink to compiled code soon to review. As per my advice above, If it is not "very" specific for the x86, than it would be an execellent addition under the dev-handbook. Hope this helps. Looking forward to the chapter. 8) Hiten. hiten@uk.FreeBSD.org __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message