The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Had a crack at assembling the Unix v1 kernel
Date: Mon,  4 May 2015 17:48:19 -0400 (EDT)	[thread overview]
Message-ID: <20150504214819.5EAC618C0DE@mercury.lcs.mit.edu> (raw)

    > From: Dave Horsfall <dave at horsfall.org>

    >> In V6, the bootstrap in block 0 prompts for a file name, and when that
    >> is entered, it loads that file into memory and starts it. (It doesn't
    >> have to be in the root directory, IIRC - I'm pretty sure the bootstrap
    >> will accept full path names.)

    > I'm pretty sure that it didn't have the full namei() functionality, so
    > all files had to be in the root directory.

It depends on what you mean by the first "it" above - if you meant 'V6', then
no. From the Distribution V6's /src/mdec/fsboot.s:
		
  / read in path name
  / breaking on '/' into 14 ch names

The process of breaking the name up into segments, and then later finding
each name in the appropriate directory, can be seen. The code is kind of
obscure, but if you look at the RL bootstap I dis-assembled:

  http://ana-3.lcs.mit.edu/~jnc/tech/unix/rlboot.s

it's pretty much the same code, and a little better commented in the 'read
in directories' part.

	Noel



             reply	other threads:[~2015-05-04 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 21:48 Noel Chiappa [this message]
2015-05-05 17:35 ` Ronald Natalie
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05 12:24 Noel Chiappa
2015-05-04 20:44 Noel Chiappa
2015-05-04 21:04 ` Dave Horsfall
2015-05-05  0:29   ` Mark Longridge
2015-05-04 20:23 Mark Longridge
2015-05-04 21:55 ` Warren Toomey

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=20150504214819.5EAC618C0DE@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.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).