> lucc@alge.anart.no wrote:
>> Is this list still alive?
>
> perhaps you should have a look at the list archives?
>
> cheers,
>
> Kim

I did. Thats why I asked. And it seemed like a good way
to troll for activity. Just wanted to announce my arrival
on the list. And since this is netbsd/vax, my contribution
on the hardware side is a VAXstation 4000/60 with 40Mb Ram.
dmesg output follows.

NetBSD 3.1 (GENERIC) #0: Tue Oct 31 10:04:40 UTC 2006
	ghen@b2.netbsd.org:/home/builds/ab/netbsd-3-1-RELEASE/vax/200610302053Z-obj/home/builds/ab/netbsd-3-1-RELEASE/src/sys/arch/vax/compile/GENERIC

VAXstation 4000/60
cpu0: KA46
cpu: turning on floating point chip
total memory = 40560 KB
avail memory = 36508 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: 32K entry DMA SGMAP at PA 0x3c0000 (VA 0x803c0000)
vsbus0: interrupt mask 0
le0 at vsbus0 csr 0x200e0000 vec 770 ipl 15 maskbit 1 buf 0x0-0xffff
le0: address 08:00:2b:2b:9f:e1
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 124 ipl 15 maskbit 4
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 mux 1
lkms0 at dz0
wsmouse0 at lkms0 mux 0
asc0 at vsbus0 csr 0x200c0080 vec 774 ipl 15 maskbit 0
asc0: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <QUANTUM, FIREBALL_TM2110S, 300X> disk fixed
sd0: 2014 MB, 6810 cyl, 4 head, 151 sec, 512 bytes/sect x 4124736 sectors
sd0: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1 at scsibus0 target 1 lun 0: <QUANTUM, FIREBALL ST2.1S, 0F0C> disk fixed
sd1: 2079 MB, 7068 cyl, 3 head, 200 sec, 512 bytes/sect x 4259112 sectors
sd1: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers, tagged queueing
sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST31055N, 0532> disk fixed
sd2: 1010 MB, 4177 cyl, 4 head, 123 sec, 512 bytes/sect x 2069860 sectors
sd2: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs


Seems like this model requires some sort of user input to boot
if running via vt terminal (here: vt510) when S1 is up, and
without it the VAX halts at the prompt since there is no keyboard.
It's a shame really, i don't want the vt510 visible all the time.
This is not a question, it's a statement.

/Luke