linux-decnet-user Mailing List for DECnet for Linux
Brought to you by:
chrissie_c,
ph3-der-loewe
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(8) |
Jun
(39) |
Jul
(30) |
Aug
(23) |
Sep
(9) |
Oct
(9) |
Nov
(30) |
Dec
(24) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(12) |
Feb
(4) |
Mar
(21) |
Apr
|
May
(3) |
Jun
(3) |
Jul
(13) |
Aug
(13) |
Sep
(18) |
Oct
(10) |
Nov
(25) |
Dec
(2) |
| 2002 |
Jan
(7) |
Feb
(14) |
Mar
(15) |
Apr
(29) |
May
(10) |
Jun
(23) |
Jul
(76) |
Aug
(52) |
Sep
(15) |
Oct
(47) |
Nov
(12) |
Dec
(1) |
| 2003 |
Jan
(5) |
Feb
(12) |
Mar
(21) |
Apr
(26) |
May
(66) |
Jun
(16) |
Jul
(13) |
Aug
(7) |
Sep
(21) |
Oct
(11) |
Nov
(4) |
Dec
(11) |
| 2004 |
Jan
(18) |
Feb
(1) |
Mar
(1) |
Apr
(20) |
May
(10) |
Jun
(4) |
Jul
(9) |
Aug
(9) |
Sep
|
Oct
(5) |
Nov
(13) |
Dec
(8) |
| 2005 |
Jan
(23) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(11) |
Jun
(3) |
Jul
(5) |
Aug
(15) |
Sep
(3) |
Oct
(13) |
Nov
(2) |
Dec
(7) |
| 2006 |
Jan
(5) |
Feb
(8) |
Mar
(6) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
(6) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(5) |
Jul
(7) |
Aug
|
Sep
(7) |
Oct
(7) |
Nov
(4) |
Dec
(2) |
| 2008 |
Jan
(10) |
Feb
(5) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
(14) |
Aug
(3) |
Sep
(6) |
Oct
(7) |
Nov
|
Dec
|
| 2009 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
(2) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(15) |
Sep
(9) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
(15) |
Dec
|
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(11) |
Apr
|
May
|
Jun
(17) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(12) |
Feb
(15) |
Mar
(11) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2016 |
Jan
|
Feb
(14) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
(1) |
2
(1) |
3
(2) |
4
|
5
|
|
6
|
7
|
8
(5) |
9
|
10
|
11
|
12
|
|
13
(2) |
14
|
15
|
16
|
17
|
18
|
19
|
|
20
|
21
(1) |
22
|
23
|
24
|
25
|
26
(1) |
|
27
|
28
|
29
|
30
|
31
|
|
|
|
From: Patrick C. <pa...@ty...> - 2003-07-26 09:34:11
|
On Mon, Jul 21, 2003 at 04:41:45PM -0400, Gregg C Levine wrote: > Hello from Gregg C Levine > Okay, here goes, I am getting a series of error messages, during the > compilation of the dnprogs-2.23 collection. Here's the bottom of the full > script output: > make -C netlink > make[2]: Entering directory > `/usr/src/linux-decnet/dnprogs-2.23/dnroute/netlink' > cc -Iinclude -c -o ll_map.o ll_map.c > cc -Iinclude -c -o libnetlink.o libnetlink.c > ar rcs libnetlink.a ll_map.o libnetlink.o > make[2]: Leaving directory > `/usr/src/linux-decnet/dnprogs-2.23/dnroute/netlink' > gcc -O2 -Wall -Wstrict-prototypes -Inetlink/include -pipe -fsigned-char -Wst > rict-prototypes -Wall -Wno-unused -Wno-uninitialized -I../libdap -I../includ > e -DVERSION=\"2.23\" -D_XOPEN_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -D_SVID_SOU > RCE -DSHADOW_PWD -DDNETUSE_DEVPTS -g -o dnroute get_neigh.c send_route.c > routing_msg.c csum.c netlink/libnetlink.a -Lnetlink -ldnet -lnetlink > get_neigh.c: In function `main': > get_neigh.c:259: parse error before `int' > get_neigh.c:264: `devnull' undeclared (first use in this function) > get_neigh.c:264: (Each undeclared identifier is reported only once > get_neigh.c:264: for each function it appears in.) > make[1]: *** [dnroute] Error 1 > make[1]: Leaving directory `/usr/src/linux-decnet/dnprogs-2.23/dnroute' > make: *** [all] Error 2 It looks like #include <sys/types.h> may be needed at the top of the includes list. I suppose it must be included by some other header file on Debian which is why I don't see the problem. Patrick -- patrick |
|
From: Gregg C L. <dr...@wo...> - 2003-07-21 20:41:23
|
Hello from Gregg C Levine Okay, here goes, I am getting a series of error messages, during the compilation of the dnprogs-2.23 collection. Here's the bottom of the full script output: make -C netlink make[2]: Entering directory `/usr/src/linux-decnet/dnprogs-2.23/dnroute/netlink' cc -Iinclude -c -o ll_map.o ll_map.c cc -Iinclude -c -o libnetlink.o libnetlink.c ar rcs libnetlink.a ll_map.o libnetlink.o make[2]: Leaving directory `/usr/src/linux-decnet/dnprogs-2.23/dnroute/netlink' gcc -O2 -Wall -Wstrict-prototypes -Inetlink/include -pipe -fsigned-char -Wst rict-prototypes -Wall -Wno-unused -Wno-uninitialized -I../libdap -I../includ e -DVERSION=\"2.23\" -D_XOPEN_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -D_SVID_SOU RCE -DSHADOW_PWD -DDNETUSE_DEVPTS -g -o dnroute get_neigh.c send_route.c routing_msg.c csum.c netlink/libnetlink.a -Lnetlink -ldnet -lnetlink get_neigh.c: In function `main': get_neigh.c:259: parse error before `int' get_neigh.c:264: `devnull' undeclared (first use in this function) get_neigh.c:264: (Each undeclared identifier is reported only once get_neigh.c:264: for each function it appears in.) make[1]: *** [dnroute] Error 1 make[1]: Leaving directory `/usr/src/linux-decnet/dnprogs-2.23/dnroute' make: *** [all] Error 2 ----- Basically, I have netlink created as an installable module. The problem is still happening. I shall have the full output placed on my website, in a few minutes. Look for a location decnet on the site. Oh, and the site is www.gregg.levine.name Gregg C Levine dr...@wo... "Oh my!" The Second Doctor's nearly favorite phrase. |
|
From: Patrick C. <pa...@ty...> - 2003-07-13 15:11:43
|
On Sun, Jul 13, 2003 at 01:57:57AM -0000, Mal Matheson wrote: > Greetings, > > I am currently looking at using a Linux box with DECnet to act as a file server for some old PDP-11/RSX11M+ systems (using NFT commands). > > After reading the FAQ and browsing this mailing list, I'm not sure what the current status is re compatibility with PDP-11 file transfers. Apparently there were (are?) timeout issues when copying files to/from the PDP-11 systems. > > Can someone please advise if the Linux-DECnet option is feasible for this purpose? I've been advised the files are fairly small, around 512K (or maybe 512 bytes, I'm not sure). An alternative someone has proposed is to use a Windows system with Pathworks32 - would this be more reliable? In all honesty the best I can suggest is "try it and report any problems you find" While I've "tested" the DECnet programs against RSM11M (not plus) and had some success that was only against an emulated machine running the simh PDP11 simulator. Under that emulator I can get files off the PDP but not back onto it - or was it the other way round? Anyway, I don't know how old the version of RSX11M was that I was using and I think plus is a bit different anyway. Maybe someone else out there has tried Linux/DECnet with a PDP can enlighten us! patrick |
|
From: Mal M. <mal...@sp...> - 2003-07-13 01:57:59
|
Greetings, I am currently looking at using a Linux box with DECnet to act as a file = server for some old PDP-11/RSX11M+ systems (using NFT commands). After reading the FAQ and browsing this mailing list, I'm not sure what = the current status is re compatibility with PDP-11 file transfers. = Apparently there were (are?) timeout issues when copying files to/from = the PDP-11 systems. Can someone please advise if the Linux-DECnet option is feasible for = this purpose? I've been advised the files are fairly small, around 512K = (or maybe 512 bytes, I'm not sure). An alternative someone has proposed = is to use a Windows system with Pathworks32 - would this be more = reliable? Thanking you Mal FORBES PICK - Professional Groupware Service Share Calendars, Files, Contacts & Eliminate SPAM! Click to learn more: http://www.norada.com |
|
From: Rok V. N. L. <rok...@NU...> - 2003-07-08 19:32:28
|
> > BTW: LAT doesn't run over DECnet - it is a protocol in its own right, > > independant of DECnet. > > Fair point. In my case LAT is using DECNet. No, it is not! Start VMS with LAT and no DECnet: LAT will still work. It is virtually impossible to use DECnet to transport LAT packets because of LAT's very short timeouts. Regards, Rok Vidmar Internet: rok...@nu... National and University Library Phone: +386 1 421 5461 Turjaska 1, SI-1000 Ljubljana Fax: +386 1 421 5464 Slovenia |
|
From: Patrick C. <pa...@ty...> - 2003-07-08 14:28:19
|
On Tue, Jul 08, 2003 at 03:05:31PM +0100, Rich Buckley wrote: > Patrick wrote: > > If you really want to intercept packets and do nefarious things with them > then > > you could write a PF_PACKET program to advertise a LAT service from the > Linux > > box that forwards the information (after suitable NATing) to the terminal > > server. > > This is what I want to do. I would like the ability to "understand" what the > VAX > and VT terminal are saying to each other and periodically inject information > into > the data stream. The old fashioned way of doing this would be to feed the > terminal > connection through two serial ports and sniff. This is however not very > scalable > when dealing with a large number of terminals. The PF_PACKET way is the "neatest" but probably the hardest to code because you would need to understand quite a lot of the LAT protocol in the program. What might be OK is for you to write a small program that simply behaves as a LAT service on Linux and forwards the information either into llogin or a /dev/lat port to VMS. That way you only have to deal with the raw data and not the protocol. Plus you get a copy of the filter per user, making it easier to keep a track of any context you may need. latcp -A -a myservice -C /usr/local/bin/myfilter -u someuser is the LAT command to create custom service, all your myfilter program has to do then is to fork llogin to the VMS box and watch the packets go to-and-fro, changing them as necessary. I recommend you use the -u switch for this command otherwise your filter will run as root and that's asking for trouble :-) patrick |
|
From: Rich B. <ric...@ca...> - 2003-07-08 14:08:18
|
Patrick wrote: > If you really want to intercept packets and do nefarious things with them then > you could write a PF_PACKET program to advertise a LAT service from the Linux > box that forwards the information (after suitable NATing) to the terminal > server. This is what I want to do. I would like the ability to "understand" what the VAX and VT terminal are saying to each other and periodically inject information into the data stream. The old fashioned way of doing this would be to feed the terminal connection through two serial ports and sniff. This is however not very scalable when dealing with a large number of terminals. > BTW: LAT doesn't run over DECnet - it is a protocol in its own right, > independant of DECnet. Fair point. In my case LAT is using DECNet. Thanks, --Rich |
|
From: Patrick C. <pa...@ty...> - 2003-07-08 12:12:51
|
On Tue, Jul 08, 2003 at 12:24:10PM +0100, Rich Buckley wrote: > Hi, > > Is it possible to use a DECNet enabled Linux machine to intercept, process > and forward messages between a OpenVMS machine and a terminal server. I > understand these devices run LAT over DECNet. I also anticipate having to > change some address configurations such that messages to the terminal server > are delivered to the Linux machine before being forwarded to the real > terminal > server. > > Any thoughts, experiences or advice would be gratefully received. It depends what you want really want to achieve. If you want the Linux box to act as a LAT "router" then it's probably easier to set up a LAT service on the Linux box that automatically logs into the VMS machine. If you really want to intercept packets and do nefarious things with them then you could write a PF_PACKET program to advertise a LAT service from the Linux box that forwards the information (after suitable NATing) to the terminal server. BTW: LAT doesn't run over DECnet - it is a protocol in its own right, independant of DECnet. -- patrick |
|
From: Rich B. <ric...@ca...> - 2003-07-08 11:26:57
|
Hi, Is it possible to use a DECNet enabled Linux machine to intercept, process and forward messages between a OpenVMS machine and a terminal server. I understand these devices run LAT over DECNet. I also anticipate having to change some address configurations such that messages to the terminal server are delivered to the Linux machine before being forwarded to the real terminal server. Any thoughts, experiences or advice would be gratefully received. Regards, --Rich |
|
From: Mats M. <mat...@te...> - 2003-07-03 20:18:52
|
On Tue, 1 Jul 2003 16:54:56 +0200 "bram kortleven" <br...@it...> wrote: > I have an 'old' decserver 200 which I wanted to use as a > terminal-connecting or maybe if possible dialin connection device. I > use Linux RedHat and Mandrake all the time, so I wanted to get it > running on these... Any idea how? or where to find necessary software > to do so??? Thanks You will need latd like Patrick said, and you will also need mopd and a suitable boot image file to be able to netboot the DS200. Hint: connect a termianl at the first port, set it to 9600/N/8/1 and power on the DS200, then you will see the boot process (or the failure if you don't have any mop boot source). -- /Mats Magnusson, ma...@pl... |
|
From: Mats M. <mat...@te...> - 2003-07-03 20:03:13
|
On Thu, 03 Jul 2003 12:29:13 -0700 lin...@li... wrote: > Your mail to 'Linux-decnet-user' with the subject > > Re: [Linux-decnet-user] Dec server 200 and linux > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. Sorry, i posted from wrong account. I have changed my mail program settings now so it defaults to posting from the correct account when i reply to things on the list from now on (until the next time a harddisk fails on me and i have no backup...) -- /Mats Magnusson, ma...@pl... |
|
From: Patrick C. <pa...@ty...> - 2003-07-02 07:18:05
|
On Tue, Jul 01, 2003 at 04:54:56PM +0200, bram kortleven wrote: > I have an 'old' decserver 200 which I wanted to use as a terminal-connecting > or maybe if possible dialin connection device. I use Linux RedHat and > Mandrake all the time, so I wanted to get it running on these... Any idea > how? or where to find necessary software to do so??? > Thanks LAT is the software you need: http://sourceforge.net/project/showfiles.php?group_id=4993 http://linux-decnet.sourceforge.net/lat.html There is an RPM in there but I'm not sure how well it runs on Mandrake, you may be better off building from source. By default LAT provides a login service from the terminal server which should "just work" for your dialin (provided the DECserver is set up correctly). Also included in the package is a program called "moprc" which functions like VMSs "ncp connect node" or TSM so you can manage the DECserver from the Linux machine. -- patrick |
|
From: bram k. <br...@it...> - 2003-07-01 14:46:59
|
I have an 'old' decserver 200 which I wanted to use as a terminal-connecting or maybe if possible dialin connection device. I use Linux RedHat and Mandrake all the time, so I wanted to get it running on these... Any idea how? or where to find necessary software to do so??? Thanks Kortleven Bram itos bvba br...@it... |