From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silly bind quetsion
Date: Fri, 28 Mar 2003 12:42:44 -0500 [thread overview]
Message-ID: <0ce6145379aee5a7383ad3e286b3ae33@plan9.bell-labs.com> (raw)
In-Reply-To: <8340948d82988035a4f4b22ae5e56d72@plan9.bell-labs.com>
i knew there was a reason this seemed weird.
i think the more common way to do this would be
bind -b /usr/local/386/bin /bin
bind -a /386/bin/ip /bin/ip
so that /bin is the only directory that ends
up being a union. the source mkfiles assume
that /386/bin is not a union (install goes into
/$objtype/bin, which doesn't really make sense
when you've got a union).
prev parent reply other threads:[~2003-03-28 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 17:15 steve.simon
2003-03-28 17:25 ` Fco.J.Ballesteros
2003-05-03 22:13 ` [9fans] Tcl Now Available for Plan 9 will551
2003-03-28 17:26 ` [9fans] silly bind quetsion Russ Cox
2003-03-28 17:42 ` Russ Cox [this message]
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=0ce6145379aee5a7383ad3e286b3ae33@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).