Subject: Linux-Development Digest #806
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:     Wed, 8 Jun 94 14:13:11 EDT

Linux-Development Digest #806, Volume #1          Wed, 8 Jun 94 14:13:11 EDT

Contents:
  ** HP built-in network patch ** (Laurent JULLIARD)
  Re: NCurses 1.8.5 (Stuart Herbert)
  Re: 1.1.17 and no networking won't compile (John Hayes)
  Re: Filesystem semantics (John Will)
  Support for Intel Above B (John Will)
  bash-1.14 suggested patch please comment (Neal Becker)
  (none) (David Bakin)
  Does Linux use any BIOS facilities? (Kevin P. Lawton)
  Re: Linux on Mac PPC's? (Hans Peter Engelhard)
  LSM: New Release: 05JUN94 (Jeff Kopmanis)
  LSM: Current Template w/explanations (Jeff Kopmanis)

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

From: laurentj@samsara.grenoble.hp.com (Laurent JULLIARD)
Date: Tue, 7 Jun 1994 13:04:20 GMT
Subject: ** HP built-in network patch **

Hello,


  Please find below a diff to be applied to the lance.c file. This patch
allows the LANCE driver to recognize the HP built-in network interface. This
interface is based on a 79C960 and is integrated on most recent HP
platforms.

  This patch has also been submitted to comp.os.linux.announce and will 
soon be implemented by Donald Becker in the original lance.c file.

Enjoy !
=========================== Cut here ====================================

*** lance.c.orig        Wed May 18 16:13:29 1994
--- lance.c     Tue Jun  7 08:52:05 1994
***************
*** 12,20 ****
  
      The author may be reached as becker@super.org or
      C/O Supercomputing Research Ctr., 17100 Science Dr., Bowie MD 20715
  */
  
! static char *version = "lance.c:v0.14g 12/21/93 becker@super.org\n";
  
  #include <linux/config.h>
  #include <linux/kernel.h>
--- 12,23 ----
  
      The author may be reached as becker@super.org or
      C/O Supercomputing Research Ctr., 17100 Science Dr., Bowie MD 20715
+ 
+     Modified by Laurent JULLIARD (Laurent_Julliard@grenoble.hp.com) to
+     detect built-in lance interface on HP machines
  */
  
! static char *version = "lance.c:v0.14h 07/06/94 becker@super.org\n";
  
  #include <linux/config.h>
  #include <linux/kernel.h>
*************** can be set with the low bits of the othe
*** 84,89 ****
--- 87,95 ----
  The HP-J2405A board is an exception: with this board it's easy to read the
  EEPROM-set values for the base, IRQ, and DMA.  Of course you must already
  _know_ the base address, but that entry is for changing the EEPROM.
+ Some code has been added to distinguish beetween a J2405A and a built-in
+ network interface. (Laurent_Julliard@grenoble.hp.com).
+ 
  
  III. Driver operation
  
*************** unsigned long lance_probe1(short ioaddr,
*** 241,257 ****
      struct device *dev;
      struct lance_private *lp;
      int hpJ2405A = 0;
      int i, reset_val;
  
      hpJ2405A = (inb(ioaddr) == 0x08 && inb(ioaddr+1) == 0x00
                && inb(ioaddr+2) == 0x09);
  
      /* Reset the LANCE.  */
      reset_val = inw(ioaddr+LANCE_RESET); /* Reset the LANCE */
  
      /* The Un-Reset needed is only needed for the real NE2100, and will
         confuse the HP board. */
!     if (!hpJ2405A)
        outw(reset_val, ioaddr+LANCE_RESET);
  
      outw(0x0000, ioaddr+LANCE_ADDR); /* Switch to window 0 */
--- 247,293 ----
      struct device *dev;
      struct lance_private *lp;
      int hpJ2405A = 0;
+     int hpbuilt_in = 0;
+     int hpaccport;
      int i, reset_val;
  
+ #define HP_SIO_MARKER   0x000F00F1
+ #define HP_ACCESS_PORT  0x98
+ 
+     /* This is to detect HP machine with a built in interface. */
+     if ( *((unsigned short *) 0x000F0102) == 0x5048 ) {
+ 
+         if ( *((unsigned short *) HP_SIO_MARKER) & 1) {
+             hpaccport = HP_ACCESS_PORT + 0x400;
+         } else {
+             hpaccport = HP_ACCESS_PORT;
+         }
+ 
+         if ( (inb(hpaccport) & 0x80) && (inb(hpaccport+1) & 0x80) &&
+              !(inb(hpaccport+1) & 0x40)) {
+ 
+             /* look if the configured ioaddr matches the one given */  
+             short ioaddr_tbl[4] = {0x300, 0x320, 0x340, 0x360};
+             if ( ioaddr_tbl[inb(hpaccport+1) & 0x3] == ioaddr ) {
+                 hpbuilt_in = 1;
+             } else {
+                 return mem_start;
+             }
+         }
+     }
+ 
+     /* this is a poor manner to detect a J2405, but... */
+     if (!hpbuilt_in) {
          hpJ2405A = (inb(ioaddr) == 0x08 && inb(ioaddr+1) == 0x00
                      && inb(ioaddr+2) == 0x09);
+     }
  
      /* Reset the LANCE.  */
      reset_val = inw(ioaddr+LANCE_RESET); /* Reset the LANCE */
  
      /* The Un-Reset needed is only needed for the real NE2100, and will
         confuse the HP board. */
!     if (!hpJ2405A && !hpbuilt_in)
          outw(reset_val, ioaddr+LANCE_RESET);
  
      outw(0x0000, ioaddr+LANCE_ADDR); /* Switch to window 0 */
*************** unsigned long lance_probe1(short ioaddr,
*** 310,321 ****
--- 346,371 ----
      outw(0x0000, ioaddr+LANCE_ADDR);
  
      if (hpJ2405A) {
+ 
          char dma_tbl[4] = {3, 5, 6, 7};
          char irq_tbl[8] = {3, 4, 5, 9, 10, 11, 12, 15};
          short reset_val = inw(ioaddr+LANCE_RESET);
          dev->dma = dma_tbl[(reset_val >> 2) & 3];
          dev->irq = irq_tbl[(reset_val >> 4) & 7];
          printk(" HP J2405A IRQ %d DMA %d.\n", dev->irq, dev->dma);
+ 
+     } else if (hpbuilt_in) {
+ 
+         char dma_tbl[4] = {3, 5, 6, 0};
+         char irq_tbl[8] = {3, 4, 5, 9};
+         short accport_val = inb(hpaccport+1);
+         dev->dma = dma_tbl[(accport_val >> 4) & 3];
+         dev->irq = irq_tbl[(accport_val >> 2) & 3];
+         printk(" HP built-in AMD 2100 IRQ %d DMA %d.\n", dev->irq, dev->dma);
+         if (dev->dma == 0) {
+             printk("...DREQs and IRQs disabled. Reconfigure the board\n");
+             return mem_start;
+         }
      } else {
      /* The DMA channel may be passed in on this parameter. */
      if (dev->mem_start & 0x07)




-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Laurent JULLIARD (Box 26)         | HPDesk: Laurent Julliard /HP6300/UM   ~
~ GND/High Speed Networking Lab     | Unix: Laurent_Julliard@grenoble.hp.com~
~ HEWLETT-PACKARD FRANCE            | Phone:  (33) 76 62 12 67              ~
~ 5, avenue Raymond Chanas - EYBENS | Telnet:        779 12 67              ~
~ 38053 GRENOBLE CEDEX 9            | Fax:    (33) 76 62 12 86              ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

From: ac3slh@sunc.sheffield.ac.uk (Stuart Herbert)
Subject: Re: NCurses 1.8.5
Date: 7 Jun 1994 16:58:56 GMT

Brian Stoler (sto2@netaxs.com) wrote:

: Well, I did the same as you, installed 1.8.5 over Slackware's default 
: 1.8.1, and yes, all ncurses apps' color broke. But after I recompiled 
: dialog, it worked fine. Try recompiling again .. and look at the Makefile?

Well, werase() in ncurses has been broken, as it no longer honours the
window's attributes (fixed that one).  There are other bugs hidden in
dialog - as soon as I've got rid of them all, I'll upload a patch file.

Stuart
--
Stuart Herbert -- S.Herbert@shef.ac.uk

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

From: jhh@scss3.cl.msu.edu (John Hayes)
Subject: Re: 1.1.17 and no networking won't compile
Date: 8 Jun 1994 13:57:42 GMT
Reply-To: jhh@scss3.cl.msu.edu

In article Ar5@pe1chl.ampr.org, rob@pe1chl.ampr.org (Rob Janssen) writes:
> In <1994Jun3.125831.42348@Lehigh.EDU> shl0@ihd117d.CC.Lehigh.EDU (Samson H. Lee) writes:
> 
> >I applied patch17 yesterday and tried recompiling the kernel.  I had
> >been including network support for TCP/IP and SLIP but decided to
> >remove network support until I really needed it.  (My university is in
> >the process of setting a SLIP server, but it's not ready yet.)  So I
> >tried leaving it out when I ran 'make config'.  I then ran 'make

> A previously reported problem is that the kernel won't compile when
> networking is turned off.   The responsible person is probably working
> on it.  For now, just enable networking.
> 

There may be more wrong with current releases of the kernel than this.
In comp.os.linux.help and comp.os.linux.admin there are postings where
users are complaining that gcc crashes with signal 11, signal 6 and signal 4
errors when compile jobs are being run. The report is that gcc will compile
fine when the system has been rebooted fresh but after it has been up for
a while gcc will crash, typically on longer jobs such as a kernel make.

My own experience has completely paralleled these reports. Typically, the
kernel will recompile fine after a reboot, but will fail if the machine
has been up for several hours before a kernel recompile is attempted. I am
using Linux 1.0.8 with the slackware distribution. In the NETWORK file
( approximate name ) found in /etc, the message is either "yes" or "on".
I forget which but I am using ppp at this time - and I installed the thing
off of the net. For ppp I'm using a minimal net configuration.

I also have problems with files not being found during a compile. At first
I thought that the distributions may have been deficient... but after reading
the above posts I'm not so sure. My compile problems have been so serious
that I have taken to finding binary releases for everything that I want as
I can build almost nothing that will finish making.

One problem with the layout and functionality of most news groups is that
things are posted in several different places. For instance, I posted my
report of problems with gcc and kernel compiles in comp.os.linux.help, as
I didn't want to be accused of posting in the wrong place. I also looked for
other postings reporting the same type of problems that I had been having
in that group. Nobody was suggesting any solutions there. Today I decided to
look in other places, and sure enough, people were talk about the same type
of problems in comp.os.linux.admin as well. 

I hope, by posting to com.os.linux.development, I have posted conspicuously
enough to attract some attention that may yield solutions.

If there us any advice to offer please send email to:
jhh@scss3.cl.msu.edu

Thanks, John Hayes


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

Subject: Re: Filesystem semantics
From: john.will@dscmail.com (John Will)
Date: Wed,  8 Jun 94 07:42:00 -0640

M >>My primary point which you failed to address was facility level reliablity
M >>problems caused by normal operational proceedures recovering from
M >>UNIX crashes .... due to poor filesystem designs, which include BSD/SUN/DEC.
M >
M >Since when are crashes part of normal operational procedures??  The
M >last time I rebooted was to install a UPS...
M >
M >A happy SunOS 4.1.3 user...

Boy, I'll have to second that!  I run the Sun IPX here on 4.1.3, and
the only time I've rebooted is when I notice the running time has gotten
to around 60 days.  I reboot then, but mostly to insure that some slow
memory leak doesn't get me, even then there's no indication that it's
necessary.  If this guy has a system that crashes that often, he's
obviously doing something very bad to it. :-)


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

Subject: Support for Intel Above B
From: john.will@dscmail.com (John Will)
Date: Wed,  8 Jun 94 07:47:00 -0640

ES>I recently got a intel above board ISA card and want to use this with my
ES>linux machine. When I install it, linux correctly recognizes the amount
ES>of memory available in the machine (12Mb), but crashes during mem_init....

If you ever find out, let me know. :-)  I tried a similar thing a long
time ago with an ISA extended memory board, and got the same results.
DOS ran fine with the card, but Unix crashed as soon as it attempted to
use the memory board's memory.  I'm just curious at this point... :-)

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

From: neal@ctd.comsat.com (Neal Becker)
Subject: bash-1.14 suggested patch please comment
Date: 08 Jun 1994 13:00:09 GMT

I have built bash-1.14 on linux 'out of the box'.  But I am wondering
if the following patch might be a little better.  As shipped bash-1.14
on linux defines USG and USGr3.  Linux is not really either.  I tried
a pure POSIX build instead.  It seems to work fine.  Does anyone see
anything wrong with this?  If not, I recommend it because it simpler
and cleaner.


--- ./lib/readline/rldefs.h-dist        Thu Jun  2 09:35:53 1994
+++ ./lib/readline/rldefs.h     Tue Jun  7 23:07:32 1994
@@ -2,6 +2,11 @@
    for readline.  This should be included after any files that define
    system-specific constants like _POSIX_VERSION or USG. */
 
+/* Let's make sure! (neal@ctd.comsat.com) */
+#ifdef HAVE_UNISTD_H
+#include <unistd.h>
+#endif
+
 /* Copyright (C) 1987,1989 Free Software Foundation, Inc.
 
    This file contains the Readline Library (the Library), a set of
--- ./machines.h-dist   Thu Jun  2 09:35:23 1994
+++ ./machines.h        Tue Jun  7 23:05:26 1994
@@ -756,8 +756,8 @@
 #    define done386
 #    define M_MACHINE "i386"
 #    define M_OS "Linux"
-#    define SYSDEP_CFLAGS -DUSG -DUSGr3 -DHAVE_GETDTABLESIZE -DHAVE_BCOPY \
-                         -DHAVE_GETPW_DECLS -DHAVE_GETHOSTNAME
+#    define SYSDEP_CFLAGS -DHAVE_GETDTABLESIZE -DHAVE_BCOPY \
+                         -DHAVE_GETPW_DECLS -DHAVE_GETHOSTNAME -D_POSIX_JOB_CONTROL
 #    define REQUIRED_LIBRARIES
 #    define HAVE_GETGROUPS
 #    define HAVE_STRERROR

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

From: dbakin@sybase.com (David Bakin)
Subject: (none)
Date: 8 Jun 1994 12:53:18 -0400
Reply-To: dbakin@sybase.com (David Bakin)

In article <2t367g$9ct@magus.cs.utah.edu> baford@cs.utah.edu (Bryan Ford) 
writes:
|From: baford@cs.utah.edu (Bryan Ford)
|Subject: Re: NTFS filesystem on disk layout
|Date: 8 Jun 1994 01:17:36 GMT

#1  The disk layout for NTFS is not released.
#2  Security ratings (B2 or otherwise) explicitly depend on physical security
    of the computer.  No claims need be made that if you steal the hard
    disk and install it in another machine -- or boot a different OS on the
    same machine and use Norton -- the data can't be accessed.

-- Dave

|Mikael Nykvist (viper@ludd.luth.se) wrote:
|>In <TVO.94Jun5182603@zaphod.swb.de> tvo@zaphod.swb.de (Thomas Vogler) writes:
|>>in order to do this, i will need some informations how NTFS files are stored
|>>on a disk.
|>
|>Because of the B2 (or was it C2 ?...) security, I dont think MS will release
|>any 'internal' info about NTFS... If they did, you could make a boot-disk
|>that could access the NTFS-partions and the security are lost..

|Yikes, if this is true then Microsoft is even dumber than I thought. :-)
|Security based on secret algorithms is not really security at all -
|good security is always based on widely known and easily testable algorithms.
|The only thing that needs to be kept secret is the passwords, keys, etc.

|However, all the same I wouldn't be surprised if Microsoft hasn't (and won't)
|release the disk format for NTFS.
|Maybe it's time out to pull out the disk editor...

--
Dave Bakin       "I can make cats break-dance; ask me how"
510-922-5678           -- seen on a license plate frame


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

From: kpl@ll.mit.edu (Kevin P. Lawton)
Subject: Does Linux use any BIOS facilities?
Reply-To: kpl@ll.mit.edu (Kevin P. Lawton)
Date: Wed, 8 Jun 94 16:05:47 GMT


Hi,

I'm curious if Linux uses any of the ROM BIOS facilities
which are inherent to the PC, or if it exclusively uses
its own facilities which are loaded upon booting.


Thanks much,
Kevin

-- 
+----------------------------------------------+
| "How does he know we're going the wrong way. |
|  He doesn't know where we're going."         |
|                                              |
| John Candy, "Planes, Trains and Automobiles" |
+----------------------------------------------+


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

From: engelhar@sun2.ruf.uni-freiburg.de (Hans Peter Engelhard)
Subject: Re: Linux on Mac PPC's?
Date: 8 Jun 1994 12:37:02 GMT

Philippe Steindl (ilg@imp.ch) wrote:
: Hullo People,

: is it true, that some people ware working on a MacPPC port of linux? If yes,
: would such a prt also run on the 1995 planned 604 ppcs?

: just my silly qestions :)

: Philippe Steindl

just an old answer:


From: more@power.globalnews.com
To: buggz@buggz.via.mind.org

COMP SCIENCE STUDENTS PORTING FREEWARE UNIX TO THE POWER MAC
(May 13th)Two computer science students at Bowdoin College in
Brunswick, Maine, USA are porting the free Linux Unix clone to the
Power Macintosh. Linux is a Posix-type Unix, originally written for
386/486-based PCs by Swedish programmer Linus Torvalds with the
assistance of a loosely-knit team working across the Internet. It is
freely distributable under the same term as the GNU Unix.

Charlton Wilbur and Jem Lewis began laying plans to developing a
freeware Unix on the Power Macintosh platform in January and say that
they hope to have a stable kernel running on the Power Mac by the end
of August, together with the basic Unix utilities (cd, ls, cp, mv,
gcc, emacs, vi, and bash). Until then, they want to keep the project
tightly controlled, but once it is running relatively bug-free, they
say that it will be freely available for Alpha testing and for others
to help develop device drivers etc. 

The new version of Linux for PowerPC cannot hope to  be binary
compatible with Intel Linux, however the pair say that they are
striving to maintain source code compatibility between the two
versions, so that a small amount of source tweaking and a re-compile
is all that is necessary to run existing Linux applications. They say
that they are currently  beginning to do some of the kernel design
and coding, and are beginning to port gcc. In a posting to
comp.linux.announce they said that they would appreciate not being
innundated with e-mail requests at the moment.

We'll keep you posted on developments.
(c)PowerPC News -  Free by mailing: add@power.globalnews.com

 Ed June   TeamOS2
(end of citation)

mfg Hans Peter
--
******************************************************************************
Hans Peter Engelhard                Phone:  0761/203-2440
                                    e-mail: engelhar@sun1.ruf.uni-freiburg.de
******************************************************************************

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

Crossposted-To: comp.os.linux.announce,comp.os.linux.help
From: jeffk@garnet.msen.com (Jeff Kopmanis)
Subject: LSM: New Release: 05JUN94
Reply-To: jeffk@garnet.msen.com (Jeff Kopmanis)
Date: Tue, 7 Jun 1994 17:19:11 GMT

LSM Release: 05JUN94
======================

[This is the Linux Software Map, a list of many software packages
available for Linux. --mdw]

The new version of the LSM was uploaded to sunsite.unc.edu in
/pub/Linux/Incoming/lsm-05jun94.gz and should be moved to /pub/Linux/docs
soon.  tsx-11.mit.edu's final version will appear in /pub/linux/docs also.

This is closer to what I had in mind a year ago when the LSM started.  
Periodic updates and timely releases.  FINALLY, my end has cleared up and I
have a system that is managable.  Took a while, but its here.

I have some issues that I've noticed over the last 2 months or so that
require quite a bit of editing on my part to get the entries to import
properly.  Nothing here is terribly earth-shattering, but with a little
help from YOU, the whole process can move smoother.

1. DATES.  A while back, there was a good deal of discussion about the date
   format used in the LSM.  Finally everyone agreed on ddMMMyy, a 7 character
   sequence that produces dates that look like this:  05JUN94, 22MAY94, etc.
   Stuff like "24 May 1994" and "Tues April 22, 1994 9:30:56 am" don't cut it.
   PLEASE do me a favor by properly formatting the dates.  Most come in good,
   but the exceptions take alot of time to fix up.

2. There seems to be some confusion over the Begin2/End KEYWORDS.  Yes, they
   are KEYWORDS and tell me the beginning and ending of an entry.  The 2
   is important, because it identifies the version number of the entry.

3. Unfortunately, Tabs are not considered to be white space in Visual BASIC.
   Please use spaces and not tabs.

4. Try to use the current template whenever possible.  It's easier on YOU!

5. Please try to stay away from some of those special characters (umlauts,
   hachas, enyays, etc), because they are 8-bit and non-standard.  7-bit
   ASCII characters (i.e. "Text" files) are preferred.  I don't think the
   8-bit chars are doing any harm, but there are NO guarantees of how they
   will show or what they will do with the WWW-type programs reading the LSM.

Again, these were some recurring problems that I noted as I was cleaning
up the entries to import.  If the date and Begin2/End problems are cured,
I'll be most happy, as they cause me the most grief.

And one word to the newbies out there...look in an accompanying article for
what exactly the LSM is.  It'll save alot of reiterative email replies.

Thanks for your help and support.  I hope to see you again in about a month!
-Jeff.  :)

--
Jeff Kopmanis       (Ann Arbor, Michigan)   |  email:  jeffk@msen.com
Organizer of the Linux Software Map (LSM)   |  phone: (313) 393-4784 (work)
"So shines a good deed in a weary world."  -Willy Wonka

--
Mail submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu
Be sure to include Keywords: and a short description of your software.

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

Crossposted-To: comp.os.linux.announce,comp.os.linux.help
From: jeffk@garnet.msen.com (Jeff Kopmanis)
Subject: LSM: Current Template w/explanations
Reply-To: jeffk@garnet.msen.com (Jeff Kopmanis)
Date: Tue, 7 Jun 1994 17:20:38 GMT

Here's the most current LSM entry template.  Newbies take note: there is a
short synopsis of what the LSM is at the beginning of the template.

Copies of this document can be found in the /pub/Linux/docs directories of
sunsite.unc.edu and tsx-11.mit.edu.

enjoy!
-Jeff.  :)
===========

Linux Software Map Entry Template                            Release: 20MAY94
=============================================================================

Synopsis:

The LSM is a directory of information about each of the software packages
available via FTP for the Linux operating system.  It is meant to be a public
information resource.  All entries have been entered by volunteers all over
the world via email using the template below.  New versions will appear
first on sunsite.unc.edu and will be announced in the newsgroup
comp.os.linux.announce .  Discussions pertaining to the LSM will be held in
the newsgroup comp.os.linux.help .  Any questions or comments can be
entered in comp.os.linux.help or sent to me directly at jeffk@msen.com .

Instructions:

Any new packages or updates to old entries should be entered in the template
below and sent to jeffk@msen.com (Jeff Kopmanis).  Each release of the
LSM will have the current template as part of the package.  Any changes to
the template will be made and released there.

*PLEASE* use the entry template below when submitting information.  It has
been designed so that all you have to do is fill in the blanks and send it
in as is.  Your entry will be read into the database directly from your
email response with little if any hand manipulation.


DO NOT RENAME FIELDS.  DO NOT REMOVE THE BEGIN OR END MARKERS.  Please
take a few minutes to review the field lengths listed below.  Any text
beyond these lengths will be TRUNCATED.

Complete as many fields as possible.  As of the 05SEP93 version, you don't
need to keep blank fields around, but I strongly encourage developers to
complete all the fields, as its more descriptive.  Make any corrections
that are necessary.  The initial data came from a variety of sources, 
and is not at all assumed to be correct.

Once you have completed the documentation as best as possible, upload your
package and a completed LSM template to sunsite.unc.edu:/pub/Linux/Incoming
The sunsite admin will get the LSM's to me.  If this is inconvenient, you
may also email the modified version of this file to:   jeffk@msen.com

Thank you VERY much for your time and enthusiasm.  Your contribution will
help to ensure that the Linux Software Map will continue to be a trusted
Linux resource.

-Jeff.  :)   (jeffk@msen.com) (Jeffrey J. Kopmanis)

=============================================================================
As of the 20MAY94 version....
=============================================================================

Expanded Numbers of Fields
==========================
You are allowed to have unlimited numbers of the
Desc, Site/Path/File/Filesize, Required, Comment, RelFiles and CopyPolicy
fields.  YOU MUST NUMBER each of them (ie. Desc1, Desc2, Desc3...) for now.
I'm working to make the program able to read in arbitrary numbers, but the
code just isn't there.

"HyperText" file locations
==========================
For each Site/Path/File combination that is completely filled in, a reference
is generated that should be readable and comprehended by the WWW, WAIS and
some gopher servers to automatically download the particular file for you.
I think this could be a really neat addition, and I'd like to get your
feedback to how it works.

Relaxed formatting
==================
The formatting of the entries is continually being relaxed.  A field name
must have AT LEAST one blank after its name.  Everything after the equals
sign (=) is trimmed of excess spaces and inserted into the data field.  No
column positioning is required.

=============================================================================
DESCRIPTIONS of fields used in the LSM template

DO NOT FILL IN THIS PART...THAT IS BELOW THESE FIELD DEFINITIONS!!

=============================================================================
Field:len          Description
===========        ==========================================================
Title:40           The name of the package.  example: "Emacs text editor"
Version:25         The version number or designation.
Desc1:80           5 lines of text describing the package's function or purpose
Desc2:80              The more descriptive you are the more useful the entry will be.
Desc3:80
Desc4:80
Desc5:80
Author:65          Who wrote the package originally, or, the person who ported it.
AuthorEmail:40     The author's email address, if known.
Maintainer:65      Who currently maintains the code.
MaintEmail:40      The maintainer's email address, if known.
Site1:30           FTP address of the primary site where this package is distributed.
Path1:50           The path at Site1 where the package is located.
File1:40           The filename in Path1 at Site1 where the package is located.
FileSize1:size     The size of the package.  You may use K and MB after a number.
Site2/Path2/File2/FileSize2  (same as first one)
Site3/Path3/File3/FileSize3  (same as first one)
Site4/Path4/File4/FileSize4  (same as first one)
Required1:80       Required hardware or software needed to run this package.  Please
Required2:80          be as specific as possible, for this information is VERY
Required3:80          important.
Required4:80
CopyPolicy1:80     The copyright policy of this package.
CopyPolicy2:80
Keywords:80        Keywords to use in searching for this package.
Comment1:80        Put any pertenant information that doesn't fit in the above
Comment2:80           fields or categories here.  The more you tell us, the better.
Comment3:80
Comment4:80
RelFiles1:80       List any related files that come with the package here.
RelFiles2:80
RelFiles3:80
Entered:12         The date you filled out this template. Ex:  05SEP93
EnteredBy:30       Take credit for your work!
CheckedEmail:40    Your email address (if you wish it to be in the LSM)  
=============================================================================

NOTE: The example file below contains ALL AVAILABLE fields.  You may delete
any fields you do not use.  BE SURE TO RETAIN THE BEGIN2 and END keywords...
they are VERY important!
================================ cut here ====================================
Begin2
Title        =
Version      =
Desc1        =
Desc2        =
Desc3        =
Desc4        =
Desc5        =
Author       =
AuthorEmail  =
Maintainer   =
MaintEmail   =
Site1        =
Path1        =
File1        =
FileSize1    =
Site2        =
Path2        =
File2        =
FileSize2    =
Site3        =
Path3        =
File3        =
FileSize3    =
Site4        =
Path4        =
File4        =
FileSize4    =
Required1    =
Required2    =
Required3    =
Required4    =
CopyPolicy1  =
CopyPolicy2  =
Keywords     =
Comment1     =
Comment2     =
Comment3     =
Comment4     =
RelFiles1    =
RelFiles2    =
RelFiles3    =
Entered      =
EnteredBy    =
CheckedEmail =
End

<END OF TEMPLATE DOCUMENT>
--
Jeff Kopmanis       (Ann Arbor, Michigan)   |  email:  jeffk@msen.com
Organizer of the Linux Software Map (LSM)   |  phone: (313) 393-4784 (work)
"So shines a good deed in a weary world."  -Willy Wonka

--
Mail submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu
Be sure to include Keywords: and a short description of your software.

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


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