Hello from Gregg C Levine normally with Jedi Knight Computers I can't comment on the discussions that have been zapping around here, like a pair of starfighters in a dogfight. But I can tell you Mark, a little bit about that kernel. That is if you have not deduced it already. For one thing, the initials "ac" in the version come from our own, Alan Cox. The number 10 signifies the patch level, up to the point with it ceases being 2.4.9, and evolves into 2.4.10. At least that's my interpretation of the numeration of the number 10. I suspect that even Alan Cox, will correct me. It actually depends on how the whole kernel numeration system evolved. But that is another story. I can tell you folks, that in the 2.2.18 version there is indeed S/390 support. Its my guess, that for version 2.2.16, the idea was suggested, and tossed in, and the folks at Marist made it real. As for the current discussion? I can not offer anything on it. Oh, and yes, I have downloaded patches from the kernel ftp repository, and upgraded a distributed kernel to the requested level. Pretty interesting process. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > Post, Mark K > Sent: Thursday, February 14, 2002 10:16 PM > To: [EMAIL PROTECTED] > Subject: Re: Buffersize on Linux CTC Driver > > William, > > I can tell you that the Red Hat 2.4.9-ac10 kernel that I'm running on one of > my systems does indeed have those directories and files under /proc. I > haven't had a chance to load the SuSE 2.4 stuff yet, perhaps I'll get to > that after SHARE. (I have to finish up my presentations or Neale will get > after me!) > > Mark Post > > -----Original Message----- > From: Scully, William [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 9:38 PM > To: [EMAIL PROTECTED] > Subject: Re: Buffersize on Linux CTC Driver > > > Mark, > > The quoted information is from an IBM manual which -specifically- identified > 2.2.16 as the kernel level. I am, however, running the 2.2.16 SuSE 7.0 GA > materials. Ross Patterson, who works down the aisle from me did a quick > search and he didn't think there was an update to the CTC driver related to > this. Perhaps someone else has seen something more specific? > > I have not yet worked with the SuSE 2.4 level code. Has someone seen > evidence that the file noted in the doc -does- exist at the 2.4 level? > > I confess I'm still confused by all this... . > > -----Original Message----- > From: Post, Mark K [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 3:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Buffersize on Linux CTC Driver > > > William, > > I believe that is only applicable to a system running the 2.4 kernel. Are > you running that, or a 2.2 kernel? > > Mark Post > > -----Original Message----- > From: Scully, William [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 2:27 PM > To: [EMAIL PROTECTED] > Subject: Buffersize on Linux CTC Driver > > > The IBM "Linux for S/390 Device Drivers and Installation Commands" document, > dated 18 July 2001, in Chapter Seven, "Linux for S/390 CTC/ESCON Device > Driver", has Usage Note 2 under "Preparing the Connection" which reads: > > Definitions on the remote side > > Set up the TCP/IP on the remote side, as described in the reference > manuals. > This will vary depending on which operating system is used on the remote > side. > > Note: It is important that you have IOBUFFERSIZE 32678 defined because > the > LINUX for S/390 CTC driver works with 32k internally. This is > configurable > for each device by writing the value to the buffersize file for that > device > (proc/net/ctc/<devicename>/buffersize ), for example > > echo 32768 >/proc/net/ctc/ctc0/buffersize > > I'm not sure how this is accomplished. Logging on as root and issuing the > command doesn't work. Here's what I get: > > LINUXWPS:/proc # echo 32768 >/proc/net/ctc/ctc0/buffersize > bash: /proc/net/ctc/ctc0/buffersize: No such file or directory > > What is the correct technique for creating the appropriate directories and > file? > > William P. Scully > Systems Programmer > Computer Associates International, Inc > [EMAIL PROTECTED]
