HDTenEightyP/NetNews huggingface dataset:
From: Ching-Hsiang Chen <chchen@stat.fsu.edu>
Subject: Compiling OLVWM: the steps
Reply-To: chchen@stat.fsu.edu
Organization: The Internet
Date: Tue, 28 Jul 1992 06:06:03 GMT

I've compiled successfully the olvwm following the attached posting and
some additional steps. First you got to get Flex from nic(128.214.6.100)
and xbastart, xext, xprog, 75dpi fonts. Compile Flex and that should be
no problem since even I can do it (oh, I know little about C language and
GCC compiler). Place Flex in right directory according to the README or
doc included. Now follow the steps in the attched article but in step 4.,
you still need to delete the -lobz option in the Makefile.  

Edit the the font path in Xconfig so that it includes 75dpi fonts. Change
the last line of the xinitrc file to 'exec olvwm' and change .Xresources
to .Xdefaults in the very first few lines. This should do the job.

%% I had tried the binaries version of olvwm in tsx-11 but didn't succeed
   so I have to do it myself.

Steve Chen
--------------------------------------------------------------------
Article 6266 of comp.os.linux:
From: smackinla@cc.curtin.edu.au
Subject: Compiling Open Look (olvwm)
Date: 20 Jul 92 12:41:52 GMT

Hi. I'm replying to all the recent posts for help compiling Open Look (olvwm).
There are four major steps that have to be done in order for the source to
be compiled successfully.

	1: Get a copy of the flex source. I used version 2.37, so anything
	later than that should work.
	2: Make the libraries in the olgx dir, and then use make install
	to place it in the correct directories.
	3: Modify the file slave.c in two ways. Firstly, #define notdef
	at the beginning, and secondly change the reference to "RLIMIT_NOFILE"
	to RLIMIT_OFILE. (BTW: I'm not too sure about these, could be dodgy.
	Perhaps someone could straighten out the problem in sys/resource.h?
	4: And finally, change olvwm/Makefile so that the CFLAGS include
	"-DSYSV" and so there is no reference to libobz. (Again, I don't know
	what's in that lib, but it linked ok...)

Then you should be able to compile the main program with no trouble. All I can
say is that this worked for me... The change is _definitely_ worth it. Open
Look is a huge improvement over twm.

Pat -- Have a day!
From: Michael_Kraehe@hb.maus.de (Michael Kraehe)
Newsgroups: comp.os.linux
Subject: 0.96c many probs :-(
Date: Fri, 31 Jul 92 08:42:00 GMT
Organization: MausNet
X-Gateway: MausGate/News 1.11

Hy folks,

I'am nearly upgraded from 0.96a to 0.96c,
now I'am running GCC2.2.2 with the 0.96c boot-disk and X11/v1.0
Many thanks for the "echo U*n >/dev/maus" tip, for my Logi-Maus :-)
But I've a lot of more problems :-(

1 - Running a self compiled kernel.

    If I compile the kernel with ROOTDEV=/dev/hda2 i get

       Kernel panic: unable to read i-node block.

    Looking at the build-messages I've seen that build says "root (0,2)"
    patch "root_major=3" in line 83 just after the stat() call solves it ???

    Is stat broken in GCC2.2.2 ???

2 - Running X11/v1.0

    If I now use this kernel, log in as root and type startx,
    my X-Server starts, but

       NOTHING STARTS AFTER THE X-SERVER :-(

    I've tried to change my /.xinitrc so that only xterm comes up
    but realy nothing gets up :-(

3 - Running X11/v1.1

    When I install X11/v1.1/xbase, and type startx I only have a
    blank screen. It doesnt matter if I do that from boot/0.96c, or
    from my own kernel ???

Many Thanks Michael.
Newsgroups: comp.os.linux
From: steffen@gfz-potsdam.dbp.de
Subject: Re: Patch Level 3?
Reply-To: steffen@gfz-potsdam.dbp.de
Organization: The Internet
Date: Wed, 29 Jul 1992 06:26:01 GMT

RFC-822-Headers:
X-Mailer: ELM [version 2.3 PL11]

==================
X-Mn-Key: normal
"owner-linux-activists@joker.cs.hut.fi writes :"

   RFC-822-HEADERS:
   X-Note1: Remember to put 'X-Mn-Key: normal' to your mail body or header

      I was not able to find linux 0.96c patch level 3 on banjo.concert.net - are you sure
   you don't mean patch level 2 - that included the new irq_request stuff.  What was in
   patch level 3 that you need? My kernel grabbed the IRQ fine ( I am using 10 ) and it
   noticed that the extra driver (I forgot to remove) had already grabbed IRQ10.

   						Bob Harris

I have looked for patch 3 on banjo and nic.funet.fi (where is should be first
because of the short way ;) - no patch 3. And I do not remember Linus having
announced a new patch this weekend (although it breaks a tradition :-)
So Ross may have switched the numbers erroneously... It's hard to keep up
with version numbers consisting of a major (0), a minor (96), a sub-minor (c)
AND a patch level number...

--
Steffen Grunewald | IP : steffen@gfz-potsdam.dbp.de | Phone : (+49)331-310526
GeoForschungsZentrum Potsdam,  Telegrafenberg A3,   O-1561 Potsdam,   Germany
#include <disclaimer.h>     /* >>> I don't like Mondays - and .sig's ! <<< */
From: hedrick@dartagnan.rutgers.edu (Charles Hedrick)
Newsgroups: comp.os.linux
Subject: Re: tlQ: why does Linux 0.96c auto-logout during long make?
Date: 29 Jul 92 06:48:32 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

laakkone@klaava.Helsinki.FI (Tero Laakkonen) writes:

>hi. i have some stuff that takes about 8 hours to compile.
>i typed "make -k all >& mall &" at 11.30pm and when i
>came back to my linux box at 7.30am, the OS had done an auto-logout
>for the user (root) who had originated that make, but the machine was
>still churning away at the make.
>if i had wanted to switch the machine off for some reason, 
>i don't know how i could have killed the process to enable it.
>is this auto-logout behaviour normal from Linux (or unices in general)?
>what is the cure?

Your process ended up in the background, i.e. not attached to a tty.
You can kill it using the command "kill NN" where NN is the process
number.  Use "ps" to find the process number.  You can kill any
process you own, and of course root can kill anybody's.

Autologout sounds like tcsh.  At least on the versions we use on the
Sun (which have a different lineage) you do "unset autologout" in
.cshrc.
From: unixsys@ssg.com (Rick Emerson)
Newsgroups: comp.os.linux
Subject: Re: Splitting the comp.os.linux group
Date: 22 Jul 92 16:03:13 GMT
Organization: System Support Group

wirzeniu@klaava.Helsinki.FI (Lars Wirzenius) writes:

> [chauvenism review omitted]
> There is no reason that the poster of the RFD needs to be in any
> particular part of the world or under any particular domain.  He only
> needs to follow the guidelines.  Which means that I could do it (and I
> don't pay for Usenet access, since I am a student and use the
> university's networking), but since I am mostly opposed to the idea, I
> won't.

That's what I understand.
 
> So what's it gonna be, splitters?  _DO_ you really want a split of
> comp.os.linux, or do you not?  If you want it badly enough, post an RFD,
> and get the ball rolling.  It isn't going to happen by itself, and I am
> under the impression that any discussion before an RFD (and probably
> outside of news.groups) is going to be wasted, as far as the guidelines
> are concerned.  So do something, or let the thread die.
> 
> Post an RFD, or stop wasting everybody's time with splitting discussion.
> 

Agreed!

Rick


| Richard B. Emerson     | Replies may be sent to:                         |
| System Support Group   |         unixsys@ssg.com  -or-  rick@ssg.com     |
| Post Office Box 180    |-------------------------------------------------+
| Lansdale, PA 19446 USA |     "If I knew what I was doing,                |
| Voice: 215.855.1607    |      I wouldn't do it." - Me                    |
Newsgroups: comp.os.linux
Subject: Re: SoftWare.
From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Date: Wed, 29 Jul 1992 17:01:28 GMT
Organization: Illinois State University

Hi,

In article <awatts.712044818@guinevere> awatts@st.nepean.uws.edu.au (Andrew Watts) writes:
>
>Second: (pretty trivial, but anyhow) I was trying to compile xhextris from
>the contrib area of X11 ftp areas, well, it compiles fine, but (always a but
>isnt there :) I get this error -

> [error describing how xhextris fails getting font deleted]
>

I noticed that the makefile blows up, unable to convert the font to
type 'snf'.  Since X under linux uses 'pcf' fonts, I went in and
ran bdftopcf by hand, moved the hex10.pcf font to my misc fonts
directory, ran mkfontdir, xset fp rehash, and the program still fails.
Anyone else have better luck?

>Thats all the program reports as it exists, i was told that maybe using xset 
>to set the 'fp' to the default would work, but.. I dont have xset. So Two 
>questions, anyone else get Xhextris working, and does anyone have xset? 
>(I have seen neither mentioned for Linux X11)

Someone posted something about this before, but it is important enough
that it bears repeating.  THE LINUX X11R5 DISTRIBUTION ISN'T THE COMPLETE
MIT DISTRIBUTION!  Most notably, various clients and utilities are not
included, such as oclock, xset, etc.  This isn't a problem, and there is
no need to bloat the x release with this stuff (IMHO) since it can be
ftped:  (well, perhaps xset aught to be in the standard release...

export.lcs.mit.edu:/pub/R5untarred/[mit | contrib]/clients

Each directory contains an (untarred) set of files needed to build the
client.  Just 'mget *' from within the appropriate directory (make sure
you do it from an empty dir on your local machine or you'll get confused
real fast).  Everything I've gotten from there so far has compiled strait
out of the box, by running xmkmf, editing the Makefile to set USRLIBDIR
to /usr/lib/gcc-lib/i386-linux/2.2.2[/shared] and replacing two other 
$(USRLIBDIR) references with /usr/lib, and running make, make install, 
and make clean.

Perhaps the docs in the X11 release should mention this, particularly as
xset, xconsole are much used components of X.   

Hope all this is some help!

Jean.

BTW - For laughes, check out oclock.  Its alot more fun than xclock!


-- 
Jean Liddle                                 | == Bill Clinton for President ==
Computer Science, Illinois State University | 
e-mail:  jliddle@ilstu.edu                  | - Carol Mosley Braun for Senat -
Newsgroups: comp.os.linux
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: Re: /dev/fd1 not detected
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Tue, 28 Jul 1992 09:03:11 GMT

In article <NEGAARD.92Jul27122123@fungus.aero.org> negaard@aero.org (Eric Negaard) writes:
> Linux doesn't seem to recognize my /dev/fd1 properly.
>
> It correctly identifies fd0 at boot time (fd0 is 1.2M), and the second
> (1.44M) drive works if I create /dev/PS1, it's only the auto-detecting
> driver that doesn't seem to work.

At boot time, the floppy driver prints whatever is configured in the
CMOS setup. When using the auto-detecting floppy devices, this
information determines what formats are tried.

So your CMOS setup is probably wrong. You should boot into the setup
program and define your B: as a 1.44MB drive.

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
From: davidh@muppet.bt.co.uk (David Hobley)
Newsgroups: comp.os.linux
Subject: linux support for (PC) notebooks
Keywords: linux notebooks support
Date: 29 Jul 92 13:41:03 GMT
Reply-To: davidh@muppet.bt.co.uk
Organization: British Telecom Research Laboratories

From reading c.o.l for a while, linux seems pretty damn good.
I was thinking of buying a 3/486 notebook. Does anyone have any
experience in using linux with something like this? I have not
had much experience with PC's so far, but this seems like an excellent
opportunity to start.

Many thanks,
david
---
Newsgroups: comp.os.linux
From: joef@extro.ucc.su.OZ.AU ()
Subject: Keyboard bug?
Keywords: bug, yet another one, blame linus :-)
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Sat, 25 Jul 1992 04:28:36 GMT

  I haven't seen this one posted, so I thought I might bring it up. 

  Bootup sequence: when it asks you to press return or any key to continue,
if you happen to press 2 keys accidently, or a 'grey' key [ctrl, alt, caps-
lock, etc] the keyboard will lock up.  I haven't even had a look at the 
source of it yet, but I thought I better bring it up to make sure it's a 
real bug.  It's happened on 2 other systems apart from mine, so it's not
a hardware dependant bug.
    
 
             Joe
 
---
joef@extro.ucc.su.oz.au
From: drew@juliet.cs.colorado.edu (Drew Eckhardt)
Newsgroups: comp.os.linux
Subject: Re: List of BBS's carrying Linux
Date: 28 Jul 92 03:07:26 GMT
Organization: University of Colorado at Boulder

In article <1992Jul28.011903.9794@iat.holonet.net> healyzh@iat.holonet.net (Zane H. Healy) writes:
>Here is a list of Public access BBS systems that carry Linux files.
>This list is dated 26 July 1992.

<list deleted>

FIDO users might also look in their area for a public access Unix 
system, such as Denver University's NYX system.  Some of these
will allow access to other internet sites via ftp. 

Talk to your local universities / colleges, you might find something.
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Help : Linux and DRDOS 6.0 and Superstor
Organization: University of Colorado at Boulder
Date: Wed, 29 Jul 1992 08:27:01 GMT

In article <1992Jul29.055722.18049@dragon.acadiau.ca> 882028s@dragon.acadiau.ca (Ghazali Shafie) writes:
>
>I'm wondering if Linux will work with DR DOS 6.0 and superstor or
>do I have to set aside a few megs not compressed by superstor
>for Linux .
>
>Thanks
>.
>

Linux is a real operating system, and has nothing to do with DOS.  
This means that you need to give it it's own partition, a DOS 
partition (Stacker'd, Superstor'd, or not) will not work.

Newsgroups: comp.os.linux
From: james@netcom.com (James L. Paul)
Subject: Can't compile 0.96c patch 2
Date: Thu, 23 Jul 92 22:58:18 GMT
Organization: Netcom

Running 0.96c and GCC 2.2.2 from sc.tamu.edu. I'm trying to move to patch2.

Compiling 0.96c sources from tsx-11 works fine, runs fine.
Patching source for patch1 and/or patch2 succeeds ok. I've also gotten
the patch level 2 sources from the incoming dir on banjo.

When doing a make on fresh p1 or p2 source, I get the following error:

sync
ld -M boot/head.o init/main.o kernel/kernel.o mm/mm.o fs/fs.o net/net.o fs/mini
x/minix.o fs/ext/ext.o fs/msdos/msdos.o kernel/blk_drv/blk_drv.a kernel/chr_drv/
chr_drv.a kernel/blk_drv/scsi/scsi.a kernel/math/math.a lib/lib.a -o tools/syst
em > system.map
ld: No such file or directory for kernel/kernel.o
make: *** [tools/system] Error 1

This consistently happend each time I try to make a patched version, but
has never happened when making a non-patched version. I've tried patching
fresh copies, and finally compared my patched source to the pl2 source on
banjo. My current conclusion is that my patched source is good, but something
is wrong somewhere else.

Any ideas why kernel.o isn't getting made. or how I can fix this?

-- 
James L. Paul

Internet:    netcom!james@apple.com | AppleLink: D1231 | CompuServe: 72767,3436
UUCP:   {apple,amdahl}!netcom!james | GEnie:    J.PAUL | Voice:    607 776-3070
Packet: N6SIW@WB2PSI.#WNY.NY.USA.NA | Delphi:   JLPaul | Home Fax: 607 776-3070
America Online:   JLPaul or Memorex | BIX:      JLPaul | Prodigy:       PWTB41A
From: tony@vax.oxford.ac.uk
Newsgroups: comp.os.linux
Subject: Re: /dev/eth not on 0.96c
Date: 21 Jul 92 11:42:11 GMT
Organization: Oxford University VAXcluster

In article <1992Jul18.071403.22731@csd.uch.gr>, kanagn@athina.cc.uch.gr (Kostas Anagnostakis) writes:
> Hi Linuxers !
>     I am trying to install ka9q but it seems that /dev/eth is not available
>     on my /dev directory... What should I do ? I just installed Linux on a
>    486/33 , 4 MB RAM, 20 MB swap , 170 MB HD , PCNIC ethernet...
>  
>     Greetings,
>     Kostas

I think you mean /usr/include/maybe_linux_sub_dir_cant_remember/eth.h

here it is.  Perhapse tis could go into the GCC includes ... ??? ...

eth.h
======================= cut here ===========================
#define ETHERMTU 2048
#define ETHER_MIN_LEN 64
#define ETHER_HEADER 14
#define ETHER_ADDR_LEN 6
/* this must be a power of 2 */
#define ETH_BUFF_SIZE 0x2000

/* some ioctls. */
#define ETH_START 0
#define ETH_STOP 1

typedef void * (*callback)(void *);

============================================================


Tony.
                                                    _
Tony Kew,   Oxford University Computing Services,  (_)xford,  England,  U.K.
====================================================|=========================
Janet:- tony@uk.ac.oxford.vax                     --+--    Disclaimer :-
Internet:- tony%vax.oxford.ac.uk@nsfnet-relay.ac.uk | Who is the more foolish?
Earn/Bitnet:- tony%vax.oxford.ac.uk@ukacrl	    |    The fool, or the
Phone:- +44 (0)865 273268   Fax:- +44 (0)865 273275 |  man who follows him?
==================================================\=|=/=======================
                                                   \|/
Newsgroups: comp.os.linux
From: kraus@rtsg.mot.com (David Kraus)
Subject: SCSI, tar -cvMf /dev/fd1 errors, MCC .96
Organization: Motorola Inc., Cellular Infrastructure Division
Distribution: comp
Date: Wed, 29 Jul 1992 15:13:14 GMT

Just last night, for the first time, I tried doing a multi-volume tar to
back up some of the mass of .tar.Z files I have laying around.  (Been
running Linux for about 2 weeks so far.)  When I attempted this, though,
every time that /dev/fd1 (a 3 1/2" HD floppy) is running at the HD starts
up, I get horrendous noises from the floppy, a stream of 'Floppy Reset
Called' messages, and at least 1 I/O error (don't remember the device, but
can recreate pretty much at will).

Setup is as follows:

386DX 33MHz
AMI BIOS
4M RAM
4M swap
/dev/sda ST296N with ST01 controller partitioned 40M Linux/40M DOS
	Linux everything is on /dev/sda1
/dev/fd0 is 5 1/4" 1.2M
/dev/fd1 is 3 1/2" 1.44M
MCC .96 interim distribution

Thus far, everything's been running great.  But, if there is a problem with
simultaneous disk accesses beyond just tar, it would mean not being able to
easily back up the HD...

This may have been covered long ago - checked the faq 06.1, which is the
last I have, and didn't see mention of it there, though.

What's going on?
--
Dave Kraus                                         Internet: kraus@rtsg.mot.com
Motorola Cellular Infrastructure Group             FidoNet : 1:115/439.8
Disclaimer: My employer's views and my views may necessarily differ.
OBQuote: "Chicago is civilization?" - Me
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: compiling bin86
Date: 26 Jul 92 19:57:52 GMT
Organization: Computing Centre, University of Manchester

Someone recently mentioned that there are difficulties in compiling
the as86 and ld86 contained in the bin86.tar.Z package.

In order to get things to work, I had to make the following changes:

In a.out.h/bsd-a.out.h, delete the line defining getpagesize()
at about line 104.

In as/Makefile, change typeconv.o to ../ld/typeconv.o in the
definition of OBJS.  This saves having to copy it across as
described in the README file.

In ld/Makefile, add '-I../a.out.h' to the CFLAGS, and delete the
line 'chmem =232000 ld'.

In ld/type.h, about line 163, delete the line '#undef NULL'.
Further down in the same file, about line 172, delete the prototypes
for 'chmod' and for 'umask'.

In ld/writebin.c, about line 10, in '#define page_size() 4096',
change the 4096 to 0; this seems nonsensical, but makes the binaries
come out the same as those produced by the distributed ld86.
In the same file, about line 50, in '#define FILEHEADERLENGTH 48',
change the 48 to 32.  About line 79, before the line beginning with
'#define offsetof(struc,', insert the line '#undef offsetof'.
About line 912, comment out or delete the two lines stating that
'if (uzp) header.a_flags |= A_UZP;'.

After compiling with the above changes, I found that both the
kernel compilation and lilo work correctly; whether there are errors
in the above which will appear in the future, I cannot say.

     -- Owen
     LeBlanc@mcc.ac.uk
Newsgroups: comp.os.linux
From: drs0587@sc.tamu.edu (Dave Safford)
Subject: Re: Installation
Reply-To: drs0587@sc.tamu.edu
Organization: Texas A&M University
Date: Fri, 31 Jul 1992 14:19:33 GMT

In article 5472@mccuts.uts.mcc.ac.uk, zlsiial@uts.mcc.ac.uk (A. V. Le Blanc) writes:
>The version of Linux on sc.tamu.edu is NOT the MCC interim version, but
>a different version containing many files taken from the MCC interim
>version.  Please do not confuse the two of them.  I am getting quite a
>few messages from people having installed from the sc.tamu.edu version
>and having some problem or other which does not occur with the MCC version.
>It would be better if the sc.tamu.edu version had a name of its own.
>
>     -- Owen
>     LeBlanc@mcc.ac.uk
My package on sc.tamu.edu is a multivolume compressed tar snapshot of
an installed MCC-interim with the four X11 volumes added.  I felt it
would be dishonest for me to take credit for your major effort in putting
MCC-interim together, in contrast to my simple snapshot repackaging,
so I left the MCC-interim banner on logon, while asking in the
README and INSTALL documents for all questions to come to me. I have
received a *LARGE* number of questions and suggestion by email, but 
do apologize for any that were misdirected to you.  I am planning an
updated set of readmes for the TAMU package this weekend.  I will
try to clarify this further in the readmes, and if you prefer, I 
would be happy to change the logon banner to something like
"TAMU package of MCC-interim".  I certainly want you to retain
credit for your work in assembling MCC-interim, which has been 
such a boon to the linux community, while understanding your concern
for clarification of the package involved in a given user question.

dave safford
drs0587@sc.tamu.edu
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Newsgroups: comp.os.linux
Subject: Re: Trying to get olvwm to work
Keywords: olvmw
Date: 28 Jul 92 17:31:08 GMT
Organization: State University of New York -- Institute of Technology

In article <1992Jul28.024155.6124@mach4.wlu.ca> gis@mach4.wlu.ca (gis research) writes:
>
>I downloaded the olvwm binaries from banjo and installed them as intructed,
>but I'm not too sure about how to run it. I start X and then type olvwm at
>the Xterm, but it gives me "Segmentation Fault (core dumped)" Is this how to
>run it, and if so any ideas why I get the error. If not, could someone
>instruct me how to get it going. Thanks for any help,
>
>Alastair Small
>asmall2@mach1.wlu.ca or
>gis@mach4.wlu.ca
>
>

olvwm is a window manager, just as twm is, and should be started before any
xterms.  Just comment out the "twm" line in xinitrc (?) and add the line
"olvwm".

I created a .xinitrc in my $HOME directory so that other users (if I ever
have any on my system) will have twm by default.  A personal copy of .xinitrc
overrides the default xinitrc.

Hope this helps,



-- 
Jim H.
*
* James L. Henrickson                                 ujlh@sunyit.edu
* "Yet another Jim in the Linux world."  :-)
Newsgroups: comp.os.linux
From: lye@fraser.sfu.ca (Bill Lye)
Subject: Re: Ok. You Win. I give up.
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Tue, 21 Jul 1992 15:56:28 GMT

joef@extro.ucc.su.OZ.AU () writes:

>   OK. I give up. After looking thru every concevable archive site I must 
>submit myself to posting.. <sigh>  When I run xman it can't find neqn and
>tbl.  Any ideas ppl?  [I've also talked to a few other ppl, and they don't 
>know where it is, so please post, not mail..]
>  
>        Joe

>---
>joef@extro.ucc.su.oz.au

I 'ln -s'ed geqn to neqn, and that worked for some manual pages, but I
tried to link the GNU tbl in for tbl, and it didn't work.  Any ideas?
-- 
Bill Lye, lye@sfu.ca
SFU claims these views....NOT!