Subject: Linux-Development Digest #552 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Mon, 14 Mar 94 09:13:20 EST Linux-Development Digest #552, Volume #1 Mon, 14 Mar 94 09:13:20 EST Contents: Small patch for Umsdos, please give it a try (Jacques Gelinas) Brief summary of interface sockets? (H. Peter Anvin N9ITP) Re: Specialix Driver Round 2 (From specialix) (Donald J. Becker) Re: TTY overruns cost money. (Kai Petzke) Performance on remote machine using rlogin (Barry Yip kam-wa) Update on `hard-params' program (Bram Bouwens) Linux not answering timedc c (Rafal Maszkowski) Linux 1.0---A better UNIX than Windows NT (Linus Torvalds) Re: GOD SPEAKS ON LINUX! (Anton Toom) Re: Short delays outside of the kernel (Lawrence Foard) Re: UDP report card (H. Peter Anvin N9ITP) Re: VT's must all use the same font [was Re: Loaded fonts discarded aft] (H. Peter Anvin N9ITP) I'm looking for the Latest GCC and Libs (Jean-Paul Chia) ---------------------------------------------------------------------------- From: jack@solucorp.qc.ca (Jacques Gelinas) Subject: Small patch for Umsdos, please give it a try Date: Mon, 14 Mar 94 05:16:49 GMT umsdos 0.2 is now used by many. I have received few bug reports difficult to replicate. All those were related to the inability to locate a file even if it is there (a ls just after the failure shows it). I have located and fixed at least one bug. A small diff follow. Those who have that kind of odd behavior, could you try it. If possible could you email again even if this is fixing it or not. I have received a number of mail reporting mostly "false alarm" bug. To make things more complicated, my email system went a little crazy and I am pretty sure I have lost some messages (since 3 weeks ago). I have updated to the latest sendmail and now all look fine. This patch must be applied in /usr/src/linux/fs/umsdos ==================================================================== *** dir.bak Sat Feb 5 15:36:10 1994 --- dir.c Sun Mar 13 23:45:30 1994 *************** *** 329,334 **** --- 329,337 ---- memcpy (entry->name,dirent.d_name,dirent.d_reclen); entry->name[dirent.d_reclen] = '\0'; entry->name_len = dirent.d_reclen; + inode->u.umsdos_i.i_dir_owner = dir->i_ino; + inode->u.umsdos_i.i_emd_owner = 0; + umsdos_setup_dir_inode(inode); break; } } ====================================================== Thanks in advance! PS: For those who asked, here is the status of umsdos. 1-Make sure all known bug are solved (pretty close I guess). 2-Promote integration in the standard kernel right after 1.0 is out. 3-Enhance performance. In parallel I intend to produce LADR (Linux Advanced Desktop Release). I am currently exploring the Andrew Multimedia system to produce the help and administration system. Anyone with good experience with it ? Some pointers would be welcome :-) -- ======================================================== Jacques Gelinas (jacques@solucorp.qc.ca) Maintainer of US4BINR jacques@us4binr.login.qc.ca ------------------------------ From: hpa@ahab.eecs.nwu.edu (H. Peter Anvin N9ITP) Subject: Brief summary of interface sockets? Reply-To: hpa@nwu.edu (H. Peter Anvin) Date: Mon, 14 Mar 1994 07:37:10 GMT Hi there, I wonder if someone could email me, post, or give me a pointer to a brief summary of using SOCK_PACKET to obtain raw Ethernet packets under Linux. I have a prototype program that uses raw Ethernet sockets under SGI IRIX, but before releasing it I would like it to run on Linux as well. I only need to know the things that are specific to the SOCK_PACKETS interface compared to UDP or RAW sockets (or, if you happen to know the SGI SNOOP/DRAIN interface, the differences between that and Linux). I am primarily interested in nonpromiscuous use (based on a specific Ethertype). /hpa -- INTERNET: hpa@nwu.edu FINGER/TALK: hpa@ahab.eecs.nwu.edu IBM MAIL: I0050052 at IBMMAIL HAM RADIO: N9ITP or SM4TKN FIDONET: 1:115/511 or 1:115/512 STORMNET: 181:294/101 Purgamentum init, exit purgamentum. ------------------------------ From: becker@super.org (Donald J. Becker) Subject: Re: Specialix Driver Round 2 (From specialix) Date: Sun, 13 Mar 1994 16:05:29 GMT In article , Alan Drew wrote: >Looks like I've been missing some of the fun. I'm not sure what >this argument is really all about, tho' I *am* sure that one >of you kind souls will enlighten me. What happened was the typical Usenet digression. Everyone (that understood the topic, that is) agreed that what Specialix wanted to do was perfectly fine. The topic moved to loadable device drivers (*not* the original downloaded embedded code), and some uninformed people started flaming the Linux developers for claiming something that had never been claimed. The out-of-context quotes caused even more people to jump in, and ... the flames went on. >A device driver (Partcularily an Intelligent device driver) usual fits >something like this (in block diagram format) into your system. > >+-----+ +--------------+ +---------------+ +-------------------+ >| O/S |----| Device Driver|-----| Download Code |----| modem/terminal etc| >+-----+ +--------------+ +---------------+ +-------------------+ I disagree with this diagram. The vast majority of devices have a register-level interface that appears as hardware, and the device drivers are tightly integrated with the kernel +--------------------+ +------------------------------------------+ | O/S + Device Driver|-----| modem/terminal etc (opt. Download Code))| +--------------------+ +------------------------------------------+ -- Donald Becker becker@super.org IDA Supercomputing Research Center 17100 Science Drive, Bowie MD 20715 301-805-7482 ------------------------------ From: wpp@marie.physik.tu-berlin.de (Kai Petzke) Subject: Re: TTY overruns cost money. Date: 14 Mar 94 10:23:06 GMT I wrote: >I noticed these serial overruns from my mouse long times before. >They happen on my 386 DX 40, when I do data transfer with my >internal modem at 115200 bps. OOps. Not the modem caused the problem. The printer did. The last sentence should read as "They happen on my 386 DX 40, when I send large bitmaps to the printer." Sorry for my confusion. -- Kai Petzke Advertisement by Microsoft in a well-known German magazine: If you don't like our programmes, then make your own ones. However, they expect you to use Microsoft products for this -:) ------------------------------ From: g609296@win.or.jp (Barry Yip kam-wa) Subject: Performance on remote machine using rlogin Date: 14 Mar 94 10:00:42 GMT Hi everyone, I have serious problem when rlogin a remote machine and do some modem stuffs. For example, after rlogin another machine and run kermit, I can't dialup to outer world successfully no matter it is a BBS host or a unix machine. I did get connected but a lot of characters dropped. Is it the *famous* TTY overrun? Doing same thing on the machine (sitting in front of it :-) works fine up to 38400 without a glitch. I am using a AMD386 DX40 and ZyXEL 1496E+ and 16450 though. In another occassion, I tried download some files (a few MB) from a dialup unix host. Everything fine until I rlogin this machine from another one. I do some 'ls', 'rm, 'cp' stuffs etc. Then lots of retry coming out. I stop, it continues fine. Doing similar things locally shows no problem. Is it a network problem or the remote stuff is so demanding(seems not so)? -- \ \\/o\ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ \ \\/o\ >===== / | Barry Yip Fido 6:730/16.0 | >===== / //// ~ | ^^^^^^^^^ g609296@win.or.jp | //// ~ ------------------------------ From: d70@nikhef.nl (Bram Bouwens) Subject: Update on `hard-params' program Date: 14 Mar 94 09:20:31 GMT Reply-To: d70@nikhefh.nikhef.nl (Bram Bouwens) I tried the hard-params.c program posted in this group last week on my HP, but it crashed, so I asked the author, Steven.Pemberton@cwi.nl, about it. It is now called `enquire', to be found in {pub}/misc on ftp.eu.net, or http://www.cwi.nl/ftp/steven/www/enquire.html for WWW-users, and it works fine. Bram ------------------------------ From: rzm@oso.chalmers.se (Rafal Maszkowski) Subject: Linux not answering timedc c Date: Mon, 14 Mar 1994 10:45:18 GMT I tried to check time difference on my 1.0 (March 13) with timedc c dain but it looks like dain is not answering and timedc doesn't disply anything and stops. What can be the reason? R. -- Rafal Maszkowski rzm@oso.chalmers.se rzm@mat.uni.torun.pl <-finger for public snail: Omgangen 464-82, 412-80 Goteborg, Sweden; tel: +46-31-7780831 key Opinia publiczna powinna byc zaalarmowana swoim nieistnieniem - St. J. Lec ------------------------------ From: Linus Torvalds Crossposted-To: comp.os.linux.announce,comp.os.linux.misc Subject: Linux 1.0---A better UNIX than Windows NT Date: 14 Mar 1994 12:51:16 GMT Finally, here it is. Almost on time (being just two years late is peanuts in the OS industry), and better than ever: Linux kernel release 1.0 This release has no new major features compared to the pl15 kernels, but contains lots and lots of bugfixes: all the major ones are gone, the smaller ones are hidden better. Hopefully there are no major new ones. The Linux kernel can be found as source on most of the Linux ftp-sites under the names linux-1.0.tar.gz (full source) linux-1.0.patch.pl15.gz (patch against linux-0.99pl15) linux-1.0.patch.alpha.gz (patch from linux-pre-1.0) it should be available at least at the sites ftp.funet.fi: pub/OS/Linux/PEOPLE/Linus (now) sunsite.unc.ed: pub/Linux/Incoming (now) pub/Linux/kernel (soon) tsx-11.mit.edu: pub/linux/sources/system (soon) ftp.cs.helsinki.fi: pub/Software/Linux/Kernel (now) This release finally moves Linux out of Beta status and is meant as a base for distributions to build on. It will neither change Linux' status as FreeWare under the GPL, nor will it mean the end of development on Linux. In fact many new features where held back for later releases so that 1.0 could become a well tested and hopefully stable release. The Linux kernel wouldn't be where it is today without the help of lots of people: the kernel developers, the people who did user-level programs making linux useful, and the brave and foolhardy people who risked their harddisks and sanity to test it all out. My thanks to you all. (Editorial note: if you think this sounds too much like the Academy Awards ceremony, just skip this: it's not getting any better.) Thanks to people like Aaron Kushner, Danny ter Haar and the authors of the AnwenderHandbuch (and others) who have helped me with hardware or monetary donations (and to the Oxford Beer Trolls and others who took care of the drinkware). And thanks to Dirk, who helped me write this announcement despite my lazyness ("hey, it's just another release, who needs an announcement anyway?"). To make a long and boring story a bit shorter and boring, here is at least a partial list of people who have been helping make Linux what it is today. Thanks to you all, Krishna Balasubramanian Arindam Banerji Peter Bauer <100136.3530@compuserve.com> Fred Baumgarten Donald Becker Stephen R. van den Berg Hennus Bergman Ross Biro Bill Bogstad John Boyd Andries Brouwer Remy Card Ed Carp Raymond Chen Alan Cox Laurence Culhane Wayne Davison Thomas Dunbar Torsten Duwe Drew Eckhardt Bjorn Ekwall Doug Evans Rik Faith Juergen Fischer Jeremy Fitzhardinge Ralf Flaxa Nigel Gamble Philip Gladstone Bruno Haible Andrew Haylett Dirk Hohndel Nick Holloway Ron Holt Rob W. W. Hooft Michael K. Johnson Fred N. van Kempen Olaf Kirch Ian Kluft Rudolf Koenig Bas Laarhoven Warner Losh H.J. Lu Tuomas J. Lukka Kai M"akisara Pat Mackinlay John A. Martin Bradley McLean Craig Metz William (Bill) Metzenthen Rick Miller Corey Minyard Eberhard Moenkeberg Ian A. Murdock Johan Myreen Stefan Probst Daniel Quinlan Florian La Roche Robert Sanders Peter De Schrijver Darren Senn Chris Smith Drew Sullivan Tommy Thorn Jon Tombs Theodore Ts'o Simmule Turner Stephen Tweedie Thomas Uhl Juergen Weigert Matt Welsh Marco van Wieringen Stephen D. Williams G\"unter Windau Lars Wirzenius Roger E. Wolff Frank Xia Eric Youngdale Orest Zborowski A more detailed list with contact and description information can be found in the CREDITS file that accompanies the kernel sources. -- Mail submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu PLEASE remember Keywords: and a short description of the software. ------------------------------ From: ontonca@the-college.iwctx.edu (Anton Toom) Crossposted-To: comp.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc Subject: Re: GOD SPEAKS ON LINUX! Date: 13 Mar 94 01:57:07 GMT Glen Buhlmann (gbuhlman@uoguelph.ca) wrote: : I am God......and I use an Amiga...... a friend of mine, a greek god, uses his old apple2. says it's ok. -- user ontonca@the-college.iwctx.edu: file ~/.signature not found ------------------------------ From: entropy@world.std.com (Lawrence Foard) Subject: Re: Short delays outside of the kernel Date: Mon, 14 Mar 1994 06:05:55 GMT In article <1994Mar12.162933.25336@cc.gatech.edu>, Byron A Jeff wrote: >I'm in the process of building a EPROM/Microcontroller board. I'm planning >on writing the software under linux. One of the requirements is to have >a very short (100 uS) pulse to program the parts. You might want to just put a 1 shot on the board, this would avoid having any tight timing requirments. -- ====== Call the skeptic hotline 1=900=555=5555 talk to your own personal . \ / skeptic 24 hours/day. Just say no to victimless crimes. . . \ / High quality Linux application development available. . . . \/ The true theory of everything will run on a finite turing machine. . . . ------------------------------ From: hpa@ahab.eecs.nwu.edu (H. Peter Anvin N9ITP) Subject: Re: UDP report card Reply-To: hpa@nwu.edu (H. Peter Anvin) Date: Mon, 14 Mar 1994 09:58:28 GMT In article of comp.os.linux.development, evansmp@mb48026.aston.ac.uk (Mark Evans) writes: > > It is a common problem, 127.0.0.2 can be even more dangerous, quite a few > machines only have 127.0.0.1 rather than 127.0.0.0 as a route to loopback. > Thus such an address can end up going through serveral machines, simply > being forwarded to default routes until it gets to a machine which accepts > it. In some instances telnet 127.0.0.2 will connect you to a (psudo-random) > machine somewhere on the internet. > I found that neither my Silicon Graphics host nor my Linux host answered correctly to 127.0.0.2. When I put in an explicit route to network 127.0.0.0 netmask 255.0.0.0 it correctly assigned it to the loopback interface and then connecting to 127.0.0.2 worked. Personally I find this use of a class A network for this purpose pretty ridiculous, but I can see where having multiple loopback addresses could be of use; 127.0.0.1 should then be the equivalent to the "outside" entrypoint. But a Class A? Give me a break. /hpa -- INTERNET: hpa@nwu.edu FINGER/TALK: hpa@ahab.eecs.nwu.edu IBM MAIL: I0050052 at IBMMAIL HAM RADIO: N9ITP or SM4TKN FIDONET: 1:115/511 or 1:115/512 STORMNET: 181:294/101 Linux system administrator (3 systems on the net, one off) ------------------------------ From: hpa@ahab.eecs.nwu.edu (H. Peter Anvin N9ITP) Subject: Re: VT's must all use the same font [was Re: Loaded fonts discarded aft] Reply-To: hpa@nwu.edu (H. Peter Anvin) Date: Mon, 14 Mar 1994 10:12:51 GMT In article of comp.os.linux.development, aeb@cwi.nl (Andries Brouwer) writes: > > You asked this question before, and I answered it. Now you ask > it again, and the answer will be the same. > Several implementations of font loading code were floating around, > and I liked Crosser's version best, polished it a little and proposed > including it in the standard kernel, which Linus did. > [So, no behaviour was changed, but a choice was made.] > > Now should there be a separate font for each VT? > If everyone wants it, then yes. If many people want it, then > it should at least be a configuration option. > But there is a danger of pollution: there are many potentially > nice things, and at configuration time one could easily have > fifty keyboard/console-related questions. > > Separate fonts for each VT take a lot of memory, and are used > by relatively few Linux users, so cannot be the default, I think. > Two issues: 1. I would assume support could be there; memory could me kmalloc()ed at load time if the font is loaded with the "set only this VT" option. Since the maximum size of a font is 32x256 = 8K, having two data block pointers/VT would do it. If set to NULL, use the global font. 2. The EGA/VGA hardware supports 512-character fonts as well; you lose highlighting the foreground or blink (if you chose to lose the blink you have to force the CRTC into 8-column mode and invert the font, then swap foreground and background). Once my exams are over this quarter, I am going to look into this and a couple of other features I have been thinking about. > > Of course this is a kludge, but my vision of future development > is not one with a VT for English, one for Hebrew and one for Russian, > but Unicode on all VTs, so that you can mix all alphabets everywhere. > After 1.0. > >512 characters would require a graphical console. /hpa -- INTERNET: hpa@nwu.edu FINGER/TALK: hpa@ahab.eecs.nwu.edu IBM MAIL: I0050052 at IBMMAIL HAM RADIO: N9ITP or SM4TKN FIDONET: 1:115/511 or 1:115/512 STORMNET: 181:294/101 Linux system administrator (3 systems on the net, one off) ------------------------------ From: jean-paul@garion.it.com.au (Jean-Paul Chia) Subject: I'm looking for the Latest GCC and Libs Date: 12 Mar 1994 10:17:44 +0800 Does anyone know what the latest version is? And where to get it? I'm usng 4.4.4 at the moment and 2.4.5 GCC.. And It's a bit old.. but it seems to run ok with the ALPHA-1.0 Kernel.. :) Ohwell Thanks.. Please reply to jean-paul@garion.it.com.au JP ------------------------------ ** 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 ******************************