From:     Digestifier <Linux-Misc-Request@senator-bedfellow.mit.edu>
To:       Linux-Misc@senator-bedfellow.mit.edu
Reply-To: Linux-Misc@senator-bedfellow.mit.edu
Date:     Fri, 22 Oct 93 08:28:09 EDT
Subject:  Linux-Misc Digest #233

Linux-Misc Digest #233, Volume #1                Fri, 22 Oct 93 08:28:09 EDT

Contents:
  Binaries of Internet-Go-Server client ? (G. Engels)
  SLS flaming <yawn> ! (Ian Parkin)
  *** PLEASE READ THIS BEFORE POSTING *** (misc-2.06) (Ian Jackson)
  Re: Bogomip (Thomas Kroener)
  Re: Linux Applications (Bernd Christiansen)
  Icmake 6.07 is out (Karel Kubat)
  Re: Collage: Ported to Linux on sunsite.unc.edu (Very ALPHA) (Michael Schack)
  ftp - displaying dir info when cd-ing (Karl Keyte, ESOC Darmstadt)
  Questions : xload, login (Andreas Gloege)
  Re: Bogomip (Joost Helberg)
  Re: Questions : xload, login (Nicholas Ambrose)

----------------------------------------------------------------------------

From: engelsg@uni-duesseldorf.de (G. Engels)
Subject: Binaries of Internet-Go-Server client ?
Date: 22 Oct 1993 07:52:09 GMT

I'm looking for the binaries of one of the Internet-Go-Server clients,
for example xigs or xgospel, for Linux. I tried to compile the source,
but I got errors on my machine.

I know that my Linux-installation is partially damaged (because of a
hard disk failure) and I can't fix this damage by hand, but I also don't
want to install the whole thing again (maybe in a few weeks), so I'm
looking for the binaries. But maybe you also got errors and maybe you can 
tell me how to fix them.

If you want to reply by email, please use

engelsg@uni-duesseldorf.de ,

but I will also continue to read this group.

Have a nice day.

------------------------------

From: iparkin@iris.bt.co.uk (Ian Parkin)
Subject: SLS flaming <yawn> !
Reply-To: iparkin@iris.bt.co.uk
Date: 22 Oct 93 10:04:48 GMT

>SLS reminds me of a three-legged rhinocerous in full charge.
>It's huge, damaged, has lots of inertia and is best avoided
>if at all possible.

Just my 0.02's worth :-

Why all this flaming of SLS ?

When it was the first *major* distribution of Linux, it was heralded as the best thing since a Caterham super 7 on a windey road in the summer. People could be heard singing it's praises from the rooftops.

It became the 'de facto' release, the FAQ states as much, untold hordes installed, played and learnt with it. Sure it had problems, but we all had fun fixing them and we all learnt from that process. I would guess that there are more SLS based installations out there than any other release - no need to take a survey on this BTW.

But now the sun appears to be setting on it, the faint tones of the 'last post' can be heard floating across the water and the swan is duetting with the fat lady.

We should not be roasting it's corpse in a flame-fest. We should be respecting it as an elder-statesman of our community ( hopefully though unlike Margaret Thatcher it will not write a book (-: ), who has brought great benefits to us all. 

Indeed I would suggest that it's widespread use will continue for some time yet. So, IMHO don't write it off just yet. Just because it has problems does not mean that people cannot benefit from it.

As I said just my 0.02's worth. 

IAP


------------------------------

From: ijackson@nyx.cs.du.edu (Ian Jackson)
Subject: *** PLEASE READ THIS BEFORE POSTING *** (misc-2.06)
Date: Fri, 22 Oct 1993 10:03:02 GMT

Please do not post questions to comp.os.linux.misc - read on for details of
which groups you should read and post to.

If you have a question about Linux you should get and read the Linux Frequently
Asked Questions with Answers list from sunsite.unc.edu, in /pub/Linux/docs, or
from another Linux FTP site.  It is also posted periodically to c.o.l.announce.

In particular, read the question `You still haven't answered my question!'
The FAQ will refer you to the Linux HOWTOs (more detailed descriptions of
particular topics) found in the HOWTO directory in the same place.

Then you should consider posting to comp.os.linux.help - not
comp.os.linux.misc.

Note that X Windows related questions should go to comp.windows.x.i386unix, and
that non-Linux-specific Unix questions should go to comp.unix.questions.
Please read the FAQs for these groups before posting - look on rtfm.mit.edu in
/pub/usenet/news.answers/Intel-Unix-X-faq and .../unix-faq.

Only if you have a posting that is not more appropriate for one of the other
Linux groups - ie it is not a question, not about the future development of
Linux, not an announcement or bug report and not about system administration -
should you post to comp.os.linux.misc.


Comments on this posting are welcomed - please email me !
--
Ian Jackson  <ijackson@nyx.cs.du.edu>  (urgent email: iwj10@phx.cam.ac.uk)
2 Lexington Close, Cambridge, CB4 3LS, England;  phone: +44 223 64238

------------------------------

From: kroener@cs.uni-sb.de (Thomas Kroener)
Subject: Re: Bogomip
Date: 22 Oct 1993 10:15:28 GMT

In article <CF5pDD.tv@usenet.ucs.indiana.edu>, ericg@nickel.ucs.indiana.edu (Eric Chris Garrison) writes:
|> In article <CEKz9D.MC@scrum.greenie.muc.de>,
|>  <root@scrum.greenie.muc.de> wrote:
|> >choltje@ux1.cso.uiuc.edu (Christian Holtje) writes:
|> >
|> >>>>>>>Two more datapoints:
|> >>>>>>>486DX-33 -----> 16.5 bogomips
|> >>>>>>>486DLC-33 -----> 11.2 bogomips   (Cyrix cross between 386 and 486)
|> >>>>>>386DX-25  --> 3.91 BogoMips(tm).
|> >>>>>386DX-33/387DX-33 --> 6.03 BogoMips(tm)
|> >>>> 486DX66/2 --> 34.06 BogoMips (tm)
|> >>>386DX40   ---> 6.99 BogoMips (tm)
|> >>486DX50/2  ---> 25.0 BogoMips (tm)
|> >486SX25  ---> 12.24 BogoMips (tm)
|> 386DX40 ---> 7.29 BogoMips (tm)
|> 
|> I wonder why mine is faster than the other 386DX40?  I only have
|> 4 meg of memory.  Maybe it is the disk drive?  I have around a 19 ms 
|> access time...

386DX40 ---> 7.29 BogoMips (tm) seems to be normal, the DX40->6.99 BM is
to slow.

|> 
|> Eric

    ...Thomas

-- 
 -------------------------
|o Thomas Kroener        o|   Mittag ess' ich eigentlich nie,
|  thkro@stud.uni-sb.de   |    
|  kroener@cs.uni-sb.de   |       denn ich stuecke sehr spaet frueh...
|o TKROENER@OUTWORLD.ZER o|
 -------------------------

------------------------------

Date: 21 Oct 1993 00:08:00 +0100
From: bernd@xtreme.sh.sub.org (Bernd Christiansen)
Subject: Re: Linux Applications

Hi !

Where can the *Linux Software Map* be found ??

Thanks for answering (a silly ?) question !!

Bernd Christiansen
Hamburg, Germany
## CrossPoint v2.1 ##

------------------------------

Crossposted-To: comp.os.linux.development
From: karel@icce.rug.nl (Karel Kubat)
Subject: Icmake 6.07 is out
Date: Fri, 22 Oct 1993 11:16:37 GMT

Hi Linuxers:

Yes, yet another version of Icmake is out. I've uploaded it to 
tsx-11.mit.edu, so it should be moved to the appropriate location 
(sources/usr.bin) within a few days. In the meantime, if you want it, try 
beatrix.icce.rug.nl, pub/unix. The files are:
        icmake-6.07.tar.gz   --   archive with sources, DOS binaries,
                                  postscript doc file
        icmake.doc           --   installation notes, introduction, etc.

For those who haven't seen Icmake yet, below is the contents of icmake.doc.
Cheers,
Karel (karel@icce.rug.nl)

=============================================================================
                                ICMAKE
                  the Intelligent C-like MAKEr, or
                        the ICce MAKE utility

            Copyright (c) Frank B. Brokken and Karel Kubat

           ICCE, State University of Groningen, Netherlands
=============================================================================


Introduction
============

        Icmake is a hybrid between a 'make' utility and a 'shell script'
language.  Originally, it was concocted to provide a useful tool for
automatic program maintenance and system administrative tasks on MS-DOS
platforms.  As we learned to appreciate its flexibility, Icmake was
eventually ported to Unix platforms (SCO and Linux). By now Icmake also runs
on a HP-Unix platform.

        To give an impression of "what Icmake does", take a look at the
following makefile. It is used for automatic program maintenance, where it
is assumed that in some directory all files with the extension ".c" (C
source files) constitute a program "myprog". The automatic maintenance makes
sure that, once Icmake is invoked, C source files which are more recent
(newer) than a library file "libmyprog.a" are recompiled and placed in the
library. A new program is then made and installed in a directory
"/home/user/bin".

void main ()
{
    list
        cfiles;                                 // list of .c files
    int
        i;                                      // counter variable
    string
        sourcefile;                             // string with name of
                                                // 1 source file

    cfiles = makelist ("*.c", younger,          // cfiles is now a list of
        "libmyprog.a");                         // all files to recompile

    if (cfiles)                                 // if there are any files..
        for (i = 0; i < sizeof (cfiles),        // recompile them
             i++)
        {
            sourcefile = element (i, cfiles);   // get the name from the list
            exec ("gcc", "-c -Wall", sourcefile); // recompile
        }

    if (makelist ("*.o"))                       // any "*.o" files here?
    {
        exec ("ar", "rvs", "libmyprog.a", "*.o");  // add to library
        exec ("rm", "*.o");                        // remove them
        exec ("gcc", "-o myprog", "libmyprog.a");  // re-link program
        exec ("mv", "myprog", "/home/user/bin");   // and install in bin dir
    }
}

        The source files for Icmake look remarkably like C sourcefiles. The
resemblance is so close that this cannot be pure chance!  Yes, we have
implemented Icmake to be a language with a syntax which largely overlaps C.
Since we know how to program in C, we decided that we didn't want to learn
some new macro language.  The Icmake language is a "subset" of C in the
sence that not all operators or functions of C are implemented (but a good
deal are, e.g., gets(), getch(), printf(), etc.).  The Icmake language has
its own extensions to make it a handy language for the purpose of
maintenance: e.g., the operator "younger" compares two files in respect to
their date of last modification, a type "list" is defined to hold several
strings.

        The usage of Icmake is not restricted to program maintenance. The
setup, which allows for functions, arguments, local or global variables, the
calling of external programs, etc.  makes Icmake also extremely suitable as
a shell script language.  E.g., it is easy to accomplish to let Icmake
figure out which files need to be backupped since the last backup date and
to start a process to do so, to send mail about it etc.

        This guide provides a short description how Icmake can be ported to
new platforms.  The documentation for the usage of Icmake, including a
description of the grammar and of all built-in functions, comes with the
distribution files.


Installing Icmake
=================

        The installation files for Icmake come as an archive, e.g.,
"icmake.zip" or "icmake-6.00.tar.gz". These archives unpack to several
directories and files. Please note that the archives unpack to the *current*
directory.

        To unpack the archives, create an appropriate directory (e.g.,
"/usr/local/src/icmake" for Unix platforms, or "c:\c\icmake" for DOS) and
change-dir to that directory. Use an appropriate archiver to unpack. Some
possibilities are described below:

(a) The archive in the form ".tar.Z" can be unpacked using
"cat icmake-5.00.tar.Z | uncompress | tar xvf -"

(b) Archives in the form ".tar.gz", ".tar.z" or ".tgz" can be unpacked using
"gzip -c -d icmake-5.00.tar.gz | tar xvf -"

(c) The archives with the extension ".zip" can be unpacked using
"unzip icmake.zip" or "pkunzip -d icmake.zip".

        The extraction of files from the archive should yield a lot of C
source files in a number of directories. The default distribution of Icmake
may or may not contain makefiles for the Unix-utility "make"; but the
programs can always be created by compiling all files "by hand".
Furthermore, the directory "dosbin" contains compiled versions of the Icmake
programs for DOS platforms.

        To compile all files "by hand" in order to make the programs, please
follow these steps:

(a) Change-dir to the directory "rss". This directory contains sourcefiles
for the Runtime Support System. These functions are used in all the programs
of the Icmake family.

Compile all files, using the appropriate compiler flags which cause your
compiler to compile-only and which cause it to treat "char"s as "unsigned
char"s.  If your compiler supports memory models, choose the "small" model.
E.g., these compiler flags are:

        for GNU's gcc:                  gcc -c -funsigned-char
        for Microsoft C 7.00:           cl -c -J -AS

While compiling, you may need special definition flags to produce workable
code for 'exotic' (well.. exotic to me) systems. Please check the section
below to see if you need any special flags.

Next, place the produced object files into one library. A suggested name is
"libicrss.a" for Unix systems, or "icrss.lib" for DOS systems.  See the
documentation of your library manager ("ar" or "lib") for the required
command line.  E.g., for Unix systems try "ar rsv libicrss.a *.o" in the
directory "rss".

(b) The following five directories must also be created from the archive:
"make", "pp", "comp", "exec", "un". The directories hold respectively the
files needed for the top-level program "icmake", for the preprocessor
"icm-pp", for the compiler "icm-comp", for the executor "icm-exec" and for
the unassembler "icmun". These program names are on Unix-based systems
without extension; supply ".exe" for DOS.

Change-dir to each of these directories, and compile and link all .c files
into the appropriate program. E.g., for a Unix system you might type:
        cd make
        gcc -funsigned-char -o icmake *.c ../rss/libicrss.a
        cd ../pp
        gcc -funsigned-char -o icm-pp *.c ../rss/libicrss.a
        cd ../comp
        gcc -funsigned-char -o icm-comp *.c ../rss/libicrss.a
        cd ../exec
        gcc -funsigned-char -o icm-exec *.c ../rss/libicrss.a
        cd ../un
        gcc -funsigned-char -o icmun *.c ../rss/libicrss.a
        cd ..
For a DOS platform with the Microsoft compiler, you might type:
        cd make
        cl -AS -J -Feicmake.exe *.c ..\rss\icrss.lib
        cd ..\pp
        cl -AS -J -Feicm-pp.exe *.c ..\rss\icrss.lib
        cd ..\comp
        cl -AS -J -Feicm-comp.exe *.c ..\rss\icrss.lib
        cd ..\exec
        cl -AS -J -Feicm-exec.exe *.c ..\rss\icrss.lib
        cd ..\un
        cl -AS -J -Feicmun.exe *.c ..\rss\icrss.lib
        cd ..

Whichever platform you use, please make sure to include the "unsigned chars"
flag when compiling, and name the resulting program by the appropriate name
(one of "icmake", "icm-pp", "icm-comp", "icm-exec", "icmun", optionally
followed by an extension ".exe" for DOS systems). The reason for this is the
fact that the top-level program "icmake" must be able to call all subsequent
programs, of which the names therefore must be known. Furthermore, you may
need special compilation flags for rare systems (see the section below).

During the compilation your compiler may report some warnings. You can
ignore these.

(c) If all goes well, you've now created all necessary programs. Move the
executable files to a system directory; e.g., "/usr/local/bin" for Unix
systems, "c:\sys\bin" for DOS systems, etc.

(d) For all subsequent releases of Icmake which you may wish to install, you
can use your old programs of the Icmake family and the included icmake-files.
E.g., the installation includes a file "unix.im" to create Icmake for Unix
platforms. Prior to using the makefiles, you may wish to edit this file, to
define your favorite compiler, your system directory, etc. Even when you
successfully create Icmake by hand, it may be a good idea to re-make it with
the makefile to check its workings. Just type "icmake unix", or "icmake
dos-msc" or whatever is appropriate; then follow the instructions which are
printed by the makefile.


Special flags while compiling
=============================

        A large part of the source code of Icmake should compile on any
platform. The exceptions we have encountered so far are the following:

(a) On MSDOS platforms, the constant MSDOS must be defined. This symbol is
by default defined by the Microsoft compiler. For other compilers on DOS
systems, a flag "-DMSDOS" may be necessary when invoking the compilations.
Non-DOS systems should, obviously, *not* have a defined symbol MSDOS.

(b) Sparc stations which require double-word alignment, require that the
constant SPARC be defined. Parts of the code, especially the file
"comp/patchup.c", handle assignments differently when SPARC is defined. On
such systems, "-DSPARC" should be added to the compiler flags. (Many thanks
to Wilco Oelen (W.Oelen@el.utwente.nl)).


The Documentation
=================

        Icmake is documented in a Postscript file, "icmake.ps", located in 
the directory "doc".  This file is generated from a .dvi file using dvips, 
and can be processed with GhostScript.  Note that the file is generated for 
a printer resolution of 300 dpi, which suits a LaserJet family printer.  If 
your site lacks the means to print this file, you can mail us at the address 
below to obtain a printed copy of the documentation.  (However, we will 
charge you a small amount to cover our costs).  

        The directory "doc" furthermore contains the file "icmake.1". This 
is a crude "man" page for Unix systems.  You can install it by copying it to 
a directory which contains formatted manual pages.  To use this feature, 
your "man" command must be able to show an already-formatted manual entry.  
E.g., on Linux systems you can copy this file to "/usr/man/cat1".  Typing 
"man icmake" will then show the information.  Some man systems also support 
compressed manual pages.  On these systems you may achieve a lower disk 
usage by compressing the file "icmake.1" to "icmake.1.Z", using the Unix 
program "compress".  

        A few makefiles are provided as examples in the directory
"examples". You may wish to look at these to see how makefiles can be
organized.


Some Legal Stuff
================

        Icmake is shareware. This means that no fee is charged for it. As
with everything that's free, there's no pay but also *absolutely no
warranty*.  Furthermore, you are allowed (and encouraged) to distribute
Icmake, provided that you include this information with each distribution
and provided that you do *not* charge any amount for it.  Not even the $5
for shipping.

        The source files and the documentation for Icmake are copyrighted by
us.  The reason for this is (a) that we'd like to have always the last
version of Icmake, and (b) that we'd like to have the last word in all
modifications.  If you have requests (or even better, "working code" to
include in Icmake) please mail us and we'll gladly oblige when we find the
time.


Requests, Bug Reports, etc.
===========================

        It is possible, even highly likely, that the version of Icmake which
you received contains bugs. We are continuously fighting a battle against
the insects which pop up from time to time to tease us.

        Therefore, we'd very much appreciate it if you'd let us know if you
encounter any bugs. Also, if you have requests or comments about the
programs or the documentation, mail us. We can be reached at:

                Frank Brokken                   Karel Kubat
e-mail:         F.B.Brokken@icce.rug.nl         K.Kubat@icce.rug.nl
phone:          (+31) 50 63 36 88               (+31) 50 63 36 47
address:        Westerhaven 16                  Westerhaven 16
                Groningen                       Groningen
                Netherlands                     Netherlands

-- 
                      The ICCE usenet account
                   providing access to usenet news
                      for the ICCE Experience 
               _WERKEN_AAN_DE_GRENZEN_VAN_HET_KUNNEN_

------------------------------

From: root@miki.toppoint.de (Michael Schack)
Subject: Re: Collage: Ported to Linux on sunsite.unc.edu (Very ALPHA)
Date: Fri, 22 Oct 1993 10:48:08 GMT

elie@netcom.com (Elie I. Mourad) writes:

>You can find the binaries at:
>             sunsite.unc.edu:/pub/Linux/Incoming/collage*
>You'll need 5MB+ for the uncompressed executables.
>I still have to upload the HDF libraries, but you can try the module on a GIF
>image.
>For a quick start:  collage -load file.gif

>                                                Regards, Elie.
>                                                mourad@three.dts.harris.com

Hi Elie,

great work! Is there a chance for a collage_server (with Linux)? I tried
the sources from ncsa.uiuc.edu but I'll need motif-lib's or what?

bye. micha...







------------------------------

Date: Fri, 22 Oct 1993 10:35:59 CET
From: Karl Keyte, ESOC Darmstadt <KKEYTE@ESOC.BITNET>
Subject: ftp - displaying dir info when cd-ing

Can anyone tell me how one gets anonymous ftp to display the text
when someone cd's into a directory?  'sunsite' for example gives
some intro stuff when you do a 'cd pub/Linux'.  I presume I have
to create a file in the directory, but what's it called?

Anyone?

Thanks, Karl

------------------------------

From: gloege@Informatik.TU-Muenchen.DE (Andreas Gloege)
Subject: Questions : xload, login
Date: Fri, 22 Oct 1993 12:02:16 GMT


Thanks now for any help from you with df and swapfile ... !

I have Linux with X succesfully installed. Now there are some questions :

        1. Is it a known bug that xload after some minutes (or hours)]
           of working, only values of load 0 shows. (the program top
           does not). Xload shows nothing but a line on the bottom ???
        
        2. I am using lilo, to boot from harddisk. When I login, I have
           to insert every time the VGA-Mode for displaying (ex. 0...6)
           If I boot from disk I don't have to do so (I have used rdev)

        3. Is it possible when starting LINUX to automatically start X
           and than something like a login - Window appears ????

For any help I would be very thankful.
        
        ciao    Andreas

==========================================================================
                Andreas Gloege
        smail : Limesstrasse 28a, 81243 Muenchen, Germany, ~089/870436
        email : gloege@Informatik.TU-Muenchen.DE
==========================================================================


------------------------------

From: jhelberg@nlsun8.oracle.nl (Joost Helberg)
Subject: Re: Bogomip
Date: Fri, 22 Oct 1993 11:25:17 GMT

In article <CF5pDD.tv@usenet.ucs.indiana.edu> ericg@nickel.ucs.indiana.edu (Eric Chris Garrison) writes:
   In article <CEKz9D.MC@scrum.greenie.muc.de>,
    <root@scrum.greenie.muc.de> wrote:
   >choltje@ux1.cso.uiuc.edu (Christian Holtje) writes:
   >
   >>>>>>>Two more datapoints:
   >>>>>>>486DX-33 -----> 16.5 bogomips
   >>>>>>>486DLC-33 -----> 11.2 bogomips   (Cyrix cross between 386 and 486)
   >>>>>>386DX-25  --> 3.91 BogoMips(tm).
   >>>>>386DX-33/387DX-33 --> 6.03 BogoMips(tm)
   >>>> 486DX66/2 --> 34.06 BogoMips (tm)
   >>>386DX40   ---> 6.99 BogoMips (tm)
   >>486DX50/2  ---> 25.0 BogoMips (tm)
   >486SX25  ---> 12.24 BogoMips (tm)
   386DX40 ---> 7.29 BogoMips (tm)
Pentium ---> 23.96 BogoMips (tm)

A bit disappointing, isn't it?
--
   Joost Helberg                              Rijnzathe 6
   jhelberg@oracle.nl                         NL-3454 PV De Meern
   jhelberg@nl.oracle.com                     The Netherlands

   Oracle Europe BV                           Product Line Development  
   Phone: +31 3406 94211                      Fax:   +31 3406 65609

------------------------------

From: na2@doc.ic.ac.uk (Nicholas Ambrose)
Subject: Re: Questions : xload, login
Date: 22 Oct 1993 13:12:55 +0100


In article <1993Oct22.120216.11166@Informatik.TU-Muenchen.DE>, gloege@Informatik.TU-Muenchen.DE (Andreas Gloege) writes:
|> 
|> Thanks now for any help from you with df and swapfile ... !
|> 
|> I have Linux with X succesfully installed. Now there are some questions :
|> 
|>      1. Is it a known bug that xload after some minutes (or hours)]
|>         of working, only values of load 0 shows. (the program top
|>         does not). Xload shows nothing but a line on the bottom ???
|>      
|>      2. I am using lilo, to boot from harddisk. When I login, I have
|>         to insert every time the VGA-Mode for displaying (ex. 0...6)
|>         If I boot from disk I don't have to do so (I have used rdev)
|> 
|>      3. Is it possible when starting LINUX to automatically start X
|>         and than something like a login - Window appears ????
|> 
|> For any help I would be very thankful.
|>      
|>      ciao    Andreas
|> 
well, i dont know about xload ( and i havent got the time to spend watching it
for hours to see if the same thing happens on mine!)

but, i know that if you re-compile the kernel, it is possible to fix the screen
mode that is set on boot-up, rather than having to specify it each time. it is
defined in one of the make files i think, and the docs for making a kernel
do explain how to set it.

also, i think that loding up xdm (x display manager) after all the other 
daemons are loaded, will present an X-windows login type affair window, which
allows you to log in ( funnily enuff) and will load up you X-session for you

hope some of this makes sense.
Nick
-- 
The sooner you make your first 5000 mistakes, the sooner you will be
able to correct them.
                -- Nicolaides

------------------------------


** 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-Misc-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: Linux-Misc@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-Misc Digest
******************************