[Simh] Attach tar to tape device and access it from v7 in simh

[Clem Cole]

On Tue, Nov 7, 2017 at 3:37 PM, Clem Cole <clemc at ccc.com> wrote:

> You need to convert the foo.tar file to a foo.tap before simh's mag tape
> reader will understand it.
>

​1.) ​
gunzip 1bsd.tar.gz
2
​.)
enblock <1bsd.tar >
​1bsd
.tap
​

​3.) ​in simh:    att mt0 1bsd.tap
​4.) in unix:  ​tar vxfb /dev/rmt0 ...




> If you want to skip that step, attach the foo.tar (or foo.tar.gz) file as
> a virtual disk.  The open it as a raw device
>
​I should have been more specific, attach the foo.tar file to >>simh<< as a
virtuak disk, the under the simulated OS (UNIX) you can open it as a raw
device.​


​i.e.
1.) ​
gunzip 1bsd.tar.gz
​3.) ​in simh:    att
​rk3
 1bsd.ta
​r

​4.) ​in unix:  tar vxfb /dev/rrk3  ....






> Clem
>
> On Tue, Nov 7, 2017 at 2:58 PM, Will Senn <will.senn at gmail.com> wrote:
>
>> Hi,
>>
>> I think I may have asked this a couple of years ago, but I am unable to
>> find the email conversation, so I'll ask it again from a position of
>> experience and greater but still lacking knowledge... here's the background
>> - I am running a v7 instance in simh that I am quite pleased with. However,
>> I saw somewhere where someone was running some additional software on their
>> instance and of course, I just had to have it for my own. Unfortunately,
>> it's not clear how they got the software, where it's from, or how they got
>> it running. There are hints that the stuff came from early bsd. So... I
>> thought I would try getting the bsd source on to my v7 instance to see if I
>> could compile it and play around with it. There's a 1bsd.tar.gz in the tuhs
>> archive. It being a tar file, I figured I could:
>>
>> gunzip 1bsd.tar.gz
>>
>> in simh:
>>
>> att mt0 1bsd.tar
>>
>> in v7, which defaults to mt1 for some reason, (not a configured device on
>> my system and isn't created by make tm in /dev):
>>
>> tar vxfb /dev/rmt0 1
>> nboot.ini-13> boot rp0
>>
>> Invalid magtape record length, PC: 002400 (MOV 177776,R0)
>>
>> or
>>
>> tar xv0
>>
>> nboot.ini-13> boot rp0
>>
>> Invalid magtape record length, PC: 002400 (MOV 177776,R0)
>>
>> I don't know why the nboot.ini-13> boot rp0 artifact is appearing (prolly
>> some buffer flush when the sim aborts)... but of more concern is why I
>> can't access the tar. I'm sure it is a gap in my understanding, so I'd
>> appreciate some help.
>>
>> Thanks,
>>
>> Will
>>
>> _______________________________________________
>> Simh mailing list
>> Simh at trailing-edge.com
>> http://mailman.trailing-edge.com/mailman/listinfo/simh
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20171107/87779342/attachment.html>