From: Boyd Roberts boyd@plan9.cs.su.oz.au
Subject: Correct use of bind and fs/tarfs?
Date: Mon, 25 Sep 1995 19:53:07 -0400 [thread overview]
Message-ID: <19950925235307.qa1Ev9JhISzltLas3HaXW5Fks-pJlVFd9mHtsFIxwGo@z> (raw)
From: Frank Ashford <fashford@crl.com>
I am able to bind the SCSI controller with:
bind '#S' /dev
This produces directories 0 though 7 and scsiid in my /dev directory.
I get no errors from:
fs/tarfs -m /n/tapefs /dev/3
I am unable to:
tar -cvf /n/tapefs *
tarfs provides a read only file-system interface to a tar file.
/n/tapefs is a directory which tar will not like.
you just want to run tar straight onto the device (/dev/?/data)
next reply other threads:[~1995-09-25 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-25 23:53 Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-25 23:38 Steve
1995-09-25 19:05 Frank
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=19950925235307.qa1Ev9JhISzltLas3HaXW5Fks-pJlVFd9mHtsFIxwGo@z \
--to=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).