9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: 9fans@cse.psu.edu
Subject: [9fans] boot question
Date: Sun,  7 Nov 2004 21:46:32 -1000	[thread overview]
Message-ID: <Pine.BSI.4.58.0411072143100.24294@malasada.lava.net> (raw)

I've been reading through the kernel to try to figure this one
out but I still don't get it.

The port specific data builds an *init* process to fire off
the machine.  This process does an exec of "/boot".  The
config file causes a "boot" file to be added to the devroot
when main calls links().  However, it looks like the "boot"
file is added under the "/boot" directory of devroot, right?
How does the exec get to the boot file (/boot/boot?  or is it
/boot/boot/boot?  After I log in to a running system /boot and
/boot/boot are directories).  Is there some bind/mount operation
somewhere that I'm missing?

Tim N.


             reply	other threads:[~2004-11-08  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  7:46 Tim Newsham [this message]
2004-11-08  8:00 ` geoff
2004-11-08 10:06 ` Charles Forsyth

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=Pine.BSI.4.58.0411072143100.24294@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).