From: Digestifier To: Linux-Activists@senator-bedfellow.mit.edu Reply-To: Linux-Activists@senator-bedfellow.mit.edu Date: Sat, 14 Aug 93 21:13:05 EDT Subject: Linux-Activists Digest #116 Linux-Activists Digest #116, Volume #6 Sat, 14 Aug 93 21:13:05 EDT Contents: Re: Who is in charge of curses? (Zeyd M. Ben-Halim) Re: Ctrl-Alt-Del with SLS 1.03 (David Fox) Can't get X windows to work (Paul Quinn) [Q] Are WD IDE drives OK? (Denise Tree) SLS 1.03 - Problem with NFS install with 5 1/4" disk. Can't mount (Seng-Poh Lee, Speedy) Weird floppy behavior (Daniel Jimenez) Re: [Q] Are WD IDE drives OK? (Steve Sheldon) [Q] Problems with LILO ... (Holger Wiese) Re: where is dump? (Brandon S. Allbery) Slackware Enet and kernel compiling problems (Byron A Jeff) Re: Only recieved two of four new groups... (Ian Kluft) Re: Slackware Enet and kernel compiling problems (Patrick J. Volkerding) Is there a driver for my Colorado Jumbo tape drive ? (Edwin Tisdale) NN thrashes .newsrc file (esp over NFS) (Nick Andrew) Welcome to the comp.os.linux.* hierarchy! (Matt Welsh) ---------------------------------------------------------------------------- From: zmbenhal@netcom.com (Zeyd M. Ben-Halim) Subject: Re: Who is in charge of curses? Date: Sat, 14 Aug 1993 21:00:40 GMT In article pcg@aber.ac.uk (Piercarlo Grandi) writes: >>>> On Thu, 12 Aug 93 13:32:56 GMT, hjl@nynexst.com (H.J. Lu) said: > >H> I don't know anyone who is working on the curses in the Linux C >H> library. But I am preparing to dump it for the ncurses once the >H> nncurses is stabilized. The main problem is I am not sure if the >H> ncurses is 100% compatible with the old one. I am concerned about the >H> shared library. > >Whatever thing happens, I want to make a very strong plug for libterm. >Libterm is a termcap clone that has two amazing properties: it reads >both terminfo and termcap format terminal descriptions, and $TERMCAP is >a colon separated path of places where to look for terminal >descriptions. These two features are very important; using libterm as a >substratum for both curses and ncurses would make them way more >compatible more transparently. Not quite. Ncurses doesn't use a separate terminfo lib but actually implements it internally. This makes libterm totally incompatible with ncurses. I'm working on termcap emulation in ncurses, that way you only need to link with -lncurses to get terminfo/termcap/curses. Zeyd ------------------------------ From: dfox@hip-hop.suvl.ca.us (David Fox) Subject: Re: Ctrl-Alt-Del with SLS 1.03 Date: Sat, 14 Aug 1993 18:41:29 GMT C-A-D is really a DOS thing, and not proper Unix shutdown procedure. I suggest 'shutdown -h now' and hit the reset button after you see the "system halted" message. -- David E. Fox email: hip-hop!dfox@amdahl.com 5479 Castle Manor Drive San Jose, CA 95129 Thanks for letting me change the magnetic 408/ 253-7992 images on your hard drive. ------------------------------ From: p_quinn@pavo.concordia.ca (Paul Quinn) Subject: Can't get X windows to work Date: Sat, 14 Aug 1993 22:48:00 GMT I installed Linux. The install went fine. When i tried to get X windows to work I got this message (or something very similar): X client error: no screens availible. Any ideas? I have a graphics Ultra with 1 MB VRAM. If anyone has the Xconfig for this please send it to me. Thanks --------------------------------------------------------- | Paul Quinn | | | p_quinn@pavo.concordia.ca | | | | System Architecture | | Concordia University | | | Montreal, Que | | --------------------------------------------------------- ------------------------------ Crossposted-To: comp.os.linux.help From: tree@whatever.cs.jhu.edu (Denise Tree) Subject: [Q] Are WD IDE drives OK? Date: Sat, 14 Aug 1993 21:58:28 GMT Hi Activists... I am thinking of getting a new drive and I've noticed lots of cheap western digital IDE drives around.... the 340 meg one is going for ~310 from most people. Is anyone using one of these ok? Thanks... Denise Tree ------------------------------ From: splee@pd.org (Seng-Poh Lee, Speedy) Crossposted-To: comp.os.linux.help Subject: SLS 1.03 - Problem with NFS install with 5 1/4" disk. Can't mount Date: 14 Aug 1993 22:33:36 GMT I'm trying to install SLS 1.03 via NFS. I'm using a1.5 since the machine only has a 5 1/4" disk. The boot goes ok, the 3com 3c503 card is detected at 0x300, int5, c800. I log in as install and set the new ip and routes. I also put in the address of the NFS server and the directory (A Sun running 4.1.1). At this point, Linux fails to mount the NFS directory. I know it says try several time, and I did, many times. No go. I then logged in as root, and tried a manual mount. Still no good. I see the updated SLS has a new 3 1/2" disk with NFS fixes. Does the 5 1/4" disk require some fix before it can do a NFS install? I was able to install fine from a mounted DOS hard disk, with the same disk. -- Seng-Poh Lee ------------------------------ Crossposted-To: comp.os.linux.misc From: djimenez@ringer.cs.utsa.edu (Daniel Jimenez) Subject: Weird floppy behavior Date: Sat, 14 Aug 1993 22:24:07 GMT I got a new computer recently, a 486DLC with an "FA3" motherboard. I put Linux on the hard disk and it worked quite nicely until I upgraded to 8 megabytes (from 4). For some weird reason, the floppy drive didn't work. When I tar'ed something onto the floppy and untar'ed it elsewhere, I got a bunch of garbage. Also, I couldn't boot off of a floppy (so I didn't suspect Linux). When I took out four of the 1x9 SIMMs, everything went back to normal. Weird. So I stuck back in the SIMMs, and recompiled the kernel with LAST_DMA_ADDR in /usr/src/linux/kernel/dlk_drv/floppy.c equal to 4 megs instead of 16 megs (so no DMA transfers would occur above 4M to or from the floppy). Now, surprisingly, the floppy drive works under Linux but I still can't boot off of it, unless I go back down to 4 megs. Isn't this weird? Has anyone heard of this happening? (I did try the classic `all possible permutations' algorithm on the CMOS; it doesn't matter whether the external or internal caches are enabled; the problem is the same.) -- Daniel Jimenez djimenez@ringer.cs.utsa.edu "I've so much music in my head" -- Maurice Ravel, shortly before his death. " " -- John Cage ------------------------------ Crossposted-To: comp.os.linux.help From: sheldon@iastate.edu (Steve Sheldon) Subject: Re: [Q] Are WD IDE drives OK? Date: Sat, 14 Aug 1993 22:45:37 GMT In tree@whatever.cs.jhu.edu (Denise Tree) writes: >Hi Activists... >I am thinking of getting a new drive and I've noticed lots of cheap >western digital IDE drives around.... the 340 meg one is going for >~310 from most people. Is anyone using one of these ok? I have used these with Linux and SCO Unix. I have had no problems to date, and this is after about 9 months of heavy usage. -- sheldon@iastate.edu Steve Sheldon #insert "standard disclaimer" Iowa State University ------------------------------ From: cindy@tron.gun.de (Holger Wiese) Subject: [Q] Problems with LILO ... Date: 14 Aug 93 10:32:00 GMT Hi, i have got severe problems installing LILO. During the last two or three weeks i installed the SLS distribution of Linux (1.02 & 1.03) on several computers, all equipped with standard IDE-Controllers and always had the same problem. After successfully installing all disks of the distribution i tried to install LILO to boot DOS or Linux from harddrive. But two attempts out of three failed to work. Either LILO complains about something like an unknown boot signature or it seems to install correct but after a reboot i get the message invalid partition table (seldom) or it starts up writing "LI" (not "LILO") to the screen and then it hangs (often). I do not know what i am doing wrong. Has anyone experienced similar problems and knows what to do about it? Does anyone know wether there is a possibility to repair a LILO boot-sector? Up to now i always installed the whole beast again, hoping it will work. Okay, usually after two or three attempts everything works fine, but this method is rather frustrating and time consuming. If you need more information on my hardware or the way i installed the package please email me. It would be nice if anyone has got an idea. Thank you. Bye, Holger ... Windws is ine for bckgroun comunicaions -- THE ANSWER V2.03 ------------------------------ From: bsa@kf8nh.wariat.org (Brandon S. Allbery) Subject: Re: where is dump? Date: Sat, 14 Aug 1993 22:52:00 GMT In article dfox@hip-hop.suvl.ca.us (David Fox) writes: >Also I don't really see the distinction between different dump levels in >the dump utility (perhaps one can elaborate on this) - I see two different >backup stategies, namely a full backup, and an incremental one, which is >easily derivable from (for example) touching a file in /etc after the >full backup, and using find -newer to get filenames modified since the >last full backup. When dump and restor were written and subsequently Berzerkeleyized, find didn't understand -newer. The other reason had to do with a "tower of Hanoi" (so called by the "dump" manpage; actually, it was a geometric progression) backup schedule which arranged for a series of progressively older tapes: at one tape per dump level and the dump levels alternated according to a binary sequence (1, 2, 1, 3, 1, 2, 1, 4, 1, 2, 1, 3, 1, 2, 1, 5, ...) you get (assuming daily backups): 1 week on 4 tapes 2 weeks on 5 tapes 4 weeks on 6 tapes 8 weeks on 7 tapes 16 weeks on 8 tapes 32 weeks on 9 tapes 64 weeks on 10 tapes, which is the limit. Tape # N (starting from 1) corresponds to dump level 10-N, which is why 10 tapes is as high as you can go. This can save your *ss if something from half a year ago needs to be restored from tape for some reason. (It happened to me once.) But, from the same period, keeping track of what tape/dump level to use on what day is a bit of a problem, because days/weeks/months just don't fit into powers of 2 too well. ++Brandon -- Brandon S. Allbery kf8nh@kf8nh.ampr.org bsa@kf8nh.wariat.org ------------------------------ Crossposted-To: comp.os.linux.help From: byron@cc.gatech.edu (Byron A Jeff) Subject: Slackware Enet and kernel compiling problems Date: Sat, 14 Aug 1993 23:56:14 GMT Well Slackware is getting better. 3 complete installations in 4 days after the first 3 hour bout with the network installation. A couple of problems though in the ethernet and kernel compiling areas. The Configuration: Machine: 50 Mhz 486 VLB, 220 Meg IDE HD, 8 Megs of RAM, WD8003E Enet card 8 Meg swap partition. Linux: .99PL12 Slackware 1.01 distribution. Just installed and unchanged Ok. First the Enet problem. The WD8003 card works fine with DOS packet drivers and worked fine on the previous SLS 1.02 installation. When I fire up the card using ifconfig I get error along the line of eth0: Bogus packet ... size = kmemory: cannot allocate buffer size 65533 over and over and over again until I shut the card down. I read a couple of days ago that turning off the packet forwarding would take this problem away. So I dug into /linux/net/inet/ip.c and commented out the define on packet forwarding. I then went to the top level, did an make config, make dep, make clean, make zImage. Well disaster stuck because the kernel won't compile. I get internal compiler error in places like init/main.c and kernel/chr_drv/keyboard.c. I though it might be a swap problem (because the first time I ran the make I didn't have the swap partition attached -- and when I attached it top showed some swaping) but even with the swap attached and about 1.6M of it used I get errors. Do I have a bad gcc2.4.5? Is there anything else I should look at. My machine is fairly useless if the net is disabled. I'm typing this using DOS ;-(. Any help greatly appriciated. BAJ --- Another random extraction from the mental bit stream of... Byron A. Jeff - PhD student operating in parallel! Georgia Tech, Atlanta GA 30332 Internet: byron@cc.gatech.edu ------------------------------ From: ikluft@uts.amdahl.com (Ian Kluft) Crossposted-To: comp.os.linux.misc Subject: Re: Only recieved two of four new groups... Date: 14 Aug 93 23:41:38 GMT stephen@sun1.clark.net (Stephen Balbach) writes in comp.os.linux.misc: >Hmmm. our site has only recieved two of the four new groups (c.o.l.help >and c.o.l.misc), are they coming in batches or should I begin to check >further up the pipe and see whats up. They were posted on August 11 and should all have appeared around the same time. You and anyone else in the same situation should talk to your system/news administrator and request that they add them. Unless they follow news.groups, they will probably ask you if you are requesting real newsgroups. Show them a copy of the results. You can print this out and show it to your sysadmin if they need the info. comp.os.linux reorganization results - 1842 votes Yes No : 2/3? >100? : Pass? : Group ---- ---- : ---- ----- : ----- : ------------------------------------------- 1692 135 : Yes Yes : Yes : comp.os.linux.admin 1741 90 : Yes Yes : Yes : comp.os.linux.development 1647 177 : Yes Yes : Yes : comp.os.linux.help 1660 155 : Yes Yes : Yes : comp.os.linux.misc All the new groups are unomderated. -- Ian Kluft KD6EUI PP-ASEL Amdahl Corporation, Open Systems Development ikluft@uts.amdahl.com Santa Clara, CA [disclaimer: any opinions expressed are mine only... not those of my employer] ------------------------------ From: bf703@cleveland.Freenet.Edu (Patrick J. Volkerding) Crossposted-To: comp.os.linux.help Subject: Re: Slackware Enet and kernel compiling problems Date: 15 Aug 1993 00:16:47 GMT Reply-To: bf703@cleveland.Freenet.Edu (Patrick J. Volkerding) In a previous article, byron@cc.gatech.edu (Byron A Jeff) says: [...problems with ifconfig...] I have not heard other reports of this, but TCP/IP in the Slackware distribution is going to be upgraded to some extent in a new release that will be out soon. I want to do some real actual network testing first, though. >the kernel won't compile. I get internal compiler error in places like >init/main.c and kernel/chr_drv/keyboard.c. I though it might be a swap >problem (because the first time I ran the make I didn't have the swap >partition attached -- and when I attached it top showed some swaping) but >even with the swap attached and about 1.6M of it used I get errors. > >Do I have a bad gcc2.4.5? Is there anything else I should look at. >My machine is fairly useless if the net is disabled. I'm typing this using >DOS ;-(. This much I know is not true in general... I compile the kernel at least a couple times a day! :^) I noticed a new .99pl12A went up on nic.funet.fi, and I'm integrating that into the Slackware distribution right now, along with improved setup of the ethernet card for NFS installs. There will be some other new things as well, including a new E series with emacs 19.18. Take care, -- Patrick Volkerding volkerdi@mhd1.moorhead.msus.edu bf703@cleveland.freenet.edu ------------------------------ From: edwin@maui.cs.ucla.edu (Edwin Tisdale) Subject: Is there a driver for my Colorado Jumbo tape drive ? Date: Sun, 15 Aug 93 00:02:34 GMT In answer to FAQ VIII.19, Charlie Brady mentions an unfinished driver for QIC-40 na QIC-80 tape drives. Has there been any progress on this since June, 1993? If so, where can I get a copy of the driver? Thanks in advance, Bob Tisdale (edwin@cs.ucla.edu) ------------------------------ From: nick@kralizec.zeta.org.au (Nick Andrew) Crossposted-To: news.software.nn,comp.protocols.nfs Subject: NN thrashes .newsrc file (esp over NFS) Date: 15 Aug 1993 00:26:51 +1000 I noticed this problem while running NN over NFS. Every time I go to a new group NN rewrites the .newsrc file in its entirety. I am running NN 6.4.18. I've been running NN locally for years and never noticed it. I can guess then that it isn't a problem when done locally. However if I run it over NFS I can hear the disk thrash at the time of writing. Moreover, it takes longer. A looping shell script (doing a regular ls -l .newsrc) shows the file growing. NFS is a stateless protocol. Does this imply that my server (Sun 3/60 running SunOS 4.0) biod must open and close the .newsrc file many times? The client is a Linux box. I have heard that Linux only supports small block sizes (rsize=1024,wsize=1024). Does this contribute to the thrashing? My .newsrc is about 32k long. Finally although I appreciate Nn's motive in keeping my .newsrc up-to-date, surely this effort is wasted. Wouldn't it be more appropriate to update the file every 5 minutes and on exit only? Nick. -- Kralizec Dialup Unix (Public Access) Data: +61-2-837-1183, 14400 24hrs 8N1 Zeta Microcomputer Software Data: +61-2-837-1868, 2400 24hrs 8N1 P.O. Box 177, Riverstone NSW 2765 Plan: To beat Gnuchess 4.1 ! ------------------------------ From: mdw@TC.Cornell.EDU (Matt Welsh) Crossposted-To: comp.os.linux.announce.help,comp.os.linux.development,comp.os.linux.admin,comp.os.linux.misc,comp.os.linux Subject: Welcome to the comp.os.linux.* hierarchy! Date: 14 Aug 1993 20:47:50 -0400 Welcome to the comp.os.linux.* hierarchy! Background ========================================================================= This posting is an introduction to the comp.os.linux.* hierarchy of USENET newsgroups. Linux is a free implementation of UNIX for 80386/80486 machines covered by the GNU GPL. Most of the development of the Linux kernel has been done by Linus Torvalds, an internationally reknowned UNIX wizard from Helsinki, Finland. For the past two years or so, the newsgroup comp.os.linux has grown be one of the most popular groups on USENET. Late in 1992, a CFV for splitting comp.os.linux was posted; the only group which passed was comp.os.linux.announce, a moderated newsgroup for Linux announcements and patches. Six months later, during the summer of 1993, another CFV for splitting comp.os.linux was posted. The voting period for the comp.os.linux reorganization results ended at 23:59:59 UTC on 4 August 1993 (4:59PM US Pacific Time, 7:59PM US Eastern Time.) The results are as follows: comp.os.linux reorganization results - 1842 votes Yes No : 2/3? >100? : Pass? : Group ---- ---- : ---- ----- : ----- : ------------------------------- 1692 135 : Yes Yes : Yes : comp.os.linux.admin 1741 90 : Yes Yes : Yes : comp.os.linux.development 1647 177 : Yes Yes : Yes : comp.os.linux.help 1660 155 : Yes Yes : Yes : comp.os.linux.misc Because of this split, the newsgroup comp.os.linux will be deleted on 11 November 1993. The new newsgroups will be created on 11 August 1993. This posting describes these newsgroups, including comp.os.linux.announce, which will remain entact. General Policy ========================================================================= The general policy for the Linux newsgroups is simple. Who sets the policy? We all do. All of us on USENET are interested in communicating openly about a number of topics. That's why we have USENET. If you want the Linux newsgroups to work for you, a few suggestions: * Read the Linux FAQ and follow the newsgroups for some time before posting questions. This is very important. comp.os.linux suffered from HUGE amounts of noise and traffic because much of the growing readership never bothered to READ the newsgroup; they only posted questions. The same thing will happen with the new newsgroups unless you read the FAQ (found on sunsite.unc.edu in the file pub/Linux/docs/FAQ) and read the newsgroup for some time before posting questions. Chances are, your question has already been recently answered, and a simple browsing of the newsgroup will answer it. We suggest using a threaded newsreader such as "trn" which will allow you to browse and mark articles by subject, so you don't have to read each and every article in each newsgroup. * Crossposting between the Linux newsgroups is STRONGLY discouraged. If you do crosspost questions between Linux newsgroups, expect to be flamed to oblivion. The reason we have a newsgroup split is to categorize discussions into separate newsgroups. Crossposting negates this effect. If your posting cannot fit into ONE of the newsgroups c.o.l.admin, c.o.l.help, or c.o.l.development, then you should post it to c.o.l.misc. The one exception is for announcements. Occasionally, an important announcement (such as this one) will be crossposted between c.o.l.announce and one or more of the other c.o.l.* groups. These announcements must be approved by the .announce moderator; see below. * Reply to questions via e-mail if at all possible. While discussion in the newsgroups is encouraged, if someone is asking a simple question to which the answer is well-known, there is no reason to post the reply. Don't assume that the person posting the question actually reads the newsgroup or will even note your followup if they do. Reply via e-mail unless the reply is of general interest. * Don't flame newbies. Over the course of the past few months, the Linux community has developed an oversensitive ego and a reputation for being unfriendly towards newcomers, mostly because of unwarranted flaming by a handful of righteous individuals. If someone posts, saying, "Hi! I'm new to this group! What is Linux?" (which will inevitably happen as the new newsgroups are propagated), DO NOT FLAME THEM. When someone sees a new newsgroup pop up within "rn", they are justifiably curious about the new group and probably don't know that well over 80,000 people who know EVERYTHING about Linux read the group. Right? Instead of being rude, you can send a polite note to the poster, saying, "Hello, Linux is a free implementation of UNIX for the 386 and 486. You can get the FAQ from sunsite.unc.edu in /pub/Linux/docs. Let me know if I can be of help!". That's all. Not difficult, eh? You can even save your stock reply in a file and simply send form-letters to newbies if you wish. But there is very little point in flaming or ever being rude. It goes against everything that Linux can and should be. Just remember that nobody knows everything---not even Linus--- and that you were a newbie once, too. :) comp.os.linux.announce ========================================================================= Comp.os.linux.announce is a moderated newsgroup for Linux announcements and source patches. The purpose of this group was to get all of the ``important'' Linux information out of the regular newsgroup and into a place where all Linux users could see the important announcements without having to wade through a jungle of other postings. So far, this group has been very successful. The moderators for this group are myself (Matt Welsh, mdw@tc.cornell.edu) and Lars Wirzenius (wirzeniu@cc.helsinki.fi). We will be sharing the moderator duty, and backing each other up to make sure that postings to this group will be approved as soon as possible after they're submitted. Submissions to this group should be mailed to the address: linux-announce@tc.cornell.edu If you have any problems or questions about c.o.l.announce, please send mail to the moderators at linux-announce-request@tc.cornell.edu Or simply mail us directly. This is not a request address for mailing list subscription; see below. A separate posting details the guidelines for submitting to this group. I plan to approve just about anything that's posted to this group, except for questions or discussions about Linux. So, please, post away. :) There are also archives of comp.os.linux.announce available at a number of Linux FTP sites: check sunsite.unc.edu:/pub/Linux/docs/linux-announce.archive There is a mailing list mirror of the comp.os.linux.announce newsgroup; to join, send mail to linux-activists-request@niksula.hut.fi With the line X-Mn-Admin: join ANNOUNCE at the top of the body (not in the subject). Approved postings to c.o.l.announce will automatically be mailed to this mailing list channel. comp.os.linux.admin ========================================================================= This newsgroup was created simply to thwart the unique newsgroup acronym "c.o.l.a", previously used by c.o.l.announce. However, this newsgroup is also used for discussions and questions about running Linux systems, either in a single-user or multi-user environment. Clearly, there is no large distinction between c.o.l.admin and c.o.l.help. However, .admin should be mostly used for discussions about RUNNING Linux, not USING or PROGRAMMING it. Unfortunately, especially with Linux, the line between system administrator and system user is very fuzzy. In short, we anticipate c.o.l.admin to be mostly about questions with installing, setting up, and configuring Linux systems, as well as other discussions relating to system administration. comp.os.linux.development ========================================================================= c.o.l.development, or "c.o.l.d" for short, is a newsgroup for questions and discussions about Linux kernel and systems-level development. Please note that this is a newsgroup about development OF Linux, not development FOR Linux. In other words, c.o.l.d isn't for questions about programming or porting software to Linux. Instead, this is a newsgroup for discussions about developing the Linux kernel itself, including writing device drivers, adding new features, and so on. In addition, discussions about development of shared libraries, and other essential systems-level projects, are welcome here. Hopefully, this newsgroup will embody some of the content and scope of the linux-activists mailing list channels such as GCC, KERNEL, SCSI, and NET. comp.os.linux.help ========================================================================= Comp.os.linux.help is perhaps the most general of Linux newsgroups. It is for any general user, programming, or setup questions and discussion about Linux. If your question is about Linux development, post to c.o.l.development. If it is about system administration, post to c.o.l.admin. However, if your question is of a more general nature, such as "How do I set up Linux for use with an NE2000 card?", c.o.l.help is your place. Remember that you should not crosspost between .help and other Linux newsgroups. This means that if you are asking for help in .development, that's fine, but .help is for those questions which don't fit into .admin and .development. comp.os.linux.misc ========================================================================= This group is the canonical ``catch-all'' for discussions and questions which don't fit into the other Linux newsgroups. While c.o.l.help is generally for questions, c.o.l.misc is for discussions of a general nature about Linux, such as setting up a file hierarchy standard, questions about Linus' personal life and virtual beer, and the inevitable flame war. Again, it should be noted that crossposting between c.o.l.misc and other Linux newsgroups is strongly discouraged. If your posting or question does not fit into ONLY ONE of the other Linux newsgroups, post it to .misc. Comments ========================================================================= If you have questions or comments about this document, please direct them to mdw@tc.cornell.edu. Flames to /dev/null; cheques and money orders to Linus Torvalds. Thanks. -- Matt Welsh, mdw@tc.cornell.edu "On the Internet, nobody knows you're a dog." ------------------------------ ** 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-Activists-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux) via: Internet: Linux-Activists@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 tupac-amaru.informatik.rwth-aachen.de pub/msdos/replace The current version of Linux is 0.99pl9 released on April 23, 1993 End of Linux-Activists Digest ******************************