On Fri, Mar 06, 2009 at 12:15:29AM +0000, Stuart Henderson wrote:
> On 2009/03/05 23:46, Stefan Sperling wrote:
> > On Thu, Mar 05, 2009 at 09:26:22PM +0000, Stuart Henderson wrote:
> > > On 2009/03/05 19:13, Christian Weisgerber wrote:
> > > > Here's a list of build failures I collected while building a subset
> > > > of the ports tree on a vax. I can probably provide more detail and
> > > > logs on request.
> > >
> > > Porters, don't forget you can emulate the VAX in SIMH. It's easy to setup
> > > if you follow the instructions at http://www.openbsd.org/vax-simh.html.
> > > Just be careful with Ctrl-E...
> >
> > Is this supposed to work with -current? Or only 4.3?
>
> I installed it with the latest snapshot a couple of days ago.
>
> > ra1: write protected (hardware) (code 6, subcode 2)
>
> Your problem is connected with the second emulated drive, I've had
> it running with multiple emulated drives before and it worked ok.
> Have you checked the simple things like openbsd.ra1.disk being
> writable by the user running simh?
Bingo:
-rw-r--r-- 1 stsp stsp 1.4G Mar 5 23:40 openbsd.ra0.disk
-rw-r--r-- 1 root stsp 1.4G Mar 5 22:26 openbsd.ra1.disk
^^^^
I ran it as root once to see if that would make networking work,
it's possible that I added the second drive in the same go.
Later I ran it as non-root user again.
It didn't manage to get an address via dhcp btw, I could see
dhcp traffic going in and out the hosts interface though.
Is there anything special involved in setting up networking?
(I haven't read the simh docs much yet, so feel free to ignore
this question if it will eventually be solved by RTFM.)
Thanks!
Stefan
