9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /bin/import
Date: Thu, 28 Dec 2000 09:41:44 -0500	[thread overview]
Message-ID: <20001228144145.AFFDC19A08@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 24 bytes --]

is ar listening on il?

[-- Attachment #2: Type: message/rfc822, Size: 2225 bytes --]

From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] /bin/import
Date: Thu, 28 Dec 2000 23:03:02 -0500
Message-ID: <20001228141011.C30D7199FF@mail.cse.psu.edu>

Hello

Manual says:
     SYNOPSIS
          import [ -abcC ] [ -f ] system file [ mountpoint ]
that is, `import' allows C option.

On the other hand, we will find in /sys/src/cmd/import.c:
void
main(int argc, char **argv)
{
	char *mntpt;
	int fd, mntflags;

	mntflags = MREPL;
	ARGBEGIN{
	case 'a':
		mntflags = MAFTER;
		break;
	case 'b':
		mntflags = MBEFORE;
		break;
	case 'c':
		mntflags |= MCREATE;
		break;
	case 'f':
		fflag = 1;
		break;
	default:
		usage();
	}ARGEND;

Is the absence of C option in the source is a simple bug?

By the way, it is required as much as 60 sec to connect to my host `ar'
from my home plan9 terminal via ISDN line.
It seems IL does not reach  `ar'. Therefore I am using TCP.
	term% import  tcp!ar /n/kfs /n/ar
The connection time is same when I put `f' option to `import'
On the other hand, cpu command
	term% cpu -h tcp!ar -a netkey
responds without any delay.
Are there any reasons `import' requires much connection time?

Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp

             reply	other threads:[~2000-12-28 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28 14:41 presotto [this message]
2000-12-28 14:54 rob pike
2000-12-29  4:03 arisawa
2000-12-29 19:42 arisawa
2000-12-29 21:32 arisawa

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=20001228144145.AFFDC19A08@mail.cse.psu.edu \
    --to=presotto@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).