It was a misconfiguration of the bridge, forgot the port number, the bridge tried to open an interface named silverback.sampsa.com which didn'\t work obviously.
Sampsa
On 26 Sep 2009, at 23:18, Johnny Billquist wrote:
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Not sure what you are doing. Is the problem coming from running simh, or from running the bridge program???
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Not sure what you are doing. Is the problem coming from running simh, or from running the bridge program???
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Yup, that was it, forgot the port number after the IP. Works now, cheers.
Sampsa
On 26 Sep 2009, at 22:53, gerry77 at mail.com wrote:
On Sat, 26 Sep 2009 22:43:14 +0100, you wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting
the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
If I remember correctly, you must tell it a port number for any remote bridge
or it will consider "silverback.sampsa.com" and such as a local device, which
obviously does not exist. Try appending ":4711" or whatever at the end of the
second line :)
G.
On Sat, 26 Sep 2009 22:43:14 +0100, you wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting
the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
If I remember correctly, you must tell it a port number for any remote bridge
or it will consider "silverback.sampsa.com" and such as a local device, which
obviously does not exist. Try appending ":4711" or whatever at the end of the
second line :)
G.
Running 'bridge' as root in the VM?
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting
the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Sampsa
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Sampsa
Hi.
Mark Wickens wrote:
Guys,
Thought someone might be interested in my 'the minimum you need to know'
guide about setting up a RAID-1 system disk using volume shadowing under
OpenVMS:
http://lakesdev.blogspot.com/2009/09/volume-shadowing-system-disk-on-vax.ht…
Nice writeup. Maybe I shouldn't tell how easy it is under RSX... :-)
Johnny
gerry77 at mail.com wrote:
On Wed, 23 Sep 2009 10:25:36 +0200, you wrote:
Wow. I apologize. I thought I had that under control... :-)
I wonder if VMS have changed along the way, or if it has always been like that...?
It's my feeling that it has been always like that, anyway I can certify that
VAX/VMS V4.7 works as I expected:
[...Same tests as done by Bob]
FLORRY::RPT$ type test.dat;-0
one
FLORRY::RPT$ show system
VAX/VMS V4.7 on node FLORRY 23-SEP-2009 10:21:58.14 Uptime 15 08:30:54
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00000100 NULL COM 0 0 15 08:29:27.66 0 0
00000101 SWAPPER HIB 16 0 0 00:00:00.06 0 0
[...]
Bye, :)
G.
P.S.: This V4.7 was obtained by upgrading a V4.6, so I'm assuming that even on
that release the behaviour would have been the same.
I would expect that if anything, the change would have happened between V3 and V4 of VMS. V3 had the same 9+3 filename length limits as RSX... (Started using VMS at V3.7 (I think it was), a long long time ago...)
Johnny
On Wed, 23 Sep 2009 10:25:36 +0200, you wrote:
Wow. I apologize. I thought I had that under control... :-)
I wonder if VMS have changed along the way, or if it has always been
like that...?
It's my feeling that it has been always like that, anyway I can certify that
VAX/VMS V4.7 works as I expected:
[...Same tests as done by Bob]
FLORRY::RPT$ type test.dat;-0
one
FLORRY::RPT$ show system
VAX/VMS V4.7 on node FLORRY 23-SEP-2009 10:21:58.14 Uptime 15 08:30:54
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00000100 NULL COM 0 0 15 08:29:27.66 0 0
00000101 SWAPPER HIB 16 0 0 00:00:00.06 0 0
[...]
Bye, :)
G.
P.S.: This V4.7 was obtained by upgrading a V4.6, so I'm assuming that even on
that release the behaviour would have been the same.
