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

Re: [Linux-decnet-user] Applying Kernel patch

[Patrick C. <pa...@pa...>]

On Sat, Aug 26, 2000 at 11:30:09AM -0400, Akihiko Tanaka wrote:
> I think I have three options to try:
> 
> 1) Continue to work with Linux 2.2-14 and apply DECnet kernel patch 2.2-16.
> 
> 2) Upgrade Linux 2.2-14 to 2.2-16 and apply DECnet kernel patch 2.2-16.
> 
> 3) Upgrade Linux to 2.4.
> 
> How do I look at the current configuration before doing "make [x|menu]config?
> 
> Is Linux 2.4 officially released?

I would recommend you download a new 2.2.16 or 17 if it's released yet (should
be soon now). Look in the file .config to see what the configuration options
are, that's the file that gets generated by make *config and gets included by
the Makefile.

2.4 is not an official release yet. It seems fairly stable to me but some areas
are still missing so I can't really recommend it. eg smbfs doesn't compile and
ISDN doesn't seem to work for me either - DECnet does though!


Patrick

Re: [Linux-decnet-user] Applying Kernel patch

[Akihiko T. <TAN...@sp...>]

I think I have three options to try:

1) Continue to work with Linux 2.2-14 and apply DECnet kernel patch 2.2-16.

2) Upgrade Linux 2.2-14 to 2.2-16 and apply DECnet kernel patch 2.2-16.

3) Upgrade Linux to 2.4.

How do I look at the current configuration before doing "make [x|menu]config?

Is Linux 2.4 officially released?

Akihiko 
---------- Original Message ----------------------------------
From: Patrick Caulfield <pa...@pa...>
Date: Sun, 20 Aug 2000 08:29:13 +0100

>On Sat, Aug 19, 2000 at 12:25:06PM -0400, Akihiko Tanaka wrote:
>> I skipped "make clean" but I still got the same error:
>> 
>> make: *** No rule to make target 'bzImage'. Stop.
>> 
>> Do I need to upgrade a kernel 2.2.16 before applying DECNET kernel patch 2.2.16?
>
>No, you can build on any Linux version you like.
>
>I think your kernel source tree is suspect here. Try expanding the sources in a
>new directory, applying the patch to that and then rebuilding (don't forget to
>make [x|menu]config !)
>
>Unless you have a horribly old and broken make I'm sure that will work.(<fx>
>ducks!)
>
>Patrick 
>
>_______________________________________________
>Linux-decnet-user mailing list
>Lin...@li...
>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>

Re: [Linux-decnet-user] 2.4.0 kernel

[Patrick C. <pa...@pa...>]

On Tue, Aug 22, 2000 at 06:53:20AM -0700, ecc wrote:
> 
> I am experiencing a problem with the 2.4.0 kernel (sorry don't know the
> release)
> It appears that I can use Decnet out of my linux box, but not into it.
> 
> I thought it was my changes and have tried to find the cause, but I
> reinstalled the original dnprogs-2.05 with the same result.
> 
> Tcpdump shows the connection attempts with no response from Linux, but
> from Linux I can sethost to vax.
> 
> Is there something I may have missed in setting up the new kernel?
> I am running decnet as a module ( never did before), but cat
> /proc/modules shows "decnet  59016 0" (the zero worries me).
> 
> Insmod decnet, replies module already exists.
> Per Steve we do not need to "startnet", and it did not make any
> difference when I did.(Steve: I thought maybe I needed it for module
> decnet)
> 
> I will try to recompile in the kernel. My prerelease built itself like
> this, so if it really is an issue others will have the same experience.

That is odd, my 2.4 kernels have all been fine since test3 and I've just tried
test7 and that's OK too.

I know you don't want to hear me say this but which compiler are you using to
compile 2.4.0? I had problems with 2.7.2 so switched to 2.95.2 and that seems
better. Mind you, the kernel doesn't compile at all with 2.7.2 so you'd probably
notice that!

The zero on the end of the modules line should only worry you if you have a
DECnet server running. in which case it hasn't opened the socket correctly. Try
stracing the server and see what it says - there may also be a failure message
in syslog.

Finally (and you knew I was going to say this) make sure your dnprogs are
compiled against the right kernel...

patrick

Re: [Linux-decnet-user] Fwd: DECnet & Kernel 2.4

[Patrick C. <pa...@pa...>]

On Tue, Aug 22, 2000 at 08:51:36PM +0000, Eduardo Serrat wrote:
> 
> Hi Josef,
> 
> 
> >From: "J.Heinen" <J.H...@fz...>
> >To: ems...@ge...
> >Subject: DECnet & Kernel 2.4
> >Date: Tue, 22 Aug 2000 16:08:26 +0200
> >
> >Hi,
> >
> >we are using your DECnet programs under Linux 2.2.16 without
> >any problems on a Pentium II with a DEC Tulip card. Great!
> >
> >Now we tried to use the latest 2.4 kernel. When we run the
> >startnet programm, we receive the following error message:
> >
> >sysctl(set exec dev): No such device
> >


The quickest thing is to remove startnet altogether because it's not
really needed for 2.4 kernels. However you will need to set the MAC
address manually if you do this, even for a tulip card.

If you're using modules, make sure that the module for the tulip is
loaded before startnet is run too.

Patrick

[Linux-decnet-user] Fwd: DECnet & Kernel 2.4

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

Hi Josef,


>From: "J.Heinen" <J.H...@fz...>
>To: ems...@ge...
>Subject: DECnet & Kernel 2.4
>Date: Tue, 22 Aug 2000 16:08:26 +0200
>
>Hi,
>
>we are using your DECnet programs under Linux 2.2.16 without
>any problems on a Pentium II with a DEC Tulip card. Great!
>
>Now we tried to use the latest 2.4 kernel. When we run the
>startnet programm, we receive the following error message:
>
>sysctl(set exec dev): No such device
>
>Do you have any idea?
>
>Best Wishes and thanks in advance...
>
>jh
>--
>       Von/From: Josef Heinen             Forschungszentrum Juelich GmbH
>  Telefon/Phone: +49 (2461) 61-3912   Institut fuer Festkoerperforschung
>           Mail: J.H...@fz...                  D-52425 Juelich
>            WWW: http://iffwww.iff.kfa-juelich.de/~jheinen

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

[Linux-decnet-user] 2.4.0 kernel

[ecc <ec...@cy...>]

I am experiencing a problem with the 2.4.0 kernel (sorry don't know the
release)
It appears that I can use Decnet out of my linux box, but not into it.

I thought it was my changes and have tried to find the cause, but I
reinstalled the original dnprogs-2.05 with the same result.

Tcpdump shows the connection attempts with no response from Linux, but
from Linux I can sethost to vax.

Is there something I may have missed in setting up the new kernel?
I am running decnet as a module ( never did before), but cat
/proc/modules shows "decnet  59016 0" (the zero worries me).

Insmod decnet, replies module already exists.
Per Steve we do not need to "startnet", and it did not make any
difference when I did.(Steve: I thought maybe I needed it for module
decnet)

I will try to recompile in the kernel. My prerelease built itself like
this, so if it really is an issue others will have the same experience.

greetings,

Ed Calderon

Re: [Linux-decnet-user] Applying Kernel patch

[Patrick C. <pa...@pa...>]

On Sat, Aug 19, 2000 at 12:25:06PM -0400, Akihiko Tanaka wrote:
> I skipped "make clean" but I still got the same error:
> 
> make: *** No rule to make target 'bzImage'. Stop.
> 
> Do I need to upgrade a kernel 2.2.16 before applying DECNET kernel patch 2.2.16?

No, you can build on any Linux version you like.

I think your kernel source tree is suspect here. Try expanding the sources in a
new directory, applying the patch to that and then rebuilding (don't forget to
make [x|menu]config !)

Unless you have a horribly old and broken make I'm sure that will work.(<fx>
ducks!)

Patrick 

Re: [Linux-decnet-user] Applying Kernel patch

[Akihiko T. <TAN...@sp...>]

I skipped "make clean" but I still got the same error:

make: *** No rule to make target 'bzImage'. Stop.

Do I need to upgrade a kernel 2.2.16 before applying DECNET kernel patch 2.2.16?

Akihiko
---------- Original Message ----------------------------------
From: ecc <ec...@cy...>
Date: Thu, 17 Aug 2000 07:49:04 -0700

>Here is what I do.
>
>cd/usr/src/linux
>make config
>make dep
>make bzImage
>make modules
>make modules_install
>
>I believe your problem is "make clean"..is cleaning!
>You can use make clean before make dep if you would like, but try not doing it
>before bzImage.
>
>good luck!
>Ed
>
>Akihiko Tanaka wrote:
>
>> I tried the following commands to make bzImaze:
>>
>> cd /usr/src/linux
>> make dep; make clean
>> make bzImage
>>
>> I got a make error:
>>
>> make: *** No rule to make target 'bzImage'. Stop.
>>
>> DO I need to modify Makefile? Is it in /usr/src/linux/arch/i386/boot directory?
>>
>> Akihiko
>> >-----Original Message-----
>> >From: Akihiko Tanaka [mailto:TAN...@sp...]
>> >Sent: Tuesday, 15 August 2000 9:04
>> >To: Patrick Caulfield
>> >Cc: lin...@li...; ak...@co...
>> >Subject: Re: [Linux-decnet-user] Applying Kernel patch
>> >
>> >
>> >I modified proc_fs.h and executed "make zImage" as shown in the kernel
>> >installation guide. It complied and linked. However, the following errors
>> >were displayed:
>> >
>> >Root device is (3,8)
>> >Boot sector 512 bytes.
>> >Setup is 3440 bytes.
>> >System is 619kB
>> >System is too big. Try using bzImage or modules.
>> >make[1]:***[zImage] Error 1
>> >make[1]:Leaving directory 'usr/src/linux-2.2.14/arch/i386/boot'
>> >make:***[zImage]Error 2
>> >
>> >Do I need to fix these errors? It looks zImage is created.
>> >
>> >Akihiko
>> >---------- Original Message ----------------------------------
>> >From: Patrick Caulfield <pa...@pa...>
>> >Date: Fri, 11 Aug 2000 08:27:54 +0100
>> >
>> >>On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
>> >>> I downloaded the latest patch for DECNET and tried to install on my Red
>> >Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the
>> >Kernel Patch Installation Guide on the web. When I did
>> >>>
>> >>> patch -p1 <decnet-2_2_16.diff
>> >>>
>> >>> I got an error and created proc_fs.h.rej file. It seems that patch tried
>> >to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
>> >>>
>> >>> I went ahead to execute make zImage. But because PROC_NET_DECNET is not
>> >defined in proc_fs.h, I had a compile error from af_decnet.c.
>> >>>
>> >>> How can I correct a patch error? Do I need to start from patch and the
>> >follow the instruction again? 'Make config' asked a lot of questions. It
>> >looks like defining a lot of Environment Variables. Can I skip this and use
>> >the previously defined values?
>> >>
>> >>
>> >>That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
>> >>either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:
>> >>
>> >>Look for PROC_NET_LAST and add the following line just before it:
>> >>
>> >>PROC_NET_DECNET,
>> >>
>> >>Don't forget the trailing comma or it won't compile.
>> >>
>> >><whinge mode>
>> >>Considering 2.2.x is supposed to be a stable kernel I find it a little
>> >galling
>> >>that new /proc/net entries seem to turn up in almost every new release :-(
>> >></whinge mode>
>> >>
>> >>Just to confirm that, the file should look a little like this in that area:
>> >>
>> >>
>> >>        PROC_NET_BRIDGE,
>> >>        PROC_NET_DECNET,
>> >>        PROC_NET_LAST
>> >>};
>> >>
>> >>enum scsi_directory_inos {
>> >>        PROC_SCSI_SCSI = 256,
>> >>        PROC_SCSI_ADVANSYS,
>> >>
>> >>
>> >>Patrick
>> >>
>> >>_______________________________________________
>> >>Linux-decnet-user mailing list
>> >>Lin...@li...
>> >>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>> >>
>> >
>> >_______________________________________________
>> >Linux-decnet-user mailing list
>> >Lin...@li...
>> >http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>> >
>> >EOM
>> >
>> >NOTICE - This message contains information intended only for the use of the
>> >addressee named above.  It may also be confidential and/or privileged.  If
>> >you are not the intended recipient of this message you are hereby notified
>> >that you must not disseminate, copy or take any action in reliance on it.
>> >If you have received this message in error please notify pos...@bh....
>> >
>> >
>> >_______________________________________________
>> >Linux-decnet-user mailing list
>> >Lin...@li...
>> >http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>> >
>>
>> _______________________________________________
>> Linux-decnet-user mailing list
>> Lin...@li...
>> http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>
>

Re: [Linux-decnet-user] Applying Kernel patch

[Patrick C. <pa...@pa...>]

On Wed, Aug 16, 2000 at 08:02:39PM -0400, Akihiko Tanaka wrote:
> I tried the following commands to make bzImaze:
> 
> cd /usr/src/linux
> make dep; make clean
> make bzImage

Check you are building the right kernel - your original message said the sources
were in /usr/src/linux-2.2.14

bzImage has been there since - well, I don't know when but a very long time,
certainly 2.0.38 and all after that has it.
 
> I got a make error:
> 
> make: *** No rule to make target 'bzImage'. Stop.
> 
> DO I need to modify Makefile? Is it in /usr/src/linux/arch/i386/boot directory?

The makefile that does the work is in there but you shouldn't need to change it
at all.

V.odd.

Patrick

[Linux-decnet-user] Swansea University Computer Society FTP Archive (DECnet)

[Steve W. <st...@gw...>]

Hi,

The FTP archive hosted on the Swansea University Computer Society's 
machine (ftp.sucs.swan.ac.uk) will be out of action for the next few
days. The admin are using the summer break as an oppertunity to upgrade
the software on the server. During the upgrade the DECnet archive was
deleted, since they didn't take a backup, I'll have to recreate the
archive from my patch collection here unless some else was mirroring
site and is willing to send me a copy?

I do not have all the historic information, only the more recent patch
versions, so some of the old obsolete patches will have been lost
forever, but everything thats actually useful, I have copies of here.

Please bear with us for a few days whilst this is sorted out,

Thanks,

Steve.

RE: [Linux-decnet-user] Applying Kernel patch

[Akihiko T. <TAN...@sp...>]

I tried the following commands to make bzImaze:

cd /usr/src/linux
make dep; make clean
make bzImage

I got a make error:

make: *** No rule to make target 'bzImage'. Stop.

DO I need to modify Makefile? Is it in /usr/src/linux/arch/i386/boot directory?

Akihiko 
>-----Original Message-----
>From: Akihiko Tanaka [mailto:TAN...@sp...]
>Sent: Tuesday, 15 August 2000 9:04
>To: Patrick Caulfield
>Cc: lin...@li...; ak...@co...
>Subject: Re: [Linux-decnet-user] Applying Kernel patch
>
>
>I modified proc_fs.h and executed "make zImage" as shown in the kernel
>installation guide. It complied and linked. However, the following errors
>were displayed:
>
>Root device is (3,8)
>Boot sector 512 bytes.
>Setup is 3440 bytes.
>System is 619kB
>System is too big. Try using bzImage or modules.
>make[1]:***[zImage] Error 1
>make[1]:Leaving directory 'usr/src/linux-2.2.14/arch/i386/boot'
>make:***[zImage]Error 2
>
>Do I need to fix these errors? It looks zImage is created.
>
>Akihiko
>---------- Original Message ----------------------------------
>From: Patrick Caulfield <pa...@pa...>
>Date: Fri, 11 Aug 2000 08:27:54 +0100
>
>>On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
>>> I downloaded the latest patch for DECNET and tried to install on my Red
>Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the
>Kernel Patch Installation Guide on the web. When I did
>>> 
>>> patch -p1 <decnet-2_2_16.diff
>>> 
>>> I got an error and created proc_fs.h.rej file. It seems that patch tried
>to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
>>> 
>>> I went ahead to execute make zImage. But because PROC_NET_DECNET is not
>defined in proc_fs.h, I had a compile error from af_decnet.c.
>>> 
>>> How can I correct a patch error? Do I need to start from patch and the
>follow the instruction again? 'Make config' asked a lot of questions. It
>looks like defining a lot of Environment Variables. Can I skip this and use
>the previously defined values?
>>
>>
>>That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
>>either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:
>>
>>Look for PROC_NET_LAST and add the following line just before it:
>>
>>PROC_NET_DECNET,
>>
>>Don't forget the trailing comma or it won't compile.
>>
>><whinge mode>
>>Considering 2.2.x is supposed to be a stable kernel I find it a little
>galling
>>that new /proc/net entries seem to turn up in almost every new release :-(
>></whinge mode>
>>
>>Just to confirm that, the file should look a little like this in that area:
>>
>>
>>        PROC_NET_BRIDGE,
>>        PROC_NET_DECNET,
>>        PROC_NET_LAST
>>};
>>
>>enum scsi_directory_inos {
>>        PROC_SCSI_SCSI = 256,
>>        PROC_SCSI_ADVANSYS,
>>
>>
>>Patrick
>>
>>_______________________________________________
>>Linux-decnet-user mailing list
>>Lin...@li...
>>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>>
>
>_______________________________________________
>Linux-decnet-user mailing list
>Lin...@li...
>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>
>EOM 
>
>NOTICE - This message contains information intended only for the use of the
>addressee named above.  It may also be confidential and/or privileged.  If
>you are not the intended recipient of this message you are hereby notified
>that you must not disseminate, copy or take any action in reliance on it.
>If you have received this message in error please notify pos...@bh....
>
>
>_______________________________________________
>Linux-decnet-user mailing list
>Lin...@li...
>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>

Re: [Linux-decnet-user] Applying Kernel patch

[ecc <ec...@cy...>]

Akihiko,

Use make bzImage instead of make zImage, kernels are too big for zImage.

good luck,

Ed Calderon



Akihiko Tanaka wrote:

> I modified proc_fs.h and executed "make zImage" as shown in the kernel installation guide. It complied and linked. However, the following errors were displayed:
>
> Root device is (3,8)
> Boot sector 512 bytes.
> Setup is 3440 bytes.
> System is 619kB
> System is too big. Try using bzImage or modules.
> make[1]:***[zImage] Error 1
> make[1]:Leaving directory 'usr/src/linux-2.2.14/arch/i386/boot'
> make:***[zImage]Error 2
>
> Do I need to fix these errors? It looks zImage is created.
>
> Akihiko
> ---------- Original Message ----------------------------------
> From: Patrick Caulfield <pa...@pa...>
> Date: Fri, 11 Aug 2000 08:27:54 +0100
>
> >On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
> >> I downloaded the latest patch for DECNET and tried to install on my Red Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the Kernel Patch Installation Guide on the web. When I did
> >>
> >> patch -p1 <decnet-2_2_16.diff
> >>
> >> I got an error and created proc_fs.h.rej file. It seems that patch tried to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
> >>
> >> I went ahead to execute make zImage. But because PROC_NET_DECNET is not defined in proc_fs.h, I had a compile error from af_decnet.c.
> >>
> >> How can I correct a patch error? Do I need to start from patch and the follow the instruction again? 'Make config' asked a lot of questions. It looks like defining a lot of Environment Variables. Can I skip this and use the previously defined values?
> >
> >
> >That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
> >either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:
> >
> >Look for PROC_NET_LAST and add the following line just before it:
> >
> >PROC_NET_DECNET,
> >
> >Don't forget the trailing comma or it won't compile.
> >
> ><whinge mode>
> >Considering 2.2.x is supposed to be a stable kernel I find it a little galling
> >that new /proc/net entries seem to turn up in almost every new release :-(
> ></whinge mode>
> >
> >Just to confirm that, the file should look a little like this in that area:
> >
> >
> >        PROC_NET_BRIDGE,
> >        PROC_NET_DECNET,
> >        PROC_NET_LAST
> >};
> >
> >enum scsi_directory_inos {
> >        PROC_SCSI_SCSI = 256,
> >        PROC_SCSI_ADVANSYS,
> >
> >
> >Patrick
> >
> >_______________________________________________
> >Linux-decnet-user mailing list
> >Lin...@li...
> >http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
> >
>
> _______________________________________________
> Linux-decnet-user mailing list
> Lin...@li...
> http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user

RE: [Linux-decnet-user] Applying Kernel patch

[Crowe, G. G. <Cro...@bh...>]

Your kernel image is too large, try a "make bzImage" instead of "make
zImage" as you will get better compression and thus a smaller kernel.

-----Original Message-----
From: Akihiko Tanaka [mailto:TAN...@sp...]
Sent: Tuesday, 15 August 2000 9:04
To: Patrick Caulfield
Cc: lin...@li...; ak...@co...
Subject: Re: [Linux-decnet-user] Applying Kernel patch


I modified proc_fs.h and executed "make zImage" as shown in the kernel
installation guide. It complied and linked. However, the following errors
were displayed:

Root device is (3,8)
Boot sector 512 bytes.
Setup is 3440 bytes.
System is 619kB
System is too big. Try using bzImage or modules.
make[1]:***[zImage] Error 1
make[1]:Leaving directory 'usr/src/linux-2.2.14/arch/i386/boot'
make:***[zImage]Error 2

Do I need to fix these errors? It looks zImage is created.

Akihiko
---------- Original Message ----------------------------------
From: Patrick Caulfield <pa...@pa...>
Date: Fri, 11 Aug 2000 08:27:54 +0100

>On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
>> I downloaded the latest patch for DECNET and tried to install on my Red
Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the
Kernel Patch Installation Guide on the web. When I did
>> 
>> patch -p1 <decnet-2_2_16.diff
>> 
>> I got an error and created proc_fs.h.rej file. It seems that patch tried
to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
>> 
>> I went ahead to execute make zImage. But because PROC_NET_DECNET is not
defined in proc_fs.h, I had a compile error from af_decnet.c.
>> 
>> How can I correct a patch error? Do I need to start from patch and the
follow the instruction again? 'Make config' asked a lot of questions. It
looks like defining a lot of Environment Variables. Can I skip this and use
the previously defined values?
>
>
>That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
>either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:
>
>Look for PROC_NET_LAST and add the following line just before it:
>
>PROC_NET_DECNET,
>
>Don't forget the trailing comma or it won't compile.
>
><whinge mode>
>Considering 2.2.x is supposed to be a stable kernel I find it a little
galling
>that new /proc/net entries seem to turn up in almost every new release :-(
></whinge mode>
>
>Just to confirm that, the file should look a little like this in that area:
>
>
>        PROC_NET_BRIDGE,
>        PROC_NET_DECNET,
>        PROC_NET_LAST
>};
>
>enum scsi_directory_inos {
>        PROC_SCSI_SCSI = 256,
>        PROC_SCSI_ADVANSYS,
>
>
>Patrick
>
>_______________________________________________
>Linux-decnet-user mailing list
>Lin...@li...
>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>

_______________________________________________
Linux-decnet-user mailing list
Lin...@li...
http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user

EOM 

NOTICE - This message contains information intended only for the use of the
addressee named above.  It may also be confidential and/or privileged.  If
you are not the intended recipient of this message you are hereby notified
that you must not disseminate, copy or take any action in reliance on it.
If you have received this message in error please notify pos...@bh....

Re: [Linux-decnet-user] Applying Kernel patch

[Akihiko T. <TAN...@sp...>]

I modified proc_fs.h and executed "make zImage" as shown in the kernel installation guide. It complied and linked. However, the following errors were displayed:

Root device is (3,8)
Boot sector 512 bytes.
Setup is 3440 bytes.
System is 619kB
System is too big. Try using bzImage or modules.
make[1]:***[zImage] Error 1
make[1]:Leaving directory 'usr/src/linux-2.2.14/arch/i386/boot'
make:***[zImage]Error 2

Do I need to fix these errors? It looks zImage is created.

Akihiko
---------- Original Message ----------------------------------
From: Patrick Caulfield <pa...@pa...>
Date: Fri, 11 Aug 2000 08:27:54 +0100

>On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
>> I downloaded the latest patch for DECNET and tried to install on my Red Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the Kernel Patch Installation Guide on the web. When I did
>> 
>> patch -p1 <decnet-2_2_16.diff
>> 
>> I got an error and created proc_fs.h.rej file. It seems that patch tried to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
>> 
>> I went ahead to execute make zImage. But because PROC_NET_DECNET is not defined in proc_fs.h, I had a compile error from af_decnet.c.
>> 
>> How can I correct a patch error? Do I need to start from patch and the follow the instruction again? 'Make config' asked a lot of questions. It looks like defining a lot of Environment Variables. Can I skip this and use the previously defined values?
>
>
>That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
>either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:
>
>Look for PROC_NET_LAST and add the following line just before it:
>
>PROC_NET_DECNET,
>
>Don't forget the trailing comma or it won't compile.
>
><whinge mode>
>Considering 2.2.x is supposed to be a stable kernel I find it a little galling
>that new /proc/net entries seem to turn up in almost every new release :-(
></whinge mode>
>
>Just to confirm that, the file should look a little like this in that area:
>
>
>        PROC_NET_BRIDGE,
>        PROC_NET_DECNET,
>        PROC_NET_LAST
>};
>
>enum scsi_directory_inos {
>        PROC_SCSI_SCSI = 256,
>        PROC_SCSI_ADVANSYS,
>
>
>Patrick
>
>_______________________________________________
>Linux-decnet-user mailing list
>Lin...@li...
>http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
>

[Linux-decnet-user] LATD 0.9 released

[Patrick C. <pa...@pa...>]

I've released latd 0.9. This is a bugfix release. Mainly for users having two 
or more reverse-LAT connections to the same terminal server

Here's the NEWS extract:

- latcp now shows local ports too
- Send group numbers with queued connect request
- Increased maximum number of connections to 254
- Fixed confusion when you had a reverse LAT session to the
  same terminal server and referred to them by port names.
- Fixed disappearing ports when using two queued reverse LAT
  connections to the same terminal server

Get it from: http://download.sourceforge.net/linux-decnet/latd-0.9.tar.gz

The next release will be 1.0 (I hope) and binaries will be made available.

patrick

Re: [Linux-decnet-user] Applying Kernel patch

[Patrick C. <pa...@pa...>]

On Thu, Aug 10, 2000 at 08:54:21PM -0400, Akihiko Tanaka wrote:
> I downloaded the latest patch for DECNET and tried to install on my Red Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the Kernel Patch Installation Guide on the web. When I did
> 
> patch -p1 <decnet-2_2_16.diff
> 
> I got an error and created proc_fs.h.rej file. It seems that patch tried to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.
> 
> I went ahead to execute make zImage. But because PROC_NET_DECNET is not defined in proc_fs.h, I had a compile error from af_decnet.c.
> 
> How can I correct a patch error? Do I need to start from patch and the follow the instruction again? 'Make config' asked a lot of questions. It looks like defining a lot of Environment Variables. Can I skip this and use the previously defined values?


That's normal for applying the 2.2.16 patch to a 2.2.14 kernel. You should
either upgrade to 2.2.16 or edit the include/proc_fs.h file as follows:

Look for PROC_NET_LAST and add the following line just before it:

PROC_NET_DECNET,

Don't forget the trailing comma or it won't compile.

<whinge mode>
Considering 2.2.x is supposed to be a stable kernel I find it a little galling
that new /proc/net entries seem to turn up in almost every new release :-(
</whinge mode>

Just to confirm that, the file should look a little like this in that area:


        PROC_NET_BRIDGE,
        PROC_NET_DECNET,
        PROC_NET_LAST
};

enum scsi_directory_inos {
        PROC_SCSI_SCSI = 256,
        PROC_SCSI_ADVANSYS,


Patrick

[Linux-decnet-user] Applying Kernel patch

[Akihiko T. <TAN...@sp...>]

I downloaded the latest patch for DECNET and tried to install on my Red Hat 6.2 Kernel 2.2.14-50 i586 machine for the first time. I follwed the Kernel Patch Installation Guide on the web. When I did

patch -p1 <decnet-2_2_16.diff

I got an error and created proc_fs.h.rej file. It seems that patch tried to add PROC_NET_PNP and PROC_NET_DECNET to proc_fs.h file.

I went ahead to execute make zImage. But because PROC_NET_DECNET is not defined in proc_fs.h, I had a compile error from af_decnet.c.

How can I correct a patch error? Do I need to start from patch and the follow the instruction again? 'Make config' asked a lot of questions. It looks like defining a lot of Environment Variables. Can I skip this and use the previously defined values?

Thank you for your help,

Akihiko

Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[ecc <ec...@cy...>]

Hello,

I have my 2.4.0-???(caldera preview) up and running decnet in modular form.
(first time).

I had  "lo" only in my /proc/net/decnet_device

I realized the module needed loading, at which point was too late, since the
entire boot was completed.

I added "decnet" to my /etc/modules.default and rebooted, tested dnping
successfully.

Ed Calderon
(RSX11M)


Raimund Huemmer wrote:

> Hi,
>
> wonderfull, it seems to work :-)
>
> Now I tried "decnet=1,177" at lilo prompt.
>
> At Boot-time the script /etc/init.d/dnprogs seems to start (with my
> modified line about echo eth0).
>
> After logging in I tried "sethost vax" but again: "no route to host".
>
> And now it comes:
>
> I said:
> $ /etc/init.d/dnprogs stop
> $ /etc/init.d/dnprogs start
>
> $ sethost vax
> Connecting to vax
> (no error message, OK, I have no VAX at home, but it tried here really to
> connect. tomorrow in the office I will see).
>
> The funny thing is, in the past I have always tried
> "/etc/init.d/dnprogs restart" but nothing happens. Only to stop DECnet
> an start it again, is the solution.
>
> Thank you very much & nice weekend.
>
> Raimund
>
> --
> Life's too short to read boring signatures
>
> _______________________________________________
> Linux-decnet-user mailing list
> Lin...@li...
> http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user

Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Raimund H. <ra...@ba...>]

Hi,

wonderfull, it seems to work :-)

Now I tried "decnet=1,177" at lilo prompt.

At Boot-time the script /etc/init.d/dnprogs seems to start (with my
modified line about echo eth0).

After logging in I tried "sethost vax" but again: "no route to host".

And now it comes:

I said: 
$ /etc/init.d/dnprogs stop
$ /etc/init.d/dnprogs start

$ sethost vax
Connecting to vax
(no error message, OK, I have no VAX at home, but it tried here really to 
connect. tomorrow in the office I will see).

The funny thing is, in the past I have always tried
"/etc/init.d/dnprogs restart" but nothing happens. Only to stop DECnet
an start it again, is the solution.

Thank you very much & nice weekend.

Raimund

-- 
Life's too short to read boring signatures

Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Steve W. <st...@gw...>]

Hi,

> 
> Thanks Steve and Ed,
> 
> Now I know more about the single steps, but I'm afraid of not
> understanding the whole thing :-) 
> 
> 
> On Tue, Aug 08, 2000 at 08:52:31PM +0100, Steve Whitehouse wrote:
> > 
> > with the 2.4.0 versions of DECnet you don't want to use the startnet
> > script. You can set the files in /proc/sys/net/decnet/ using
> > the echo command from the command line. The recommended way of
> > setting the DECnet address is at boot on the LILO command line
> > or at module load time (depending upon which method you use).
> 
> OK, I have also read about this in Documentation, but I was not shure
> about the right time in the boot init. Now I modified the script
> /etc/init.d/dnprogs (which comes with Debian package dnprogs). I
> deleted the line with "startnet" and added two lines with the
> echo command:
> echo -n "1.177" > /proc/sys/net/decnet/node_address

The alternative to the above command is to set the decnet address on
the boot command line using decnet=1,177 for example. You need to
get both the DECnet address of the node, and the MAC address of the
ethernet card set before the boot scripts which configure your ethernet
card for TCP/IP run. This is the reason that I suggest setting the DECnet
address on the command line, since its before any scripts will have had
a chance to run :-)

> echo -n "eth0" > /proc/sys/net/decnet/default_device
> 
> Now a "cat /proc/net/decnet_device show me the loopback and the
> eth0 device. In the other place (/proc/sys/net/...) I can see the 
> node address (1.177) but the node name is not there (only shown:???). 
> 
The nodename file is there for convenience only really. It is not actually
used by anything at the moment. You can ignore it for all practical purposes,
or use echo to set it to the node name of your machine.

> When I try "sethost vax" ("vax" is node 1.1) then appears:
> "no route to host".
> 
Ok. This is simply because eth0 is not available. If you check the
default_device file, you'll find that it does not set unless eth0 is
available (i.e. listed in /proc/net/decnet_dev) as it should be.

> > It is not recommended to load the module more than once (i.e. once
> > loaded, don't unload it) as it will very likely cause a memory leak
> > if you do.
> 
> I use DECnet support in 2.4.0 not as module.
> 
> In 2.2.14 I use Eduardos patch. I set the MAC address AA:00:04:00:B1:04
> in the network scripts, when pcmcia is coming up and ifconfig -a shows
> me also this hardware address.
> 
The same procedure is fine for setting the MAC address in 2.4.0. I
suspect that the problem is the late setting of the DECnet node address.

> Sorry for my stupid questions, but I'm a little bit confused of the
> changes to 2.4.0. Is /etc/decnet.conf still valid or is it now obsolete?
> Where to I set the other node (1.1) I want to contact to?
> 
> Thanks,
> Raimund
> 
decnet.conf is still used. It is the file that the library queries to
find hostname/number translations. It does not change its function
according to the kernel version, but only changes in the library (so far
as I know, none to date). It seems to me that the DECnet address of the
host you are trying to connect to is found, otherwise it would not get
far enough to issue the "No route to host" message. You are very close to
having a working system,

Steve.

Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Raimund H. <ra...@ba...>]

Thanks Steve and Ed,

Now I know more about the single steps, but I'm afraid of not
understanding the whole thing :-) 


On Tue, Aug 08, 2000 at 08:52:31PM +0100, Steve Whitehouse wrote:
> 
> with the 2.4.0 versions of DECnet you don't want to use the startnet
> script. You can set the files in /proc/sys/net/decnet/ using
> the echo command from the command line. The recommended way of
> setting the DECnet address is at boot on the LILO command line
> or at module load time (depending upon which method you use).

OK, I have also read about this in Documentation, but I was not shure
about the right time in the boot init. Now I modified the script
/etc/init.d/dnprogs (which comes with Debian package dnprogs). I
deleted the line with "startnet" and added two lines with the
echo command:
echo -n "1.177" > /proc/sys/net/decnet/node_address
echo -n "eth0" > /proc/sys/net/decnet/default_device

Now a "cat /proc/net/decnet_device show me the loopback and the
eth0 device. In the other place (/proc/sys/net/...) I can see the 
node address (1.177) but the node name is not there (only shown:???). 

When I try "sethost vax" ("vax" is node 1.1) then appears:
"no route to host".

> It is not recommended to load the module more than once (i.e. once
> loaded, don't unload it) as it will very likely cause a memory leak
> if you do.

I use DECnet support in 2.4.0 not as module.

In 2.2.14 I use Eduardos patch. I set the MAC address AA:00:04:00:B1:04
in the network scripts, when pcmcia is coming up and ifconfig -a shows
me also this hardware address.

Sorry for my stupid questions, but I'm a little bit confused of the
changes to 2.4.0. Is /etc/decnet.conf still valid or is it now obsolete?
Where to I set the other node (1.1) I want to contact to?

Thanks,
Raimund

Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Steve W. <st...@gw...>]

Hi,

with the 2.4.0 versions of DECnet you don't want to use the startnet
script. You can set the files in /proc/sys/net/decnet/ using
the echo command from the command line. The recommended way of
setting the DECnet address is at boot on the LILO command line
or at module load time (depending upon which method you use).

It is not recommended to load the module more than once (i.e. once
loaded, don't unload it) as it will very likely cause a memory leak
if you do.

You'll also need to set the MAC address of your ethernet card, something
which was optional with the 2.2 kernel patch (I assume that you are
using Eduardo's 2.2 patch here, my 2.2 patches are more or less obsolete
these days).

You don't say if the loopback device appears in /proc/net/decnet_dev
It should appear here if all is well to allow communication within
the node.

There are further instructions in the Documentation/networking/decnet.txt
file with the 2.4.0 kernel source. Please feel free to ask further if this
doesn't solve your problem,

Steve.

> 
> Hi,
> 
> I'm a newuser to linux-decnet. 
> 
> I connect with my Linux Notebook (Debian & Kernel 2.2.14) to
> a MicroVAX 3100-90. With the DECnet Kernelpatch for 2.2.14
> I have no problems. Sethost, dndir, dncopy, and also the
> X-Server works very fine.
> 
> Now I have tried to test the DECnet support in Kernel 2.4.0-test5.
> The command "startnet" always gives the message:
> "ioctl: invalid argument" and at /proc/net/decnet_device there is
> no eth0 working.
> 
> Any hints?
> 
> Thanks,
> Raimund
> 
>  
> 
> _______________________________________________
> Linux-decnet-user mailing list
> Lin...@li...
> http://lists.sourceforge.net/mailman/listinfo/linux-decnet-user
> 

[Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Raimund H. <ra...@ba...>]

Hi,

I'm a newuser to linux-decnet. 

I connect with my Linux Notebook (Debian & Kernel 2.2.14) to
a MicroVAX 3100-90. With the DECnet Kernelpatch for 2.2.14
I have no problems. Sethost, dndir, dncopy, and also the
X-Server works very fine.

Now I have tried to test the DECnet support in Kernel 2.4.0-test5.
The command "startnet" always gives the message:
"ioctl: invalid argument" and at /proc/net/decnet_device there is
no eth0 working.

Any hints?

Thanks,
Raimund