I just "dd"ed mine to an ISO file. No problems there. If you have some
ftp site that I can upload it to, I can send you my .iso later tonight.
Thanks, that would be quite helpful. Can you sftp? If so, I'll send you a login you can use.
If my math is right, aa:00:04:00:11:08 works out to 2.17 (and that's the
right address).
It does look like Charon-AXP changed the hardware address of the interface correctly, then.
# The trailing zone network interface
auto eth1
iface eth1 inet manual
pre-up /sbin/ifconfig eth1 hw ether aa:00:04:00:d5:08
I'll give that a try next. Question - is "auto eth1" the right thing to
do? That makes the interface start up when the boot does an "ifup -a",
right? I didn't do that (I figured Charon would start it when it got around
to it).
I'm far from an expert on Linux network interfaces. It doesn't seem to harm anything, and I do want the interface to be up for the emulated system.
Since Charon-AXP is expecting to have dedicated access to the interface, it may do a lot more configuration and management of the interface than I expect. I've been using this setup with SIMH VAX and PDP-11, and something similar for Panda (TOPS-20), so it's just a matter of course for me when I'm setting up an emulated system (that uses DECnet, anyway).
--Marc
Thanks Marc -
I ran into some strange problems with my Alpha CD.
I just "dd"ed mine to an ISO file. No problems there. If you have some
ftp site that I can upload it to, I can send you my .iso later tonight.
One thing that I did that may be useful is that I preconfigured my eth1
interface with the expected (computed) hardware address for my DECnet ...
I didn't do that, although I did do 'ifconfig eth1' on the Linux host
while the Charon/OVMS emulation was running.
eth1 Link encap:Ethernet HWaddr aa:00:04:00:11:08
inet6 addr: fe80::a800:4ff:fe00:1108/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9870 errors:0 dropped:0 overruns:0 frame:0
TX packets:751 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:602103 (602.1 KB) TX bytes:66583 (66.5 KB)
Interrupt:18 Base address:0x5000
If my math is right, aa:00:04:00:11:08 works out to 2.17 (and that's the
right address).
# The trailing zone network interface
auto eth1
iface eth1 inet manual
pre-up /sbin/ifconfig eth1 hw ether aa:00:04:00:d5:08
I'll give that a try next. Question - is "auto eth1" the right thing to
do? That makes the interface start up when the boot does an "ifup -a",
right? I didn't do that (I figured Charon would start it when it got around
to it).
Bob
I decided to try looking at Charon-AXP NCE again and did have much better luck with it myself this time. I'm glad this topic came up.
then I mounted the OpenVMS Hobbyist
Alpha CD on the simulated CDROM and re-installed my own OpenVMS.
I ran into some strange problems with my Alpha CD. I was told that there were "bad blocks" found in the PCSI database during verification. The machine came up, so it appears to be okay, but I don't know that my installation completed successfully. I tried reimaging the CD I have into fresh ISOs, but they all come out the same. I wonder whether your version is somehow different from mine.
Whenever I try any outgoing connection from the emulated Charon-AXP
system, I always get "network communication error" and "network partner
aborted logical link". No outgoing connection seems to work; not SET HOST,
not FAL, not NCP, nothing.
It seems to be working fine for me in both directions.
One thing that I did that may be useful is that I preconfigured my eth1 interface with the expected (computed) hardware address for my DECnet address (I'm using 2.213 for my new system called ANDY). For my Ubuntu system, I have this file in /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# The trailing zone network interface
auto eth1
iface eth1 inet manual
pre-up /sbin/ifconfig eth1 hw ether aa:00:04:00:d5:08
I don't know whether this is required, but I did see in the either in the log file or in the startup messages that Charon-AXP did seem to pay attention to the interface's hardware address. Maybe you should try that and see if that improves things.
--Marc
Guys -
Sorry to bother you with a question, but I was wondering if anyone who had
tried Charon-AXP-nce was successful at getting DECnet running on OVMS 8.3
under the Charon emulation?
I installed Charon-AXP-nce (no sweat there, and thanks for the pointer to
it). It boots and runs OVMS8.3 just fine. First I used their sample
pre-installed system disk image, and then I mounted the OpenVMS Hobbyist
Alpha CD on the simulated CDROM and re-installed my own OpenVMS. Registered
hobbyist licenses, etc. No problems.
Then I installed a second Ethernet card on my Linux host system. Had a
little bit of trouble getting udev, Network Manager and DECnet/Linux to all
cooperate on which interfaces to name and use, but I eventually got that all
straightened out. Now I have an eth1 device which nobody on the Linux host
is messing with. I modified the start_es40_nce to use eth1 for EWA0. It
appears to work - I can start DECnet on the emulated OVMS system, and I get
circuit up and adjacency up events from DECnet. Looks great, but...
Whenever I try any outgoing connection from the emulated Charon-AXP
system, I always get "network communication error" and "network partner
aborted logical link". No outgoing connection seems to work; not SET HOST,
not FAL, not NCP, nothing.
BUT the really weird thing is that it works in the other direction. I can
go to CODA (a real Alpha system) and SET HOST to the Charon emulated system.
That works just fine, as does NCP, FAL, etc as _inbound_ connections.
Has anybody seen this behavior with DECnet before, either under emulation
or on real hardware? What could cause this?
Thanks,
Bob
You could try to blag a hobbyist license of SYSGEM...
http://www.sysgem.com/products/svms.php
On 1 Nov 2009, at 11:48, gerry77 at mail.com wrote:
Dear All,
I'm looking for some ideas about logging user activity for a guest account.
Up until now I've used image accounting and a batch job doing some cleanup
at every month end (old accounting file closure, guest records extraction,
compression, deletion, etc.), but I'm not very satisfied.
What I'm thinking about is something like .bash_history in Linux and such,
but I cannot figure out how to accomplish something similar either with a
user-written program or with some DCL code and system facilities.
I do know that this wouldn't be a very tight security feature, and anyway
the overall control over the guest account is already quite effective
(/RESTRICTED flag, specific group UIC and login procedure, good ACLs on
TCP/IP, increased system audit, and so on), but I'm just curious about what
guests do when they enter our systems. So, a log of the commands entered at
the DCL prompt would be a very nice bonus and would be also useful to spot
both possible silly break attempts and areas needing improved security.
Any suggestions? :)
Thank you,
G.
Dear All,
I'm looking for some ideas about logging user activity for a guest account.
Up until now I've used image accounting and a batch job doing some cleanup
at every month end (old accounting file closure, guest records extraction,
compression, deletion, etc.), but I'm not very satisfied.
What I'm thinking about is something like .bash_history in Linux and such,
but I cannot figure out how to accomplish something similar either with a
user-written program or with some DCL code and system facilities.
I do know that this wouldn't be a very tight security feature, and anyway
the overall control over the guest account is already quite effective
(/RESTRICTED flag, specific group UIC and login procedure, good ACLs on
TCP/IP, increased system audit, and so on), but I'm just curious about what
guests do when they enter our systems. So, a log of the commands entered at
the DCL prompt would be a very nice bonus and would be also useful to spot
both possible silly break attempts and areas needing improved security.
Any suggestions? :)
Thank you,
G.
Sampsa,
First check to make sure the image exists where it needs to. Second,
check using "INSTALL" that the sharable image is installed.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Friday, October 30, 2009 11:40 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] Python on IA64?
Anyone managed to get Python working on Integrity? I keep getting this
error:
%DCL-W-ACTIMAGE, error activating image LIBBZ2_SHR32
-CLI-E-IMAGEFNF, image file not found
RHESUS$DKA0:[SYS0.SYSCOMMON.] [SYSLIB]LIBBZ2_SHR32.EXE;
(during the install - if I ignore the error, it gives me that when I try
to run Python. I've installed LIBBZ2 already...)
RHESUSSYS$ product show product
------------------------------------ ----------- ---------
PRODUCT KIT TYPE STATE
------------------------------------ ----------- --------- <... snip
...>
JFP I64VMS FREETYPE V2.3-7 Full LP Installed
JFP I64VMS GDCHART V0.11-4 Full LP Installed
JFP I64VMS LIBBZ2 V1.0-4 Full LP Installed
JFP I64VMS LIBGD V2.0-35 Full LP Installed
JFP I64VMS LIBIMAGING V1.1-6 Full LP Installed
JFP I64VMS LIBJPEG V6.2 Full LP Installed
JFP I64VMS LIBPNG V1.2-31 Full LP Installed
JFP I64VMS LIBXSLT V1.1-12 Full LP Installed
JFP I64VMS PYTHON254 V1.0-0 Full LP Installed
JFP I64VMS ZLIB V1.2-3 Full LP Installed
------------------------------------ ----------- ---------
Anyone managed to get Python working on Integrity? I keep getting this error:
%DCL-W-ACTIMAGE, error activating image LIBBZ2_SHR32
-CLI-E-IMAGEFNF, image file not found RHESUS$DKA0:[SYS0.SYSCOMMON.][SYSLIB]LIBBZ2_SHR32.EXE;
(during the install - if I ignore the error, it gives me that when I try to run Python. I've installed LIBBZ2 already...)
RHESUSSYS$ product show product
------------------------------------ ----------- ---------
PRODUCT KIT TYPE STATE
------------------------------------ ----------- ---------
<... snip ...>
JFP I64VMS FREETYPE V2.3-7 Full LP Installed
JFP I64VMS GDCHART V0.11-4 Full LP Installed
JFP I64VMS LIBBZ2 V1.0-4 Full LP Installed
JFP I64VMS LIBGD V2.0-35 Full LP Installed
JFP I64VMS LIBIMAGING V1.1-6 Full LP Installed
JFP I64VMS LIBJPEG V6.2 Full LP Installed
JFP I64VMS LIBPNG V1.2-31 Full LP Installed
JFP I64VMS LIBXSLT V1.1-12 Full LP Installed
JFP I64VMS PYTHON254 V1.0-0 Full LP Installed
JFP I64VMS ZLIB V1.2-3 Full LP Installed
------------------------------------ ----------- ---------
Oleg Safiullin wrote:
Bob Armstrong wrote:
Thanks for all the feedback, guys. I guess it'll be Charon-AXP NCE :-)
Did any of you guys who are using that try running DECnet and/or
Multinet/UCX/etc on it? I notice that the release notes say "WARNING:
Ethernet adapter, which is assigned to CHARON, must not be used by
third-party programs." Does "third party programs" include the host Linux
OS and can I interpret that as meaning that you need a separate, dedicated,
Ethernet card for the Charon-AXP? Everything else looks pretty
straightforward...
Thanks again,
Bob
I think the reason for using dedicated NIC is very simple: it's used in non-promiscuous mode and all the changes
to mac address/mcast filters made by guest system affect physical NIC and may conflict with host OS.
Also, if you want to talk IP, you get into problems with the host, which also talks IP on the same NIC. Confusion easily follows...
Johnny
Bob Armstrong wrote:
Thanks for all the feedback, guys. I guess it'll be Charon-AXP NCE :-)
Did any of you guys who are using that try running DECnet and/or
Multinet/UCX/etc on it? I notice that the release notes say "WARNING:
Ethernet adapter, which is assigned to CHARON, must not be used by
third-party programs." Does "third party programs" include the host Linux
OS and can I interpret that as meaning that you need a separate, dedicated,
Ethernet card for the Charon-AXP? Everything else looks pretty
straightforward...
Thanks again,
Bob
I think the reason for using dedicated NIC is very simple: it's used in non-promiscuous mode and all the changes
to mac address/mcast filters made by guest system affect physical NIC and may conflict with host OS.
