9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fd2path and devsrv
Date: Wed, 19 Nov 2008 21:55:22 -0500	[thread overview]
Message-ID: <998fbeea126caa967d58924a3b8433f6@quanstro.net> (raw)
In-Reply-To: <4924D1CE.9000001@Sun.COM>

>> i think the answer to your question is that it's a lot more useful
>> to know that it's #s/boot rather than /net/il/0/data.
> Really? Why? With /net/il/0/data you have an option of digging deeper and
> finding out the other end's address, etc. Or to flip the question -- what
> information does #s/boot provide?

the reason why #s/boot is useful is twofold.  the name means something.
this is a connection to the fs used to boot the machine.  second, /net/il/0/data
can't be mounted.  if you want the name of something to mount, ns gives
you want you want.

you're not precluded from digging around and finding what #s/boot
points to.  why are you complaining that ns gives you the most useful
information?

> Well, to me knowing that mount came out of #s/stuff has never seemed to
> be all that useful -- I can't imagine a question that this will answer.

!?  you can mount it!  the network connection by itself is not useful.

- erik




  reply	other threads:[~2008-11-20  2:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:45 Roman V. Shaposhnik
2008-11-19 19:36 ` Francisco J Ballesteros
2008-11-20  1:37   ` Roman V. Shaposhnik
2008-11-20  1:41     ` erik quanstrom
2008-11-20  2:56       ` Roman V. Shaposhnik
2008-11-20  2:55         ` erik quanstrom [this message]
2008-11-20  3:31           ` Roman Shaposhnik
2008-11-20  3:32             ` erik quanstrom
2008-11-20  3:57               ` Roman Shaposhnik
2008-11-20  4:14                 ` erik quanstrom
2008-11-20  5:05                   ` Roman Shaposhnik
2008-11-20  9:44   ` roger peppe
2008-11-20 12:59     ` Steve Simon
2008-11-20 13:50       ` roger peppe

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=998fbeea126caa967d58924a3b8433f6@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).