Subject: Linux-Development Digest #559 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Thu, 17 Mar 94 06:13:04 EST Linux-Development Digest #559, Volume #1 Thu, 17 Mar 94 06:13:04 EST Contents: kernel problem in 1.0 (matthew 'beautiful hair' mead) Specialix Driver round 3 (Alan Drew) InterViews sources for Linux? (Hans Vermeulen) Re: Andrew 6.1 for Linux: who did it? (Robert Andrew Ryan) rarpd done? berkeley packet filter? (Paul Fox) Re: Real-Time Linux and a/d device drivers (Zbigniew Wieckowski) Re: Linux 1.0 problems (No free VT) (Chris Royle) Re: Amiga File System, once again (Sami-Pekka Hallikas) struct icmp definition? (which icmp.h) (G. "Wolfe" Woodbury) Re: telnet uid length <=8?? (Kevin Brown) Synchronous X25 link & network level software (Peter Tam) My first kernel dump with 1.0 :( (FEARNLCJ@DUVM.OCS.DREXEL.EDU) Re: 127.x.x.x (was Re: UDP report card) (Vernon Schryver) Re: telnet uid length <=8?? (Peter Dalgaard SFE) Re: Real-Time Linux and a/d device drivers (Scott McClung) Re: 127.x.x.x (was Re: UDP report card) (Warner Losh) ---------------------------------------------------------------------------- From: mmead@csugrad.cs.vt.edu (matthew 'beautiful hair' mead) Subject: kernel problem in 1.0 Date: 16 Mar 1994 00:56:17 -0500 I'm using the netstat from net 0.32, and I've experienced this with a program that tried to select() a file descriptor that should have been treated as a connection refused, but didn't for some reason. Here's what I get dumped by the kernel upon the segmentation fault the program(s) receive: Mar 16 00:50:31 slapshot vmunix: Unable to handle kernel NULL pointer dereference at address 00000004 Mar 16 00:50:31 slapshot vmunix: Oops: 0000 Mar 16 00:50:31 slapshot vmunix: EIP: 0010:0012cc1b Mar 16 00:50:31 slapshot vmunix: EFLAGS: 00010202 Mar 16 00:50:31 slapshot vmunix: eax: 00000000 ebx: 00e35601 ecx: 00e35600 edx: 0012cba7 Mar 16 00:50:31 slapshot vmunix: esi: 00001be8 edi: 00198754 ebp: 0000002f esp: 00957f68 Mar 16 00:50:31 slapshot vmunix: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 Mar 16 00:50:31 slapshot vmunix: Pid: 6596, process nr: 18 (netstat) Mar 16 00:50:31 slapshot vmunix: Stack: 00e35000 00000400 0000a800 008b1a80 00198762 Mar 16 00:50:31 slapshot vmunix: Code: 8b 48 04 51 0f bf 10 52 8b 40 08 50 8b 8e 74 6b 19 00 51 8b I've seen this in pl15, but I thought someone had mentioned it. Hope someone can figure it out. -matt -- -- Matthew C. Mead -- | "I can't hardly find someone out of the mmead@slapshot.async.vt.edu | entire human race who is wise 24 hours a day." mmead@csugrad.cs.vt.edu |----------------------| - some Renaissance dude http://slapshot.async.vt.edu/~mmead |------------------------- ------------------------------ Date: 16 Mar 94 12:06:42 GMT Subject: Specialix Driver round 3 From: cdh@specialix.co.uk (Alan Drew) Well my last post certainly seems to have stirred up a hornets nest. Most suprising though is the number of people who have come forward and offered to do the work. Some of you saw the original offer some of you didn't. So.... Here's the position..... We currently have one gentleman working on the driver. I fully intend to leave him to get on with it (he was projecting end of march) and see what comes up. If nothing happens (which is a possibility as there has been radio silence from him since he was sent the Tech Ref), then I will sit down with our technical director in a few months time and review the whole situation all over again. In the meantime, I have tried to reply to all those who e-mailed me though I may heve missed a few (please forgive me if such is the case). I will keep all your names on file, though I am more likely to come back here again with an open offer and await your reply. A usefull exercise for any interested parties which would give me some usfull amunition with the powers that be, here. Is for one of you guys to do some *real* market research and try and find out just how many people *really* want this type of driver and how many ports they want to use it with. ---- Further information, if anybody is interested, we have a product called IO8+, this is *NOT* an intelligent IO controller, but it does provide you with 8 RS232 RJ12 socket devices backed up by a very good Cirrus UART. All you need to write a driver for this is the Cirrus Logic Chip reference manual for the CD1864 and the IO addresses (set on the card). You can have multiple host cards in your system. This may be a better solution for those of you who want 8-16 ports + 2 COM: ports. The driver would not be hugely different from that of a 16550 driver. One thing is though, you woldn't have the performance to run 8 SLIP lines at 115.2K BAud :) ---- As usual feel free to contact me with any questions or comments Regards Alan Drew ------------------------------ From: vermeule@wi.leidenuniv.nl (Hans Vermeulen) Crossposted-To: comp.os.linux.admin,comp.os.linux.help Subject: InterViews sources for Linux? Date: 16 Mar 1994 15:43:32 GMT Reply-To: vermeule@wi.leidenuniv.nl Hello, Where can I get the IV 3.1 sources for Linux? I like to have the sources of the complete distribution, including the libs and the examples (like idraw, ibuild and iclass). I am running Slackware 1.1.2, which includes the IV 3.1 libs and includes (but no sources). So, does anybody know where I can get these? Or who did port the IV 3.1 distribution to Linux? Maybe he/she can upload the sources to sunsite.unc.edu .. Thanks in advance, ---Hans. #------------------------------------------------------------------------------# Hans Vermeulen, Scientific Programmer Dept. of Computer Science, Leiden University, The Netherlands P.O. Box 9512, 2300 RA Leiden, The Netherlands Fax: +31 71 276985, Voice: +31 71 277106 e-mail: Hans.Vermeulen@wi.LeidenUniv.nl #------------------------------------------------------------------------------# ------------------------------ From: Robert Andrew Ryan Subject: Re: Andrew 6.1 for Linux: who did it? Date: Wed, 16 Mar 1994 12:10:36 -0500 Excerpts from netnews.comp.os.linux.development: 15-Mar-94 Andrew 6.1 for Linux: who d.. Marko Schuetz@hisplace.r (605) > Most of all it seems incomplete. For example the .overview files are > missing, templates are missing and much much more. All those things are in the andrew61prog.tar.gz file. We hope that soon after AUIS 6.3 is released on the X11R6 tape there will be a properly segmented binary release available elsewhere. (Most likely replacing 6.1 on sunsite at least.) The 6.1 release wasn't prepared by us, probably the 6.3 binary release will not be either. (Though we will offer guidance to someone we know who plans to do it.) -Rob Ryan Andrew Consortium ------------------------------ From: pgf@cayman.com (Paul Fox) Subject: rarpd done? berkeley packet filter? Date: 16 Mar 1994 18:22:16 GMT hi -- i want to use my linux box to boot a diskless Sun to run as an Xterminal (using the XKernel) to talk to the linux box. (with me so far?) to do this, i need a RARP server, since Sun's don't do bootp. to port the netbsd RARPD, i need the berkeley packet filter (bpf). has anyone put a rarpd on linux? has anyone put the Berkeley Packet Filter on linux? is there are raw network access point (i.e. /dev/nit) on linux? should i just hack the single entry i need into the arp code in my kernel, to get me running well enough to finish doing the job right, so i can contribute the changes back to posterity? (don't answer that...) (as a secondary question, has bootparamd been ported to linux?) -- ===================== paul fox, pgf@cayman.com (cayman systems inc. in heavenly woburn, ma) home: pgf@foxharp.boston.ma.us (arlington, ma) ------------------------------ From: wieckows@centi.cs.umn.edu (Zbigniew Wieckowski) Subject: Re: Real-Time Linux and a/d device drivers Date: Tue, 15 Mar 1994 20:52:51 GMT In article <1994Mar14.011322.5474@hydra.acs.ttu.edu> dboney@cs.ttu.edu writes: > >-- >Hi, > Are there any realtime extentions for Linux? Does any have a UN*X device driver >for a National Instruments AT-MIO-16 a/d board. Any type of unix would be OK. It would >give me a place to start. > >Sincerely, > >David G. Boney > >American Heart Association Medical Student Research Fellow >Texas Tech School of Medicine > >dboney@cs.ttu.edu Texas Tech University >Ph. 806-742-1191 Department of Computer Science > Lubbock, Tx. 79409 USA Solaris 2.2 has a Real Time Scheduler. Would be nice to have that in Linux. Developers of multicast were praising that feature. ============================================================================= Zbigniew Wieckowski, Department of Computer Science, University of Minnesota, 200 Union St. SE, MN 55455, U.S.A., (612)626-7510, e-mail:wieckows@cs.umn.edu ============================================================================= What is mind? No matter. What is matter? Never mind. ============================================================================= ------------------------------ Crossposted-To: comp.os.linux.help From: c@royle.org (Chris Royle) Subject: Re: Linux 1.0 problems (No free VT) Date: Wed, 16 Mar 1994 15:10:33 GMT Gene Choi (genie@sting.Berkeley.EDU) wrote: > So after I heard about the announcement of Linux 1.0, I grabbed > the source and recompiled. To my dismay, I am no longer able to > run Xfree any more. Using pl15 and pl15c(or something near c), > I had 0 problems with X. I changed 0 things in my setup from > my move from pl15 to 1.0. Anyway I tried forcing X to start > via startx and xdm (as root of course). 0 luck so far. > Under startx, Xfree complains about having no free VT. > Has something changed with setting VT's? > I am using the Xfree Mach32 drivers. > -Gene Did your pl15 setup have more than the usual 8 VTs compiled in like mine does (I use 12) ? This would account for it if you didn't change the value of NR_CONSOLES in /usr/include/linux/tty.h when you installed 1.0 Chris. -- Chris Royle "Come rest your head on these two" G&CC Undergraduate (Author: E. Hamlin) 0223 335436 car1002@cus.cam.ac.uk / c@royle.org (Internet) 0850 668151 car1002@uk.ac.cam.cus (JANET) ------------------------------ From: semi@dream.nullnet.fi (Sami-Pekka Hallikas) Subject: Re: Amiga File System, once again Date: Wed, 16 Mar 1994 01:32:40 GMT Alan Braggins (armb@setanta.demon.co.uk) wrote: > character case-insensitive filenames. So. if such a filesystem could > be written, it would have (limited) uses. I'm not so sure about that. Many people like collect all special file-systems and all other special things in their kernel. Even I have ISO filesystem in my kernel, and I don't even have CD-Rom. Anyway, sometimes you can get sofware on other format floppies then msdos, and I'm ready then. (I think, and I hope). -- +--------------------------+----------+-------------------------------------+ | semi@dream.nullnet.fi | OH1KYL | MAIL MEDIA. Do Not Expose to Flame! | | samip@freeport.uwasa.fi +----------+-------------------------------------| | semi@freenet.hut.fi | Dream World BBS * 358-21-4389843 * 24H * 9600 | +--------------------------+------------------------------------------------+ ------------------------------ From: ggw@acpub.duke.edu (G. "Wolfe" Woodbury) Subject: struct icmp definition? (which icmp.h) Date: Wed, 16 Mar 1994 03:24:30 -0500 I ftp'd the net-2 sources from tsx-11 and have been playing with them some. Nslookup works fine when it is forced to use the -I option when flexing command.l. However, I cannot get ping to compile. It complains about a missing include file "netinet/ip_vars.h" and then cannot find definitions for the structure "icmp". Prowling in some other available sources, it does seem that the file is, indeed, missing the definition of the "struct icmp", and I can't find anyplace in the Linux source trees that I can scan where "icmp_type" ( a member of struct icmp ) is defined. Comments? Pointers, FAQ's to read? (quick scan of NET-2 HowTo doesn't seem to answer the question.) -- Gregory G. "Wolfe" Woodbury @, but not speaking for Duke Univ. System Admin Demographic Studies Box 90408 Durham NC 27708 ggw@cds.duke.edu ggw@acpub.duke.edu ggw@wolves.durham.nc.us "Myth is metaphor, and ritual is the enactment of myth." ------------------------------ From: kevin@frobozz.sccsi.com (Kevin Brown) Subject: Re: telnet uid length <=8?? Date: Tue, 15 Mar 1994 02:58:08 GMT In article <2lgrgh$buo@nic.ott.hookup.net> root@borg.ott.ca (Sys admin) writes: >Only people with user id's of 8 chars or less can use my >telnet port. they can log onto my linux system through the >serial port, but not over the internet through telnet. >(or even locally for that matter.. if they have 9 char or > >userids!!!!) >Anyone to confirm this?? Thanks. Can't confirm it as I don't have telnetd running on my system (the only reason I have TCP configured in my kernel is so I can use X and XTrek). However, this problem sounds like a problem in whatever version of /bin/login telnetd is running. If your version of telnetd gets the username itself (which would be a silly thing to do if /bin/login is available), then it is a bug in telnetd. I did confirm on my system that /bin/login gives the behavior that you describe, while getty does not. Since telnetd isn't likely to run getty, you'll see whatever bugs exist in /bin/login. Try running /bin/login from your shell directly to verify if this is the case. -- Kevin Brown kevin@frobozz.sccsi.com This is your .signature virus: < begin 644 .signature (9V]T8VAA(0K0z end > This is your .signature virus on drugs: <> Any questions? ------------------------------ From: pct@lyra.STANFORD.EDU (Peter Tam) Crossposted-To: comp.os.linux.misc Subject: Synchronous X25 link & network level software Date: Thu, 17 Mar 1994 02:29:53 GMT Hi, Is there any sync card linux driver already available? I am looking for one with SCC chip! & Is there already link & network level x25 software ported to x25, for PrivateVirtualCircuits & SwitchedVirtualCircuits? THANKS FOR ANY HELP! ------------------------------ From: FEARNLCJ@DUVM.OCS.DREXEL.EDU Subject: My first kernel dump with 1.0 :( Date: Thu, 17 Mar 1994 04:24:55 GMT I successfully compiled the pre-1.0 kernel and used it moderately harshly for a day before discovering that 1.0 had just been released. So I tried to build on one success with another. Unfortunately shortly after logging in under my fresh 1.0 kernel before I could even execute a command I was greeted by something like what's below. So I thought it was my fault (I was eating and not monitoring the the build), so I recompiled. This time the error didn't come immediately after displaying the login prompt but waited until I thought all was well. Then just as I began typing a command this came up: ===========================cut here======================================= darkstar:~$ Oops: 0000 EIP: 0010:0011d2ba EFLAGS: 00010206 eax: 00dc9000 ebx: 01000000 ecx: 01000000 edx: 0000002c esi: 00dc9114 edi: 00dc9000 ebp: 00dc8fbc esp: 00dc8f60 ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 Pid: 48, process nr: 15 (login) Stack: 0000002c 00dc9114 0011d392 01000000 0000002c Code: 66 83 7b 0a 00 75 13 68 8c d2 11 00 e8 89 40 ff ff 31 c0 83 Trying to free kernel page-directory: not good ===========================cut here====================================== Well, at least cut&paste with selection works. In fact most things work, but intermittently the kernel reminds me that all is not perfect with another similar dump. Following instructions in the kernel README file I typed: nm tools/zSystem | sort | less Searching through here I think these include the range of entries one of you kernel hackers will need to tell me what's going on. 0011d0b4 T _do_open 0011d214 T _sys_open 0011d274 T _sys_creat 0011d2b4 T _close_fp <== I think this is the right line? 0011d344 T _sys_close Well, I decided to see how stable 1.0 is. The above happened right after logging in both time. So I've been up for 1 hr. 34 min. and it hasn't happened again. I was even bold enough to run XWindows and play some chess. The problem hasn't recurred. Is it a problem? It sure looked disconcerting. Do Enjoy! Chris Fearnley cfearnl@pacs.pha.pa.us UNIX SIG leader at PACS (Philadelphia Area Computer Society) ------------------------------ Crossposted-To: comp.protocols.tcp-ip From: vjs@calcite.rhyolite.com (Vernon Schryver) Subject: Re: 127.x.x.x (was Re: UDP report card) Date: Wed, 16 Mar 1994 16:12:47 GMT In article <2m6g6r$ijk@gap.cco.caltech.edu> heathh@lust.ugcs.caltech.edu (Heath I Hunnicutt) writes: >longyear@netcom.com (Alfred Longyear) writes: > >>It seems to me that the address 127.x.x.x is not special. What is special >>is the loopback device. > >This assumption is wrong. 127 is specified in the RFCs as being a pseudo- >network that includes the loopback address. The fact that it is specified >in the RFCs as a special address pretty well contradicts your premise. > >>If you don't have a route for 127.x.x.x to the "lo" device, but have a default >>route to an ethernet controller, for example, then requests to 127.0.0.1 will >>go out the wire just as requests to any other IP address. Until a route is >>created to the loopback device, the address 127.x.x.x is an unknown address >>just as if _I_ asked for address 192.83.17.1. It would need ARP to resolve it >>to a real ethernet address and subsequently the request would go out the >>default route. > >The difference is that the IP layer can make the correct decision not to put >anything to 127.* on any external interface. The idea that someone should >need to configure their system to not violate the RFCs is ridiculous. There >is a large responsibility on the part of the stack to not allow stupid things >like sending 127.* out on the net. > >>I guess what I am saying is that the routing of frames is not a function >>solely of the device's IP address, nor is it a function soley of the device >>type. There is no magical "override" which says that "Oh, you have address >>127.0.0.1. I won't bother to look it up. I know that this is the loopback >>device and will simply put it there". > >You really should research these issues before posting. For starters, see >the Hosts Requirements RFC. There is indeed something "magical" about any >address on the 127 net. Whether you set your system up with 127.0.0.1 as a >loopback or not is your problem. No matter what, you should never send >packets to 127.anything out any interface, regardless of the routing table's >(mis)configuration. "You should really research these issues before posting" as well. The first guy is right. The H-R RFC's do not say how 127 should be made special, only that it should be. Standards, including RFC's, specify external behavior, not internal implementation. You need a pretty dim view of your customers' intelligence and good sense to put special checks against non-compliant configurations of net 127 in what is in most systems the performance critical path. (Route look-up is particularly important for the performance of un-connect(2)'ed UDP sockets). Unless the customer does something wierd to the system, the normal routing mechanisms do exactly the right things. There is no excuse to waste cycles checking for something that few sane customers would change, and that practically all insane customers are too ignorant to be able to break. If the customer overrides those mechanisms, and makes the system non-compliant with any or all RFC's, do you think the Network Police will come and break someone's knee-caps? Who is to say that the customer does not have good and sufficent reasons for using some network other than 127 for loopback? Vernon Schryver vjs@rhyolite.com ------------------------------ From: pd@kubism.ku.dk (Peter Dalgaard SFE) Subject: Re: telnet uid length <=8?? Date: Wed, 16 Mar 1994 15:03:37 GMT >In article <2lgrgh$buo@nic.ott.hookup.net> root@borg.ott.ca (Sys admin) writes: >>Only people with user id's of 8 chars or less can use my >>telnet port. they can log onto my linux system through the >>serial port, but not over the internet through telnet. >>(or even locally for that matter.. if they have 9 char or > >>userids!!!!) >>Anyone to confirm this?? Thanks. To those who may think that this is another sign of buggyness of Linux: SunOS has the reverse problem (in 4.1.1 at least) getty gags on > 8 characters, while telnetd accepts them. Encountered this when trying to set up an UUCP account. -- O_ ---- Peter Dalgaard c/ /' --- Statistical Research Unit ( ) \( ) -- University of Copenhagen ~~~~~~~~~~ - (pd@kubism.ku.dk) ------------------------------ From: mcclung@squire.chinalake.navy.mil (Scott McClung) Subject: Re: Real-Time Linux and a/d device drivers Date: Thu, 17 Mar 1994 01:21:36 GMT In article wieckows@centi.cs.umn.edu (Zbigniew Wieckowski) writes: >Solaris 2.2 has a Real Time Scheduler. Would be nice to have that in Linux. >Developers of multicast were praising that feature. OK, so, when do we get started? :-) Seriously, thought, how hard would a RT scheduling class be to implement? (Actually, I guess SVR4 has 3 classes: RT, system, and TS. What's the difference between 'system' and the other two?). How difficult would it be to write a bounded latency real time scheduler, like Solaris 2 has? There are probably a lot of problems that I haven't even considered, but I assume many parts of the kernel would need to be rewritten.(?) Would every I/O call need to be asynchronous for this to work? Have I gone off the deep end to even ask these questions? I doubt that many of us need a RTOS, but it would be neat anyway... -- /* Scott McClung Opinions expressed here are mine. * Computer Engineer, SAIC "What's this word in the stage directions? * mcclung@c3ot.saic.com E-mote?" - Crow, MST3K * mcclung@nawc690.chinalake.navy.mil */ ------------------------------ Crossposted-To: comp.protocols.tcp-ip From: imp@boulder.parcplace.com (Warner Losh) Subject: Re: 127.x.x.x (was Re: UDP report card) Date: Wed, 16 Mar 1994 21:01:20 GMT In article longyear@netcom.com (Alfred Longyear) writes: >It seems to me that the address 127.x.x.x is not special. What is special >is the loopback device. No. 127.* is a special network. It was born special. IP implementations should ***ALWAYS*** ignore everything they get from this address if it comes in over the wire and should ***NEVER*** send packets to this address out over the wire. And it should do this be default. Robust implementations should enforce this compeletely and leave no room for the user to configure this. 127.* ARP requests as well should never be on the wire, and completely ignored if they are seen by a host on the wire. ICMP messages should likewise be treated. To do otherwise is broken and will cause problems. Think about the network meltdown that would happen if everybody responded to an ARP for 127.*.... Yes, SunOS 4.x is broken, in that it doesn't do all these things. Warner -- Warner Losh imp@boulder.parcplace.COM ParcPlace Boulder "... but I can't promote you to "Prima Donna" unless you demonstrate a few more serious personality disorders" ------------------------------ ** FOR YOUR REFERENCE ** The service address, to which questions about the list itself and requests to be added to or deleted from it should be directed, is: Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development) via: Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Development Digest ******************************