HP/DEC/Compaq

I managed to get an Open Genera 2.0 CD (Genera 8.5) which is perfect since I'm still waiting for a new hard disk to try to rebuild the MacIvory debacle from hell, and I have the super sexytime AlphaPC 164LX running Tru64 5.1. After I made the kernel setting changes, enabled the packet filter (and fixed their perms), upgraded the core genera executable to 8.18 and made sure the right CDFS mount options were used, Open Genera starts up: http://www.floodgap.com/iv/2715

However, I can't for the life of me get it to NFS to the host system. When I try to define the site to complete the Genera configuration, I keep getting RPC errors trying to mount it. The NFS mount points on the Tru64 host can be mounted on other systems on the network, so I know they work. Setting them to allow access to anyone, without a password, doesn't fix it.

Any ideas? Anyone running Open Genera successfully on their own Alpha? Is it Digital UNIX or Tru64?

I have it on (I think) 4.0E, but haven't done much with it because I really despise the keyboard on that system. Some day I'm going to adapt a decent keyboard and spend more time with it.
You might have to mess with soft/hard exports, the way Genera deals with NFS is different than Unix and kind of stuck in the late '80s.

How do you mean, different? It's still NFSv2, right?

Long shot here, but anyway...

- Is it *supposed* to work (as in, do you have any documentation which mentions it being supported)?
- Can you mount shares that are *not* on the host itself?

Reason for asking this is having similar symptoms with an older version of a completely different emulator (simh) on a completely different host OS. The guest OS could not talk to the host OS, but it could talk to anything else on the network. It's apparently a lowlevel niggle with how networking is implemented, and not necessarily related to a problem with the guest or software. Might be something similar on your side too - YMMV.

I have no idea if it still works on Tru64 5.1. The documentation only talks about 4.0.

I'm suspecting the packet filter, but I don't know how to debug it.

Have you tried using the updated packetfilter.mod released by Symbolics? It says it's for 4.0F but may be required for other versions, I'm not sure.

That's what I'm thinking too. I haven't gotten around to it yet.

Tried it. It doesn't even want to run -- I think the binary format is different.

So back to square one.

ClassicHasClass,

This is what I get on my alpha:

bollix> genera -network bollix
genera (POST): OK 166667 993
genera: Unable to allocate trace buffer
Not enough space
bollix> genera -network
"bollix;mask=255.255.255.0;gateway=outside"
genera (POST): OK 166666 993
genera: Unable to allocate trace buffer
Not enough space

Do you know what could cause this?

I got the same error. Assuming you're running the 8.18 executable, the problem is that the VM settings are probably too low. The vm stanza in /etc/sysconfigtab looks like this on my 5.1B system:

Good point, those issues dissapeared with 8.18; while they were present with the stock binary.

So I was able to "save world" and access nfs; this is my /etc/exports:
/ -root=0 -rw=sea-cpu-006:sea-cpu-007
/usr -root=0 -rw=sea-cpu-006:sea-cpu-007

Then we've got to have done something differently. Do you have everything locally installed? This is the part I can't get past, which is the exact commands given in the install guide:



At this point I pressed Meta-Shift-A, to see if it would pull the stuff from CD over NFS. It still doesn't:



FWIW, NFS is working fine. Here's the view from harlan. I made everything intentionally weak and open to everyone to eliminate that as a factor.



And here's the view from another host trying to mount the CD-ROM:



So what gives?

I don't have the original cdrom, just a tarball; but I did install it (setld -i .); setup nfs, according to what I posted earlier, setup packetfilter in kernel, then created the devices; compiled sudo (so I don't have to run it as root); setup my .VLM and I think that's it. Of course, I'm using the 8.18 binariy; not the stock one.

I have sys.sct copied in /var/lib/symbolics; I changed directories permissions to 755 and files to 644. I think that's all that was requested; and as you see in the telnet session; I can compile a file; therefore use the nfs in write mode; of course I was able to define site and save world.

Note: the "vm" settings are useless on tru64; only good for digital unix.

Okay, then I'll just copy everything over to /var/lib/symbolics and see what happens.

yeah.

was that helpful? Did it work?

Haven't gotten a chance yet (darn Master's degree).

well, priorities man; you can get a master's degree anyday, but this is the real deal.