New help files

New help files

[Hans Zoebelein]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1245 bytes --]

Dear blinux subscriber,

since blinux-list now comes to you from the servers of redhat.com,
we have the following changes:



Blinux-list is now available 24h a day.

Before, blinux-list ran on my private Linux box which is connected 
through a 28.8k modem. My box is not online 24h due to financial 
restraints (Germany's only phone company wants all your money :) . 
Now blinux-list is online 24h a day. Your postings are distributed to the
other subscribers as soon as you have hit the send button.



Blinux-list is unmoderated again.

Since there is no longer a bandwidth problem, blinux-list runs unmoderated
again. But if you want to tell someone stuff which isn't interesting for
the other subscribers, use mail instead.



Softpointer file will be available from leb.net/pub/blinux soon.

The softpointer file which contains a list of Linux blind related files
will be available in the future at leb.net/pub/blinux. Softpointer is no
longer stored at list site. Archive requests of softpointer no longer
works.



Attached to this posting you'll find the new help.txt and archive-help.txt
file. If you have stored these files, replace the old version by the new
one. So you can check, how to do a  archive search and more.

Enjoy!
Hans

[-- Attachment #2: Type: TEXT/PLAIN, Size: 2325 bytes --]

			General info
			------------

Subscription/unsubscription/info requests should always be sent to the -request
address of the mailing list, blinux-list-request@redhat.com

To subscribe to the mailing list, simply send a message with the word "subscribe"
in the Subject: field to the -request address of that list.

As in:		To: blinux-list-request@redhat.com
		Subject: subscribe

To unsubscribe from the mailing list, simply send a message with the word (you
guessed it :-) "unsubscribe" in the Subject: field to the -request address of
that list.

As in:		To: blinux-list-request@redhat.com
		Subject: unsubscribe

In the event of an address change, it would probably be the wisest to first
send an unsubscribe for the old address (this can be done from the new
address), and then a new subscribe to the new address (the order is important).

Most (un)subscription requests are processed automatically without human
intervention.

Do not send multiple (un)subscription or info requests in one mail.  Only one
will be processed per mail.

NOTE: The -request server usually does quite a good job in discriminating
      between (un)subscribe requests and messages intended for the maintainer.
      If you'd like to make sure a human reads your message, make it look
      like a reply (i.e. the first word in the Subject: field should be "Re:",
      without the quotes of course); the -request server does not react to
      replies.



			The archive server
			------------------
Every submission sent to this list is archived.	 The size of the archive
depends on the limits set by the list maintainer (it is very well possible
that only, say, the last two mails sent to the list are still archived, the
rest might have expired).

You can look at the header of every mail coming from this list to see
under what name it has been archived.  The X-Mailing-List: field contains
the mail address of the list and the file in which this submission was
archived.

If you want to access this archive, you have to send mails to the -request
address with the word "archive" as the first word of your Subject:.
To get you started try sending a mail to the -request address with
the following:

                To: blinux-list-request@redhat.com
		Subject: archive help

--

[-- Attachment #3: Type: TEXT/PLAIN, Size: 3220 bytes --]

Help for the blinux-list archive server
---------------------------------------

You want to access the blinux archive? OK, so you send a 
mail to blinux-list-request@redhat.com with the word 
"archive" as the *first* word of your Subject: line followed
by a command. 

Take care to remove disclaimers and footers,
because the archive server might try to interpret these
lines and if he can't understand them, you'll get back
a help.txt. Instead of removing footers you can put
the 'quit' command in the body of the message before 
your disclaimer and the archive server won't read your
disclaimer/footer.  


The blinux archive server knows the following commands:


You may put the following commands in the subject line
or in the body of a mail. If you put the commands in the body 
you can send multiple commands in one mail. If you submit 
a new software pointer don't put other commands in the body
of your message, they will be ignored. 
Lines starting with a '#' are ignored.


get filename ...
  You will get the file 'filename' by email


ls directory ...
   You will get an overview of the directory 'directory'


egrep case_insensitive_regular_expression filename ...
   Will search the file 'filename' for the expression.
   Upper or lower case letters will be treated equal.
 

maxfiles nnn
   Set the maximum number of files that can sent to you to nnn.
   This will protect you from a flood of files if you do
   a get directory/*. Setting maxfiles to zero will remove the 
   limit (to protect you against yourself no more than maxfiles 
   files will be returned per request).
 

version
  Sends the version of the SmartList list server which is 
  run here at redhat.com.


quit
  Terminates an archive request. This can be useful if you 
  have a signature at the end of your message and don't want
  the archive server to interpret your signature.


Since this is a smart server, the following aliases are understood:
Aliases for 'get': send, sendme, getme, gimme, retrieve, mail
Aliases for 'ls': dir, directory, list, show
Aliases for 'egrep': search, grep, fgrep, find
Aliases for 'quit': exit


Egrep supports most common flags.
If you append a non-standard signature, you should use the quit
command to prevent the archive server from interpreting the signature.


Examples:

You want to get all the latest available mails which are stored in the 
directory 'latest'. So you send the following mail:

<here begins the header>
To: blinux-list-request@redhat.com
Subject: archive get latest/*
<here ends the header>


You want to find out which files are available for you to get
from the main archive directory:

<here begins the header>
To: blinux-list-request@redhat.com
Subject: archive ls *
<here ends the header>


You are searching for the word 'scanner' in the latest 
messages of blinux-list. These messages are stored in the
subdirectory 'latest'. You are also searching for the word
'speech' in all messages of the main archive directory:

<here begins the header>
To: blinux-list-request@redhat.com
Subject: archive
<here ends the header>
egrep scanner latest/*
egrep speech *