T.R | Title | User | Personal Name | Date | Lines |
---|
2191.1 | | KITCHE::schott | Eric R. Schott USG Product Management | Sat Feb 08 1997 09:30 | 2 |
| Which versions of Digital UNIX are supported?
|
2191.2 | Digital UNIX 3.2g & 4.0b on all Alpha platforms with one exception. | TAPE::STONEHAM | | Mon Feb 10 1997 09:10 | 4 |
| Digital UNIX 3.2g on all Alpha platforms except 150/2000.
Digital UNIX 4.0b on all Alpha platforms.
Charlie
|
2191.3 | What about V4.0 or V4.0a? Any problem with them? David | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Tue Feb 11 1997 09:30 | 0 |
2191.4 | Give it a try and let us know. | TAPE::STONEHAM | | Tue Feb 11 1997 10:11 | 6 |
| By all means give it a try and send mail to tape::infoserver to let us know
if it works. I did some testing on 4.0 before 4.0b became the official base,
so I'm fairly confident it will work. Version 4.0a on the other hand,
received no attention.
Charlie
|
2191.5 | Not having any luck... | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Wed Feb 12 1997 16:58 | 39 |
| I'm not having any luck getting this to run! I've installed according
to the document but get the following errors:
/sbin/init.d/ladc: network interface in /etc/rc.config not recognized,
using "ln0"
Enabling LAD on network interface "ln0"
framework error: subsystem 'ladc' failure
subsystem error: File exists
loadlast: cannot open (AF_LAST, LASTPROTO_CTL) socket: Protocol wrong
type for socket
(Is the LASTport driver linked in the running /vmunix?
startlast: cannot open LAST socket: Protocol wrong type for socket
loadladc: cannot open (AF_LAST, LASTPROTO_LADC) socket: Protocol not
supported
(Did you run "loadlast" and "startlast" first?)
My rc.config looks like this:
ec2157i_# grep NETDEV_ /etc/rc.config
# NETDEV_n - network device name for network devices currently
# for example, NETDEV_0="ln0"
NETDEV_0="fta0"
NETDEV_1="fta1"
NETDEV_2="tu1"
NETDEV_3=
NETDEV_4=
NETDEV_5=
NETDEV_6=
NETDEV_7=
export NETDEV_0 NETDEV_1 NETDEV_2 NETDEV_3 NETDEV_4 NETDEV_5 NETDEV_6
NETDEV_7
It evidently doesn't like one of fta0, fta1, or tu1. Why not?
I'm going to try to enable manually to see what happens.
David
|
2191.6 | hardware/software environment | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Wed Feb 12 1997 17:00 | 7 |
| Forgot to tell you the hardware/software environment:
AlphaStation 500/333 w/ Digital UNIX V4.0B
Plenty of memory
Plenty of disk space
David
|
2191.7 | Manual start doesn't work! | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Wed Feb 12 1997 17:13 | 22 |
| Just found that in the /sbin/init.d/ladc startup file, you don't allow
anything other than ln0 or tu0 devices! That is amazingly restrictive!
I hope this will be fixed. In my case, my only connection to the
Easynet/Plant network is via FDDI!
Also, I tried the procedure in section 5.2 to manually startup the UNIX
client. NONE of it works!
ec2157i_# cd /dev/ladc
ec2157i_# ls
ec2157i_# sysconfig -q ladc bmajor cmajor
framework error: subsystem 'ladc' not found
ec2157i_# sysconfig -s ladc
ladc: unloaded
ec2157i_# sysconfig -c ladc
framework error: subsystem 'ladc' failure
subsystem error: File exists
Where do I go from here...?
David
|
2191.8 | Yet more info... | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Wed Feb 12 1997 17:33 | 7 |
| I edited the /sbin/init.d/ladc file to change the default ln0 to fta1 and then
rebooted. LAST came up like a charm on fta1 EXCEPT that nothing works! I tried
a showladservice and it just sits there interrogating the network without
displaying anything. I even specified -serviceclass ods-2 as I know that there
are TONS of services out on the network. Nothing shows up though.
David
|
2191.9 | How long did you wait for showladservice ? | TAPE::STONEHAM | | Thu Feb 13 1997 13:34 | 6 |
| David,
How long did you wait for the showladservice command ? A long time
(i.e. several minutes) ?
Thanks, Charlie
|
2191.10 | Waited minutes... | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Fri Feb 14 1997 09:50 | 13 |
| Charlie,
I'm not used to having to wait more than about 30 seconds before
SOMETHING is shown to me. There are at least 20 InfoServers visable to me in
Salem on the network. If I do a show service from a VMS system there is a pause
and then the information is displayed.
I can certainly try the showladservice again and let it sit there.
Currently the system is running with the LAST protocol running on fta1.
What else can I check for you? If needed, I can arrange access to the
system for you.
David
|
2191.11 | Ultrix service on net doesn't show up either | DAVIDF::FOX | David B. Fox -- DTN 285-2091 | Fri Feb 14 1997 14:13 | 13 |
| Charlie,
Just tried it again specifying -serviceclass ods_2. I just let it
sit and nothing was returned to me.
One comment... the InfoServer software V3.4 DOES NOT have a service
class of UNIX. It is ULTRIX. I'm not sure if that matters or not.
Wanted to bring it to your attention.
I created an Ultrix service and am trying it again... nothing was
displayed until the program ended.
David
|