linux-decnet-user — Discussion for users of DECnet on Linux

Re: [Linux-decnet-user] All finished

[Philipp S. <li...@li...>]

reflum,

On Wed, 2014-06-11 at 15:17 +0100, Steven Whitehouse wrote:
> On Tue, 2014-06-10 at 17:54 -0700, Larry Baker wrote:
> > Chrissie,
> > 
> > 
> > You have made a tremendous contribution.  Thank you.

I think there can not be better words: Thank you!
It was a lot fun to work with you. I'm sure I will miss this time. And
still hope to see you soon again on IRC :). You haven't just been any
other person working on the same project but also a very good friend.


> > What will happen to the mailing list?  Will updates to the code be
> > possible?
> > 
> Well I'd assume that the mailing list will just carry on. I may have had
> admin access to the stuff at sourceforge at one stage... its so long ago
> that I forget now. I doubt that any of it is going away, but if someone
> wants to take it on and continue developing it, then I dare say that
> access can be granted somehow or other.

I still have admin access to all the sf.net related resources.
If anyone want to help, just drop me a mail.


> The whole problem recently had been the lack of interested developers,
> so my suspicion is that it will not happen, but we'll see.

I did a commit today ;). (Not something interesting, just killing a
warning.)

The main problem I see is that there is nobody willing to maintain the
kernel part. That one is hard:
requires some knowlage of the kernel internals as well as being strong
on the kernel list. I heared sometimes it's a little stormy on the
list. ;)


> I'm glad to hear that people are still using DECnet though - it does
> make all the effort in the past worth it. Nice to hear from Eduardo
> again too!

The group became smaller, but I don't think we are down to zero. At
least my MAC address still starts with 'AA:00:04:00:'.


> Steve.
> 
> 
> > Larry Baker
> > US Geological Survey
> > 650-329-5608
> > ba...@us...
> > 
> > 
> > 
> > 
> > On 10 Jun 2014, at 1:02 AM, Chrissie wrote:
> > 
> > > So this is it, I'm announcing the end of my involvement in all
> > > things 
> > > Linux/DECnet related.
> > > 
> > > I've orphaned all the Debian packages and I'm going to leave
> > > Sourceforge 
> > > and this mailing list. I'm not going to delete the project (if
> > > that's 
> > > even possible) as I think there's value in leaving the code online
> > > in 
> > > case people want it.
> > > 
> > > Thank you do everyone who has contributed to this project in the
> > > form of 
> > > code, documentation, help on the mailing list, and just general 
> > > encourangement. It's been fun.
> > > 
> > > But life moves on and this project has been almost dead for a while
> > > and 
> > > I need to stop pretending that it's something I'm doing.
> > > 
> > > XX
> > > Chrissie
> > > 
> > > ------------------------------------------------------------------------------
> > > HPCC Systems Open Source Big Data Platform from LexisNexis Risk
> > > Solutions
> > > Find What Matters Most in Your Big Data with HPCC Systems
> > > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> > > Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> > > http://p.sf.net/sfu/hpccsystems
> > > _______________________________________________
> > > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> > > 
> > > Linux-decnet-user mailing list
> > > Lin...@li...
> > > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> > > 
> > > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> > Find What Matters Most in Your Big Data with HPCC Systems
> > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> > Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> > http://p.sf.net/sfu/hpccsystems
> > _______________________________________________
> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> > 
> > Linux-decnet-user mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> > 
> 
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 
-- 
Philipp.
 (Rah of PH2)

Re: [Linux-decnet-user] All finished

[Steven W. <st...@ch...>]

Hi,

On Tue, 2014-06-10 at 17:54 -0700, Larry Baker wrote:
> Chrissie,
> 
> 
> You have made a tremendous contribution.  Thank you.
> 
> 
> What will happen to the mailing list?  Will updates to the code be
> possible?
> 
Well I'd assume that the mailing list will just carry on. I may have had
admin access to the stuff at sourceforge at one stage... its so long ago
that I forget now. I doubt that any of it is going away, but if someone
wants to take it on and continue developing it, then I dare say that
access can be granted somehow or other.

The whole problem recently had been the lack of interested developers,
so my suspicion is that it will not happen, but we'll see.

I'm glad to hear that people are still using DECnet though - it does
make all the effort in the past worth it. Nice to hear from Eduardo
again too!

Steve.


> Larry Baker
> US Geological Survey
> 650-329-5608
> ba...@us...
> 
> 
> 
> 
> On 10 Jun 2014, at 1:02 AM, Chrissie wrote:
> 
> > So this is it, I'm announcing the end of my involvement in all
> > things 
> > Linux/DECnet related.
> > 
> > I've orphaned all the Debian packages and I'm going to leave
> > Sourceforge 
> > and this mailing list. I'm not going to delete the project (if
> > that's 
> > even possible) as I think there's value in leaving the code online
> > in 
> > case people want it.
> > 
> > Thank you do everyone who has contributed to this project in the
> > form of 
> > code, documentation, help on the mailing list, and just general 
> > encourangement. It's been fun.
> > 
> > But life moves on and this project has been almost dead for a while
> > and 
> > I need to stop pretending that it's something I'm doing.
> > 
> > XX
> > Chrissie
> > 
> > ------------------------------------------------------------------------------
> > HPCC Systems Open Source Big Data Platform from LexisNexis Risk
> > Solutions
> > Find What Matters Most in Your Big Data with HPCC Systems
> > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> > Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> > http://p.sf.net/sfu/hpccsystems
> > _______________________________________________
> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> > 
> > Linux-decnet-user mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> > 
> > 
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 

Re: [Linux-decnet-user] All finished

[Larry B. <ba...@us...>]

Chrissie,

You have made a tremendous contribution.  Thank you.

What will happen to the mailing list?  Will updates to the code be possible?

Larry Baker
US Geological Survey
650-329-5608
ba...@us...



On 10 Jun 2014, at 1:02 AM, Chrissie wrote:

> So this is it, I'm announcing the end of my involvement in all things 
> Linux/DECnet related.
> 
> I've orphaned all the Debian packages and I'm going to leave Sourceforge 
> and this mailing list. I'm not going to delete the project (if that's 
> even possible) as I think there's value in leaving the code online in 
> case people want it.
> 
> Thank you do everyone who has contributed to this project in the form of 
> code, documentation, help on the mailing list, and just general 
> encourangement. It's been fun.
> 
> But life moves on and this project has been almost dead for a while and 
> I need to stop pretending that it's something I'm doing.
> 
> XX
> Chrissie
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 

Re: [Linux-decnet-user] All finished

[Dave M. <mc...@ne...>]

  Thank you both for working on this for so long.  I hope someone is
able to pick it up and at least maintain it as kernel interfaces evolve.

  You might be surprised about how many people use it.  It's true that
most of those people are in the preservation/vintage computing world, as
I am, but we do depend on it.  I myself have a building full of PDP-11s
(and PDP-10s, VAXen, etc...but the PDP-11s are the "big deal" for me)
and have used Linux DECnet to great advantage for many years.

               -Dave

On 06/10/2014 09:44 AM, Eduardo Marcelo Serrat wrote:
> I get a little nostalgic about this project we started back in 1998 now
> is end of life.
> But you are right, life moves on. Thank you very much for joining in the
> very beginning and all the hard support you gave to it.
> 
> Regards, Eduardo
> 
>> Date: Tue, 10 Jun 2014 09:02:37 +0100
>> From: chr...@go...
>> To: lin...@li...
>> Subject: [Linux-decnet-user] All finished
>>
>> So this is it, I'm announcing the end of my involvement in all things
>> Linux/DECnet related.
>>
>> I've orphaned all the Debian packages and I'm going to leave Sourceforge
>> and this mailing list. I'm not going to delete the project (if that's
>> even possible) as I think there's value in leaving the code online in
>> case people want it.
>>
>> Thank you do everyone who has contributed to this project in the form of
>> code, documentation, help on the mailing list, and just general
>> encourangement. It's been fun.
>>
>> But life moves on and this project has been almost dead for a while and
>> I need to stop pretending that it's something I'm doing.
>>
>> XX
>> Chrissie
>>
>>
> ------------------------------------------------------------------------------
>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
>> Find What Matters Most in Your Big Data with HPCC Systems
>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>> http://p.sf.net/sfu/hpccsystems
>> _______________________________________________
>> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>>
>> Linux-decnet-user mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>>
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> 
> 
> 
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 


-- 
Dave McGuire, AK4HZ
New Kensington, PA

Re: [Linux-decnet-user] All finished

[Eduardo M. S. <ems...@ho...>]

Hi Chrissie,
I get a little nostalgic about this project we started back in 1998 now is end of life.But you are right, life moves on. Thank you very much for joining in thevery beginning and all the hard support you gave to it.
Regards, Eduardo
> Date: Tue, 10 Jun 2014 09:02:37 +0100
> From: chr...@go...
> To: lin...@li...
> Subject: [Linux-decnet-user] All finished
> 
> So this is it, I'm announcing the end of my involvement in all things 
> Linux/DECnet related.
> 
> I've orphaned all the Debian packages and I'm going to leave Sourceforge 
> and this mailing list. I'm not going to delete the project (if that's 
> even possible) as I think there's value in leaving the code online in 
> case people want it.
> 
> Thank you do everyone who has contributed to this project in the form of 
> code, documentation, help on the mailing list, and just general 
> encourangement. It's been fun.
> 
> But life moves on and this project has been almost dead for a while and 
> I need to stop pretending that it's something I'm doing.
> 
> XX
> Chrissie
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 
 		 	   		  

[Linux-decnet-user] All finished

[Chrissie <chr...@go...>]

So this is it, I'm announcing the end of my involvement in all things 
Linux/DECnet related.

I've orphaned all the Debian packages and I'm going to leave Sourceforge 
and this mailing list. I'm not going to delete the project (if that's 
even possible) as I think there's value in leaving the code online in 
case people want it.

Thank you do everyone who has contributed to this project in the form of 
code, documentation, help on the mailing list, and just general 
encourangement. It's been fun.

But life moves on and this project has been almost dead for a while and 
I need to stop pretending that it's something I'm doing.

XX
Chrissie

Re: [Linux-decnet-user] [PATCH] decnet: fix possible NULL deref in dnet_select_source()

[David M. <da...@da...>]

From: Eric Dumazet <eri...@gm...>
Date: Mon, 07 Apr 2014 21:51:44 -0700

> On Mon, 2014-04-07 at 15:18 -0400, David Miller wrote:
> 
>> And in the loopback case, it is the decnet stack's responsibility to
>> make sure ->dn_ptr is setup properly, else it should fail the module
>> load and stack initialization.
>> can fix this properly.
> 
> This was based on Sasha report and my limited time.
> It seems you have more time than me to spend on decnet !

Understood, I'll take a deeper look into this.

Re: [Linux-decnet-user] [PATCH] decnet: fix possible NULL deref in dnet_select_source()

[David M. <da...@da...>]

From: Eric Dumazet <eri...@gm...>
Date: Sun, 06 Apr 2014 14:59:14 -0700

> From: Eric Dumazet <edu...@go...>
> 
> dnet_select_source() should make sure dn_ptr is not NULL.
> 
> While looking at this decnet code, I believe I found a device
> reference leak, lets fix it as well.
>  
> Reported-by: Sasha Levin <sas...@or...>
> Signed-off-by: Eric Dumazet <edu...@go...>
> ---
> It seems this bug is very old, no recent change is involved.

The callers work hard to ensure this.

Analyzing all call sites:

1) __dn_fib_res_prefsrc() uses the FIB entry device pointer, we should not
   be adding FIB entries pointing to devices which do not have their
   decnet private initialized yet.

2) dn_route_output_slow()

   The paths leading to the dnet_select_address() call(s) check if
   dev_out->dn_ptr is not NULL, except when using loopback.

In some other paths the device comes from neigh->dev, from which the
'neigh' was looked up in dn_neigh_table.  There should not be neighbour
entries in this table pointing to devices which do not have their
decnet private setup yet.

And in the loopback case, it is the decnet stack's responsibility to
make sure ->dn_ptr is setup properly, else it should fail the module
load and stack initialization.

I think there is some core fundamental issue here, and just adding
a NULL check to dnet_select_source() is just papering around the issue.

Please look closer at the stack trace, this code, and my analysis
above to figure out what's really going on so we can fix this properly.

Thanks.

Re: [Linux-decnet-user] Non routable protocol usage for Linux

[Larry B. <ba...@us...>]

Sampsa,

I'm pretty sure the programming interface is the same sockets calls used for IP networks.  The network address family name changes from AF_INET to AF_DECnet.  Data structure member names then have to match to protocol conventions.  Is the IPv4 Python interface IP only, or sockets based?  If the latter, DECnet should work as well as IP.

Larry Baker
US Geological Survey
650-329-5608
ba...@us...



On 8 May 2013, at 12:19 PM, Sampsa Laine wrote:

> 
> On 8 May 2013, at 20:05, Larry Baker <ba...@us...> wrote:
> 
>> Umur,
>> 
>> DECnet is a routable protocol.  However, it requires DECnet routers; IP routers do not know how to route DECnet packets.  (We used to have Cisco routers which routed DECnet, IP, and AppleTalk.)  If that still qualifies for your purposes, I recommend you look at the source code for the Linux DECnet  dnprogs, like the terminal emulator for examples.  I have not programmed DECnet on Linux; only on OpenVMS, where it is tightly integrated with the file system and special network operations are typically not required.  Of course, if you use one of the Private Internets (RFC 1918), those are never supposed to appear on the public Internet.  Those are the 10/8, 172.16/12, and 192.168/16 networks.  If that satisfies your requirements, you can stick with IP.
>> 
> 
> Anybody know if it'd be possible to use the Linux DECNET stack from Python?
> 
> 
> 

Re: [Linux-decnet-user] Non routable protocol usage for Linux

[Larry B. <ba...@us...>]

Umur,

DECnet is a routable protocol.  However, it requires DECnet routers; IP routers do not know how to route DECnet packets.  (We used to have Cisco routers which routed DECnet, IP, and AppleTalk.)  If that still qualifies for your purposes, I recommend you look at the source code for the Linux DECnet  dnprogs, like the terminal emulator for examples.  I have not programmed DECnet on Linux; only on OpenVMS, where it is tightly integrated with the file system and special network operations are typically not required.  Of course, if you use one of the Private Internets (RFC 1918), those are never supposed to appear on the public Internet.  Those are the 10/8, 172.16/12, and 192.168/16 networks.  If that satisfies your requirements, you can stick with IP.

Larry Baker
US Geological Survey
650-329-5608
ba...@us...



On 8 May 2013, at 7:06 AM, Umur Devellioğlu wrote:

> Hi all,
> 
> I am a new member of this list and here is my first question.
> 
> I need to write an application that makes a communication connection between two linux machines on the same network with a non routable protocol. On that network only non routable protocols are allowed to flow. I have experience on tcp and udp socket programming but have no idea how to use non routable protocols.
> 
> If anybody can help me it would be wonderful.
> 
> Thank you...
> 
> -- 
> Umur DEVELLİOĞLU
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and 
> their applications. This 200-page book is written by three acclaimed 
> leaders in the field. The early access version is available now. 
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may_______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> 
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> 

[Linux-decnet-user] Non routable protocol usage for Linux

[Umur D. <umu...@gm...>]

Hi all,

I am a new member of this list and here is my first question.

I need to write an application that makes a communication connection
between two linux machines on the same network with a non routable
protocol. On that network only non routable protocols are allowed to flow.
I have experience on tcp and udp socket programming but have no idea how to
use non routable protocols.

If anybody can help me it would be wonderful.

Thank you...

-- 
Umur DEVELLİOĞLU

Re: [Linux-decnet-user] [PATCH -next] decnet: remove duplicated include from dn_table.c

[David M. <da...@da...>]

From: Wei Yongjun <wei...@gm...>
Date: Thu, 4 Apr 2013 09:33:07 +0800

> From: Wei Yongjun <yon...@tr...>
> 
> Remove duplicated include.
> 
> Signed-off-by: Wei Yongjun <yon...@tr...>

Applied.

Re: [Linux-decnet-user] File name parse error confusion

[Chrissie C. <chr...@go...>]

That's good to hear :-)

I'm a bit snowed under at the moment (partly literally) but I will get a 
new release out in the next few weeks.

Chrissie

On 23/03/13 10:34, Peter Allan wrote:
> Thanks, Chrissie. I have rebuilt dnprogs with those changes and it now
> works a treat.
>
> Peter
>
>
> On 18 March 2013 16:46, Chrissie Caulfield
> <chr...@go...
> <mailto:chr...@go...>> wrote:
>
>     AHA!
>
>     No, I see it.
>
>     in libdap/connection.h MAX_PASSWORD is set to 12 - it should be 40
>     to match the kernel implementation. As should MAX_USER and MAX_ACCOUNT.
>
>     I'll do an update when I get time, but in the meantime that edit
>     should fix things.
>
>
>     Chrissie
>
>
>
>     On 17/03/2013 18:52, Peter Allan wrote:
>>     Having got DECnet working on my CentOS 5.9 system (thanks again
>>     for those who helped), I am confused by a problem that I am having
>>     with connecting to a remote computer. (It is an Alpha workstation
>>     running VMS 7.2-1)
>>
>>     I can log into it using "dnlogin node8". That works fine.
>>
>>     However, if I try to use dndir to get a directory listing, then
>>     sometimes it works and sometimes it fails with
>>        File name parse error
>>
>>     For example, the following commands work
>>
>>     dndir 'node8::sys$manager:systartup_vms.com
>>     <http://systartup_vms.com>'
>>
>>     dndir 'node8"system password123"::sys$manager:systartup_vms.com
>>     <http://systartup_vms.com>'
>>         (The system password isn't really password123, but it is 11
>>     characters long.)
>>
>>     dndir 'node8"system password123"::'
>>
>>     If I try
>>     dndir 'node8"system password1234"::'
>>     the I get an error of connect failed: Login information invalid at
>>     remote node, as you would expect
>>
>>     However (and this is the point), if I try
>>     dndir 'node8"system password12345"::'
>>     then I get
>>     File name parse error
>>
>>     Playing around with different lengths of username and password
>>     indicates that the length of the username has no effect on whether
>>     I get a file name parse error. (Admittedly, I only tried shorter
>>     usernames.) It is the length of the password that seems to be the
>>     critical factor.
>>
>>     You will probably deduce that my password used to be longer than
>>     12 characters, which is how I came across this. VMS allows
>>     passwords to be up to 32 characters long, hence my surprise at
>>     finding this problem.
>>
>>     Is this a problem with dnprogs, with the linux shell (which seems
>>     unlikely) or something else?
>>
>>     Peter Allan
>>
>>
>>     ------------------------------------------------------------------------------
>>     Everyone hates slow websites. So do we.
>>     Make your web apps faster with AppDynamics
>>     Download AppDynamics Lite for free today:
>>     http://p.sf.net/sfu/appdyn_d2d_mar
>>
>>
>>     _______________________________________________
>>     Project Home Page:http://linux-decnet.wiki.sourceforge.net/
>>
>>     Linux-decnet-user mailing list
>>     Lin...@li...  <mailto:Lin...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>>
>
>
>     ------------------------------------------------------------------------------
>     Everyone hates slow websites. So do we.
>     Make your web apps faster with AppDynamics
>     Download AppDynamics Lite for free today:
>     http://p.sf.net/sfu/appdyn_d2d_mar
>     _______________________________________________
>     Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>
>     Linux-decnet-user mailing list
>     Lin...@li...
>     <mailto:Lin...@li...>
>     https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>
>
>


-- 
Chrissie

Re: [Linux-decnet-user] File name parse error confusion

[Peter A. <pet...@gm...>]

Thanks, Chrissie. I have rebuilt dnprogs with those changes and it now
works a treat.

Peter


On 18 March 2013 16:46, Chrissie Caulfield <
chr...@go...> wrote:

>  AHA!
>
> No, I see it.
>
> in libdap/connection.h MAX_PASSWORD is set to 12 - it should be 40 to
> match the kernel implementation. As should MAX_USER and MAX_ACCOUNT.
>
> I'll do an update when I get time, but in the meantime that edit should
> fix things.
>
>
> Chrissie
>
>
>
> On 17/03/2013 18:52, Peter Allan wrote:
>
> Having got DECnet working on my CentOS 5.9 system (thanks again for those
> who helped), I am confused by a problem that I am having with connecting to
> a remote computer. (It is an Alpha workstation running VMS 7.2-1)
>
>  I can log into it using "dnlogin node8". That works fine.
>
>  However, if I try to use dndir to get a directory listing, then
> sometimes it works and sometimes it fails with
>    File name parse error
>
>  For example, the following commands work
>
>  dndir 'node8::sys$manager:systartup_vms.com'
>
>  dndir 'node8"system password123"::sys$manager:systartup_vms.com'
>     (The system password isn't really password123, but it is 11 characters
> long.)
>
>  dndir 'node8"system password123"::'
>
>  If I try
>  dndir 'node8"system password1234"::'
>  the I get an error of connect failed: Login information invalid at
> remote node, as you would expect
>
>  However (and this is the point), if I try
>  dndir 'node8"system password12345"::'
>  then I get
> File name parse error
>
>  Playing around with different lengths of username and password indicates
> that the length of the username has no effect on whether I get a file name
> parse error. (Admittedly, I only tried shorter usernames.) It is the length
> of the password that seems to be the critical factor.
>
>  You will probably deduce that my password used to be longer than 12
> characters, which is how I came across this. VMS allows passwords to be up
> to 32 characters long, hence my surprise at finding this problem.
>
>  Is this a problem with dnprogs, with the linux shell (which seems
> unlikely) or something else?
>
>  Peter Allan
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_d2d_mar
>
>
>
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>
> Linux-decnet-user mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>
>
>

Re: [Linux-decnet-user] [PATCH net-next 1/2] decnet: Parse netlink attributes on our own

[David M. <da...@da...>]

From: Thomas Graf <tg...@su...>
Date: Fri, 22 Mar 2013 14:27:35 +0000

> On 03/21/13 at 06:04pm, Steven Whitehouse wrote:
>> You shouldn't need any special hardware to test this. A copy of iproute2
>> should be enough as you should be able to use that to create an
>> interface or two and a route between them, etc. Although DECnet routing
>> works in a different way to ip routing, the Linux implementation tries
>> to stick fairly closely to the ip way of doing things whenever it can in
>> order to share infrastructure. Now that ip has diverged a fair bit over
>> time that isn't quite as true as it was, but there shouldn't be anything
>> too surprising in there.
> 
> Alright, I did some basic testing with iproute2. I do not claim
> to understand what I did but I ran the following:
> 
> $ ip -f dnet route add 1.661 dev em1
> $ ip -f dnet route list
> 1.661 dev em1  scope link
> 
> $ ip -f dnet neigh add 6.662 dev em1
> $ ip -f dnet neigh list
> 6.662 dev em1 lladdr aa:00:04:00:96:1a PERMANENT
> 
> $ ip -f dnet addr add 1.111 dev em1
> $ ip -f dnet addr list
> 2: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
>     dnet 1.111/16 scope global em1

That's good enough for me, both patches applied, thanks Thomas!

Re: [Linux-decnet-user] File name parse error confusion

[Chrissie C. <chr...@go...>]

AHA!

No, I see it.

in libdap/connection.h MAX_PASSWORD is set to 12 - it should be 40 to 
match the kernel implementation. As should MAX_USER and MAX_ACCOUNT.

I'll do an update when I get time, but in the meantime that edit should 
fix things.

Chrissie



On 17/03/2013 18:52, Peter Allan wrote:
> Having got DECnet working on my CentOS 5.9 system (thanks again for 
> those who helped), I am confused by a problem that I am having with 
> connecting to a remote computer. (It is an Alpha workstation running 
> VMS 7.2-1)
>
> I can log into it using "dnlogin node8". That works fine.
>
> However, if I try to use dndir to get a directory listing, then 
> sometimes it works and sometimes it fails with
>    File name parse error
>
> For example, the following commands work
>
> dndir 'node8::sys$manager:systartup_vms.com <http://systartup_vms.com>'
>
> dndir 'node8"system password123"::sys$manager:systartup_vms.com 
> <http://systartup_vms.com>'
>     (The system password isn't really password123, but it is 11 
> characters long.)
>
> dndir 'node8"system password123"::'
>
> If I try
> dndir 'node8"system password1234"::'
> the I get an error of connect failed: Login information invalid at 
> remote node, as you would expect
>
> However (and this is the point), if I try
> dndir 'node8"system password12345"::'
> then I get
> File name parse error
>
> Playing around with different lengths of username and password 
> indicates that the length of the username has no effect on whether I 
> get a file name parse error. (Admittedly, I only tried shorter 
> usernames.) It is the length of the password that seems to be the 
> critical factor.
>
> You will probably deduce that my password used to be longer than 12 
> characters, which is how I came across this. VMS allows passwords to 
> be up to 32 characters long, hence my surprise at finding this problem.
>
> Is this a problem with dnprogs, with the linux shell (which seems 
> unlikely) or something else?
>
> Peter Allan
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
>
>
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>

Re: [Linux-decnet-user] File name parse error confusion

[Chrissie C. <chr...@go...>]

I don't have the ability to test this any more, but the code suggests 
that passwords up to 64 chararacters should work, so I don't know why 
you're seeing a much lower limit. Has anyone else seen this?

Chrissie

On 17/03/2013 18:52, Peter Allan wrote:
> Having got DECnet working on my CentOS 5.9 system (thanks again for 
> those who helped), I am confused by a problem that I am having with 
> connecting to a remote computer. (It is an Alpha workstation running 
> VMS 7.2-1)
>
> I can log into it using "dnlogin node8". That works fine.
>
> However, if I try to use dndir to get a directory listing, then 
> sometimes it works and sometimes it fails with
>    File name parse error
>
> For example, the following commands work
>
> dndir 'node8::sys$manager:systartup_vms.com <http://systartup_vms.com>'
>
> dndir 'node8"system password123"::sys$manager:systartup_vms.com 
> <http://systartup_vms.com>'
>     (The system password isn't really password123, but it is 11 
> characters long.)
>
> dndir 'node8"system password123"::'
>
> If I try
> dndir 'node8"system password1234"::'
> the I get an error of connect failed: Login information invalid at 
> remote node, as you would expect
>
> However (and this is the point), if I try
> dndir 'node8"system password12345"::'
> then I get
> File name parse error
>
> Playing around with different lengths of username and password 
> indicates that the length of the username has no effect on whether I 
> get a file name parse error. (Admittedly, I only tried shorter 
> usernames.) It is the length of the password that seems to be the 
> critical factor.
>
> You will probably deduce that my password used to be longer than 12 
> characters, which is how I came across this. VMS allows passwords to 
> be up to 32 characters long, hence my surprise at finding this problem.
>
> Is this a problem with dnprogs, with the linux shell (which seems 
> unlikely) or something else?
>
> Peter Allan
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
>
>
> _______________________________________________
> Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>

[Linux-decnet-user] File name parse error confusion

[Peter A. <pet...@gm...>]

Having got DECnet working on my CentOS 5.9 system (thanks again for those
who helped), I am confused by a problem that I am having with connecting to
a remote computer. (It is an Alpha workstation running VMS 7.2-1)

I can log into it using "dnlogin node8". That works fine.

However, if I try to use dndir to get a directory listing, then sometimes
it works and sometimes it fails with
   File name parse error

For example, the following commands work

dndir 'node8::sys$manager:systartup_vms.com'

dndir 'node8"system password123"::sys$manager:systartup_vms.com'
    (The system password isn't really password123, but it is 11 characters
long.)

dndir 'node8"system password123"::'

If I try
dndir 'node8"system password1234"::'
the I get an error of connect failed: Login information invalid at remote
node, as you would expect

However (and this is the point), if I try
dndir 'node8"system password12345"::'
then I get
File name parse error

Playing around with different lengths of username and password indicates
that the length of the username has no effect on whether I get a file name
parse error. (Admittedly, I only tried shorter usernames.) It is the length
of the password that seems to be the critical factor.

You will probably deduce that my password used to be longer than 12
characters, which is how I came across this. VMS allows passwords to be up
to 32 characters long, hence my surprise at finding this problem.

Is this a problem with dnprogs, with the linux shell (which seems unlikely)
or something else?

Peter Allan

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Peter A. <pet...@gm...>]

Thanks Larry. That is very clear.

Peter

On 1 March 2013 21:51, Larry Baker <ba...@us...> wrote:

> Peter,
>
> Well, working our way backwards.  As you noticed, you can't run DECnet on
> Linux without the decnet kernel module, decnet.ko.  If you had one, you
> would want to put it somewhere in /lib/modules/`uname -r` where modprobe
> (actually, insmod) could find it.  That is because the decnet init script
> runs modprobe decnet before running any of the decnet daemons (dnetd,
> phoned).  The last step:
>
> # Install the CentOS 5.9 decnet kernel module
> mkdir -p /lib/modules/`uname -r`/updates
> \cp net/decnet/decnet.ko /lib/modules/`uname -r`/updates/
> depmod
>
>
> puts our decnet.ko into a directory under /lib/modules/`uname -r` so it
> will be found by modprobe.  The depmod command updates the Linux database
> of module dependencies, since there is a new module to consider now.
>
> Alas, Red Hat does not provide decnet.ko in any of their binary RPMs.  In
> the old days, you had to recompile the entire Linux kernel to add a module.
>  That is no longer necessary.  All a kernel module needs are the kernel
> development header files and libraries, the configuration header file for
> the running kernel, and the symbol table for the running kernel.  Given
> that we have the necessary Linux source files and build files, and that we
> have installed the gcc compiler and kernel development tools, we create our
> own decnet.ko:
>
> # Build the CentOS 5.9 decnet kernel module
> cd /usr/src/redhat/BUILD/kernel-2.6.18/linux-`uname -r`.`uname -i`
> make mrproper
> \cp /boot/config-`uname -r` .config
> make oldconfig
> make prepare
> make modules_prepare
> zcat /boot/symvers-`uname -r`.gz >Module.symvers
> make M=net/decnet CONFIG_DECNET=m
>
>
> We are following the instructions for adding any module (could be one we
> wrote) to an existing CentOS Linux system (
> http://wiki.centos.org/HowTos/BuildingKernelModules).  The
>
> \cp /boot/config-`uname -r` .config
>
>
> and
>
> zcat /boot/symvers-`uname -r`.gz >Module.symvers
>
>
> steps grab the configuration file and symbol table file for the running
> kernel.  The rest of the file we need come from the Linux
> kernel development environment.
>
> That presumes we already have the Linux kernel development environment set
> up.  Red Hat has a source RPM for their Linux kernel, but it is not quite
> set up; you have to perform some additional steps after installing the
> kernel source RPM (http://wiki.centos.org/HowTos/I_need_the_Kernel_Source).
>  We perform those steps to create the kernel source tree we need to compile:
>
> # Get the CentOS 5.9 kernel source RPM
> cd /usr/src/redhat/SRPMS
> RELEASE=`awk '{print $3}' /etc/redhat-release`
> wget -N http://vault.centos.org/${RELEASE}/updates/SRPMS/kernel-`uname
> -r`.src.rpm
>
> # Install the CentOS 5.9 kernel sources
> cd /usr/src/redhat/SRPMS
> rpm -ivh kernel-`uname -r`.src.rpm 2>&1 | grep -v mock
>
> # Prepare the CentOS 5.9 kernel sources
> cd /usr/src/redhat/SPECS
> yum install unifdef
> rpmbuild -bp kernel.spec
>
>
> That's why we did what we did.
>
> We didn't do any patching ourselves of an decnet source files; we used the
> decnet source files prepared for us by the Red Hat Linux kernel source RPM.
>  For Red Hat/CentOS 5.9, no patches are needed.  For Red Hat/CentOS 6.x,
> there will be additional steps to apply the patches I wrote before building
> the decnet.ko kernel module.  You're not there yet.
>
> Larry Baker
> US Geological Survey
> 650-329-5608
> ba...@us...
>
>
>
> On 1 Mar 2013, at 5:22 AM, Peter Allan wrote:
>
> Larry,
>
> Thanks for the script that you sent to me. I went through it yesterday
> (doing line-by-line copy and paste as you suggested) and it all worked
> wonderfully.
>
> I clearly don't understand properly what is happening, even though it all
> works. The reason that I was getting nowhere before I mailed this list was
> that I was looking for an rpm that contained either decnet.ko or a source
> file (decnet.c) that could be built into decnet.ko. My system now has a
> decnet.c file, but it did not come directly out of an rpm. It presume that
> the patches in the src.rpm file do a lot more than just patch an existing
> file.
>
> Can you educate me about what the script is doing please. My understanding
> of what is going on in this process is sadly lacking and I much prefer to
> understand what I am doing.
>
> I will keep an eye out for the 6.3 stuff, but having got 5.9 working, I am
> perfectly happy for now.
>
> Thanks for your assistance. Now to try it with my emulated VAX with simh!
>
> Peter
>
> On 28 February 2013 17:22, Larry Baker <ba...@us...> wrote:
>
>> Peter,
>>
>> CentOS 5.9 is the last CentOS release that does not require a patch to
>> the decnet kernel module.  For CentOS 6.3 you will need the patch.  Without
>> the patch, whenever the DECnet devices are brought down and up (which is
>> what happens when you write the DECnet executor node address to
>> /proc/sys/net/decnet/node_address), all the /proc/sys/net/decnet entries
>> disappear, except the conf entries.  DECnet works fine, but you have one
>> chance to get everything configured, and you can't tell what's going on by
>> reading the /proc/sys/net/decnet entries after that.  I have patches for
>> Linux that cures this that I also need to add to the Wiki.
>>
>> Larry Baker
>> US Geological Survey
>> 650-329-5608
>> ba...@us...
>>
>>
>>
>> On 28 Feb 2013, at 9:12 AM, Peter Allan wrote:
>>
>> Larry,
>>
>> Thanks for the script. I will take a look at it.
>>
>> I had found that dnprog 2.53 does not build because of the missing test.c
>> file, which is why I am using 2.52. This seems ok for now.
>>
>> Cheers
>>
>> Peter
>>
>> On 28 February 2013 16:38, Larry Baker <ba...@us...> wrote:
>>
>>> Peter,
>>>
>>> Chrissie has granted me permission to modify the Wiki, but I have not
>>> had time to get back to it.  In the mean time, attached is a shell script
>>> with the commands to install the decnet kernel module on CentOS 5.9.  I did
>>> not run the commands from the script -- I ran each one manually using
>>> cut-and-paste to a terminal window.
>>>
>>> The other thing that needs to be documented is that the dnprogs 2.53
>>> distribution make fails because the test.c file is missing from libvaxdata,
>>> which I wrote.  So, I have my own copy which I used.  Let me know if you
>>> need that as well.
>>>
>>>
>>> Larry Baker
>>> US Geological Survey
>>> 650-329-5608
>>> ba...@us...
>>>
>>>
>>>
>>> On 28 Feb 2013, at 3:32 AM, Peter Allan wrote:
>>>
>>> > I am trying to get DECnet working from a Linux system to an Alpha
>>> running VMS 7.3. I have succeeded in doing this from Fedora Core 14, which
>>> includes the kernel module decnet.ko, and downloading and building the
>>> dnprogs version 2.52.
>>> >
>>> > However, my main Linux system runs CentOS 5.9. (I am in the process of
>>> moving to CentOS 6.3). My problem is that I cannot find the decnet kernel
>>> module for any CentOS 5 or 6 system. Can anyone point me to (ideally) the
>>> build kernel module or the source code for the module so I can build it
>>> myself.
>>> >
>>> > An e-mail from Larry Baker a couple of weeks ago implies that the
>>> module does exist for CentOS 5.9 i386, hence my request to this group.
>>> >
>>> > I am using the 64bit versions of CentOS.
>>> >
>>> > Regards
>>> >
>>> > Peter Allan
>>> >
>>> ------------------------------------------------------------------------------
>>> > Everyone hates slow websites. So do we.
>>> > Make your web apps faster with AppDynamics
>>> > Download AppDynamics Lite for free today:
>>> >
>>> http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________
>>> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>>> >
>>> > Linux-decnet-user mailing list
>>> > Lin...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>>> >
>>>
>>>
>>>
>>
>>
>
>

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Larry B. <ba...@us...>]

Peter,

Well, working our way backwards.  As you noticed, you can't run DECnet on Linux without the decnet kernel module, decnet.ko.  If you had one, you would want to put it somewhere in /lib/modules/`uname -r` where modprobe (actually, insmod) could find it.  That is because the decnet init script runs modprobe decnet before running any of the decnet daemons (dnetd, phoned).  The last step:

> # Install the CentOS 5.9 decnet kernel module
> mkdir -p /lib/modules/`uname -r`/updates
> \cp net/decnet/decnet.ko /lib/modules/`uname -r`/updates/
> depmod

puts our decnet.ko into a directory under /lib/modules/`uname -r` so it will be found by modprobe.  The depmod command updates the Linux database of module dependencies, since there is a new module to consider now.

Alas, Red Hat does not provide decnet.ko in any of their binary RPMs.  In the old days, you had to recompile the entire Linux kernel to add a module.  That is no longer necessary.  All a kernel module needs are the kernel development header files and libraries, the configuration header file for the running kernel, and the symbol table for the running kernel.  Given that we have the necessary Linux source files and build files, and that we have installed the gcc compiler and kernel development tools, we create our own decnet.ko:

> # Build the CentOS 5.9 decnet kernel module
> cd /usr/src/redhat/BUILD/kernel-2.6.18/linux-`uname -r`.`uname -i`
> make mrproper
> \cp /boot/config-`uname -r` .config
> make oldconfig
> make prepare
> make modules_prepare
> zcat /boot/symvers-`uname -r`.gz >Module.symvers
> make M=net/decnet CONFIG_DECNET=m


We are following the instructions for adding any module (could be one we wrote) to an existing CentOS Linux system (http://wiki.centos.org/HowTos/BuildingKernelModules).  The

> \cp /boot/config-`uname -r` .config

and

> zcat /boot/symvers-`uname -r`.gz >Module.symvers

steps grab the configuration file and symbol table file for the running kernel.  The rest of the file we need come from the Linux kernel development environment.

That presumes we already have the Linux kernel development environment set up.  Red Hat has a source RPM for their Linux kernel, but it is not quite set up; you have to perform some additional steps after installing the kernel source RPM (http://wiki.centos.org/HowTos/I_need_the_Kernel_Source).  We perform those steps to create the kernel source tree we need to compile:

> # Get the CentOS 5.9 kernel source RPM
> cd /usr/src/redhat/SRPMS
> RELEASE=`awk '{print $3}' /etc/redhat-release`
> wget -N http://vault.centos.org/${RELEASE}/updates/SRPMS/kernel-`uname -r`.src.rpm
> 
> # Install the CentOS 5.9 kernel sources
> cd /usr/src/redhat/SRPMS
> rpm -ivh kernel-`uname -r`.src.rpm 2>&1 | grep -v mock
> 
> # Prepare the CentOS 5.9 kernel sources
> cd /usr/src/redhat/SPECS
> yum install unifdef
> rpmbuild -bp kernel.spec

That's why we did what we did.

We didn't do any patching ourselves of an decnet source files; we used the decnet source files prepared for us by the Red Hat Linux kernel source RPM.  For Red Hat/CentOS 5.9, no patches are needed.  For Red Hat/CentOS 6.x, there will be additional steps to apply the patches I wrote before building the decnet.ko kernel module.  You're not there yet.

Larry Baker
US Geological Survey
650-329-5608
ba...@us...



On 1 Mar 2013, at 5:22 AM, Peter Allan wrote:

> Larry,
>  
> Thanks for the script that you sent to me. I went through it yesterday (doing line-by-line copy and paste as you suggested) and it all worked wonderfully.
>  
> I clearly don't understand properly what is happening, even though it all works. The reason that I was getting nowhere before I mailed this list was that I was looking for an rpm that contained either decnet.ko or a source file (decnet.c) that could be built into decnet.ko. My system now has a decnet.c file, but it did not come directly out of an rpm. It presume that the patches in the src.rpm file do a lot more than just patch an existing file.
>  
> Can you educate me about what the script is doing please. My understanding of what is going on in this process is sadly lacking and I much prefer to understand what I am doing.
>  
> I will keep an eye out for the 6.3 stuff, but having got 5.9 working, I am perfectly happy for now.
>  
> Thanks for your assistance. Now to try it with my emulated VAX with simh!
>  
> Peter
> 
> On 28 February 2013 17:22, Larry Baker <ba...@us...> wrote:
> Peter,
> 
> CentOS 5.9 is the last CentOS release that does not require a patch to the decnet kernel module.  For CentOS 6.3 you will need the patch.  Without the patch, whenever the DECnet devices are brought down and up (which is what happens when you write the DECnet executor node address to /proc/sys/net/decnet/node_address), all the /proc/sys/net/decnet entries disappear, except the conf entries.  DECnet works fine, but you have one chance to get everything configured, and you can't tell what's going on by reading the /proc/sys/net/decnet entries after that.  I have patches for Linux that cures this that I also need to add to the Wiki.
> 
> Larry Baker
> US Geological Survey
> 650-329-5608
> ba...@us...
> 
> 
> 
> On 28 Feb 2013, at 9:12 AM, Peter Allan wrote:
> 
>> Larry,
>> 
>> Thanks for the script. I will take a look at it.
>> 
>> I had found that dnprog 2.53 does not build because of the missing test.c file, which is why I am using 2.52. This seems ok for now.
>> 
>> Cheers
>> 
>> Peter
>> 
>> On 28 February 2013 16:38, Larry Baker <ba...@us...> wrote:
>> Peter,
>> 
>> Chrissie has granted me permission to modify the Wiki, but I have not had time to get back to it.  In the mean time, attached is a shell script with the commands to install the decnet kernel module on CentOS 5.9.  I did not run the commands from the script -- I ran each one manually using cut-and-paste to a terminal window.
>> 
>> The other thing that needs to be documented is that the dnprogs 2.53 distribution make fails because the test.c file is missing from libvaxdata, which I wrote.  So, I have my own copy which I used.  Let me know if you need that as well.
>> 
>> 
>> Larry Baker
>> US Geological Survey
>> 650-329-5608
>> ba...@us...
>> 
>> 
>> 
>> On 28 Feb 2013, at 3:32 AM, Peter Allan wrote:
>> 
>> > I am trying to get DECnet working from a Linux system to an Alpha running VMS 7.3. I have succeeded in doing this from Fedora Core 14, which includes the kernel module decnet.ko, and downloading and building the dnprogs version 2.52.
>> >
>> > However, my main Linux system runs CentOS 5.9. (I am in the process of moving to CentOS 6.3). My problem is that I cannot find the decnet kernel module for any CentOS 5 or 6 system. Can anyone point me to (ideally) the build kernel module or the source code for the module so I can build it myself.
>> >
>> > An e-mail from Larry Baker a couple of weeks ago implies that the module does exist for CentOS 5.9 i386, hence my request to this group.
>> >
>> > I am using the 64bit versions of CentOS.
>> >
>> > Regards
>> >
>> > Peter Allan
>> > ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> > http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________
>> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>> >
>> > Linux-decnet-user mailing list
>> > Lin...@li...
>> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>> >
>> 
>> 
>> 
> 
> 

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Peter A. <pet...@gm...>]

Larry,

Thanks for the script that you sent to me. I went through it yesterday
(doing line-by-line copy and paste as you suggested) and it all worked
wonderfully.

I clearly don't understand properly what is happening, even though it all
works. The reason that I was getting nowhere before I mailed this list was
that I was looking for an rpm that contained either decnet.ko or a source
file (decnet.c) that could be built into decnet.ko. My system now has a
decnet.c file, but it did not come directly out of an rpm. It presume that
the patches in the src.rpm file do a lot more than just patch an existing
file.

Can you educate me about what the script is doing please. My understanding
of what is going on in this process is sadly lacking and I much prefer to
understand what I am doing.

I will keep an eye out for the 6.3 stuff, but having got 5.9 working, I am
perfectly happy for now.

Thanks for your assistance. Now to try it with my emulated VAX with simh!

Peter

On 28 February 2013 17:22, Larry Baker <ba...@us...> wrote:

> Peter,
>
> CentOS 5.9 is the last CentOS release that does not require a patch to the
> decnet kernel module.  For CentOS 6.3 you will need the patch.  Without the
> patch, whenever the DECnet devices are brought down and up (which is what
> happens when you write the DECnet executor node address to
> /proc/sys/net/decnet/node_address), all the /proc/sys/net/decnet entries
> disappear, except the conf entries.  DECnet works fine, but you have one
> chance to get everything configured, and you can't tell what's going on by
> reading the /proc/sys/net/decnet entries after that.  I have patches for
> Linux that cures this that I also need to add to the Wiki.
>
> Larry Baker
> US Geological Survey
> 650-329-5608
> ba...@us...
>
>
>
> On 28 Feb 2013, at 9:12 AM, Peter Allan wrote:
>
> Larry,
>
> Thanks for the script. I will take a look at it.
>
> I had found that dnprog 2.53 does not build because of the missing test.c
> file, which is why I am using 2.52. This seems ok for now.
>
> Cheers
>
> Peter
>
> On 28 February 2013 16:38, Larry Baker <ba...@us...> wrote:
>
>> Peter,
>>
>> Chrissie has granted me permission to modify the Wiki, but I have not had
>> time to get back to it.  In the mean time, attached is a shell script with
>> the commands to install the decnet kernel module on CentOS 5.9.  I did not
>> run the commands from the script -- I ran each one manually using
>> cut-and-paste to a terminal window.
>>
>> The other thing that needs to be documented is that the dnprogs 2.53
>> distribution make fails because the test.c file is missing from libvaxdata,
>> which I wrote.  So, I have my own copy which I used.  Let me know if you
>> need that as well.
>>
>>
>> Larry Baker
>> US Geological Survey
>> 650-329-5608
>> ba...@us...
>>
>>
>>
>> On 28 Feb 2013, at 3:32 AM, Peter Allan wrote:
>>
>> > I am trying to get DECnet working from a Linux system to an Alpha
>> running VMS 7.3. I have succeeded in doing this from Fedora Core 14, which
>> includes the kernel module decnet.ko, and downloading and building the
>> dnprogs version 2.52.
>> >
>> > However, my main Linux system runs CentOS 5.9. (I am in the process of
>> moving to CentOS 6.3). My problem is that I cannot find the decnet kernel
>> module for any CentOS 5 or 6 system. Can anyone point me to (ideally) the
>> build kernel module or the source code for the module so I can build it
>> myself.
>> >
>> > An e-mail from Larry Baker a couple of weeks ago implies that the
>> module does exist for CentOS 5.9 i386, hence my request to this group.
>> >
>> > I am using the 64bit versions of CentOS.
>> >
>> > Regards
>> >
>> > Peter Allan
>> >
>> ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> >
>> http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________
>> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
>> >
>> > Linux-decnet-user mailing list
>> > Lin...@li...
>> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
>> >
>>
>>
>>
>
>

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Larry B. <ba...@us...>]

Peter,

Chrissie has granted me permission to modify the Wiki, but I have not had time to get back to it.  In the mean time, attached is a shell script with the commands to install the decnet kernel module on CentOS 5.9.  I did not run the commands from the script -- I ran each one manually using cut-and-paste to a terminal window.

The other thing that needs to be documented is that the dnprogs 2.53 distribution make fails because the test.c file is missing from libvaxdata, which I wrote.  So, I have my own copy which I used.  Let me know if you need that as well.

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Larry B. <ba...@us...>]

Peter,

CentOS 5.9 is the last CentOS release that does not require a patch to the decnet kernel module.  For CentOS 6.3 you will need the patch.  Without the patch, whenever the DECnet devices are brought down and up (which is what happens when you write the DECnet executor node address to /proc/sys/net/decnet/node_address), all the /proc/sys/net/decnet entries disappear, except the conf entries.  DECnet works fine, but you have one chance to get everything configured, and you can't tell what's going on by reading the /proc/sys/net/decnet entries after that.  I have patches for Linux that cures this that I also need to add to the Wiki.

Larry Baker
US Geological Survey
650-329-5608
ba...@us...



On 28 Feb 2013, at 9:12 AM, Peter Allan wrote:

> Larry,
> 
> Thanks for the script. I will take a look at it.
> 
> I had found that dnprog 2.53 does not build because of the missing test.c file, which is why I am using 2.52. This seems ok for now.
> 
> Cheers
> 
> Peter
> 
> On 28 February 2013 16:38, Larry Baker <ba...@us...> wrote:
> Peter,
> 
> Chrissie has granted me permission to modify the Wiki, but I have not had time to get back to it.  In the mean time, attached is a shell script with the commands to install the decnet kernel module on CentOS 5.9.  I did not run the commands from the script -- I ran each one manually using cut-and-paste to a terminal window.
> 
> The other thing that needs to be documented is that the dnprogs 2.53 distribution make fails because the test.c file is missing from libvaxdata, which I wrote.  So, I have my own copy which I used.  Let me know if you need that as well.
> 
> 
> Larry Baker
> US Geological Survey
> 650-329-5608
> ba...@us...
> 
> 
> 
> On 28 Feb 2013, at 3:32 AM, Peter Allan wrote:
> 
> > I am trying to get DECnet working from a Linux system to an Alpha running VMS 7.3. I have succeeded in doing this from Fedora Core 14, which includes the kernel module decnet.ko, and downloading and building the dnprogs version 2.52.
> >
> > However, my main Linux system runs CentOS 5.9. (I am in the process of moving to CentOS 6.3). My problem is that I cannot find the decnet kernel module for any CentOS 5 or 6 system. Can anyone point me to (ideally) the build kernel module or the source code for the module so I can build it myself.
> >
> > An e-mail from Larry Baker a couple of weeks ago implies that the module does exist for CentOS 5.9 i386, hence my request to this group.
> >
> > I am using the 64bit versions of CentOS.
> >
> > Regards
> >
> > Peter Allan
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________
> > Project Home Page: http://linux-decnet.wiki.sourceforge.net/
> >
> > Linux-decnet-user mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
> >
> 
> 
> 

Re: [Linux-decnet-user] DECnet kernel module for CentOS?

[Steven W. <st...@ch...>]

Hi,

On Thu, 2013-02-28 at 11:32 +0000, Peter Allan wrote:
> I am trying to get DECnet working from a Linux system to an Alpha
> running VMS 7.3. I have succeeded in doing this from Fedora Core 14,
> which includes the kernel module decnet.ko, and downloading and
> building the dnprogs version 2.52.
> 
> However, my main Linux system runs CentOS 5.9. (I am in the process of
> moving to CentOS 6.3). My problem is that I cannot find the decnet
> kernel module for any CentOS 5 or 6 system. Can anyone point me to
> (ideally) the build kernel module or the source code for the module so
> I can build it myself.
> 
Since CentOS is a clone of RHEL, and RHEL doesn't ship/support DECnet
there is not an "official" module.

> An e-mail from Larry Baker a couple of weeks ago implies that the
> module does exist for CentOS 5.9 i386, hence my request to this group.
> 
Well, the code exists, so you can build the module if you build your own
kernel. It should just be a case of installing the kernel source package
and tweeking the config to turn it on, and then rebuilding the package,

Steve.

[Linux-decnet-user] DECnet kernel module for CentOS?

[Peter A. <pet...@gm...>]

I am trying to get DECnet working from a Linux system to an Alpha running
VMS 7.3. I have succeeded in doing this from Fedora Core 14, which includes
the kernel module decnet.ko, and downloading and building the dnprogs
version 2.52.

However, my main Linux system runs CentOS 5.9. (I am in the process of
moving to CentOS 6.3). My problem is that I cannot find the decnet kernel
module for any CentOS 5 or 6 system. Can anyone point me to (ideally) the
build kernel module or the source code for the module so I can build it
myself.

An e-mail from Larry Baker a couple of weeks ago implies that the module
does exist for CentOS 5.9 i386, hence my request to this group.

I am using the 64bit versions of CentOS.

Regards

Peter Allan