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

Linux-Development Digest #180, Volume #1         Fri, 22 Oct 93 08:13:09 EDT

Contents:
  Can I run Linux on Pentium PC? (R. Ramesh)
  Re: /dev not needed? (Keith Smith)
  Internet connectivity [RE: Puzzled by internet] (Robert Moser)
  NCR SCSI Controller (Mathias Koerber)
  Re: QIC-150 Drivers... (Hennus Bergman)
  Re: ugly name for core dumps (core.imagename) -> patch for "img.core" (Joost Helberg)
  Icmake 6.07 is out (Karel Kubat)

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

From: ramesh@utdallas.edu (R. Ramesh)
Subject: Can I run Linux on Pentium PC?
Date: 22 Oct 1993 03:10:48 GMT

Hi:

We are planning to buy quite a few Pentium PC's to put in Labs. I see that
Gateway has one that has PCI/ISA bus. Will this cause any problems with Linux?
Can I access a PCI based video card the normal way? What about buying other
hardware like ethernet cards and SCSI adapters?

Since I thought answering my questions needs deeper understanding of kernel
that only kernel developer/hacker has, I am posting this to this group.
I am sorry if this is inappropriate (but please reply).

Thanks much.

Ramesh
ramesh@utdallas.edu

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

From: keith@ksmith.com (Keith Smith)
Subject: Re: /dev not needed?
Date: Fri, 22 Oct 93 03:08:38 GMT

In article <WAYNE.93Oct20074034@backbone.uucp>,
Wayne Schlitt <wayne@backbone.uucp> wrote:
>In article <1993Oct19.234432.1474@kf8nh.wariat.org> bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
>> Somehow I can't foresee either the Linux camp or the BSD camp taking such a
>> worry seriously.
>
>Not _requiring_ a compiler to rebuild the kernel is an advantage.
>Because you don't have to have disk space taken up by a compiler, or
>spend the time to run the compiler, it means that you can reconfigure
>things on a system that has a smaller disk, and quite possibly do the
>reconfiguration much quicker.

While I agree in principle ...

The reality is the likes of such things as space.c type files that
control certian kernal parameters.  SCO (for example) provides a broken
compiler in 'ld' that has just enough brains to compile extrememly
simple 'C' source, and no user libraries, to facilitate the rebuilding
of the kernel.

I would _love_ to see linux with a more modular independent kernel that
could be re-compiled/linked more quickly though.  It seems all the code
in the drivers are dependendent on each other.  Also it appears that the
drivers are major device number aware. <sigh>.

-- 
Keith Smith          keith@ksmith.com              5719 Archer Rd.
Digital Designs      BBS 1-919-423-4216            Hope Mills, NC 28348-2201
Somewhere in the Styx of North Carolina ...

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

From: araw@elm.circa.ufl.edu (Robert Moser)
Crossposted-To: comp.os.linux.admin,comp.os.linux,comp.os.linux.help,comp.os.linux.misc
Subject: Internet connectivity [RE: Puzzled by internet]
Date: 22 Oct 1993 01:35:16 GMT

To everyone curious what happened to the "Puzzled by internet" followup:

The articles finally stopped trickling in yesterday.  Here they are:

From dave@humbug.demon.co.uk Sun Oct 17 05:30:38 1993
From: Dave Hudson <dave@humbug.demon.co.uk>
Subject: no subject (file transmission)
Date: Sun, 17 Oct 1993 09:14:29 +0100 (BST)

To: araw@elm.circa.ufl.edu (Robert Moser)
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin
Organization: Dave's Linux Box
X-Newsreader: TIN [version 1.2 PL1]

> I would welcome postings and mail regarding other internet connections
> available to individuals.  I will post a summary article of the mail
> responses I receive.

Well I guess you're looking for US connections, but if you want all
connections (so it will be usefull to everyone on the net), in the UK
there's Demon Internet (all of us with .demon.co.uk :-) in our names).  The
charge is 11.75 UK pounds (about $17) per month with about the same as a one
time startup fee.  That gives you modem access (up to 16.8k I think, but I
always run at 14.4k), with full mail, news, ftp, etc.

The demon ftp site holds scripts for Linux mail, news, and SLIP connection.

===============================================================================
Dave Hudson                                             dave@humbug.demon.co.uk
===============================================================================

From jes@grendel.demon.co.uk Sun Oct 17 13:56:14 1993
Date: Sun, 17 Oct 93 17:47 GMT
From: jes@grendel.demon.co.uk (Jim Segrave)
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin

In article <29qg0tINNj6f@no-names.nerdc.ufl.edu> you write:
>In article <1993Oct16.214822.18084@cobra.uni.edu> simmonr5387@cobra.uni.edu writes:
>
>>at colleges who want to get internet on ETHERNET accomplish this miracle
>>without running a cable 400 miles to the nearest connected site. I am 
>>sure that I am missing something here. I am interested in the hardware 
>
>How do the colleges do it?  They do precisely what you said they wouldn't do,
>they run a cable 400 miles to the nearest connect.  Actually, they generally
>lease a line from a data carrier.  Most of the long distance carriers offer
>this.  At UF, T1 lines are used to connect us to SURA net in Maryland.  
>Most institutions will use T1 (1.5MBPS) and T3 (42MBPS) lines, depending on
>traffic.  AT&T, Sprint, WilTel and many others offer these services.  In
>addition, a gateway is required at each end.
>
>>I want to know,
>>1) what hardware is required 
>>2) how to get my beautiful new pentium based linux system internetted
>>via internet and the total estimated cost outlay for this. 
>
>If you as an individual want internet, by far the cheapest is to get some
>kind soul to give you a slip connection from campus.  Since these are hard
>to come by, there is at least one commercial offering available.  UUNET
>offers dialup slip for the neighborhood of $250 per month, with a one-time
>startup fee (I don't remember how much).  They offer higher rate connections
>upto 10MBPS, but they get out of the reach of individuals.  
>
>I would welcome postings and mail regarding other internet connections
>available to individuals.  I will post a summary article of the mail
>responses I receive.
>
>Hope this helps,
>
>ARAW

Not much help, but here in the UK, Demon Internet Services offers SLIP
dialup for UKP 10 /month - about $17/month. There are no setup charges
and no connectr time charges - except the phone company itslef. They run
three dial in sites around the country - one in London, one in Warrington 
about halfway up the country, and one in Scotland. Each customer has
a permanently assigned IP address. Demon acts as an MX site and holds
mail for users. While connected, you are a full internet host - demon is
simply a router. They also take a full Usenet feed - about 300Mb/day and
hold news for 10 days. All in all a superb deal. In about 1 1/2 years of
operation they have gone from 150 users to about 2000 odd, plus commercial
links for businesses.

-- 
Jim Segrave        (Segrave Software Services jes@grendel.demon.co.uk)


From pshrink!veck@mcs.com Sun Oct 17 14:19:08 1993
Date: Sun, 17 Oct 93 09:35 CDT
From: veck@pshrink.chi.il.us (Steven King)
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin

[my stuff deleted]

Dial-up SLIP access is getting more and more common.  It's available
quite inexpensively from a number of suppliers.  Check the PDIAL list
(posted in several newsgroups and available at rtfm.mit.edu) for a good
listing of Internet providers, including a number of SLIP/PPP providers. 

I know that in the Chicago area alone there are several suppliers.  My
UUCP host offers SLIP links for the same price as UUCP links.  That is,
approximately $1.00/hour, $15/month minimum!  Now *THAT'S*
entertainment!  There are other competing vendors, but I don't know much
about them. 

My host is MCSnet, run by Karl Denninger.  Write to info@genesis.mcs.com
if you want the rate sheet.

--
Steven King, Proprietor of the PShrink Wrap BBS         veck@pshrink.chi.il.us
Data Communications for the Psychology Professional      2400: +1 708 487 9727
"Put your analyst on danger money, baby...  Now!"       14400: +1 708 487 5864

From truffula!cls@hustle.rahul.net Sun Oct 17 21:38:55 1993
Date: Sun, 17 Oct 93 18:13 PDT
From: cls@truffula.sj.ca.us (Cameron L. Spitzer)
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin

In article <29qg0tINNj6f@no-names.nerdc.ufl.edu> you write:
[my stuff deleted]

I use a uucp link to a commercial connectivity retailer.
For US$20/month, I get email, file transfer, and a limited (100 MB/month)
Usenet News feed.  I also get a shell on a well-connected, carefully
administered system when I need it for archie and browsing newsgroups
I don't have at home.  For me, SLIP would be overkill.

Cameron
cls@truffula.sj.ca.us

From bsmart@bsmart.tti.com Mon Oct 18 19:16:17 1993
Date: Mon, 18 Oct 93 16:17:29 PDT
From: bsmart@bsmart.tti.com (Bob Smart)
To: araw@elm.circa.ufl.edu (Robert Moser)
Subject: Re: Puzzled by internet

In your summary of ways for individuals to get connected to the Internet, you might want to mention Ed Krol's book, The Whole Internet Resource Guide and Catalogue.  In the back is a list of access providers, broken down by geographic region, which tells how to contact them and what kinds of access they offer.

You might also want to mention the NIXPUB list, which also serves as a directory of service providers but is available online and so gets updated regularly (monthly, I think).

=========

A fanatic is someone who does what he knows that God would do if God knew the
facts of the case.

From dlc@access.digex.net Mon Oct 18 08:01:56 1993
Date: Mon, 18 Oct 1993 08:02:59 -0400
From: "David L. Craig" <dlc@access.digex.net>
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin

In article <29qg0tINNj6f@no-names.nerdc.ufl.edu> you write:
>
>I would welcome postings and mail regarding other internet connections
>available to individuals.  I will post a summary article of the mail
>responses I receive.
>

In addition to its standard access service ($25 monthly, $250 annual),
Digital Express now provides SLIP/PPP links for those that are interested
in having their own machines connected to the network. There are two levels
of SLIP accounts:

Business IP:    $99 install, $45 monthly
                Separate namespace/domain name

Personal IP:    no install, $35 monthly
                Registered as <hostname>.digex.net

For more information or to sign up, contact one of the following:

Technical questions:    Send mail to help@access.digex.net
Sales questions/signup: Call 301-220-2020 and ask for Andy Bartalone

From john@bilton.demon.co.uk Tue Oct 19 02:56:00 1993
Date: Mon, 18 Oct 93 18:48 GMT
From: John Burton <john@bilton.demon.co.uk>
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet
Newsgroups: comp.os.linux.admin

In article <29qg0tINNj6f@no-names.nerdc.ufl.edu> you write:
>In article <1993Oct16.214822.18084@cobra.uni.edu> simmonr5387@cobra.uni.edu writes:
>
>I would welcome postings and mail regarding other internet connections
>available to individuals.  I will post a summary article of the mail
>responses I receive.

I'm not sure it you wanted non-USA internet connections but I connect my
linux machine through demon internet services who offer a SLIP connection
to internet for 10 pounds per month.

-- John Burton

From jkaidor@synoptics.com Tue Oct 19 20:37:28 1993
Date: Tue, 19 Oct 93 17:36:27 PDT
From: Jerome Kaidor <jkaidor@synoptics.com>
To: araw@elm.circa.ufl.edu
Subject: Re: Puzzled by internet

In article 29qg0tINNj6f@no-names.nerdc.ufl.edu, araw@elm.circa.ufl.edu (Robert Moser) writes:
[my stuff deleted]
[IMHO, this is another excellent way to go]
  **** One can get many of the benefits of Internet through a UUCP connection.
This can be gotten for cheap or for free in many places.  A uucp connection gets
you email and News.

     A free uucp connection can be found by:

    1)  Getting the uucp maps for your area from comp.mail.maps. ( I know, chicken&egg here )
    2)  Looking through the maps for occurrences of the name of your home town, or other
          towns that are in your local calling area.
     3)  Calling up the nice sysadmins whose name and numbers are listed in the list entries.

               - Jerry Kaidor ( jkaidor@synoptics.com, jerry@tr2.com )





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

From: mathias@solomon.technet.sg (Mathias Koerber)
Crossposted-To: comp.periphs.scsi,comp.os.linux.misc
Subject: NCR SCSI Controller
Date: 22 Oct 93 05:18:06 GMT

I have an ICL ErgoPRO D486/66dXG that has on the motherboard a NCR 53C94
SCSI controller. DOS (via BIOS) can use the controller fine, but Linux
does not know how to handle it.

Does anyone know where I can get
        a) either a driver for that chip
    or  b) technical specs so that I can try and write the driver myself
          (if that is not too hard to do)?

Any pointers are appreciated.

--
Mathias Koerber                     | Tel: +65 / 7780066 ext 29
SW International Systems Pte Ltd    | Fax: +65 / 7779401
14 Science Park Drive #04-01        |
The Maxwell, Singapore Science Park | email: mathias@solomon.technet.sg
Singapore 0511                      |        swispl@solomon.technet.sg
===============================================================================
  * Eifersucht ist eine Leidenschaft die mit Eifer sucht was Leiden schafft *

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

From: hennus@sky.nl.mugnet.org (Hennus Bergman)
Subject: Re: QIC-150 Drivers...
Date: Wed, 20 Oct 1993 14:27:18 GMT

In article <2a19tb$f6s@wvhpadm1.mentorg.com>,
Dave Clemans <dave_clemans@mentorg.com> wrote:
>One other note...
>
>tpqic02.* assumes that the drive supports a "set density" command.
>There are drives that don't; indicated by getting an "illegal command"
>status back whenever the drive is opened.  An example is the Teac
>150mb data cassette drive.
>
>To work with those drives, you'll have to ifdef out the code that
>tries to issue a "set density" command. The obvious ifdef is the
>flag TP_HAVE_DENS (or something like that) from tpqic02.h.
>
If your drive doesn't support the set density command, you should
be able to use a device file with minor number 0. [Mine does support it,
so I haven't tested this lately...]
Note that doing a `mt rewind' or any other `mt' command will
implicitly use the the default tape drive device [/dev/tape or
${TAPE}] which may force setting density, if the minor number
is not 0.

>dgc
>

Hennus


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

From: jhelberg@nlsun8.oracle.nl (Joost Helberg)
Subject: Re: ugly name for core dumps (core.imagename) -> patch for "img.core"
Date: Fri, 22 Oct 1993 08:31:56 GMT

In article <CF9sJz.3qr@Colorado.EDU> drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:
   In article <RFRANKEL.93Oct21112742@obelix.obelix.us.oracle.com>,
   Rick Frankel <rfrankel@us.oracle.com> wrote:
   >(Sorry about the null prev. message, I seem to be hitting a lot of
   >wrong keys lately :{)
   >
   >In article <koenig.751208718@nova> koenig@nova.tat.physik.uni-tuebingen.de (Harald Koenig) writes:
   >
   >koenig> I find it's a good idea to get "named" core dumps for each
   >koenig> image but the current naming convention in pl13 isn't that
   >koenig> good since - you can't find and remove all core.* files (some
   >koenig> people call source files core.c or core.h
   >
   >I agree, I have the same problem in pl12. core.[ch] is EXTREMELY
   >common (I think it's even in the gcc source), so it is very dangerous
   >to search and destroy core files wiht the current implementation


   BTW - in cases where users are doing development, you shouldn't delete core
   files from users home directories.  Instead, have you script mail them with
   a polite suggestion to remove the core files found in their directory (with
   a list of the core files) when they nolonger need them, and to prevent messages
   like this, they should move the core files to something other than core.*.

   Implementing this is left as an exercise for the reader.

I agree, core files are usefull! Don't remove them. 
`You are only allowed to remove a core-file iff you solved the problem causing it'
is a great rule that applies here and works great!
--
   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

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

Crossposted-To: comp.os.linux.misc
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_

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


** 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
******************************