The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: KenUnix <ken.unix.guy@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix v7 tape drive question
Date: Thu, 2 Mar 2023 10:00:56 -0500	[thread overview]
Message-ID: <CAJXSPs9uzHAV-MFaOfpd9qs7egH0N4fCRmUr6HR6Z=yxQvqogg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4-rFSnZ3LGW7pr9hbEMOwEg3ww8+=QA+28C8bBSySGpQ@mail.gmail.com>

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

Dan,

Thanks, that did the trick.

# dump
     date = Thu Mar  2 09:52:02 2023
dump date = the epoch
dumping /dev/rrp3 to /dev/rmt1
I
II
estimated 24870 tape blocks on 0 tape(s)
III
IV
level 9 dump on Thu Mar  2 09:52:02 2023
DONE
25228 tape blocks on 1 tape(s)

And, I will change dump.c and dumpdir.c to use tm0.

Ken


On Thu, Mar 2, 2023 at 9:40 AM Dan Cross <crossd@gmail.com> wrote:

> On Thu, Mar 2, 2023 at 9:28 AM KenUnix <ken.unix.guy@gmail.com> wrote:
> > 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?
> >
> > Any help is appreciated.
>
> I'd start with the man page.
>
> Dump(1M) says that argument `f` causes `dump` to, "Place the dump on
> the next argument file instead of the tape". Did you try using that
> option with `/dev/rmt0`?
>
> Alternatively, I don't see why you couldn't hard-link /dev/rmt1 to
> /dev/rmt0:
>
> # cd /dev
> # ln rmt1 rmt0
>
> Or use `mknod` to create a device file with the same major/minor numbers:
>
> # cd /dev
> # /etc/mknod rmt1 c 12 0
>
> Or even, as a very last resort, edit the source and change the default
> dump device.  It's in /usr/src/cmd/dump.c
>
> Hope that helps!
>
>         - Dan C.
>


-- 
End of line
JOB TERMINATED

[-- Attachment #2: Type: text/html, Size: 2234 bytes --]

  reply	other threads:[~2023-03-02 15:01 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 [this message]
2023-03-02 16:57 ` Clem Cole

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='CAJXSPs9uzHAV-MFaOfpd9qs7egH0N4fCRmUr6HR6Z=yxQvqogg@mail.gmail.com' \
    --to=ken.unix.guy@gmail.com \
    --cc=crossd@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).