From root@localhost Thu Sep 15 02:23:40 1994
Return-Path: root
Received: (from root@localhost) by localhost (8.6.9/8.6.9) id CAA05783 for root; Thu, 15 Sep 1994 02:23:39 -0500
Date: Thu, 15 Sep 1994 02:23:39 -0500
From: root
Message-Id: <199409150723.CAA05783@localhost>
To: root
Subject: Register with the Linux counter project

HELP FOR THE LINUX USAGE COUNTER
================================
This message is intended for you to edit, and send right back to the
Linux-counter@uninett.no address.
DO NOT USE "REPLY"!!!!!!!!!!!!!!!

(Practice has shown that putting the counter in the Reply-To: or From:
fields of a message is a GREAT way of causing mail loops, and defending
against them is a *lot* of effort. Therefore, this counter does not do it)

There are two ways of registering: Simple and complex.
For the SIMPLE method, simply send a message with the subject line being
one of:

   I use Linux at home
   I use Linux at work
   I use Linux at school
   I do not use Linux

You can also do combinations, like "I use Linux at home and at work".
The counter will attempt to guess your country of origin, and count you
accordingly. Information about you will not be made public.

Complex registration
--------------------
The complex features of the counter are accessed by using commands.
A command looks like (for instance) //MACHINE, and starts in the left
column.

You can register MACHINES, FRIENDS and data about YOURSELF (PERSON).
Below is listed an example of each of the sections, with comments that
aid you in filling them out correctly.

Only use the FRIENDS section if it is unlikely that the people will
register themselves!

When the templates are accepted by the daemon, they will be added to the
database. Data will be added even if it is not parsed properly.
They may be thrown out in later duplicate elimination, or you may receive
a query from me regarding the validity of the data, but otherwise, they will
be counted.

You can get a report from the counter by specifying the command

  //REPORT <reportname>

The following reports are available:

  short    - The standard listing of Linux usage, including per-country data
  machines - Statistics on registered Linux machines
  persons  - Persons who use Linux, sorted by country, and some statistics

All these reports are also available by anonymous FTP to aun.uninett.no,
directory pub/misc/linux-counter.

The counter also understands //HELP.
When you use a command, the subject line of the message is *not* recorded
in the counter.

Good luck!

             Harald Tveit Alvestrand


//FRIEND
# Your Linux-using friends, in the pattern
# E-mail address: place of usage
# For people without E-mail address, use
# ?Givenname.Surname@geographical.area.country
# like ?Joe.Smith@london.gb or ?bill.gates@newyork.ny.us


//MACHINE
# Fill in one such section per machine that runs Linux
accounts:
# Number of accounts in /etc/passwd, not counting root and so on
country:
# ISO 3166 two-letter country code
cpu:
# The pattern is MakerNumberBus/Speed, for example
# Cx386, amd486, 386DX/33, 586SX/16
disk:
# Number of MBytes of disk installed - number only
distribution:
# Slackware, SLS, LGX, TAMU, MCC, Debian,
OTHER or DIY (do-it-yourself) with optional version number
memory:
# Number of MBytes of memory installed - number only
name:
# DNS or UUCP name of machine if it has one
# If no unique network name is available, use ?machinename@geo.area.country
network:
# Type of network - SLIP, Ethernet, Term, PPP, AX.25 or none
source:
# Where you fetch Linux. FTP, BBS, Floppy/Friend, Floppy/<Company>,
# CD/Yggdrasil, CD/Morse, CD/Snow, Tape/Friend, Tape/<company>,
# NFS, AFS, HD/friend...
users:
# Number of persons who use this machine regularly


//PERSON
# This is about yourself, the sender of this message
country:
# ISO 3166 two-letter country code of where you live
email:
# Your E-mail address
may-publish:
# YES if you agree that information about you can be published
# If not given, nothing but statistical information will be published
name:
# Your name
started:
# Month and year you started using Linux, like "nov 93"
usage:
# The place where you use Linux. Home, school, work or combinations of these


//END
The END command is only required if you have a mailer that adds stuff
below the last line of the message.

From volkerdi@mhd1.moorhead.msus.edu  Wed Jun 12 14:16:14 1996
Return-Path: volkerdi
Received: (from volkerdi@localhost) by darkstar.slackware.com (8.7.5/8.6.9) id OAA03071; Wed, 12 Jun 1996 14:15:10 -0500
Date: Wed, 12 Jun 1996 14:15:08 -0500 (CDT)
From: "Patrick J. Volkerding" <volkerdi@darkstar.slackware.com>
To: root
Subject: Welcome to Linux (Slackware 3.2)!
Message-ID: <Pine.LNX.3.91.960612140626.3041A-100000@darkstar.slackware.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Welcome! Glad to see you've made it this far! :^)

Here are a few hints to help you navigate through the Linux operating 
system a little bit better:

-- Remember those screens you saw while each package was installing? You 
   can see all the information (and more) again. The simplest way is to use 
   the 'pkgtool' utility to view the package contents. Another way is to use 
   'less' or a text editor to read the files in /var/adm/packages and 
   /var/adm/scripts (this is the method I use).

-- You may need to make some changes to the /etc/rc.d/rc.serial script if 
   you're using serial ports other than /dev/ttyS0 or /dev/ttyS1 (com1: and
   com2: under DOS), or if these ports use non-standard IRQs.

   I suggest using the section about halfway through that lets you set up
   the ports manually. Here's an example of how I set up the ports on my 
   machine for /dev/ttyS0 and /dev/ttyS2:
   
   # These are the standard COM1 through COM4 devices
   #
   ${SETSERIAL} /dev/cua0 uart 16450 port 0x3F8 irq 4
   # ${SETSERIAL} /dev/cua1 uart 16450 port 0x2F8 irq 3
   ${SETSERIAL} /dev/cua2 uart 16450 port 0x3E8 irq 5
   # ${SETSERIAL} /dev/cua3 uart 16450 port 0x2E8 irq 3

   You'll also need to uncomment the line in /etc/rc.d/rc.S that starts the
   rc.serial script.

-- If you've got hardware such as a CD-ROM drive or ethernet that doesn't
   seem to work with Linux, it's possible that the kernel you're using 
   doesn't contain the needed support.  In that case, you can do one of
   two things:

      1.  Recompile your kernel, including the needed driver(s).
      2.  Load the support with kernel modules.  This is probably the
          simplest way to handle the situation.  Just edit 
          /etc/rc.d/rc.modules so that it loads the modules you need.
   
   In the case of the Sony CDU31a and CDU33a CD-ROM drives, people commonly
   report problems.  This is usually because the driver doesn't probe for
   the hardware location -- it expects the user to provide some parameters
   to the kernel so that it knows where to look.  If you're having problems
   with a CDU31a or CDU33a, look in these places for help:
   /usr/src/linux/Documentation/cdrom/cdu31a  (also in /docs/kernel.20 on
                                               the Slackware CD-ROM)
   The BOOTING file also has some good information on how to pass 
   parameters (like cdu31a=0x1f88,0,PAS) to your kernel. 

-- If you're on a standalone LAN without a nameserver, make sure you 
   don't have a nameserver line in /etc/resolv.conf, or you may experience 
   delays with many network commands as they attempt to query the bogus 
   nameserver.

-- Want to run NFS? You'll to run the folllowing daemons in /etc/rc.d/rc.inet2:
   rpc.portmap, rpc.mountd, and rpc.nfsd. Then, edit your /etc/exports to allow
   NFS access.

-- If you have any supported busmouse other than the PS/2 type, you'll 
   need to recompile the kernel to add the driver if you plan to use it.

-- If you installed the F disk, there will be lots of FAQs (lists of 
   Frequently Asked Questions with answers), and HOWTOs (files explaining 
   how to do a particular Linux task), in /usr/doc/faq. These should be 
   helpful in getting you going with Linux.

Have fun!

---
Patrick Volkerding
volkerdi@mhd1.moorhead.msus.edu

