From: Clem Cole <clemc@ccc.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix v7 tape drive question
Date: Thu, 2 Mar 2023 11:57:01 -0500 [thread overview]
Message-ID: <CAC20D2N-Pa2EN-xHO6P2cBhdOEVz==ejDd03XQibxC595WM=ZA@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs-Q95Rv_DqzdnVKKPFEzwGqh0nyNTVpUoMA9dtt39t9Uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
On Thu, Mar 2, 2023 at 9:28 AM KenUnix <ken.unix.guy@gmail.com> wrote:
> Hi,
>
> I am trying to use the 'dump' program but it references rmt1.
>
> My system only has rmt0. I have been unable to find how to
> create this device. I have looked over the reference material
> but it only references rmt0.
>
> Is there any way to redirect a dump to use rmt0?
>
Some thoughts...
1.) start with the man page: https://man.cat-v.org/unix_7th/1/dump
You note the first key parameter described is f - i.e. dump fu0 /dev/rmtXXX
/dev/rrpY
Remember on traditional research systems like V6/V7you should use rmtX and
rrpY not mtX and rpY as you don't what to use the buffer cache (modern
UNIXs & Linux use the paging HW so things like need for the old I/O buffer
cache are avoided).
2.) next: read: https://man.cat-v.org/unix_7th/4/tm
cd /dev; ls -l *mt*
(if you type: cat makefile that would not hurt)
I suspect you will see three devices: mt0 (a blocked device i.e. thru the
buffer cache and then copied in/out to your program) and two raw devices:
rmt0 and nrmt0 (character devices i.e. direct I/O to your program). Using
mknod create the next Unit number - i.e. three more device files: mt1 rmt1
and nrmt1 - don't forget chmod them too
Now with simh, you can add: attach tm1 some_local_file
3.) since you are using simh, you could also use the RH11/RH70 based Tapes
which are the ht devices: https://man.cat-v.org/unix_7th/4/ht
The makefile in dev will create 2 drives for you and make sure you use a
UNIX kernel configured with the ht driver included.
Also in simh, enable TU0 and TU1 instead of TM0 and TM1
I would not recommend recompiling the tape utilities, although as Dan said
you could do that.
ᐧ
[-- Attachment #2: Type: text/html, Size: 5988 bytes --]
prev parent reply other threads:[~2023-03-02 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 14:27 [TUHS] " KenUnix
2023-03-02 14:39 ` [TUHS] " Dan Cross
2023-03-02 15:00 ` KenUnix
2023-03-02 16:57 ` Clem Cole [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='CAC20D2N-Pa2EN-xHO6P2cBhdOEVz==ejDd03XQibxC595WM=ZA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=ken.unix.guy@gmail.com \
--cc=tuhs@tuhs.org \
/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).