Re: [Linux-decnet-user] More RH7.1 / kernel 2.4 copying woes
Brought to you by:
chrissie_c,
ph3-der-loewe
|
From: Patrick C. <pa...@ty...> - 2001-03-27 16:07:18
|
On Tue, Mar 27, 2001 at 04:06:20PM +0100, Paul Sherwin wrote: > At 14:14 27/03/01 +0100, you wrote: > >On Tue, Mar 27, 2001 at 12:28:29PM +0000, Eduardo Serrat wrote: > >> I am afraid the problem is related to the MTU (Max Transfer Unit) that > >> Steve's Kernel implementation of DECnet uses. This was set to 230 Bytes > >> so I had to issue a patch for DAPFS to work with it (BLOCK I/O would fail > >> because it needs more that 230 bytes (????)). You can obtain it > downloading > >> the dapfs patch and applying it. > > > >It was changed in 2.4.1 to default to 1498 or whatever the remote end > needs (if > >less than that). That's one of the reasons I made a new 2.4.2 dapfs patch :-) > > I'm getting confused here. Does this mean I need to apply a patch the > standard 2.4.2 kernel and that will fix my problem, or is there a real > problem with 2.4.2 which is as yet unfixed? Sorry, that was as typo as well as badly phrased. The MTU was fixed in 2.4.1 and 2.4.2 has the same DECnet code in as 2.4.1, so there should be no MTU problems in the kernel you have. I made a new DAPFS patch for 2.4.1 because Eduardo's original 2.4.0 dapfs patch included the MTU fix. That was probably an irrelevant piece of information there. patrick |