9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ide fs patch for the current plan9 version
Date: Wed, 16 May 2001 15:31:35 -0400	[thread overview]
Message-ID: <20010516193136.B6FB4199D7@mail.cse.psu.edu> (raw)

> To apply the patch, I suggest you create two directories
> ./idefs/port and ./idefs/plan9pc, then run rc idefs.rc on ./idefs and
> bind -bc ./idefs/port /sys/src/fs/port 
> bind -bc ./idefs/plan9pc /sys/src/fs/plan9pc
> 
> after that you can mk in /sys/src/fs/plan9pc.  

You probably ought to "mk clean" before you "mk" in
/sys/src/fs/plan9pc.  We tried this sort of overlaid source tree and
found a couple of hazards: existing object (.8) files in the
underlying tree (/sys/src/fs in this case) can cause trouble if they
are unwritable (e.g., due to lack of permission) or if they are newer
than source files in the overlaying tree (./idefs in this case).

Russ and I didn't quite finish a program called stitch to perform this
sort of overlay dynamically (it worked under light load).  Stitch
changed the semantics of creation slightly so that new files in the
served tree were always created in the uppermost layer, though that
could be easily adjusted.  I also made a small tweak to mk to
understand enough about overlays that it would ignore targets (e.g.,
newer object files) in lower layers for the purpose of computing work
to be done.



             reply	other threads:[~2001-05-16 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 19:31 geoff [this message]
2001-05-16 21:00 ` Francisco J Ballesteros
  -- strict thread matches above, loose matches on Subject: below --
2001-05-16 21:13 geoff
2001-05-16 13:02 nemo
2001-05-17  4:54 ` Eric Dorman

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=20010516193136.B6FB4199D7@mail.cse.psu.edu \
    --to=geoff@collyer.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).