File: issue10.html

package info (click to toggle)
lg-issue10 4-4
links: PTS
area: main
in suites: woody
size: 552 kB
ctags: 102
sloc: makefile: 36; sh: 4
file content (3257 lines) | stat: -rw-r--r-- 114,686 bytes
parent folder | download | duplicates (2)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
   <TITLE> Linux Gazette Table of Contents Issue 10</TITLE>
   <META NAME="GENERATOR" CONTENT="Mozilla/3.0Gold (X11; I; Linux 2.0.20 i586) [Netscape]">
</HEAD>
<BODY>

<H1><IMG SRC="../gx/banner.gif" ALT="Linux Gazette" HEIGHT=112 WIDTH=593></H1>

<P><A NAME="lg_toc10"></A></P>

<H1>Table of Contents Issue #10</H1>

<H5>Copyright (c) 1996 Specialized Systems Consultants, Inc. <BR>
For information regarding copying and distribution of this material see
the <A HREF="../ssc.copying.html">COPYING</A> document.</H5>

<P>
<HR></P>

<UL>
<LI><A HREF="#lg_frontpage">The Front Page</A> </LI>

<LI><A HREF="#lg_mail10">The MailBag</A> </LI>

<LI><A HREF="#lg_tips10">More 2 Cent Tips</A> </LI>

<UL>
<LI><A HREF="#pipe">Tcl/TK Tips</A> </LI>

<LI><A HREF="#perl">Perl Control M Trick</A> </LI>

<LI><A HREF="#emacs">Another Emacs Control M Trick</A> </LI>

<LI><A HREF="#xterm">XTerm Title Bar Function</A> </LI>

<LI><A HREF="#vi">More on Commenting Code in VI</A> </LI>

<LI><A HREF="#x2">More on X Term Title Trick 2</A> </LI>

<LI><A HREF="#bash">Bash Quick Tip</A> </LI>

<LI><A HREF="#redhat">Neat Red Hat Management Trick</A> </LI>

<LI><A HREF="#find">More on Find and Alternatives</A> </LI>

<LI><A HREF="#pico">Pico Control M Trick</A> </LI>

<LI><A HREF="#emacm">Yet Another Emacs Control M Trick</A> </LI>
</UL>

<LI><A HREF="#lg_bytes10">News Bytes</A> </LI>

<UL>
<LI><A HREF="#general">News in General</A> </LI>

<LI><A HREF="#software">Software Announcements</A> </LI>
</UL>

<LI><A HREF="feddi/feddi.como.html">FEddi-COMO (article in Spanish)</A>,
by Manual Soriano </LI>

<LI><A HREF="#radio">Hams, Packet Radio and Linux</A>, by Phil Hughes </LI>

<LI><A HREF="#in.memory">In Memory of Mark A. Horton</A>, by Victoria Welch
</LI>

<LI><A HREF="#mconv2">Mconv2 Utility</A>, by Nik Tjirkalli </LI>

<LI><A HREF="#netday">NetDay96 and Linux</A>, by Paul A. Rogers </LI>

<LI><A HREF="#plugin.gimp">Sample Plug-In SMGL Source Template</A>, by
Michael J. Hammel </LI>

<LI><A HREF="#dynamicweb">Setting Up a Dynamic IP Web Server</A>, by Henry
H. Lu </LI>

<LI><A HREF="#xaos">XaoS: A New Fractal Program for Linux</A>, by Larry
Ayers </LI>

<LI><A HREF="#xmosaic">Xmosaic Development on a Roll</A>, by Larry Ayers
</LI>

<LI><A HREF="#lg_backpage10">The Back Page</A> </LI>

<UL>
<LI><A HREF="#authors">About This Month's Authors</A> </LI>

<LI><A HREF="#notlinux">Not Linux</A> </LI>
</UL>
</UL>

<P>
<HR></P>

<H2><IMG SRC="../gx/SSC_LOGO.gif" ALT="" HEIGHT=130 WIDTH=105><A HREF="http://www.ssc.com/">
SSC - Publishers of Linux Journal</A></H2>

<P>
<HR></P>

<P>
<HR></P>

<P><!-- ======================================================================--><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32>
Date: Thu, 5 Sep 1996 08:34:05 -0700 (PDT)<BR>
<B>Subject: Re: Linux Gazette Suggestion <BR>
From: kaehny@execpc.com (Mark Kaehny)</B> <BR>
</P>

<P>Hi, </P>

<P>Like the Linux Gazette but would you please (for us linear thinkers)
put some navigation aid so we can go to next and previous pages? I don't
like clicking back to the menu, I like flipping through things... </P>

<P>Thanks for the work, appreciated. <BR>
Mark Kaehny </P>

<BLOCKQUOTE>
<P><I>(Done -- good suggestion. --Editor)</I> </P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Thu, 05 Sep 1996
13:22:23 -0700 <BR>
<B>Subject: Linux trademark issues. <BR>
From: Earl Stutes estutes@palladium.corp.sgi.com </B><BR>
</P>

<P>Yet again, it appears someone is attempting to make a buck on something
that most of the rest of us feel should be a free or at least public domain
thing. In this case the word Linux. I don't have any suggestions as to
how &quot;we&quot; deal directly with this issue, but I certainly hope
that all of you folks that are a part of the growing Linux commercial community
will take the lead in fighting this yo-yo. Of course part of my contribution
to support you is the fact that I buy the magazine from the
newstand(fatbrain.com, actually) every month. </P>

<P>I have enjoyed your magazine right from the beginning, and will continue
to be a supporter over the long term. </P>

<P>Thanks for listening </P>

<P>=eas= </P>

<BLOCKQUOTE>
<P><I>(Since the Gazette is strictly on-line, I'm assuming you are talking
about the Linux Journal when you refer to buying the magazine. Latest news
about the trademark can be found by clicking the Hot Linux News button
on the Front Page. There are also couple of items in the current News Bytes
section. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Fri, 6 Sep 1996
08:58:23 +0100 (BST) <BR>
<B>Subject: LG Issue #9 <BR>
From: Dave Pearson davep@hagbard.demon.co.uk </B><BR>
</P>

<P>Hi. </P>

<P>First, I'd like to say congrats on taking over support of the LG, it's
a very handy resource and it's nice to see it getting continued support.
</P>

<P>However, I've got a question about how you are going to handle it. In
the past I've always downloaded a copy of the latest issue of LG and installed
it on my own machine so that I could read it at my leisure. IIRC, each
issue included a new top level index file that would list the TOCs of all
issues, this ment it was simple and easy to install and to quickly search
for a specific article. </P>

<P>Correct me if I'm wrong, but issue 9 does not appear to follow this
install style. Was there a reason for this? </P>

<P>Thanks for your time. </P>

<PRE>--  
Take a look in Hagbard's World: |     w3ng - The WWW Norton Guide reader. 
http://www.acemake.com/hagbard  |  ng2html - The NG to HTML converter. 
Resist UK Internet Censorship:  |       eg - Norton Guide reader for OS/2.  
http://babylon.ivision.co.uk    |   dgscan - DGROUP scanner for Clipper.  
</PRE>

<BLOCKQUOTE>
<P><I>(You are not wrong. I did change it, not realizing what a hassle
it was going to cause some people. The reason for part of the change that
will most likely remain, is that I wanted to be able to keep issues 1-8
exactly as they were when John put them out -- i.e. not changing the front
page, etc. The way it works now should not be that different.</I> </P>

<P><I>The front page offers a spot to click for the TOC of issues 1-8 and
a spot for TOC 9. When 10 comes out next month, it will be on top of TOC
9. I personally thought that having each TOC in a separate file would make
it easier -- perhaps I was wrong, it's been known to happen. I'm considering
a search program, when I have time to set it up, and in the meantime, I
will add an index containing all TOCs. --Editor)</I> </P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Fri, 6 Sep 1996
06:30:39 -0500 (CDT) <BR>
<B>Subject: new LG issue <BR>
From: Larry Ayers layers@vax2.rain.gen.mo.us </B><BR>
</P>

<P>Last night I saw the new LG issue on the SSC website. So evidently in
the last week of August writers came through for you. There are some great
articles in issue 9; an auspicious beginning for SSC's sponsorship (and
your editing duties). </P>

<P>By the way, I got an email the other day from another LG reader, complaining
that the graphics from the TkDesk article I wrote in LG #8 were not accessible
to a web-browser. I loaded the article into Netscape (from the SSC website)
and found this to be true. Perhaps the directory structure was changed
somehow when LG #8 was put on the site, rendering a link inactive? I just
checked issue 8 again, and found that most of the inline images in my pieces
won't display. I think the problem is that the directory which John Fisk
used was ./gx/ayers, whereas it looks like SSC's gazette graphics all go
in ./gx. </P>

<P>Regards, Larry Ayers </P>

<BLOCKQUOTE>
<P><I>(Thanks. Yes, authors did come through for me, including you, and
I thank you all.</I> </P>

<P><I>Sorry, I know about the problem with the links, and it is now fixed.
The directories were set up correctly; there were just a lot of missing
files. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Fri, 6 Sep 1996
10:25:43 -0700 (PDT) <BR>
<B>Subject: Re: Linux Gazette Issue #9 <BR>
From: schuld@btv.ibm.com (David W. Schuler) </B><BR>
</P>

<P>I just tried to take a look at the Linux Gazette Issue #9. Unfortunately,
I did not find the &quot;I'll read it myself&quot; button at the top of
the index that would allow me to see the whole thing at one time and print
it out for later reading at home. I would appreciate if you could add this
option back, rather than causing me to have to go into each section to
print it out so that I can read it later at home. </P>

<P>Thanks. </P>

<P>David W. Schuler - Advisory Engineer <BR>
Semiconductor Contract Manufacturing <BR>
IBM Microelectronics Internet: schuld@btv.ibm.com <BR>
B/863-2 Z/863D AOL: schuld@aol.com <BR>
(Personal Mail) <BR>
1000 River Street Phone: (802) 769-7636 <BR>
Essex Junction, VT 05452-4299 FAX: (802) 769-6800 <BR>
For IBM Microelectronics information: http://www.chips.ibm.com <BR>
</P>

<BLOCKQUOTE>
<P><I>(Yes, I took that out -- didn't realize how popular it was. I've
gotten lots of mail about this change, so am planning to put it out there
both ways beginning this month. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Sun, 8 Sep 1996
14:02:08 +-200 <BR>
<B>Subject: LOCAL:(Belgium,Antwerp) Linux day on 2 november 1996 <BR>
From: POE poe@glo.be </B><BR>
</P>

<P>Hello, </P>

<P>we are the recently started Antwerp Linux Users Club. We invite you
all to come to our Linux day meeting on 2 November 1996 in the CC'De Schorren'
at Hoboken-Polder Graspolderlaan from 10h till 18h. We are demonstrating
the Linuxkernel 2.0 with a lot of working applications including a Webserver
and if you become a member You can join our Intranet. </P>

<P>You can reach us at our homepage http://user.glo.be/~poe/alug.htm Be
carefull : it can get you a while before you get in but once you are in
it's pretty fast! </P>

<P>Patrick &amp; Armand <BR>
</P>

<BLOCKQUOTE>
<P><I>(All right, Antwerp! Get out there and support Linux. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Mon, 9 Sep 1996
08:57:17 -0700 (PDT) <BR>
<B>Subject: Re: Linux Gazette <BR>
From: tinus@betterthan.northstar.k12.ak.us (Sunit Das) </B><BR>
</P>

<P>Hello! I was wondering if you have an archive with the past issues of
the Linux Gazette(tar-ed and gzip-ed) so that us (the readers) can download
and browse at our leisure? If not, would it be too much trouble to do so?
I hope I'm not imposing too much, but I am on a shared phone line, and
much as I would like to stay on the net all day (it's tempting), I can't.
Thanks for *any* help! </P>

<P>--Sunit Das </P>

<BLOCKQUOTE>
<P><I>(No problem. tar files are available, I've just been having technical
difficulties -- they were unreadable. At any rate John Fisk sent us new
files that are now up at ftp://ftp.ssc.com/pub/lg/. Also, our issue 10
file, lg_issue10.tar.gzp and all issues (1-10) file, LinuxGazette_oct96.tar.gzp
are located at that site. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Tue, 10 Sep 1996
23:05:36 +0200 <BR>
<B>Subject: Suggestion: Search Engine <BR>
From: &quot;Johannes Norinder&quot; dante@inferno.skurup.se </B><BR>
</P>

<P>My suggestion is that you ought to have some kind of simple search engine
so that you easily can search for phrases within one or all of the issues
of LG. As is it's hard to know if you've covered Iomegas Zipdrive, for
example. </P>

<P>Otherwise thanks for a great service. </P>

<P>Johannes Norinder </P>

<BLOCKQUOTE>
<P><I>(I agree. In fact it's something that I have already thought about.
There is a search engine for Linux Journal, and I will probably use the
same one for the Gazette. However, it means doing a lot of front end work
to get it set up. When I'll have time to do this is not certain, but it
is definitely on the list. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Wed, 11 Sep 1996
00:32:27 -0400 <BR>
<B>Subject: my 2 cents <BR>
From: &quot;Aaron L. Hastings&quot; alhastin@mtu.edu </B><BR>
</P>

<P>hey there <BR>
im just gettin into linux <BR>
i got it to help me learn unix <BR>
which it has helped a lot on <BR>
but i have found it to be totally awesome in its own right <BR>
</P>

<P>it is almost cliche but nothing in any commercial sense has <BR>
managed to pull together in a near utopian ( except for bugs ) <BR>
environment a cooperative effort of people worldwide <BR>
</P>

<P>it just shows what people can do when they work together <BR>
( like i said cliche but rarely achieved )<BR>
</P>

<P>well this site is just another example of this cooperation <BR>
</P>

<P>YEAH </P>

<BLOCKQUOTE>
<P><I>(shades of e e cummings --editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Wed, 11 Sep 96
12:36:54 -0400 <BR>
<B>Subject: Linux Gazette <BR>
From: Bill Cronk bcronk@nvl.army.mil </B><BR>
</P>

<P>I am very glad to see a new issue put out. I was sad thinking that it
had gone by the wayside. </P>

<P>I would like to see a section of tips and tricks devoted towards the
novice user who needs to learn the tricks to setting up hardware, software
and all the other things that come along. I remember when the first Byte
magazine came out and for the longest time there were articles on hardware
and software for the novices. After a while that ended as people grew up
and demanded more in depth articles. I would think that most people would
have a hard time finding those back issues. In the case of the Gazette
all the back issues will most likely be archived and if a basic index was
published once or twice a year many new people to the world of Linux would
have all kinds of useful tips and tricks to read through. </P>

<P>Either way I enjoy reading the Gazette and will look forward to new
issues. I wish you success in publishing the Gazette. </P>

<P>In the future, maybe the far future, I will be able to provide an article
now and then on some hardware and software items related to laboratory
instrumentation interfacing and controlling of automated test equipment.
</P>

<P>Best wishes,<BR>
Bill </P>

<PRE>-- 
Bill Cronk                                   Phone:         (703) 704-3692 
E-OIR Measurements, Inc                      Fax:           (703) 704-1821  
P.O. Box 1240                                E-mail: bcronk@nvl.army.mil 
Spotsylvania, VA 22553                       Amateur Radio: WB2LUU 
</PRE>

<BLOCKQUOTE>
<P><I>(I agree that this is a good idea and will put it out there in the
next issue and see if anyone responds. I'll look forward to the time when
you send me an article. New contributors are always welcome. --Editor)
</I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Fri, 13 Sep 1996
08:51:41 -0700 (PDT)<BR>
<B>Subject: Gazette on a DOS machine <BR>
From: gv.livingston@brokersys.com (G.V.Livingston II) </B><BR>
</P>

<P>Wondering if there are any copies of the Gazette in HTML format with
DOS filenames? I would like to set up a personal mirror of all issues on
a DOS machine that I use regularly but unTARring the files from the FTP
site is fruitless because the filenames are made DOS compliant and the
links no longer match what is in the directory. </P>

<P>I basically want my &quot;site&quot; to exactly mirror the SSC pages.
</P>

<P>Thanks for any help you can provide. </P>

<P>GVL II </P>

<BLOCKQUOTE>
<P><I>(Sorry, but no. Frankly, this is quite an unusual request, since
most of our readers do use Linux boxes. Love to have you mirror us, but
this is more work than I have time for. Tried to e-mail you, but it kept
coming back to me. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Tue, 17 Sep 1996
08:36:40 -0700 (PDT) <BR>
<B>Subject: COOL it works with LINUX <BR>
From: Paul Bingman &lt;paul@edgewood.net&gt; </B><BR>
</P>

<P>I suspect many/most of you have seen the new logo promoted by Linux
Journal, that can be licensed for $1 a year, to show that your software
or hardware product works with Linux. See: <BR>
http://www.linuxjournal.com/Morelj/cool.html <BR>
</P>

<P>What is a very pleasant surprise is to see that logo starting to appear
in the mainstream trade press. On page 41 of the September 16, 1996, InfoWorld,
is a half-page Equinox ad for their multiport serial cards. The COOL logo
is the first one displayed, before Windoze, Novell, or SCO. </P>

<PRE>------------------------------------------------------------------------  
Paul Bingman                paul@edgewood.net      Voice +1 503 222 3846  
Edgewood Engineering     http://www.edgewood.net     FAX +1 503 223 3071  
WWW/CGI, Internet, Linux, application software, firmware, device drivers 
------------------------------------------------------------------------ 
</PRE>

<BLOCKQUOTE>
<P><I>(Cool. --Editor) </I></P>
</BLOCKQUOTE>

<P>
<HR></P>

<P><IMG SRC="../gx/letter.gif" ALT="" HEIGHT=32 WIDTH=32> Date: Fri, 13 Sep 1996
16:00:12 +0000 <BR>
<B>Subject: LG : french translation + mirroring ? <BR>
From: Patrick Mevzek &lt;Patrick.Mevzek@Babbage.espci.fr&gt; <BR>
</B>To: fiskjm@ctrvax.Vanderbilt.Edu <BR>
</P>

<P>Hi, </P>

<P>I discovered your Linux Gazette some months ago, and it's great and
very interesting. I've discovered Linux a little before, because I will
need to install here at my school (you know I'm only a student like you
;-) !!) a small LAN of computers for students, with PC (Win 95) and one
LINUX-PC (which will be a firewall-mailhost-webserver, etc...). So I'm
quite interested with everything in relation with Linux. </P>

<P>In fact, I can propose you to translate the LG in French. I would be
very pleased to do that. But I can promise you I will always have enough
time to do it quickly, because first I'm a student, and therefore I've
exams, (you know that...), and second, like I said before, I have to work
a lot to install students'LAN. </P>

<P>So, let me know if I can help you that way !! </P>

<P>BTW, because I will be the maintainer of the web server of the students
too, it could be possible, somewhat in January or February 97 to start
mirroring the LG, here at the ESPCI. I can't promise you big things, because
mainly in 3 years I won't be in that school anymore, and I can't say that
the next webserver maintainer will keep mirroring LG !! I hope to hear
from you soon </P>

<P>Regards,<BR>
</P>

<PRE>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
~ Patrick Mevzek                   Patrick.Mevzek@Info.Escpi.fr ~  
~ HomePage (co-developer): http://www.geocities.com/Paris/4206  ~  
~     'I like these calm little moments before the storm...'    ~  
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
</PRE>

<BLOCKQUOTE>
<P><I>(Glad you like the magazine. John Fisk forwarded your letter to me
as SSC is now handling the Linux Gazette. I think it would be wonderful
if you were to translate the LG into French, whenever you have time. It
would certainly give the Gazette a wider French audience. We have very
liberal copying requirements, especially if you are a mirror site (virtually
none). We always welcome another mirror. Thanks for your interest. -- Editor)
</I></P>
</BLOCKQUOTE>

<P><!-- ======================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<a name="lg_tips10">
<CENTER><P>
<HR><!-- QUICK TIPS SECTION ==================================================
--></P></CENTER>

<H2 ALIGN=CENTER><A NAME="tips"></A><IMG SRC="../gx/twocent.gif" ALT="" HEIGHT=84 WIDTH=135 ALIGN=CENTER>More
2&cent; Tips! </H2>

<P>
<HR></P>

<H3>Contents:</H3>

<UL>
<LI><A HREF="#pipe">Tcl/TK Tips</A> </LI>

<LI><A HREF="#perl">Perl Control M Trick</A> </LI>

<LI><A HREF="#emacs">Another Emacs Control M Trick</A> </LI>

<LI><A HREF="#xterm">XTerm Title Bar Function</A> </LI>

<LI><A HREF="#vi">More on Commenting Code in VI</A> </LI>

<LI><A HREF="#x2">More on X Term Title Trick 2</A> </LI>

<LI><A HREF="#bash">Bash Quick Tip</A> </LI>

<LI><A HREF="#redhat">Neat Red Hat Management Trick</A> </LI>

<LI><A HREF="#find">More on Find and Alternatives</A> </LI>

<LI><A HREF="#pico">Pico Control M Trick</A> </LI>

<LI><A HREF="#emacm">Yet Another Emacs Control M Trick</A> </LI>
</UL>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="pipe"></A>Tcl/Tk
Tips</H3>

<P>Date: Tue, 03 Sep 1996 13:29:37 +0100 <BR>
From: Liang Shing Ng <A HREF="mailto:L.S.Ng@ecs.soton.ac.uk">&lt;L.S.Ng@ecs.soton.ac.uk&gt;<BR>
</A>To: fiskjm@ctrvax.Vanderbilt.Edu <BR>
Subject: Tcl/Tk tips NOT IN Welch's Book <BR>
</P>

<P>I see that you just got hooked with Tcl/Tk. </P>

<P>I found an *OLD* way of interfacing C program with Tk scripts, which
is not documented in Welch's Book. </P>

<P>What is it? Pipe! </P>

<P>My C prog (parent) create two pipes to communicate with the Tk prog
(child). The Tk prog only need to use stdin and stdout without knowing
that this is controlled by the C prog. This provides a much easier way
than the interface procedures described in Welch. </P>

<P>Attached here are my C prog and my Tk prog. If you think this is worth
writing a full article, please let me know. I will do that for the Gazette.
:) </P>

<P>Cheers <BR>
Liang-Shing Ng </P>

<P>Description: simple C and Tk prog pair showing how to read/write with
each other. example of use: C may use this Tk for graphical interface.
C does some image processing, then ask Tk to display it. </P>

<P>C Prog: </P>

<PRE> 
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;unistd.h&gt;

int create_pipe(char *child, int opipe[2], int ipipe[2])
{
    pid_t pid;
    
    /* Create output pipe and input pipe  */
    if (pipe (opipe)) {
        fprintf (stderr, &quot;Pipe failed.\n&quot;);
        return EXIT_FAILURE;
    }
    if (pipe (ipipe)) {
        fprintf (stderr, &quot;Pipe failed.\n&quot;);
        return EXIT_FAILURE;
    }

     /* Create the child process.  */
    pid = fork ();
    if (pid == (pid_t) 0) {
        /* This is the child process.  */
        /* Child stdin is opipe[0] */
        close(0);
        dup(opipe[0]);
        close(opipe[0]);
        /* Child stdout is ipipe[1] */
        close(1);
        dup(ipipe[1]);
        close(ipipe[1]);
        /* Closed unused FD */
        close(opipe[1]);
        close(ipipe[0]);
        execlp(child, child, NULL);
    }
    else if (pid &lt; (pid_t) 0) {
        /* The fork failed.  */
        fprintf (stderr, &quot;Fork failed.\n&quot;);
        return EXIT_FAILURE;
    }
    return pid;
}

main(int argc, char *argv[])
{
    FILE *po, *pi;
    char s[128];
    pid_t pid;
    int opipe[2], ipipe[2];
    char buff[256];
    
    if (argc&lt;2) {
        fprintf(stderr, &quot;Tk display subprogram required.\n&quot;);
        fprintf(stderr, &quot;Usage: %s display.tk\n&quot;, argv[0]);
        exit(1);
    }

    /* Change low level pipe FD to streams */
    pid=create_pipe(argv[1], opipe, ipipe);
    po=fdopen(opipe[1], &quot;w&quot;);
    pi=fdopen(ipipe[0], &quot;r&quot;);

    while (gets(s)!=NULL) {
        fprintf(po, &quot;%.5s\n&quot;, s);
        fflush(po);
        fgets(buff, 256, pi);
        fprintf(stderr, &quot;%s: %s&quot;, argv[0], buff);
    }

    /* Close output pipe and wait input pipe flush */
    fclose(po);
    fgets(buff, 256, pi);
    fprintf(stderr, &quot;%s: %s&quot;, argv[0], buff);

    return 0;
}
</PRE>

<P>--- <BR>
Tk prog </P>

<PRE> 
#!/bin/sh
# the next line restarts using wish \
exec wish4.0 &quot;$0&quot; &quot;$@&quot;

proc Reader { pipe } {
    gets $pipe line
    puts stderr &quot;tk: $line&quot;
    puts stdout &quot;from tk: $line&quot;
    flush stdout
}

image create photo imb -file a.ppm
label .c -image imb
pack .c
wm geometry . +100+100
update

while { 1 } {

if {[eof stdin]} {
    exit
} else {
    fileevent stdin readable [ Reader stdin ] 
}

}
</PRE>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="perl"></A>Perl
Control M Trick</H3>

<P>Date: Wed, 4 Sep 1996 17:02:40 -0700 (PDT) <BR>
From: Jonathan Gross <BR> 
</A>Subject: Perl Tip <BR>
</P>

<P>I read the most recent issue of the gazette, and the control M issue
caught my eye. Using vi or emacs is great, but if you have more than one
file, you can do this: </P>

<PRE> 
perl -pi.bak -e 's/\r//g;' filelist
</PRE>

<P>FYI. </P>

<PRE>-----------------------  
Jonathan
</PRE>

<P>
<HR></P>

<P><!-- =====================================================================
--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="emacs"></A>Another
Emacs Control M Trick</H3>

<P>Date: Thu, 05 Sep 1996 13:34:09 -0700 <BR>
From: Earl Stutes <A HREF="mailto:estutes@eas.com">&lt;estutes@eas.com&gt;<BR>
</A>Subject: $.02 emacs tip <BR>
</P>

<P>Here is the way I handle the ^M in files. Put this in your .emacs: </P>

<PRE> 
(defun dos-unix ()
  (interactive)
  (goto-char (point-min))
  (while (search-forward &quot;\r&quot; nil t) (replace-match &quot;&quot;)))
(defun unix-dos ()
  (interactive)
  (goto-char (point-min))
  (while (search-forward &quot;\n&quot; nil t) (replace-match &quot;\r\n&quot;)))
</PRE>

<P>IP don't usually bind these to keys, but you certainly could. When you
call the function M-xdos-unix, it will delete all of the delete all of
the &lt;CR&gt; characters in the file. And of course the other function
will put them back. </P>

<P>=eas= </P>

<P>
<HR></P>

<P><!-- =====================================================================
--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="xterm"></A>X
Term Titlebar Function</H3>

<P>Date: Fri, 06 Sep 1996 17:53:00 -0600 <BR>
From: &quot;Michael J. Hammel&quot; <A HREF="mailto:mjhammel@emass.com">&lt;mjhammel@emass.com&gt;<BR>
</A>Subject: Gazette #9 comments -- xterm title bar function<BR>
</P>

<P>Nice job on the new Linux Gazette! I'm just scanning it and had a few
notes I thought I'd pass to you. </P>

<P>In the mail, there are a couple of things. Jim Murphy says that the
&quot;-print&quot; option to find is necessary to get output from the find
command and follows that up with &quot;get used to it, its *nix&quot;.
Well, he's part right. Linux does require this. However, any users who
work on other Unix boxes will find slight differences in some of the common
CLI commands (CLI is &quot;command line interface&quot;). For example,
&quot;find&quot; on Solaris does not require the -print option to get output.
Just food for thought. </P>

<P>Second, I have an xterm title bar function that people might find useful.
I'll give the code first, then explain what it does: </P>

<P>In your .bashrc (or .kshrc - note this only works on ksh style shells)
add the following: </P>

<PRE> 
HOSTNAME=`uname -n`
if [ &quot;$TERM&quot; = &quot;xterm&quot; ] &amp;&amp; [ &quot;$0&quot; = &quot;-bash&quot; ]
then
   ilabel () { echo -n &quot;^[]1;$*^G&quot;; }
   label () { echo -n &quot;^[]2;$*^G&quot;; }
   alias stripe='label $HOSTNAME - ${PWD#$HOME/}'
   alias stripe2='label $HOSTNAME - vi $*'
   cds () { &quot;cd&quot; $*; eval stripe; }
   vis () { eval stripe2; &quot;vi&quot; $*; eval stripe;}
   alias cd=cds
   alias vi=vis
   eval stripe
   eval ilabel &quot;$HOSTNAME&quot;
fi
</PRE>

<P>This does three things (as long as you're in an xterm and running bash):
</P>

<OL>
<LI>when the xterm is first opened, the name of the current host is displayed
in the title bar. </LI>

<LI>when you cd to a directory, the current path is displayed in the xterm
title bar with the users $HOME directory stripped off the front end of
the path (to save some space when you're somewhere in your own directory
tree). The path is preceded by the current hosts network name. </LI>

<LI>when you use vi to edit a file the name of the file is displayed in
the title bar along with the current hosts name. When you exit your vi
session, the title bar reverts to the &quot;hostname - path&quot; format
described in #2 above. </LI>
</OL>

<P>I found this very useful for all my ksh based systems because it removed
the path from my shell prompt, thus saving me space for prompt commands.
Since bash is a ksh compatible shell, this works quite well on standard
Linux systems. </P>

<P>Hope everyone finds this useful. </P>

<PRE>--  
Michael J. Hammel           | 
mjhammel@emass.com          | Consciousness: that annoying time between naps.
mjhammel@csn.net            | 
http://www.csn.net/~mjhammel| 
</PRE>

<P>
<HR></P>

<P><!-- =====================================================================
--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="vi"></A>More
on Commenting Code in vi</H3>

<P>Date: Mon, 09 Sep 1996 22:23:25 -0400 <BR>
From: Jeff Blaine <A HREF="mailto:jblaine@nda.com">&lt;jblaine@nda.com&gt;<BR>
</A>Subject: $0.02 tip - More on commenting code in vi <BR>
</P>

<P>I'm generally ON the code I want to comment, so instead of having to
find out line numbers and then perform a substitution on those lines to
insert # characters, I just map my # key to &quot;go to the beginning of
the current line, go into insert mode, insert a # and a space, exit insert
mode, go down one line&quot; </P>

<P>You can map your # key this way (or whatever key you want to assign
it to, but be careful) by putting the following in your .exrc file: </P>

<PRE>map # I# ^[j
</PRE>

<P>That &quot;^[&quot; is created by typing Ctrl-v and then hitting ESC,
so you literally type: </P>

<PRE>map&lt;SPACE&gt;#&lt;SPACE&gt;I#&lt;SPACE&gt;&lt;Ctrl-v&gt;&lt;ESC&gt;j
</PRE>

<P>Then all you have to do to go comment-crazy is find where you want to
start and hold down your # key. </P>

<P>Jeff Blaine <BR>
</P>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="x2"></A>More
X Term Title Trick 2</H3>

<P>Date: Sun, 08 Sep 1996 23:38:31 -0500 <BR>
From: the Edward Blevins <A HREF="mailto:thedward@mail.utexas.edu">&lt;thedward@mail.utexas.edu&gt;
<BR>
</A>Subject: Re:XTerm Title Trick 2 <BR>
</P>

<P>In issue #9 of LG, one of the two cent tips is about how to put the
hostname in the title of your xterm. It mentions precmd for csh, but not
the bash equivalent. The way I do this in bash is as follows: </P>

<PRE> 
  if [ $TERM = 'xterm' ]
  then export PROMPT_COMMAND='echo -ne
&quot;\033]2;&quot;`whoami`@`hostname`&quot;\007&quot;'
  fi
</PRE>

<P>this can just go in your .bashrc, lots of fun. I add the whoami, because
I am a sysadmin, and its a convienient way to tell if I am root, in addition
to the '#' on the prompt. Another variation I use sometimes is : &quot;`whoami`@`hostname`:`pwd`&quot;
then I can remove the path from my prompt. </P>

<P>ps the LG is GREAT! Keep up the good work. Thank you very much! </P>

<PRE>--  
the Edward Blevins 
thedward@mail.utexas.edu  
</PRE>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="bash"></A>Bash
Quick Tip</H3>

<P>Date: Thu, 12 Sep 1996 14:59:41 +1000 <BR>
From: Jeremy Laidman <A HREF="mailto:JPLaidman@ACSLink.net.au">&lt;JPLaidman@ACSLink.net.au&gt;<BR>
</A>Subject: Bash Quick tip <BR>
</P>

<P>Issue 8 had a 2c tip &quot;There and Back!&quot; describing a neat way
to change between two directories quickly. The method was to use &quot;cd
~-&quot; which will set the working directory to the previous one you were
in. </P>

<P>Bash (and several other shells I've tested) will do this without the
tilde, ie &quot;cd -&quot;. This saves me two keystrokes (including the
shift key). </P>

<P>Cheers </P>

<PRE>---------------------------------------------------------------- 
Jeremy Laidman                          JPLaidman@ACSLink.net.au  
Networking Consultant                            +61 0416 290866  
Canberra Institute of Technology                  +61 6 207 4272  
</PRE>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="redhat"></A>Neat
Red Hat Management Trick</H3>

<P>Date: Mon, 16 Sep 1996 01:33:51 -0400 (EDT) <BR>
From: Mike Acar <A HREF="mailto:mike@contract.kent.edu">&lt;mike@contract.kent.edu&gt;<BR>
</A>Subject: Neat Red Hat management trick <BR>
</P>

<P>Well, it's not really a trick per se. If you're like me, you make an
attempt to keep your Red Hat system current- at least, in some respects.
Tonight, looking at a man page which mentioned Linux 0.99.11 brought to
mind the thought that I should upgrade my aging Red Hat 2.0 installation
to something more current; fast on its heels was a curiousity about just
what I have taken from where. So with a little bit of shell-play and some
suggestions from my friend, the following was produced: </P>

<PRE> 
rpm -qai | grep Dist | awk -F': ' '{print $3}' | sort | uniq -c
</PRE>

<P>This will tell you all the distributions you have installed RPMs from,
and the number of RPMs from each. </P>

<P>Mike Acar, mike@contract.kent.edu <BR>
Bret Martin, bret.martin@yale.edu <BR>
</P>

<PRE>--  
DZ-015 (Mike Acar)         Information Retrieval        Ministry of Information 

</PRE>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="find"></A>More
on Find and Alternatives</H3>

<P>Date: Sat, 14 Sep 1996 19:50:55 -0400 (EDT) <BR>
From: Bill Duncan <A HREF="mailto:bduncan@beachnet.org">&lt;bduncan@beachnet.org&gt;<BR>
</A>Subject: find tip... <BR>
</P>

<P>Hi Jim Murphy. <BR>
Saw your &quot;find&quot; tip in issue #9, and thought you might like a
quicker method. I don't know about other distributions, but Slackware and
Redhat come with the GNU versions of locate(1) and updatedb(1) which use
an index to find the files you want. The updatedb(1) program should be
run once a night from the crontab facility. To ignore certain sub-directories
(like your /cdrom) use the following syntax for the crontab file: </P>

<PRE> 
41 5 * * *  updatedb --prunepaths=&quot;/tmp /var /proc /cdrom&quot; &gt; /dev/null 2&gt;&amp;1
</PRE>

<P>This would run every morning at 5:41am, and update the database with
filenames from everywhere but the subdirectories (and those below) the
ones listed. </P>

<P>To locate a file, just type &quot;locate filename&quot;. The filename
can also do partial matching. The search only takes a few seconds typically,
and I have tens of thousands of files. </P>

<P>The locate(1) command also has regular expression matching, but I often
just pipe it through agrep(1) (a faster grep) to narrow the search if I
want. Thus: </P>

<PRE> 
  locate locate | agrep -v man
</PRE>

<P>..would exclude the manpage for example, and only show me the binary
and perhaps the sources if I had them online. (The -v flag excludes the
pattern used as an argument.) Or the binary alone along with a complete
directory listing of it with the following command: </P>

<PRE> 
  ls -l `locate locate | agrep bin`
</PRE>

<P>The find(1) command is a great &quot;swiss-army knife&quot; (and actually
not that bad once you get used to it), but for the 90% of the cases where
you just want to search by filename, the locate(1) command is *far* faster,
and much easier to use. </P>

<PRE>--  
Bill Duncan, VE3IED  | BeachNet  --&gt;  http://www.beachnet.org 
bduncan@BeachNet.org |   - Network/System Administration 
bduncan@ve3ied.uucp  |   - Web Design, Hosting Services  
+1 416 693-5960      |   - System Analysis/Design/Programming 
</PRE>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="pico"></A>Pico
Control M Trick</H3>

<P>Date: Sat, 14 Sep 96 09:28 PDT <BR>
From: Peter <A HREF="mailto:pb@europa.com">&lt;pb@europa.com&gt;<BR>
</A>Subject: Easier ^M removal with Pico <BR>
</P>

<P>I've been using this trick for a long time .. its a lot easier then
defining macros in Emacs, too. All it requires is a recent copy of the
Pico editor. </P>

<P>Load the file you wish to strip ^Ms from, make a small change in the
file (like hitting the space bar, then delete), and save it. No more ^Ms!
</P>

<P>Peter </P>

<P>
<HR></P>

<P><!--===================================================================--></P>

<H3><IMG SRC="../gx/lil2cent.gif" ALT="" HEIGHT=51 WIDTH=126 ALIGN=CENTER><A NAME="emacm"></A>Yet
Another Emacs Control M Trick</H3>

<P>Date: Tue, 24 Sep 1996 19:26:10 -0700 <BR>
From: Dan Gunter <A HREF="mailto:dang@hooked.net">&lt;dang@hooked.net&gt;<BR>
</A>Subject: re: emacs ^M trick </P>

<P>I'm new to emacs, so I use a very simple trick to search &amp; replace
on special characters: I cut or copy them into the paste buffer, then Meta-%
and hit Control-Y to yank them back into the minibuffer. This isn't elegant,
but it's very easy to remember, and seems to work for everything. </P>

<P>
<HR></P>

<P><!--====================================================================--><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<P>
<HR></P>

<P><A NAME="lg_bytes10"></A><IMG SRC="../gx/bytes.gif" ALT="News Bytes" HEIGHT=133 WIDTH=267>
</P>

<P>
<HR></P>

<H3>Contents:</H3>

<UL>
<LI><A HREF="#general">News in General</A> </LI>

<LI><A HREF="#software">Software Announcements</A> </LI>
</UL>

<P>
<HR></P>

<CENTER><P><!-- =================================================================== --></P></CENTER>

<H3 ALIGN=CENTER><A NAME="general"></A>News in General </H3>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Linux Trademark: Let's
fix it.</H3>

<P>From: Paul Bingman <A HREF="mailto:paul@edgewood.portland.or.us">paul@edgewood.portland.or.us</A><BR>
</P>

<P>As you are no doubt aware, some (insert your favorite deragatory epithet)
has trademarked the name &quot;Linux&quot; is now out trying to collect
from everyone they can. </P>

<P>An intellectual property attorney friend of mine, G. Gervaise Davis
III, is offering to get this trademark killed pro bono, if we can cover
the expenses. His opinion, not having seen the original papers filed for
the trademark, is that the original has absolutely no legal standing, and
will probably be killed by the U.S. Patent and Trademark Office as soon
as we make the proper legal moves. </P>

<P>Please forward this email to anyone/everyone. I'm especially interested
in hearing from anyone who has received a collection letter, and also from
Linus or someone else who can direct us to where the trademark should rightfully
go. Also, this effort should be coordinated nationally or globally. </P>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Message from WorkGroup
Solutions</H3>

<P>September 19, 1996 <BR>
Mark Bolzern, President WGS <BR>
Member Board of Directors, Linux International <BR>
</P>

<P>With regard to the attack made on WGS, as well as the Greater Linux
Community by William R. Della Croche claiming that he owns the Linux Trademark...
There is no way this is true. We have retained an attorney and will be
making a public announcement soon that benefits the entire Linux community.
Thousands are aware of this situation, and have offered to help. The best
help you could give us, is to see if there is something we offer in our
Linux Shopping mall that you would like to own, and if so buy it. We add
new products almost daily. If you don't see what you want, ask, or refer
a friend to us. Thank you! </P>

<P>News &amp; Information Account: wgsnews@wgs.com WorkGroup Solutions,
Inc. <BR>
mailto:info@wgs.com, http://www.wgs.com/, ftp://ftp.wgs.com/ <BR>
Telephone: 303-699-7470 Fax: 303-699-2793 <BR>
</P>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Linux HOWTO Project:
Consultants HOWTO</H3>

<P>The first public release of the Linux Consultants HOWTO has been published.
The Linux Consultants HOWTO is a listing of companies providing commercial
Linux related support. </P>

<P>Version 2.12, dated September 18, 1996, can be obtained from the following
places: </P>

<UL>
<LI>http://www.sypher.com/tbm/Consultants-HOWTO <BR>
</LI>

<LI>ftp://ftp.sypher.com/tbm/HOWTO <BR>
</LI>
</UL>

<P>The following files are available: </P>

<UL>
<LI>Consultants-HOWTO.txt </LI>

<LI>Consultants-HOWTO.sgml </LI>

<LI>Consultants-HOWTO.html </LI>
</UL>

<P>Additional Information: Martin Michlmayr, <A HREF="mailto:tbm@sypher.com">tbm@sypher.com
<BR>
</A><A HREF="http://www.sypher.com/tbm">http://www.sypher.com/tbm </A><BR>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Linux Articles</H3>

<P>Here's some articles of Linux interest that can be found on the web:
</P>

<UL>
<LI>&quot;Linux Matters&quot; <I>Byte</I> (Feb 96): An overview (5 pgs)
of what linux is, how to get it, what to do with it. <A HREF="http://www.byte.com/art/9602/sec11/art7.htm">http://www.byte.com/art/9602/sec11/art7.htm</A>
</LI>

<LI>&quot;The Linux Phenomenon&quot; <I>Byte</I> (Nov 95): Short (1/2 pg)
overview. <A HREF="http://www.byte.com/art/9511/sec6/art3.htm">http://www.byte.com/art/9511/sec6/art3.htm</A>
</LI>

<LI>&quot;Implementing Loadable Kernel Modules for Linux&quot; by Matt
Welsh <I>Dr. Dobbs</I>: (5 pgs). <A HREF="http://www.ddj.com/ddj/1995/1995.05/welsh.htm">http://www.ddj.com/ddj/1995/1995.05/welsh.htm</A>
</LI>
</UL>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Linux User Support Team
(L.U.S.T.)</H3>

<P>Purpose: To fill in an existing gap in the Linux world and provide users
with various services/data that are not otherwise available online. To
provide a clearing house for these same services. </P>

<P>Discussion: The L.U.S.T. (surprised nobody thought of the name earlier!)
is not intended to be involved with programming, patching, updating, or
such. It's to support the everyday, run-of-the-mill user with various support
not offered elsewhere in the Linux world with data or services such as
the Workman Database Project described below. </P>

<P>To join/get involved in/comment on L.U.S.T., send email to: <A HREF="mailto:joat1@concentric.net">joat1@concentric.net</A>
</P>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>WWW: Enterprise Computing
Linux</H3>

<P>I have started collecting information on Linux as an Enterprise Computing
Platform. By &quot;Enterprise Computing&quot; I mean what the big companies
mean: large systems, high availability, high performance and &quot;industrial
strength&quot; in general. Currently, topics include: </P>

<UL>
<LI>Databases </LI>

<LI>Clusters/SMP </LI>

<LI>Configuration Mangemet </LI>

<LI>WAN Internetworking, incl Frame Relay and X.25 </LI>

<LI>Network Mangement and Administration </LI>

<LI>Disk Mirroring and RAID </LI>

<LI>Fault Tolerance </LI>
</UL>

<P>The pages can be viewed from </P>

<P><A HREF="http://204.157.166.19/linux/index.html">http://204.157.166.19/linux/index.html
</A></P>

<P>Additional information: Linas Vepstas, Lamebrain Enterprises <A HREF="mailto:linas@fc.net">linas@fc.net</A>
</P>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Linus News</H3>

<P>Pablo Kiryluk of GM Communications, InterSoft's RRPP, writes: </P>

<P>Linus Torvalds, the Finish guru creator of the operating system &quot;Linux&quot;
landed in Buenos Aires, Argentina, to the expectation of many. Invited
by InterSoft, the multinational software producer, Mr. Torvalds lectured
to a wide range of public about the &quot;Software Free&quot; concept,
its relation with Internet and Linux' characteristics. </P>

<P>The range of ideas spread by Linus Torvalds in Argentina where laid
out in terms of &quot;knowledge sharing&quot; and &quot;composing from
different creators&quot;. &quot;Company's tendencies will integrate parts
of free software forming a system to curb the commercial industry of software&quot;
--substantiated Mr. Torvalds. Also, the concept of &quot;the idea that
technology were humanity' patrimony, based on the free distribution of
software and its source codes&quot; was expressed in several occasions.
</P>

<P>Also, Torvalds decided also to introduce &quot;Scriptum&quot;, the first
adaptable editor to different Linux' environments, created by InterSoft.
Scriptum was created in Argentina and developed as a powerful tool capable
to run of different platforms and offer several features. With Scriptum,
almost the entire working environment can be configured, totally integrated
to RCS/SCCS tools and UNIX (grepp, diff, etc.) and powerful navigation
commands to find sources, data and documents. </P>

<P>
<HR></P>

<P><!-- =====================================================================  --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>More Linus News</H3>

<P>The San Jose Mercury News published an interview with Linus Torvalds
on September 8, 1996 in which Linus is quoted as saying </P>

<BLOCKQUOTE>
<P><I>Microsoft operating systems are bad, and their morals are even worse.
But they make some good applications. </I></P>
</BLOCKQUOTE>

<P>Check it out in Section E of that newspaper, or web site: <A HREF="http://www.sjmercury.com/business/finland/torvalds.htm">http://www.sjmercury.com/business/finland/torvalds.htm</A>
</P>

<P>
<HR></P>

<CENTER><P><!-- =================================================================== --></P></CENTER>

<H3 ALIGN=CENTER><A NAME="software"></A>Software Announcements </H3>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Soft Braille for Linux:
BRLTTY 1.0.1</H3>

<P>The official release of BRLTTY, a software system to allow access to
the console of a Unix system for users of soft Braille displays, has been
announced. </P>

<P>BRLTTY currently runs under Linux (kernel version 1.1.92 or later) on
a PC or DEC Alpha. </P>

<P>The package has been uploaded to sunsite.unc.edu in the directory /pub/Linux/Incoming.
It is expected to move to /pub/Linux/system/Access at some later date (please
note the move from /pub/Linux/utils/console). </P>

<P>FEATURES </P>

<UL>
<LI>Full implementation of the standard screen review facilities. </LI>

<LI>A wide range of additional optional features, including blinking cursor
and capital letters, screen freezing for leisurely review, attribute display
to locate highlighted text, hypertext links, etc. </LI>

<LI>`Intelligent' cursor routing. This allows easy movement of the cursor
in text editors etc. without moving the hands from the Braille display.
</LI>

<LI>A cut &amp; paste function. This is particularly useful for copying
long filenames, complicated commands etc. </LI>

<LI>An on-line help facility. </LI>

<LI>Support for multiple Braille codes. </LI>

<LI>Modular design allows relatively easy addition of drivers for other
Braille displays, or even (hopefully) porting to other Unix-like platforms.
</LI>
</UL>

<P>Additional information: Nikhil Nair: founder of the BRLTTY project and
author of the Tieman B.V. CombiBraille driver. <A HREF="mailto:nn201@cus.cam.ac.uk">mailto:nn201@cus.cam.ac.uk</A>
</P>

<P>Nicolas Pitre: Author of the driver for the Alva series. <A HREF="mailto:nico@cam.org">nico@cam.org</A>
</P>

<P>Stephane Doyon: Author of the driver for the TSI displays (Navigator
and PowerBraille 40), <A HREF="mailto:doyons@jsp.umontreal.ca">doyons@jsp.umontreal.ca</A>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>FidoTools</H3>

<P>Nickolay Grygoryev of SPb State University announced another FIDONET-related
package called FidoTools. In general, it's file-echo tosser. Now it may
be used on any node as file-echo manager (but version 0.9 does not have
a mail interface for subscribing and unsubscribing - this will be done
in version 1.0). All documentation is included into archive. </P>

<PRE> 
Primary-site:   ns.aanet.ru /vol1/nick/Linux/system/Fido
                FidoTools-0.9.tar.gz
Alternate-site: sunsite.unc.edu /pub/Linux/system/Fido 
                FidoTools-0.9.tar.gz
Platforms:      C compiler, FidoNet mailer (Bink-style)
Copying-policy: GPL
</PRE>

<P>Additional information:<BR>
Nickolay G. Grygoryev <A HREF="mailto:shadow@nickhome.stud.pu.ru">shadow@nickhome.stud.pu.ru<BR>
</A>St.Petersburg, Russia </P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>GNU Hurd release 1.0</H3>

<P>Version 0.1 of the GNU Hurd, is now available via anonymous FTP from
prep.ai.mit.edu [18.159.0.42] in the file <A HREF="http://www.redhat.com/pub/gnu/hurd-0.1.tar.gz">/pub/gnu/hurd-0.1.tar.gz</A>
(about 1.2 MB compressed). There is also a patch file of diffs from the
0.0 release in <A HREF="http://www.redhat.com/pub/gnu/hurd-0.0-0.1-diff.gz">/pub/gnu/hurd-0.0-0.1-diff.gz</A>
(about 75 KB compressed). </P>

<P>The GNU Hurd, plus Mach, is a kernel, not an operating system. The GNU
operating system, like the Unix operating system, consists of many components,
including kernel, libraries, compilers, assembler, shell, parser generators,
utilities, window system, editors, text formatters, and so on. </P>

<P>Most GNU software is packed using the GNU `gzip' compression program.
Source code is available on most sites distributing GNU software. </P>

<P>For information on how to order GNU software on tape or cd-rom, and
printed GNU manuals, check the file etc/ORDERS in the GNU Emacs distribution,
ftp the file /pub/gnu/GNUinfo/ORDERS on prep, or e-mail a request to: <A HREF="mailto:gnu@prep.ai.mit.edu">gnu@prep.ai.mit.edux
</A></P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>ImageMagick Release 3.7.6</H3>

<P>ImageMagick (TM), version 3.7.6, is a package for display and interactive
manipulation of images for the X Window System. Although the software is
copyrighted, it is available for free and can be redistributed without
fee. </P>

<P>In addition to the image display program, ImageMagick also has command
line programs that perform these functions: </P>

<UL>
<LI>Describe the format and characteristics of an image </LI>

<LI>Convert an image from one format to another </LI>

<LI>Transform an image or sequence of images </LI>

<LI>Read an image from an X server and output it as an image file </LI>

<LI>Animate a sequence of images </LI>

<LI>Combine one or more images to create new images </LI>

<LI>Create a composite image by combining several separate images </LI>

<LI>Segment an image based on the color histogram </LI>

<LI>Retrieve, list, or print files from a remote network site </LI>
</UL>

<P>ImageMagick supports many of the more popular image formats including
JPEG, PNG, TIFF, Photo CD, etc. </P>

<PRE> 
Primary-site:   ftp.wizards.dupont.com /pub/ImageMagick/binaries
                841k ImageMagick-i486-linux-ELF.tar.gz

Alternate-site: sunsite.unc.edu /pub/Linux/X11/xapps/graphics
                841k ImageMagick-3.7.6-elf.tgz
                  1k ImageMagick-3.7.6-elf.lsm

Platforms:      Linux 1.2/2.0, XFree 3.1.2
</PRE>

<P>Additional Information: <BR>
Alexander.Zimmermann <A HREF="mailto:zimmermanna@fmi.uni-passau.de">zimmermann@fmi.uni-passau.de<BR>
</A><A HREF="http://www.redhat.com/linux-info/lg/issue10/http ://www.uni-passau.de/~zimmerma">http://www.uni-passau.de/~zimmerma
</A></P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>masqd/masq for Linux
Firewall</H3>

<P>A new release of masqd/masq software is available free at: </P>

<P><A HREF="http://www.els.url.es/~si03786/masq.html">http://www.els.url.es/~si03786/masq.html
</A></P>

<P>This is a software to manage remotely a Linux firewall with masquerade
support. There are three main programs: A daemon (masqd), a network client
to connect to the daemon (masq) and a local configuration utility (lmasq)
which integer this masq kit. </P>

<P>Some characteristics of the kit are: </P>

<UL>
<LI>Possibility of controling the three firewalls in a Linux System (input,
forward and output). </LI>

<LI>Supports of masquerade policy, to masquerade paquets if Linux kernel
supports it. </LI>

<LI>User authentification in each connection. </LI>

<LI>CRC checking of network packets. </LI>

<LI>Allows to control remotely masquerade entries. </LI>
</UL>

<P>Additional Information: <BR>
Jaume Miralles, <A HREF="mailto:si03786@els.url.es">si03786@els.url.es
<BR>
</A>Barcelona, SPAIN <A HREF="http://www.els.url.es/~si03786">http://www.els.url.es/~si03786
</A></P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>SpriteField - a sprite
library for Qt/X11</H3>

<P>The SpriteField Class Set is a collection of classes supporting multiple
simultaneous flicker-free displays of efficiently redrawn continuous and
non-continuous animated areas with the Qt GUI Toolkit. Animated areas are
two-dimensional rectangular areas upon which two-dimensional masked raster
images are in motion. Applications vary from computer games to simulations.
Qt 0.99 is required. Full sources and an precompiled example program are
included and can be found at: <BR>
<A HREF="http://student.uq.edu.au/~s002434/qt/SpriteField/doc/html/">http://student.uq.edu.au/~s002434/qt/SpriteField/doc/html/
</A><BR>
</P>

<P>Additional Information: <BR>
Warwick Allison <A HREF="mailto:warwick@cs.uq.oz.au">warwick@cs.uq.oz.au<BR>
</A>Computer Science Department <BR>
University of Queensland <BR>
Brisbane, Australia <BR>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61> TeamRooms - Internet
groupware environment for Linux</H3>

<P>Mark Roseman, University of Calgary CPSC, announced the first public
beta release of TeamRooms, an Internet groupware environment that lets
you work together with colleagues in real-time or asynchronously, using
Unix, Mac and Windows. </P>

<P>TeamRooms provides &quot;shared spaces&quot; on the Internet allowing
groups to share information. These electronic team rooms provide places
to meet in real-time, or a common locale to leave information for other
collaborators. TeamRooms combines real-time groupware technologies such
as shared whiteboards, chat rooms, and customizable groupware applets with
a persistent work environment. </P>

<P>Information on downloading is available on our Web site: <BR>
<A HREF="http://www.cpsc.ucalgary.ca/projects/grouplab/teamrooms/">http://www.cpsc.ucalgary.ca/projects/grouplab/teamrooms/
</A></P>

<P>Additional Information: <BR>
Mark Roseman, Research Associate, <A HREF="http://www.redhat.com/linux-info/lg/issue10/mailtoroseman@cpsc.ucalgary.ca">roseman@cpsc.ucalgary.ca
<BR>
</A>University of Calgary, <A HREF="http://www.cpsc.ucalgary.ca/~roseman">http://www.cpsc.ucalgary.ca/~roseman<BR>
</A>Calgary, Alta CANADA T2N 1N4 <BR>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>Turbo Linux 96</H3>

<P>Pacific HiTech is proud to announce Turbo Linux 96 : Slackware Edition.
</P>

<P>This product is based on the latest Slackware 3.1 Linux release. It
incorporates the 2.0 kernel, the floppy-less install, the live filesystem,
and everything else that you would expect. Best of all, we have it for
sale for only $12.95 (plus $5 shipping inside the USA, $10 international).
</P>

<P>Additional Information: <BR>
Scott M. Stone, <A HREF="mailto:sstone@pht.com">sstone@pht.com</A> <BR>
Pacific HiTech, Inc., <A HREF="http://www.pht.com/">http://www.pht.com/
</A><BR>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --></P>

<H3><IMG SRC="../gx/bolt.gif" ALT="" HEIGHT=43 WIDTH=61>V Multi-Platform GUI</H3>

<P>Version 1.13 of V for X, Windows 1.3, and WIN32 (NT, Windows95) was
released on September 9, 1996. It is available on the World Wide Web at
<A HREF="http://www.cs.unm.edu/~wampler">http://www.cs.unm.edu/~wampler
</A>or via anonymous FTP at <A HREF="ftp://ftp.cs.unm.edu/pub/wampler">ftp://ftp.cs.unm.edu/pub/wampler</A>.
</P>

<P>V is an easy to program, cross-platform C++ GUI Framework. V was designed
to make it the easiest way to write C++ graphical user interface applications
available -- commercial, shareware, or freeware. </P>

<P>Most standard GUI objects are supported by V, including windows with
menus, status bars, tool bars, and a drawing canvas; modal and modeless
dialogs with the most common controls (buttons, lists, labels, text entry,
check and radio buttons, etc.); and portable printing support. </P>

<P>Additional Information: <BR>
Bruce E. Wampler, Ph.D., <A HREF="mailto:wampler@cs.unm.edu">wampler@cs.unm.edu<BR>
</A><A HREF="http://www.cs.unm.edu/~wampler">http://www.cs.unm.edu/~wampler</A>
</P>

<P>
<HR></P>

<P><!-- =================================================================== --><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<P>
<HR WIDTH="100%"></P>

<P><A NAME="radio"></A><!--===================================================================--></P>

<H1 ALIGN=CENTER>Hams, Packet Radio and Linux</H1>

<H4 ALIGN=CENTER>by Phil Hughes, WA6SWR, <A HREF="mailto:phil@ssc.com">phil@ssc.com</A></H4>

<H5 ALIGN=CENTER>Copyright (c) 1996</H5>

<H5 ALIGN=CENTER>Published in Issue 10 of the Linux Gazette</H5>

<P>
<HR></P>

<P>This year's ARRL/TAPR sponsored conference on Digital Communications
was in Seattle on September 20-22. Being a ham, a packet fan and 18 miles
away from the conference, I decided to attend. I also offered to bring
some <I>Linux Journal</I> magazines to give away. By the end of the conference
&quot;some&quot; had become about 100. </P>

<P>The papers presented varied from very introductory material to a serious
look at how to equalize group delay of IF filters. Many of the papers and
one of the three workshops dealt with a system called Automatic Position
Report System. For those not familiar with this, a GPS receiver is combined
with a packet station to send out position reports. </P>

<P>But, the purpose of this article is not to talk about the &quot;ham
content&quot; of the conference (if you want more info on that, check out
<A HREF="http://www.tapr.org/">http://www.tapr.org/</A>, but to talk about
the L-word. </P>

<P>In the first workshop (on APRS), Keith Sproul demonstrated both a Windows
and a Mac version of the system, but regularly referenced the fact that
a Linux version also existed. I was surprised (as there was no mention
of a Sun version or any other Unix-like version), but I was now sure that
Linux had infiltrated the ham packet radio community pretty seriously.
</P>

<P>The L-word then continued to come up in discussions with people. It
varied from comments about installing Linux to how Linux became a significant
part of a ham network. For example, in Barry McLarnon and Dennis Rosenauer's
presentation on Wireless Networking Using the WA4DSY 56K RF Modem Technology,
Barry said &quot;Linux is the platform of choice&quot;. Later, when describing
the Ottawa MAN (Metropolitan Area Network) he pointed out that their Internet
server (hydra.carleton.ca) is a Linux box, and they, when talking about
the packet gateway machine, said &quot;It hasn't been converted to Linux
yet.&quot; </P>

<P>At the end of their presentation we had a chance to play with a wireless
network set up in the room. The machine on one end of the 56K link was
running Linux as was one downstream machine off the other end. </P>

<P>All in all, the conference was good for Linux. </P>

<P>Phil Hughes <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR WIDTH="100%"></P>

<P><A NAME="in.memory"></A></P>

<H3 ALIGN=CENTER>In Memory of Mark A. Horton </H3>

<P>
<HR></P>

<P>Date: Wed, 11 Sep 1996 16:46:31 GMT <BR>
From: Victoria Welch vikki@seastar.org <BR>
Organization: Welch Research laboratories <BR>
</P>

<P>Mark A. Horton (mah@netmha.com) passed away Friday September 7, 1996.
Cause currently unknown, but poor health is suspected. he did have a lot
of health problems, although he never let them keep him down long, in so
many ways he was such an inspiration! </P>

<P>Having been through the rest of the *nixes, and knowing the subject
well, he was one of the greatest proponents of Linux. His enthusiasm and
willingness to help anyone at any time were his greatest gifts to the Linux
community. </P>

<P>His kindness, willingness to help others in many ways including Linux
and his generosity will be missed by those of us that knew him and an example
for all of us to strive for. For me personally, he was my best friend and
mentor. He taught myself and *MANY* others much about the nuts and bolts
of Linux in a joyous way that was informative and instructive and often
most pleasantly humorous. Most any interaction with Mark was a good time.
</P>

<P>Having spent a great many hours with him personally as well as on the
phone, he made is very clear that he didn't want any morose happenings
should anything ever happen to him, There will be a party by his friends
to honor that request sometime in the near future. Will plan on celebrating
his contributions and the many wonderful things that there are to be remembered
about him. He was one of the true good guys and his joyous, creative, tenacious,
encouraging spirit will be missed by those that knew him. To the many that
knew Mark and to the many who didn't, hoist one to one of the greats! He
will be missed. </P>

<P>Thanks &amp; Take care, Vikki.<BR>
- -- <BR>
vikki@seastar.org, Sys/Net/WebAdmin Seastar.org, WV9K, DoD#-13 <BR>
Victoria Welch, Senior Microcontroller Applications Design Engineer.<BR>
Welch Research Laboratories; 316 West Benson Street, Suite 2100 <BR>
Decatur, GA 30030-4312; 404-371-1614 <BR>
Work: http://www.seastar.org - Personal: http://www.seastar.org/~vikki
<BR>
</P>

<P>
<HR></P>

<P><!--====================================================================--><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<P>
<HR></P>

<P><A NAME="mconv2"></A></P>

<H1 ALIGN=CENTER>Mconv2 Utility</H1>

<H4 ALIGN=CENTER>by Nic Tjirkalli <A HREF="mailto:nic@pipex-sa.net">nic@pipex-sa.net</A>,
<A HREF="http://www.pipex-sa.net/~nic">http://www.pipex-sa.net/~nic </A></H4>

<H5 ALIGN=CENTER>Copyright (c) 1996</H5>

<H5 ALIGN=CENTER>Published in Issue 10 of the Linux Gazette</H5>

<P>
<HR></P>

<P>Normally, users of <B>PS/2</B> type mice have a problem in that a PS/2
type mouse cannot simultaneously be shared among different applications
such as <I>gpm</I> (selection) and <I>XFree86</I>. That was until the discovery
of a tiny utility called, <B><FONT SIZE=+1>mconv2</FONT></B>. Mconv2 allows
several programs to use a PS/2 type mouse at the same time. <BR>
</P>

<P>The mconv2 utility also supports the use of a PS/2 type mouse with applications
that do not understand the PS/2 mouse protocol, but understand the microsoft
serial mouse protocol (such as <I>svgalib</I>). This document only descrdibes
the sharing of the PS/2 type mouse - not its use as a microsoft type mouse
- for information on this, read the <B>README</B> file included with the
mconv2 distribution. <BR>
</P>

<P>Installing and using mconv2 is <B>VERY</B> simple :- <BR>
</P>

<OL>
<LI><B>Getting mconv2</B> <BR>
Mconv2 can be downloaded from a variety of Linux archive sites. I got my
copy from <BR>
</LI>

<CENTER><P><A HREF="http://sunsite.unc.edu/pub/Linux/system/Misc/mconv2.tar.gz">http://sunsite.unc.edu/pub/Linux/system/Misc/mconv2.tar.gz</A>
<BR>
</P></CENTER>

<LI><B>Extracting Distribution<BR>
</B>Mconv2 is distributed as a compressed (gz) tar archive. Hence, it needs
to be extraceted in a suitable directory before it can be installed. I
used the <I>/usr/src</I> directory, but any directory will do. Copy the
mconv2 distribution file (mconv2.tar.gz) to the selected working directory,
eg. <I>/usr/src</I> (or the directory you care to extract it in) as follows
:- <BR>
</LI>

<PRE>    cp mconv2.tar.gz /usr/src
  </PRE>

<P>Go to the working directory and extract the mconv2 archive, as follows
:- <BR>
</P>

<PRE>    cd /usr/src
    tar -zxvf mconv2.tar.gz 
  </PRE>

<P>This will create a subdirectory called <I>mconv2</I> containing, </P>

<UL>
<LI>the mconv2 source code - <I>mconv2.c</I> </LI>

<LI>a binary compiled mconv2 executable - <I>mconv2</I> </LI>

<LI>supporting documentation files - <I>mconv2.lsm</I> and <I>README</I>
</LI>
</UL>

<P><BR>
</P>

<LI><B>To compilie mconv2, or not</B> <BR>
Together with the source and supporting documentation, the mconv2 distribution
also comes with a pre-built binary of the program. This can be used as-is
or the program can be recompiled very easily, as follows :- <BR>
</LI>

<PRE>    gcc -O2 -o mconv2 mconv2.c
  </PRE>

<P><BR>
</P>

<LI><B>Installing the mconv2 binary</B> Copy the pre-built, or newly made,
mconv2 binary file (<I>mconv2</I>) to an appropriate directory for executing
binarys from - I use <I>/usr/local/bin</I>. <BR>
</LI>

<PRE>    cp mconv2 /usr/local/bin 
  </PRE>

<LI><B>Builiding a fifo for the PS/2 mouse<BR>
</B>Create a fifo device (pseudo mouse driver) for the PS/2 mouse, as follows
:- <BR>
</LI>

<PRE>    mkfifo -m 666 /dev/ps2mouse
  </PRE>

<P><BR>
</P>

<LI><B>Using mconv2</B> <BR>
Before running any programs using the PS/2 mouse, mconv2 should be run
first and other programs needing the mouse, should be configured to use
the PS/2 pseudo device, <I>/dev/ps2mouse</I>. It is probably best, to start
mconv2 from the <I>/etc/rc.d.rc.local</I> file with the following command
:- </LI>

<PRE>    echo -n &quot;Runnig mconv2 .... &quot;
    /usr/local/bin/mconv2 /dev/psaux -ps2 /dev/ps2mouse &amp;
    echo &quot;Done&quot;
  </PRE>

<P><B>NOTE :- this assumes your original mouse device was /dev/psaux</B>
<BR>
</P>

<LI><B>Configuring other programms to use mconv2</B> <BR>
As mentioned in the point above, other programs requiring the PS/2 mouse
must be configured to use the mconv2 pseudo mouse device - <I>/dev/ps2mouse</I>.
<BR>
</LI>

<P>Examples :- <BR>
</P>

<UL>
<LI>To set up <B>gpm</B>, to use this pseudo device, invoke it as follows
:- </LI>

<PRE>    gpm -t ps2 -m /dev/ps2mouse &amp;
  </PRE>

<P><B>NOTE :- the -m option tells gpm what mouse device to use</B> <BR>
</P>

<LI>To set up <B>XFree86</B> to use the pseudo device, modify the <B>Pointer</B>
section of the <B>XF86Config</B> file to set the mouse device to <B>/dev/ps2mouse</B>
as follows :- </LI>

<PRE>    Section &quot;Pointer&quot;
      Protocol    &quot;PS/2&quot;
      Device      &quot;/dev/ps2mouse&quot;
  </PRE>
</UL>
</OL>

<P>Enjoy the PS/2 mouse sharing. My thanx to Frode Fjeld <A HREF="mailto:frodef@stud.cs.uit.no">frodef@stud.cs.uit.no</A>
for developing the mconv2 distribution. <BR>
</P>

<P>Nic Tjirkalli <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR></P>

<P><A NAME="netday"></A></P>

<H3 ALIGN=CENTER>NetDay96 and Linux </H3>

<P>
<HR></P>

<P>Date: Sat, 14 Sep 1996 08:33:11 -0500 (CDT) <BR>
From: &quot;Paul L. Rogers&quot; RogersPL@datasync.com <BR>
</P>

<P>Good Morning, </P>

<P>Late last week I became aware of the national NetDay96 project and volunteered
at my daughter's school. During the weekend, I realized that this was an
opportunity to involve the Linux community in a project that could not
only benefit our local schools, but expose new classes of people to Linux.
</P>

<P>If this topic is suitable for SSC's ventures to publicize, please help
spread the word. For NetDay96, maybe something in the _Linux Gazette_ could
reach a few people in time to for them to make a contribution. If there
is a NetDay97, perhaps an article in the _Linux Journal_ reporting on NetDay96
with suggestions on how to promote Linux during such an event would be
appropriate. </P>

<P>Attached is a posting that recently (1996/09/13) appeared on comp.os.linux.announce.
</P>

<P>A data point: The October 1996 LJ arrived in Ocean Springs, Mississippi
on Friday. </P>

<P>I strongly agree with &quot;Linux people, now is the time to strike.&quot;
and have recently become much more aggressive in sharing my experiences
with Linux. Would you be interested in an article providing guidelines
and suggestions on how to promote Linux? </P>

<P>Thank you for your time and if this project is not suitable for SSC,
perhaps other opportunities will allow us to work together in the future.
</P>

<P>Paul...<BR>
------------------------------------------------------------- <BR>
Paul L. Rogers http://www.netday96.com <BR>
RogersPL@datasync.com Are you prepared for NetDay96? <BR>
(601) 875-3779 Linux: It works for me. <BR>
------------------------------------------------------------- <BR>
</P>

<P>
<HR></P>

<H3>NetDay96 </H3>

<P>In the United States of America, preparations are under way for NetDay96.
NetDay96 is a grass-roots effort to install the basic wiring required to
make classrooms network ready. </P>

<P>If Linux enthusiasts across the United States would participate in their
local NetDay96 and be prepared to follow up with assistance in creating
highly functional and reliable networks for our school systems, much favorable
publicity could be generated for the Linux movement. </P>

<P>This is an unique opportunity to expand the name recognition of Linux.
</P>

<P>The following steps describe how you can help: </P>

<UL>
<LI>Volunteer to help wire a school and wear a Linux T-Shirt to the event.
</LI>

<LI>Be prepared to discuss the benefits (and limitations) of Linux. </LI>

<LI>Suggest that your Linux User's Group sponsors a school by funding a
wiring kit. The cost of the wiring kit ranges from $339 to $376 depending
on the vendor. </LI>

<LI>Contact a local Linux-based Internet Service Provider and request their
support for NetDay96. </LI>
</UL>

<P>For more information on NetDay96 or to volunteer, feel free to visit
their web site at <A HREF="http://www.netday96.com">http://www.netday96.com</A>.
</P>

<P>Some guidelines can be found at <A HREF="http://www.li.org/NetDay96-guidelines.html">http://www.li.org/NetDay96-guidelines.html
</A></P>

<P>If you volunteer, please consider sharing your experiences and success
stories with the community by sending them to <A HREF="mailto:li@li.org">li@li.org</A>.
We will post a report summarizing the success of this event. </P>

<P>If you do not live in the United States, you may want to consider organizing
a similar project for your community. </P>

<P>
<HR></P>

<H3>Linux International </H3>

<P>Linux International was established to promote the development and use
of Linux. The people at Linux International know how good Linux is and
want it to become an accepted competitor to products from even the largest
computer companies. Among other things, it serves as a bridge between the
dedicated and skilled community of developers, and the general world of
commerce and industry. </P>

<P>Linux International is a non-profit organization run by volunteers,
many of whom are high-profile Linux developers or activists. </P>

<P>For more information, please visit Linux International's World Wide
Web site at <A HREF="http://www.li.org/">http://www.li.org/</A> or contact
<A HREF="http://www.redhat.com/linux-info/lg/issue10/li@li.org">li@li.org</A>.
</P>

<P>Martin Michlmayr <BR>
<A HREF="http://www.redhat.com/linux-info/lg/issue10/tbm@sypher.com">tbm@sypher.com</A>
<BR>
<A HREF="http://www.sypher.com/tbm">http://www.sypher.com/tbm</A> <BR>
</P>

<P>Paul L. Rogers <BR>
(601) 875-3779 <BR>
<A HREF="http://www.redhat.com/linux-info/lg/issue10/rogerspl@datasync.com">rogerspl@datasync.com</A>
<BR>
</P>

<P>
<HR></P>

<P><!--====================================================================--><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<P>
<HR></P>

<P><A NAME="plugin.gimp"></A></P>

<P><!--======================================================================-->From
mjhammel@csn.net <BR>
Subject: Re: Gimp Tips &amp; Tricks <BR>
Date: Thu, 5 Sep 1996 22:39:21 -0600 (MDT) <BR>
</P>

<P>I have written a template for use by GIMP plug-in authors to write documentation
that will look good and be fairly uniform for our users. There is also
a detailed explanation that goes with it. The explanation is, in a sense,
a general explanation on how to use the LinuxDoc package, since that's
what we've decided to use for the GIMP Documentation Project. </P>

<P>You can take a look at both the template and the explanation at: <A HREF="http://www.csn.net/~mjhammel/gimp/gdp/gdp.html">http://www.csn.net/~mjhammel/gimp/gdp/gdp.html</A>
(look under the plug-ins documentation section). The explanation text follows
below. </P>

<P>-- Michael J. Hammel | Lottery: A tax on people who are bad at math.<BR>
<A HREF="mailto:mjhammel@csn.net">mjhammel@csn.net</A>, <A HREF="http://www.csn.net/~mjhammel">http://www.csn.net/~mjhammel</A>
<!--===================================================================--></P>

<P>
<HR></P>

<H1 ALIGN=CENTER>An Explanation of the Sample Plug-In SGML source template</H1>

<CENTER><P><FONT SIZE=-1>Copyright 1996 <BR>
by </FONT><FONT SIZE=+0>Michael J. Hammel <A HREF="mailto:mjhammel@csn.net">mjhammel@csn.net</A>
<BR>
</FONT><FONT SIZE=-1>Last Updated: 09/04/96 </FONT></P></CENTER>

<P>This is a long page, but don't let that scare you. Creating your documents
in SGML and using LinuxDoc tools to create your HTML, GNU Info, Man Page,
or other formats is really pretty simple. This page just happens to be
fairly thorough in explaining how to get it all done. </P>

<P>There are 6 sections in the SGML template: </P>

<UL>
<LI><A HREF="#title">The Title Information Section</A> </LI>

<LI><A HREF="#intro">The Introduction Section</A> </LI>

<LI><A HREF="#features">The Features Section</A> </LI>

<LI><A HREF="#dialog">The Dialog Box Section</A> </LI>

<LI><A HREF="#examples">The Examples Section</A> </LI>

<LI><A HREF="#notes">The Notes Section</A> </LI>
</UL>

<P>Each section is described below. Along with these, there are a number
of things you should be aware of when writing your document: </P>

<UL>
<LI><A HREF="#toc">The Table of Contents</A> </LI>

<LI><A HREF="#sections">Section markers</A> </LI>

<LI><A HREF="#paragraphs">Forcing new paragraphs</A> </LI>

<LI><A HREF="#comments">Comments</A> </LI>

<LI><A HREF="#lists">Lists</A> </LI>

<LI><A HREF="#examples">HTML or other format Specific tags</A> </LI>

<LI><A HREF="#various-formats">Notes about creating documents in the various
formats</A> </LI>
</UL>

<P>As far as LinuxDoc itself is concerned, here are some things you might
want to be aware of: </P>

<UL>
<LI>Where to get the LinuxDoc software: </LI>

<UL>
<LI><A HREF="http://www.informatik.tu-muenchen.de/~schwarz/linuxdoc-sgml/">The
Home Page for LinuxDoc.</A> </LI>

<LI>FTP Sites: </LI>

<UL>
<LI><A HREF="ftp://ftp.cc.gatech.edu/pub/people/gregh/linuxdoc-sgml/linuxdoc-sgml-1.5.tar.gz">ftp://ftp.cc.gatech.edu/pub/people/gregh/linuxdoc-sgml/linuxdoc-sgml-1.5.tar.gz</A>
</LI>

<LI><A HREF="ftp://tsx-11.mit.edu/pub/linux/docs/linuxdoc-sgml-1.5.tar.gz">ftp://tsx-11.mit.edu/pub/linux/docs/linuxdoc-sgml-1.5.tar.gz</A>
</LI>

<LI><A HREF="ftp://sunsite.unc.edu/pub/Linux/utils/text/linuxdoc-sgml-1.5.tar.gz">ftp://sunsite.unc.edu/pub/Linux/utils/text/linuxdoc-sgml-1.5.tar.gz</A>
</LI>

<LI><A HREF="ftp://ftp.cc.gatech.edu/pub/people/gregh/linuxdoc-sgml">ftp://ftp.cc.gatech.edu/pub/people/gregh/linuxdoc-sgml</A>
- Uptodate patches to version 1.5. </LI>
</UL>
</UL>

<LI><A HREF="#test-sgml">How to test your SGML</A> </LI>

<LI><A HREF="#linuxdoc-updates">Updates I've made to the LinuxDoc package</A>
</LI>
</UL>

<P>If you're interested in testing your SGML source, you should grab a
copy of the LinuxDoc package at (put ftp site here). 
<HR><A NAME="title"></A></P>

<H2>The Title Information Section</H2>

<P>This section has 6 tags in it: </P>

<UL>
<LI>article </LI>

<LI>title </LI>

<LI>author </LI>

<LI>inst </LI>

<LI>date </LI>

<LI>abstract </LI>
</UL>

<P>All of these tags are mandatory and <B>must</B> be placed in this order.
</P>

<P>The <I>article</I> tag has no other text associated with it. It is put
on a line by itself and is a marker to the SGML parser telling the parser
what kind of document is to be created. <BR>
Example: </P>

<PRE>        &lt;article&gt;
</PRE>

<P>The <I>title</I> tag is the name of the Plug-In. This must be one line
long and on the same line as the <I>title</I> tag. <BR>
Example: </P>

<PRE>        &lt;title&gt;The Sparkle Plug-In
</PRE>

<P>The <I>author</I> tag identifies the author of the Plug-In. This should
simply be the name of the developer. Along with this is a tag which identifies
the email address of the author. The code for the email address looks similar
to the following. <BR>
Example: <BR>
</P>

<PRE>        &lt;author&gt;Michael J. Hammel
        &lt;htmlurl url=&quot;mailto:user@some.net&quot; name=&quot;&amp;lt;user@some.net&amp;gt;&quot;&gt;
</PRE>

<P>Just substitute the appropriate email address. Note that the use of
<TT>&amp;amplt; </TT>and <TT>&amp;ampgt; </TT>are required. These get translated
into the less-than and greater-than signs, respectively, in the output.
</P>

<P>The <I>inst</I> tag is just the current version number of the Plug-In
source code. <BR>
Example: </P>

<PRE>        &lt;inst&gt;Version 1.0
</PRE>

<P>The <I>date</I> tag is the date that the source code was last updated.
The format of the text that goes with this tag should look like the following:
<BR>
Example: </P>

<PRE>        &lt;date&gt;Last Updated: 09/01/96
</PRE>

<P>The <I>abstract</I> tag marks the beginning of a paragraph of text that
describes, in general, what the Plug-In does. This is free formatted text
and must be followed by the &lt;abstract&gt; tag. <BR>
Example: </P>

<PRE>        &lt;abstract&gt;
                Some text goes here.
        &lt;/abstract&gt;
</PRE>

<P>
<HR><A NAME="intro"></A></P>

<H2>The Introduction Section</H2>

<P>This section contains two subsections: </P>

<UL>
<LI>Where to get the software </LI>

<LI>How to build the software </LI>
</UL>

<P>Both of these are mandatory subsections. </P>

<P>Example section header: </P>

<PRE>        &lt;sect&gt;Introduction
        &lt;P&gt;
</PRE>

<P>The <I>Where to get the software</I> subsetion is a URL (ftp or http
address) for the source code. If a binary version is available, the binaries
location should be listed with the this subsection. <BR>
Example: </P>

<PRE>        &lt;sect1&gt;Where to get the software
        &lt;P&gt;
        The software can be retrieved from
        &lt;htmlurl url=&quot;ftp://ftp.some.net/dir/file.tar.gz&quot; 
        name=&quot;&amp;lt;ftp://ftp.some.net/dir/file.tar.gz&amp;gt;&quot;&gt;
</PRE>

<P>The <I>How to build the software</I> subsetion is simple an explanation
on how to build the software. Example: </P>

<PRE>        &lt;sect1&gt;How to build the software
        &lt;P&gt;
        Building the source should be fairly straight forward.
        Just make sure the LIBS= line points to the location of
        libgimp.a.  Also, a copy of gimp.h is included in the
        source.  You should really delete this and make gimp.h a
        symbollic link to your copy of gimp.h (wherever you're
        keeping that) so that the latest version of gimp.h is used.
</PRE>

<P>
<HR><A NAME="features"></A></P>

<H2>The Features Section</H2>

<P>The <I>Features Section</I> is an itemized list of the features that
the plug-in provides. This should include, at a minimum, a listing of all
the buttons, sliders, or input fields in the dialog box. A very brief description
of the features can be included. This is desirable if the feature listed
is not one that is readily apparent from the dialog box. </P>

<P>Example: </P>

<PRE>        &lt;sect&gt;Features
        &lt;P&gt;
        &lt;itemize&gt;
                &lt;item&gt;Feature one
                &lt;item&gt;Feature two
                &lt;item&gt;Feature three
        &lt;/itemize&gt;
</PRE>

<P>See the section titled <I><A HREF="http://www.redhat.com/linux-info/lg/issue10/lists">Lists</A></I>
for a description on how to create lists using the template. 
<HR><A NAME="dialog"></A></P>

<H2>The Dialog Box Section</H2>

<P>The <I>Dialog Box Section</I> describes the features found in the Plug-In's
pop-up dialog box and explains how they effect images. This section is
made up of an screen capture image (for the HTML formatted output files)
of the dialog box, an numbered list of features, and a feature-by-feature
breakdown. To start this section, use the followgin: </P>

<PRE>        &lt;sect&gt;The ... Dialog Box &lt;label id=&quot;dialog&quot;&gt;
        &lt;P&gt;
</PRE>

<P>Replace the three dots with the name of the Plug-In. </P>

<P>After the section header, a list of features should be provided. The
list will look something like this following: </P>

<PRE>        &lt;itemize&gt;
                &lt;item&gt;&lt;em&gt;&lt;ref id=&quot;feature1&quot; name=&quot;Feature One&quot;&gt;&lt;/em&gt;
                &lt;item&gt;&lt;em&gt;&lt;ref id=&quot;feature2&quot; name=&quot;Feature Two&quot;&gt;&lt;/em&gt;
                &lt;item&gt;&lt;em&gt;&lt;ref id=&quot;feature3&quot; name=&quot;Feature Three&quot;&gt;&lt;/em&gt;
        &lt;/itemize&gt;
</PRE>

<P>The <I>name</I> tag is what will show up in the list. The <I>id</I>
tag is a cross reference that you will use later. The <I>&lt;em&gt;</I>
tags just cause the stuff inbetween to be put in italics. </P>

<P>After you create the list, you should force a break after the image.
This will only affect HTML output for now. This is the line you should
add to force the break: </P>

<PRE>        &lt;![%fmthtml; [ &lt;? &lt;BR clear=&quot;both&quot;&gt; &gt; ]]&gt;
</PRE>

<P>Now you should add the subsections that fully explain each feature.
For the first item in the list above, you would add the following: </P>

<PRE>        &lt;sect1&gt;Feature One &lt;label id=&quot;feature1&quot;&gt;
        &lt;P&gt;
        This is the text explaining the first feature.
</PRE>

<P>The <I>sect1</I> tag signifies you are starting a subsection. The <I>label</I>
with its <I>id</I> gives this section a name that can be used as a cross-reference.
We used this in the list of features earlier. </P>

<P>You would have a subsection just like this for each feature in your
dialog box. 
<HR><A NAME="examples"></A></P>

<H2>The Examples Section (and how to use format-specific tags)</H2>

<P>This section is more complex than the others. Examples of how the GIMP
Plug-Ins work aren't of much use without some images to go with them. Unfortunately,
not all output formats support images (remember: we're using SGML so we
can create HTML, info, man pages, and whatever other formats are supported
by the LinuxDoc package). We need to force this section to be processed
differently depending on which formatter we're running the SGML source
through. The way we do this is to use format-specific tags and the SGML
equivalent of an escape sequence. You're already seen one of these in the
section where we forced an HTML break tag. The generic format of this SGML
tag is: </P>

<PRE>        &lt;![%fmttag; [ &lt;? ... &gt; ]]&gt;
</PRE>

<P>Where <I>fmttag</I> is one of </P>

<UL>
<LI>fmthtml </LI>

<LI>fmttxt </LI>

<LI>fmttex </LI>

<LI>fmtrtf </LI>

<LI>and so forth </LI>
</UL>

<P>and the 3 dots are the format-specific text you want to be passed directly
to the output file. If the sgml parser sees the <I>fmttag</I> tag and it
matches the output format you've requested then the format-specific text
is written to the output file. If it doesn't match the format requested,
the text is ignored. </P>

<P>Thats the technical explanation. Whats worse is it doesn't appear to
work (or I'm doing it wrong - one of the two). </P>

<P>Until I figure this problem out you have one of two choices: </P>

<UL>
<LI>Put in a URL pointing to examples on some other page </LI>

<LI>Use the Sparkle SGML source as an example. </LI>
</UL>

<P>The former of these can be done with the following line: </P>

<PRE>        &lt;htmlurl url=&quot;http://www.some.net/dir/file.html&quot; 
        name=&quot;&amp;lt;http://http.some.net/dir/file.html&amp;gt;&quot;&gt;
</PRE>

<P>Just substitute the appropriate URL. </P>

<P>The latter of the two options can be downloaded from <A HREF="http://www.csn.net/~mjhammel/gimp/gdp/plug-ins/sparkle.sgml">http://www.csn.net/~mjhammel/gimp/gdp/plug-ins/sparkle.sgml</A>.
You may need to hold down the <I>Shift</I> key to force this file to be
downloaded and not displayed. 
<HR><A NAME="notes"></A></P>

<H2>The Notes Section</H2>

<P>The <I>Notes Section</I> is the place to stuff everything that doesn't
fit neatly into the other sections, such as known bugs, limitations, or
future enhancements that are planned. </P>

<P>Example: </P>

<PRE>        &lt;sect&gt;Notes
        &lt;P&gt;
</PRE>

<P>
<HR><A NAME="toc"></A></P>

<H2>The Table of Contents</H2>

<P>This is a single line that goes immediately after the <I>Title Information
Section</I> and immediately before the <I>Introduction Section</I>. It
should look exactly like this: </P>

<PRE>        &lt;toc&gt;
</PRE>

<P>
<HR><A NAME="sections"></A></P>

<H2>Section Markers</H2>

<P>There are several layers of sections available, but we only require
the top two: </P>

<PRE>        &lt;sect&gt;
        &lt;sect1&gt;
</PRE>

<P>The <I>sect</I> tag forces a new page in the output files. The <I>sect1</I>
just gets another type of formatting on that same page. You can add <I>sect2</I>
and <I>sect3</I> levels if you want, but I'm not sure what they do to the
output. </P>

<P>Note that you <B>must</B> put the following immediately after the section
tags: </P>

<PRE>        &lt;p&gt;
</PRE>

<P>This tells the SGML parser to end the section header and begin the part
of the document that belongs in that section. 
<HR><A NAME="paragraphs"></A></P>

<H2>Forcing new paragraphs</H2>

<P>This is simple, just add the following: </P>

<PRE>        &lt;p&gt;
</PRE>

<P>Note that its also possible to use blank lines to force new paragraphs,
but whether the SGML parser uses the blank line as a paragraph or not depends
on where its used. Its easier to just use the above tag to be sure. 
<HR><A NAME="comments"></A></P>

<H2>Comments</H2>

<P>If you want to put comments in your SGML, you would do it like so: </P>

<PRE>        &lt;-- This is an SGML Comment line --&gt;
</PRE>

<P>Note that this is very similar to the HTML comment. 
<HR><A NAME="lists"></A></P>

<H2>Lists</H2>

<P>To create a bulleted list, do the following: </P>

<PRE>        &lt;itemize&gt;
                &lt;item&gt;Item one
                &lt;item&gt;Item two
                &lt;item&gt;Item three
        &lt;/itemize&gt;
</PRE>

<P>To create a numbered list, do the following: </P>

<PRE>        &lt;enum&gt;
                &lt;item&gt;Item one
                &lt;item&gt;Item two
                &lt;item&gt;Item three
        &lt;/enum&gt;
</PRE>

<P>Pretty straight forward, really. 
<HR><A NAME="test-sgml"></A></P>

<H2>How to test your SGML</H2>

<P>You can verify your SGML documentation will work with the various format
converters by running it through each one. For example, to check if you
can get the HTML output with an SGML file called <I>plugin.sgml</I>, try:
</P>

<PRE>        sgml2html plugin
</PRE>

<P>To get text output, try: </P>

<PRE>        sgml2txt plugin
</PRE>

<P>To get man page output in groff format, try: </P>

<PRE>        sgml2txt -man plugin
</PRE>

<P>You should read the man pages for each of the sgml2&lt;whatever&gt;
commands to learn the command line options. They are really pretty easy
to use. 
<HR><A NAME="linuxdoc-updates"></A></P>

<H2>Updates I've made to the LinuxDoc package</H2>

<P>I've made two distinct changes to the LinuxDoc package. The first is
to the linuxdoc.dtd file, found under the <TT>lib/dtd</TT> directory after
you unpack LinuxDoc. The following was added right before the last line:
</P>

<PRE>&lt;!-- added fmt* which were somehow missing --&gt;
&lt;!-- default is ignore, override on commandline in sgml2* --&gt;
&lt;!entity % fmttex  &quot;ignore&quot;&gt;
&lt;!entity % fmthtml &quot;ignore&quot;&gt;
&lt;!entity % fmttxt  &quot;ignore&quot;&gt;
&lt;!entity % fmtinfo &quot;ignore&quot;&gt;
&lt;!entity % fmtrtf  &quot;ignore&quot;&gt;
&lt;!entity % fmtlyx  &quot;ignore&quot;&gt;
</PRE>

<P>These allow for format-specific tags in the SGML source so you can,
for example, add a graphic in your HTML output but just include the description
of the image in your text output. </P>

<P>The other change was to the html2html.l flex file under html-fix. The
changes aren't complex, but theres a number of them to allow for command
line options to set the background, text, and link colors. If you want
this I can send it to you, but its not really necessary to test your SGML
before submitting it to me. 
<HR><A NAME="various-formats"></A></P>

<H2>Notes about creating documents in the various formats</H2>

<P>First of all, there are a set of scripts in LinuxDoc for creating documents
in the various formats: </P>

<UL>
<LI>sgml2html </LI>

<LI>sgml2txt </LI>

<LI>sgml2info </LI>

<LI>sgml2rtf </LI>

<LI>sgml2lyx </LI>

<LI>sgml2latex </LI>
</UL>

<P><B>Note</B>: In order to do format specific tagging, you'll need to
update your linuxdoc.dtd file. See the section on LinuxDoc Updates (found
on the website listed in the introductory section of this article) for
the details. </P>

<P>The first of these, sgml2html, was used to create the new Sparkle documentation,
as well as the HTML version of the SGML template. It works quite well using
&quot;free-formatted&quot; input files. By free-formatted I mean that the
actual text (not the formatting tags) can be one word per line or any number
of words per line and the output will come out nicely formatted using as
many words as will fit in your web browser. </P>

<P>The text formatter, sgml2txt, also works quite well. The output has
various formatting characters that work well with the &quot;less&quot;
and, possibly, &quot;more&quot; pagers. </P>

<P>The GNU Info formatter, sgml2info, is not happy with such free formatting
of the text, however. </P>

<P>I have not tried the other formatters yet. I don't know what RTF is
and I've not used the Lyx or Latex tools so I'm not sure how to test the
output from these formatters. </P>

<P>Michael J. Hammel <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR></P>

<CENTER><P><A NAME="dynamicweb"></A></P></CENTER>

<H1 ALIGN=CENTER>Setting up dynamic IP web server via PPP connection</H1>

<H4 ALIGN=CENTER>By Henry H. Lu, <A HREF="mailto:honglu@rt66.com">honglu@rt66.com</A>,
<A HREF="http://www.tc.umn.edu/nlhome/m508/luxxx012/">http://www.tc.umn.edu/nlhome/m508/luxxx012/</A>
</H4>

<H5 ALIGN=CENTER>Copyright (c) 1996</H5>

<H5 ALIGN=CENTER>Published in Issue 10 of the Linux Gazette</H5>

<P>Have you been thinking of seting up a reachable web server at your home
PC in addition to your permenent page at ISP? There are obvious reasons
to do this: You can show off your home linux box to the world; you do not
need to use other messy method (email) to know your current IP in order
to login remotely; finally, it is fun! </P>

<P>First, You need to have ppp connection and httpd working and a PERMANENT
web page before trying the following dynamic IP solution. </P>

<H3>Description of files: </H3>

<P><B>web_up: </B>shell script I run to update webpage at permenet site
with new IP whenever connection is up. </P>

<P><B>web_down:</B> shell script I run before shutting down the link, to
inform others of the shutdown </P>

<P><B>update_uppage:</B> perl scripts to creat up.html page with updated
IP address on the fly, called by web_up. </P>

<P><B>up.html_source:</B> fixed part of up.html </P>

<P><B>down.html:</B> web page used when link is down. </P>

<P><B>/etc/add, /etc/last_add:</B> files where I put IP address. </P>

<P><B>ip-down, ip-up:</B> files executed when ppp link is disconnected
or connected. they are used to update the /etc/add files here. </P>

<H3>Now lets look at scripts web_up: </H3>

<PRE>------------------------------------------------------------------

    #!/bin/sh
    #check new IP
    new_ip()
    {
    if [ -f /etc/add ]; then
       if [ -f /etc/last_add ]; then
          if /usr/bin/diff /etc/add /etc/last_add &gt;/dev/null ; then
              exit 1 
          else
              return 0 
          fi
       else
          return 0
       fi
    else
       exit 1
    fi
    }

    #check whether maroon is connected
    try_connect()
    {
    if ping -c4 -l3 128.101.118.21  2&gt;&amp;1 | grep &quot;0 packets&quot; &gt; /dev/null
    then 
       return 1
    else
       return 0
    fi
    }
                    
    if try_connect
    then
         touch  /var/run/maroon_connected  
    else
         rm -f /var/run/maroon_connected
    fi

    # ftp to update page
    if [ -f /var/run/maroon_connected ] &amp;&amp; new_ip
    then
       # update_uppage is perl scripts, exit status is opposite of shell
       if ( ! /home/honglu/public_html/update_uppage )
       then 
          cd /home/honglu/public_html
          if echo &quot;put up.html /nlhome/m508/luxxx012/dynamic.html&quot; \
              | /usr/bin/ftp maroon  
          then 
             rm -f /etc/last_add
             cp /etc/add  /etc/last_add
             exit 0
          else
             exit 1
          fi
       fi
    else
        exit 1
    fi

-----------------------------------------------------------------
</PRE>

<P>Now let's look at web_up in detail. </P>

<P>Function <B>new_ip()</B> is used to check whether we have new IP and
whether the new IP is different from the last one. /etc/ppp/ip-up and /etc/ppp/ip-down
update IP adress in files /etc/add and /etc/last_add so that we can compare
files &quot;add&quot; with &quot;last_add&quot; to tell whether we need
to update page. </P>

<P>Function <B>try_connect()</B> is used to test whether the perment web
site is reachable. </P>

<P>Next is fun part, I used automatic feature of <B>ftp</B> to update webpage.
In order to make it work, you have to set file ~/.netrc correctly, type
&quot;man ftp&quot; for more information. </P>

<P><B>update_uppage</B> is straitforward perl scripts to parse and creat
up.html by using new IP from /etc/add file. </P>

<P>Final part is to update /etc/add /etc/last_add to reflect correct status
IP address. </P>

<P>You can put &quot;web_up&quot; in your crontab entry ( or ip-up, or
keapalive.sh) to let it execute automatically whenever your PC is connected.</P>

<H3>Web_down is a similar page, main difference is in ftp part: </H3>

<PRE>-----------------------------------------------------
......
......
# ftp to send down.html page 
if [ -f /var/run/maroon_connected ] 
then
      cd /home/honglu/public_html
      if  echo &quot;put down.html /nlhome/m508/luxxx012/dynamic.html&quot; \
        | /usr/bin/ftp maroon  
      then
          rm -f /etc/last_add
      else
          exit 1
      fi
else
      exit 1
fi

----------------------------------------------------
</PRE>

<P>Instead of ftp up.html as web_up did, web_down put down.html to permenent
web site to inform the delink of page. </P>

<P>web_down should be run before you shut down the machine. I created a
scripts called &quot;shut&quot; to shutdown machine: </P>

<PRE>-----------------------------------------
#!/bin/sh
if web_down
then
   shutdown -h now
else
   echo &quot;can not web_down&quot;
   exit 1
fi
-----------------------------------------
</PRE>

<P>For more detail check out my home page for source code: </P>

<P><A HREF="http://www.tc.umn.edu/nlhome/m508/luxxx012/">http://www.tc.umn.edu/nlhome/m508/luxxx012/</A></P>

<P>Henry H Lu <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR></P>

<P><A NAME="xaos"></A></P>

<H2 ALIGN=CENTER>XaoS: A New Fractal Program for Linux</H2>

<CENTER><P>
<HR></P></CENTER>

<H4 ALIGN=CENTER><A HREF="mailto: layers@vax2.rain.gen.mo.us">by Larry
Ayers</A></H4>

<CENTER><P>Copyright (c) 1996<BR>
</P></CENTER>

<H5 ALIGN=CENTER>Published in Issue 10 of the Linux Gazette</H5>

<P>
<HR></P>

<P>Transforming certain recursive complex-number formulae into images of
unlimited depth and complexity was only made possible by the development
of the modern computer. Benoit Mandelbrot, a Belgian researcher working
for IBM, first discovered the Mandelbrot set in 1981. By the mid-eighties
personal computers had evolved to the point that anyone could experiment
with various fractals, and programmers soon discovered that the 8-bit 256-color
vga palette could be mapped to various parameters, which allowed the creation
of stunning animated images. </P>

<P>The most comprehensive and feature-filled of all fractal-generation
programs is Fractint, a freeware program originally written for DOS. Fractint
is maintained by a far-flung group of developers, rather like Linux. It
was ported to unix by Ken Shirriff and a Linux version is commonly included
in many Linux distributions. Not all features of the DOS version work in
Linux, and if you just want to see what fractals are all about Fractint
is probably overkill. It has such a multitude of options and features that
it can be somewhat overwhelming to a new user. </P>

<P>Recently Jan Hubicka (developer of the Koules X-window game) and Thomas
Marsh have released a small fractal program for Linux called XaoS. This
is an efficient program, with the option to compile both X-Windows and
SVGA-console versions. XaoS can't render the dozens of fractal types which
Fractint can, but it does the basic Mandelbrot and Julia sets quickly,
with several keyboard options. </P>

<P>It's developers refer to XaoS as &quot;an interactive real-time fractal
zoomer,&quot; and zooming in on an area of the Mandelbrot set is where
XaoS excels. Pressing a mouse button anywhere in the image will begin a
zoom with the location of the cursor as target. The &quot;autopilot&quot;
mode is quite impressive; pressing &quot;a&quot; will start an automatic
zoom which homes in on detailed areas. In the X-windows version the default
window-size is 320x200; if you don't mind the cpu-usage a small XaoS window
zooming away on the desktop can be pleasant to contemplate as you pause
in your work. For those working in virtual consoles an SVGAlib version
can be run in a variety of resolutions. </P>

<P>Generating fractal images is inherently CPU-intensive. The faster your
processor the better, especially when zooming in real time. XaoS does pretty
well on my 80-mhz 486, but this may be near the lower limit. </P>

<P>Here's a screenshot of XaoS:<BR>
</P>

<P><IMG SRC="./gx/ayers/xaos.gif" ALT="XaoS Window at 320x200" HEIGHT=231 WIDTH=328 ALIGN=CENTER>
</P>

<P>XaoS only works on 8-bit displays at present, as is also true of Fractint.
Images can be saved to GIF files by means of a keystroke. 
<HR></P>

<H3 ALIGN=CENTER>Installation</H3>

<P>Xaos uses a configure script for compilation, and it should compile
easily on most systems. The executable is only about fifty kilobytes and
is completely self-contained, i.e. no subsidiary files are required. 
<HR></P>

<H3 ALIGN=CENTER>Availability</H3>

<P>The <A HREF="http://www.realtime.net/~amadeus/XaoS">Xaos home-page</A>
is a good source for the latest version; the source has also been uploaded
to <A HREF="ftp://sunsite.unc.edu/pub/Linux/Incoming">Sunsite</A> and its
mirrors. </P>

<P>Larry Ayers <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR></P>

<P><A NAME="xmosaic"></A></P>

<H1 ALIGN=CENTER>Xmosaic Development On A Roll</H1>

<H4 ALIGN=CENTER><A HREF="mailto: layers@vax2.rain.gen.mo.us">by Larry
Ayers</A></H4>

<CENTER><P>Copyright (c) 1996<BR>
</P></CENTER>

<H5 ALIGN=CENTER>Published in Issue 10 of the Linux Gazette</H5>

<P>
<HR></P>

<P>Netscape binaries are more-or-less freely available for Linux, and the
program works well, most of the time. As a Linux user I've become accustomed
to a large potential for customization in software, right down to the source-code
level. Netscape is available only as a large, opaque executable and the
source is proprietary. I don't necessarily want a web-browser to fetch
email and newspostings for me; I use other programs for those purposes
but with Netscape those functions are unwanted baggage, loaded into memory
every time the browser start up. </P>

<P>The recent beta versions of Xmosaic (the latest is 2.7b5) have been
quicker-loading alternatives. Background colors and images are supported,
but it just isn't as quick to load images and pages as Netscape. </P>

<P>Scott Powers, head of the Xmosaic development team at the University
of Illinois, has for the past couple of months been leading a new Xmosaic
project. The Xmosaic developers felt that the code upon which the version
2.7 and earlier browsers had been based needed a complete rewrite. Version
2.8 is now in public alpha testing. The project has been dubbed &quot;Hyperion&quot;,
as a sign that something totally new is in the works. </P>

<P>A mailing list for Hyperion has arisen lately. Perusing the messages
from the developers one can feel the excitement in the air. These people
are really motivated, and working extremely long hours as well. Most days
a &quot;snapshot&quot; of that day's code level is available from their
ftp site. </P>

<P>The first alpha releases were pretty rudimentary; there was no image
support and many HTML files couldn't be loaded. I think that the source
code was released at such an early level so that the developers could be
sure that the core parsing routines, etc., could be successfully compiled
on all targeted platforms. On September 10 the alpha version 2 was completed
and released. Image support is now functional, though at this stage you
must use specific versions of the JPEG and Xpm libraries. There's still
a long way to go before Xmosaic 2.8 is actually very usable, but that's
what the alpha tester's reports are helping to expedite. 
<HR></P>

<H3 ALIGN=CENTER>What Can We Expect?</H3>

<P>Scott Powers and the rest of the Hyperion team have an impressive list
of planned features. One of the most exciting is a modularization of the
source code. This means that if you wanted a speedy, basic browser the
compile-time option would be available to not include, say, Java and sound
support. A user could conceivably compile several versions, each with different
capabilities. </P>

<P>Developers of web-browsers are faced with some difficult decisions.
What standards to follow? How many of the &quot;Netscape-isms&quot; are
now prevalent enough to be considered desirable? As an example, tables
are now standard and to be expected in any new browser, as are forms. Frames
are another matter; they are common on the web but many find them of limited
value and they have yet to gain widespread acceptance. Xmosaic 2.8 will
be HTML-3 compliant, and various sorts of multimedia support are being
discussed. The alpha-testers have been making numerous suggestions, and
their ideas are being taken seriously by the Xmosaic team. 
<HR></P>

<H3 ALIGN=CENTER>Locations and Sources</H3>

<P>If you'd like to check in from time to time and see what progress has
been made, <A HREF="http://xmosaic.ncsa.uiuc.edu/hyperion/">Xmosaic 2.8</A>
is the home-page. The current alpha (and before too long, beta) version
source code can be downloaded from the page. The <A HREF="ftp://xmosaic.ncsa.uiuc.edu/hyperion/download">ftp
site</A> might be faster, but at this early stage the source code is only
about three hundred kilobytes. Information concerning the mailing list
is also on the home page. </P>

<P>I encourage anyone who has a little time and the inclination to participate
in the alpha testing. Every bug report contributes to a higher quality
final release, and I'd hate to see Xmosaic 2.8 work really well only on
Sparc or HPUX machines because not enough Linux users contributed reports!
</P>

<P>Larry Ayres <!--===================================================================--></P>

<P>
<HR></P>

<P><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163 ALIGN=BOTTOM></A>
</P>

<P>
<HR></P>

<P><A NAME="lg_backpage10"></A></P>

<H1>The Back Page</H1>

<UL>
<LI><A HREF="http://www.redhat.com/linux-info/lg/issue10/lg_backpage10.html#authors">About
This Month's Authors</A> </LI>

<LI><A HREF="http://www.redhat.com/linux-info/lg/issue10/lg_backpage10.html#notlinux">Not
Linux</A> </LI>
</UL>

<P>
<HR></P>

<CENTER><P><!--======================================================================--></P></CENTER>

<H3 ALIGN=CENTER><A NAME="authors"></A>About This Month's Authors </H3>

<P>
<HR></P>

<P><!--======================================================================--></P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Larry Ayers</H4>

<P>Larry Ayers lives on a small farm in northern Missouri, where he is
currently engaged in building a timber-frame house for his family. He operates
a portable band-saw mill, does general woodworking, plays the fiddle and
searches for rare prairie plants, as well as growing shiitake mushrooms.
He is also struggling with configuring a Usenet news server for his local
ISP. </P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Michael
J. Hammel</H4>

<P>Michael J. Hammel, is a transient software engineer with a background
in everything from data communications to GUI development to Interactive
Cable systems--all based in Unix. His interests outside of computers include
5K/10K races, skiing, Thai food and gardening. He suggests if you have
any serious interest in finding out more about him, you visit his home
pages at http://www.csn.net/~mjhammel. You'll find out more there than
you really wanted to know. </P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Phil Hughes</H4>

<P>Phil Hughes is the publisher of <I>Linux Journal</I>, and thereby <I>Linux
Gazette</I>. He dreams of permanently tele-commuting from his home on the
Pacific coast of the Olympic Peninsula, where he lives with his Samoyed
Suzie. As an employer, he is &quot;Vicious, Evil, Mean, &amp; Nasty, but
kind of mellow&quot; as a boss should be. </P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Henry H.
Lu</H4>

<P>Henry H. Lu has a M.S. of Biophysics, University of Minnesota and a
B.S. of Physics, Nankai University. He is currently working as contract
bioinformatics analyst in HIV database of Los Alamos National Lab in New
Mexico USA, and has developed Java / HTML, C/C++, perl, shell applications
and system tools for work (Solaris environment) at home Linux box or remote
login to workstation at Lab. For fun, he likes to hack some of systems/networking
programs, use Linux to learn on-line university courses (Operating systems
/ system programming, Network), and write Java/HTML for my own web page.
</P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Manuel Soriano</H4>

<P>Manual Soriano lives in El Perello, Valencia, Spain. He works for a
Swiss based company called Dapsys S. A. that provides the Information Retrieval
Imaging System called IRIS. He is now in Swizterland for a month--sounds
like business not vacation. Think he gets hardship pay for this one? ;-)
Manual has promised us an English translation of his article for the November
issue. </P>

<H4><IMG SRC="../gx/text.gif" ALT="" HEIGHT=45 WIDTH=60 ALIGN=BOTTOM>Nic Tjirkalli</H4>

<P>Nic Tjirkalli is currently employed as a Customer Consultant/Technical
Support Person for UUNET Internet Africa, South Africa's leading Internet
Service Provider, situated somewhere in Johannesburg, South Africa. One
of his current focus areas is Internet security--encompassing firewalls
and packet filtering on routers. He is a fan of Linux, the art of Salvador
Dali, cartoons and heavy metal, in particular, a German group called Helloween.
His home page, where I got this information and which you can access from
his article, is very interesting. </P>

<P>
<HR></P>

<H3 ALIGN=CENTER><A NAME="notlinux"></A>Not Linux </H3>

<P>
<HR></P>

<P><!--======================================================================--></P>

<P>I must say that after 2 months of being the Editor of the Gazette, I
am still having fun, and judging from the mail I think you guys, our readers,
are too. John Fisk is right--the Gazette is a lot of work, and worth every
bit of it. </P>

<P>Thanks to all our authors, not just the ones above, but also those who
wrote giving us their tips and tricks and making suggestions. Thanks also
to our new mirror sites. I get more mail about mirrors than just about
anything, except maybe readers wanting the Gazette to be available as one
big file. We are providing that this month along with the separate page
format. (See TWDT in the Table of Contents.) Doing the
Gazette in multi-file format is just the easiest way for me to build the
magazine. I've tried to be responsive to all mail and reasonable requests.
If I missed you, send your mail again, and I'll get back to you. </P>

<P>The most important thing I'm working on outside of work these days is
definitely &quot;not Linux&quot;. I'm making a baby quilt for a friend
of mine in Houston. The baby is 2 months old now, and if I don't get it
finished soon, it will be too small for her to use. The geometry, as well
the art, of quilting has always fascinated me--must have to do with being
a math person. </P>

<P>If you would like some personal information about me, clicking on my
name below will take you to my home page. It's not very jazzy at the moment,
but I'm looking for the time to fix it up. </P>

<P>
<HR></P>

<P><A HREF="http://www.ssc.com/ssc/Employees/Margie/margie.html">Marjorie
L. Richardson<BR>
</A>Editor, <I>Linux Gazette</I> <A HREF="mailto:gazette@ssc.com">gazette@ssc.com</A>
</P>

<P>
<HR></P>

<P><!--====================================================================--><A HREF="#lg_toc10"><IMG SRC="../gx/indexnew.gif" ALT="[ TABLE OF CONTENTS ]" HEIGHT=60 WIDTH=163></A>
<A HREF="../index.html"><IMG SRC="../gx/homenew.gif" ALT="[ FRONT PAGE ]" HEIGHT=60 WIDTH=163></A>
</P>

<P>
<HR></P>

<P><I>Linux Gazette</I>, http://www.ssc.com/lg/<BR>
This page written and maintained by the Editor of <I>Linux Gazette</I>,
<A HREF="mailto: gazette@ssc.com">gazette@ssc.com</A> </P>

<P>
<HR></P>

<H4>Got any <I>great</I> ideas for improvements! Send your <A HREF="mailto:gazette@ssc.com">comments,
criticisms, suggestions and ideas.</A></H4>

<P>
<HR></P>

<P>This page written and maintained by the Editor of <I>Linux Gazette</I>,
<A HREF="mailto: gazette@ssc.com">gazette@ssc.com</A> </P>

</BODY>
</HTML>