From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 tar and 2bsd.tar
Date: Mon, 27 Jul 2020 23:20:31 -0400 [thread overview]
Message-ID: <CAC20D2N8p544V4cx5xVd_3QHk7LJw5ct7P152GxeZcz2SPKNRg@mail.gmail.com> (raw)
In-Reply-To: <bcc34a7a-c2dd-53eb-9559-1ab2e0cf3762@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
below..
On Mon, Jul 27, 2020 at 11:02 PM Will Senn <will.senn@gmail.com> wrote:
> On 7/27/20 8:14 PM, Clem Cole wrote:
>
> on v7: dd if=/dev/rrkN of=ucbtar bs=1 <-- this should pull the
> binary with the padded last block in
>
> ouch my screw up... should be 1b
>
> Your instructions held up until I tried to read from the rk device -
> here's my attach:
>
> in simh:
> set rk0 rk05
att rk0 ucbtar
>
This is what I have:
; RK05 data disks (4 drives)...
;; SET RK ENABLE
SET RK0 WRITEENABLED
SET RK1 WRITEENABLED
SET RK2 WRITEENABLED
SET RK3 WRITEENABLED
SET RK4 DISABLED
SET RK5 DISABLED
SET RK6 DISABLED
SET RK7 DISABLED
ATTACH RK0 ./scratch.rk05
SHOW RK
>
> then in v7 the rk's aren't in /dev, so:
>
there is a makefile in /dev that creates them. Take a look and see what
its doing.
looked in c.c, rk is major dev 0, and rrk is dev 9, so...
> /etc/mknod /dev/rk0 b 0 0
> /etc/mknod /dev/rrk0 c 9 0
> chmod 640 /dev/*rk*
>
> and
> dd if=/dev/rrk0 of=ucbtar bs=1
>
bs=1b sorry -- my error, but I don't think that's the issue.
try this for grins: dd if=/dev/rrk0 of=/dev/null bs=1b
cannot open: /dev/rrk0
>
Hmm... be good to see what the errno value is, i.e. why?
Maybe a small C program that tries to open /dev/rrk0 and prints out errno
on failure.
[-- Attachment #2: Type: text/html, Size: 4481 bytes --]
prev parent reply other threads:[~2020-07-28 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 0:39 Will Senn
2020-07-28 1:14 ` Clem Cole
2020-07-28 3:02 ` Will Senn
2020-07-28 3:20 ` Will Senn
2020-07-28 3:21 ` Clem Cole
2020-07-28 3:47 ` Will Senn
2020-07-28 3:55 ` Will Senn
2020-07-28 13:38 ` Will Senn
2020-07-28 13:50 ` Clem Cole
2020-07-28 3:20 ` 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=CAC20D2N8p544V4cx5xVd_3QHk7LJw5ct7P152GxeZcz2SPKNRg@mail.gmail.com \
--to=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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).