What are the steps for adding storage to a SIMH vax (vax750, to be
specific) running 4.3BSD? I created disk image files on the host OS of
the proper size (for RA82s) and attached them through the .ini file.
However, they don't have partition tables and this version of BSD
doesn't seem to have a
I'm not sure if 4.3 already has disklabels. In any case, before disklabels,
partitions were compiled into the kernel, with several combinations
presupplied. Maybe /etc/disktab has some hints.
--
Sent from my Android device with K-9 . Please excuse my brevity._
I added the partition info for ra82 to /etc/disktab and indicate ra82
when I run newfs, but newfs reports "Don't have a parition table for a
DU RA 82".
On 5/9/17 10:03 AM, Rhialto wrote:
I'm not sure if 4.3 already has disklabels. In any case, before
disklabels, partitions were compiled into t
4.3BSD has its partition tables compiled into the driver. You can
generate the C code for the disk drivers using diskpart based on disktab.
Note that you must use the same entry in the device driver that you
later use for newfs (which reads the disk partition stuff from disktab).
-- R
Den 2
Sent: Wednesday, May 10, 2017 12:57 AM
> To: simh@trailing-edge.com
> Subject: [Simh] Adding storage to vax running 4.3BSD
>
> What are the steps for adding storage to a SIMH vax (vax750, to be
> specific) running 4.3BSD? I created disk image files on the host OS of
this point.
>
> If you don't care, just use the 0c devices aka 'whole disk' ... or I recall
> that working well enough.
>
>> --
>> From:Alan Perry
>> Sent:Wednesday, May 10, 2017 12:57 AM
>> To:simh@trailing-edge.com
>>
ices aka 'whole disk' ... or
> > I recall that working well enough.
> >
> >> --
> >> From:Alan Perry
> >> Sent: Wednesday, May 10, 2017 12:57 AM
> >> To:simh@trailing-edge.com
> >> Subject:[Simh] Adding storage to vax running 4.3BSD
>
on't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject: [Simh] Adding storage to vax running 4.3BSD
What are the steps fo
pes in the drivers at this point.
If you don't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject: [Simh] Adding storage to vax run
point.
If you don't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject: [Simh] Adding storage to vax running 4.3BSD
What are the step
coded partition types in the drivers at this point.
If you don't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject:[Simh] Addin
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To: simh@trailing-edge.com
Subject:[Simh] Adding storage to vax running 4.3BSD
What are the steps for adding storage to a SIMH vax (vax750, to be
specific) running 4.3BSD? I created disk i
;s a
> >>> hard coded partition types in the drivers at this point.
> >>>
> >>> If you don't care, just use the 0c devices aka 'whole disk' ... or
> >>> I recall that working well enough.
> >>>
> >>>> -
27;s a
hard coded partition types in the drivers at this point.
If you don't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject:[S
d partition types in the drivers at this point.
If you don't care, just use the 0c devices aka 'whole disk' ... or
I recall that working well enough.
--
From:Alan Perry
Sent:Wednesday, May 10, 2017 12:57 AM
To:simh@trailing-edge.com
Subject:[Simh] Adding stora
>>>>> I have tried to run newfs on partition c and it fails,
>complaining
>>>>>> about the lack of a partition table.
>>>>>>
>>>>>>> On May 10, 2017, at 07:29, Jason Stevens
>>>>>>> wrote:
>>>
> On May 11, 2017, at 9:24 AM, Jason Stevens
> wrote:
>
> Ah now that makes more sense!
>
> On May 11, 2017 5:11:34 AM GMT+08:00, Alan Perry wrote:
>
> Problem solved. Apparently this kernel doesn't know about RA82s. I
> changed them to RA81 and it worked fine.
>
> alan
Yikes. The whole
On 2017-05-11 15:34, Paul Koning wrote:
On May 11, 2017, at 9:24 AM, Jason Stevens
wrote:
Ah now that makes more sense!
On May 11, 2017 5:11:34 AM GMT+08:00, Alan Perry wrote:
Problem solved. Apparently this kernel doesn't know about RA82s. I
changed them to RA81 and it worked fine.
alan
On Thu, May 11, 2017 at 4:37 PM, Johnny Billquist wrote:
> True. However, it isn't actually the geometry that cause the Unix messup
> here, but the fact that Unix divided disks into partitions. So it needed to
> know where each partition started. And before disklabels, it was hardcoded
> per disk
On Thu, 11 May 2017 22:37:59 +0200
Johnny Billquist wrote:
> On 2017-05-11 15:34, Paul Koning wrote:
> >
> >> On May 11, 2017, at 9:24 AM, Jason Stevens
> >> wrote:
> >>
> >> Ah now that makes more sense!
> >>
> >> On May 11, 2017 5:11:34 AM GMT+08:00, Alan Perry
> >> wrote:
> >>
> >> Problem
On 2017-05-11 22:52, Clem Cole wrote:
On Thu, May 11, 2017 at 4:37 PM, Johnny Billquist mailto:b...@softjar.se>> wrote:
True. However, it isn't actually the geometry that cause the Unix
messup here, but the fact that Unix divided disks into partitions.
So it needed to know where eac
On 2017-05-11 23:02, Bob Eager wrote:
On Thu, 11 May 2017 22:37:59 +0200
Johnny Billquist wrote:
On 2017-05-11 15:34, Paul Koning wrote:
On May 11, 2017, at 9:24 AM, Jason Stevens
wrote:
Ah now that makes more sense!
On May 11, 2017 5:11:34 AM GMT+08:00, Alan Perry
wrote:
Problem solve
Johnny Billquist wrote:
> Well, MSCP was a good solution, and it's rather funny to now watch SATA
> and SAS, which is almost a carbon copy of MSCP and DSI, but 20 years later.
Unless I am mistaken, SCSI (at least in the form of SASI) preceded MSCP
chronologically and perhaps inspired the
On 2017-05-12 01:15, Sergey Oboguev wrote:
Johnny Billquist wrote:
*
*
/> Well, MSCP was a good solution, and it's rather funny to now watch SATA
and SAS, which is almost a carbon copy of MSCP and DSI, but 20 years
later
24 matches
Mail list logo
