Subject: Linux-Development Digest #984
From: Digestifier <Linux-Development-Request@senator-bedfellow.MIT.EDU>
To: Linux-Development@senator-bedfellow.MIT.EDU
Reply-To: Linux-Development@senator-bedfellow.MIT.EDU
Date:     Thu, 4 Aug 94 12:13:09 EDT

Linux-Development Digest #984, Volume #1          Thu, 4 Aug 94 12:13:09 EDT

Contents:
  Re: libc linking problem (Mitchum DSouza)
  1.1.38: Strange keyb. input (Sverre H. Huseby)
  Re: -= good programmer's editor for X? (Stuart Herbert)
  GAME development - as86 bug. (Rogon den Skjebnelause)
  wish: Removable IDE-support (Sverre H. Huseby)
  Re: threads in kernel (Tim Smith)
  Re: lpd and inet socket problems (Mirko Dziadzka)
  Re: Fatal Signal 11 - reproduceable ! (Tim Smith)
  Re: possible bug in libc 4.5.26 (__load_shared_libraries)? (Mitchum DSouza)
  Re: HOWTO: Change IRQ on EE16 netcard (John Paul Morrison)
  Re: Interesting idea for lilo developers (Drew Eckhardt)
  Re: -= good programmer's editor for X? (N J Andrews)
  A/D drivers for Linux (David P. Boswell)
  Re: Enhanced IDE??
  Re: dual monitor patches; 1.1.37 DOSEMU problem? (Alexandra Griffin)
  S3 support at the console (Christopher M. May)
  Re: S3 support at the console (Christopher M. May)
  Re: FYI -- context switching times (Zbigniew Wieckowski)
  Re: IDE patch won't work w/new kernels? (David Boyd)

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

From: Mitchum.DSouza@mrc-apu.cam.ac.uk (Mitchum DSouza)
Subject: Re: libc linking problem
Date: 4 Aug 1994 10:06:40 GMT

In article <31ptq8$o8@mustang.sdc.com.au>, "Stephen Davies" <scldad@sdc.com.au>
writes:
|> G'day.
|> 
|> /usr/lib/libc.a(ctype.o): Undefined symbol _mcount referenced from text 
|> segment
|> 
|> Twice this week I have run into the above error message while
|> compiling Linux sources. Can somebody please tell me what is wrong and
|> how to fix it.
|> 
|> I am running 1.1.37 and libc 4.5.26 and gcc 2.5.8.
|> 
|> Thanks in anticipation,
|> 

It seems you have a *very* old static library archive (libc.a) there. Please
get the latest distribution and install it as per the release notes. Read the 
GCC-FAQ on sunsite.doc.ic.ac.uk:/pub/Linux/docs/faqs for more info.

The command 
        
        nm /usr/lib/libc.a |grep mcount

should give you *NO* output.

Mitch
        

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

From: sverrehu@ifi.uio.no (Sverre H. Huseby)
Subject: 1.1.38: Strange keyb. input
Date: 3 Aug 1994 02:34:36 +0200


I upgraded from 1.1.37 to 1.1.38, and got problems with gdb and tar M.
When gdb waited for my response other than `normal' command input, it
didn't wait at all. Pausing in the help-text just aborted the program.

tar M (multi volume) was about to read my return-press for `next volume',
but responded with something like "EOD? what's that?", and aborted.

BTW: I'm running everything from xterm-windows.

Sverre.

===========================================================
Sverre H. Huseby                                    Student
sverrehu@ifi.uio.no              University of Oslo, Norway
http://www.ifi.uio.no/~sverrehu

My employer (that's me) is not responsible for my opinions.



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

From: ac3slh@sunc.sheffield.ac.uk (Stuart Herbert)
Subject: Re: -= good programmer's editor for X?
Date: 4 Aug 1994 10:15:59 GMT

: : Are there any good programmer's editors for X - not term-like ports?

: : kristof-
: : nybakken@world.std.com

JED is what I use -- works a treat.

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

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

From: rogon@engstad.tromsomh.no (Rogon den Skjebnelause)
Subject: GAME development - as86 bug.
Date: Tue, 2 Aug 1994 09:42:35 GMT

I have a user which has got problems using as86. I know that
as86 only reason for being there is to get linux started at 
bootup, but as he is developing games for 386/486 ++ he would
like this to function as an ordinary assembler. 

If anyone is developing/maintaining as86, I would like to get
email, which I can forward to him. 

By the way, if anyone knows if it is possible to compile 
386-programs for use in DOS we would like to know how (gcc).

Are there anyone else involved in game-developing using Linux?

Message from user viggo@engstad.tromsomh.no:
==================================================================
Offset error detected in as86. :-(

I discovered this error by creating a .COM file for use in DOS.
When executing my program from DOS, it promted out with ILLEGAL 
command error... Then I used (DOS) DEBUG to trace the program. 
The first CALL seemed to operate. The second CALL jumped one byte 
short of where it were supposed to land. To check even more, I put 
a NOP instruction in front of the "prnt1" procedure. (See below.)

The program then ran smoothly but not decently. The screen output 
was wrong. A farren symbol were printed out before the sentence 
in "msg1". The LEA instruction had pointed one byte short too...

LordV... |-)

**** Makefile ****
SRC=s.S
COM=s.com

all: $(COM)

AS86=as86
LD86=ld86

%.com: %.S
        $(AS86) -0 -a -o $*.o $<
        $(LD86) -T 0 -o $*.tmp $*.o
        dd if=$*.tmp of=$@ bs=1 skip=32
        rm -f $*.tmp $*.o

clean: rm *.com

**** PROGRAM (s.S) ****

use16
.text
.data
.bss

.globl _main              ! for ld86
_main:
        push    ds
        mov     ax,#$0010
        mov     bx,ds
        add     bx,ax
        mov     ds,bx

        lea     si,msg1
        call    prtstr
        mov     al,#65
        call    prnt1

        pop     ds
        ret

! Routine to print asciiz-string at DS:SI

prtstr: lodsb
        and     al,al
        jz      fin
        call    prnt1
        jmp     prtstr
fin:    ret


        nop             ! used to prevent system crash :-(
prnt1:
        push    ax
        push    cx
        xor     bh,bh
        mov     cx,#$0001
        mov     ah,#$0e 
        int     $10
        pop     cx
        pop     ax
        ret

msg1:   .ascii "Press <RETURN> to see SVGA-modes available, "
        .ascii "<SPACE> to continue or wait 30 secs."
        db      0x0d, 0x0a, 0x0a, 0x00


o-----------------------------o----------------------------------------o
| Rogon the Fateless, aka     | Work: Tromsoe College, Section of      |      
|     Paul-Kristian Engstad,  |       Economics and Engineering,       |
|     Otervegen 58,           |       Postboks 72,                     |
|     N-9017 Tromsoe, Norway. |       N-9001 Tromsoe, Norway.          |
|     +47 77 67 03 88 (P)     |       +47 77 68 02 50                  |
|                             |       +47 77 61 12 00 --- 235 (Direct) |
o-----------------------------o----------------------------------------o
| Subjects: Mathematics, cybernetics, computing, teaching and LINUX!!  |       
o----------------------------------------------------------------------o
| Email: engstad@marind.tromsomh.no  : Work, MS-Windows.               |
|        rogon@engstad.tromsomh.no   : Linux!!                         |
o----------------------------------------------------------------------o



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

From: sverrehu@ifi.uio.no (Sverre H. Huseby)
Subject: wish: Removable IDE-support
Date: 3 Aug 1994 02:40:52 +0200


I have an IDE-disk (SyQuest) with removable cartridges, but it doesn't
seem that the kernel supports removable IDEs. Before mounting new
cartridges, I have to run a little program that tells Linux to reread
the partition table of my /dev/hdb (using ioctl()).

I think it would be nice to be able to tell the kernel (or whoever is
appropriate) that this IDE is actually removable. A new mountflag, perhaps...


Sverre.

===========================================================
Sverre H. Huseby                                    Student
sverrehu@ifi.uio.no              University of Oslo, Norway
http://www.ifi.uio.no/~sverrehu

My employer (that's me) is not responsible for my opinions.


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

From: tzs@u.washington.edu (Tim Smith)
Subject: Re: threads in kernel
Date: 4 Aug 1994 10:41:41 GMT

Matthias Urlichs <urlichs@smurf.noris.de> wrote:
>A new stack at the same location means that you can't put things on the
>stack if any other thread might need them. Ugly.

Give each stack its own location, and also double map the current stack
into a fixed location.  The current thread/clone/whatever runs using the
fixed location, but can access the stacks of the others.

--Tim Smith

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

From: dziadzka@ai-lab.fh-furtwangen.de (Mirko Dziadzka)
Subject: Re: lpd and inet socket problems
Date: 4 Aug 1994 12:55:16 +0200

In article <Ctz330.4IF@inter.nl.net> denouden@inter.NL.net (J. den Ouden) writes:
[ ... ]
>However, when I submit a file for remote printing and then try to get
>a job list with lpq, lpq times out with 'connection to _host_ down'.
>After the initial print request is finished (which can take quite long
>because it has to be fed to GhostScript), lpq requests are honored again.
>
>Only remote printing suffers from this, local printing works ok.

I had the same problem. Last weekend I found a solution for me.

Here is the diff:

============================ cut here ===============================
--- lpd-590p2/lpd/printjob.c      Thu Aug  4 12:49:57 1994
*** lpd-590p2/lpd/printjob.c.orig Thu Aug  4 12:49:25 1994
*** 107,112 ****
--- 107,114 ----
  
        init();                                 /* set up capabilities */
        (void) write_retry(1, "", 1);                   /* ack that daemon is started */
+       close(1); /* @@@ md 07/31/94 ; close the socket */
+ 
        (void) close(2);                        /* set up log file */
        if (open(LF, O_WRONLY|O_APPEND, 0664) < 0) {
                syslog(LOG_ERR, "%s: %m", LF);
============================ cut here ===============================

I don't exactly know, what close(2) does in this context.  Maybe
this should be the close(1) ?


>Jan den Ouden

        Mirko Dziadzka


-- 
| Mirko Dziadzka                     | Linux - das beste Textadventure |
| <dziadzka@ai-lab.fh-furtwangen.de> | aller Zeiten                    |
|----------------------------------------------------------------------|
Das Linux-Kernel Buch: http://www.informatik.hu-berlin.de/topics/linux/

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

From: tzs@u.washington.edu (Tim Smith)
Subject: Re: Fatal Signal 11 - reproduceable !
Date: 4 Aug 1994 11:05:07 GMT

In article <CtuqL8.73o@pe1chl.ampr.org>, Rob Janssen <pe1chl@rabo.nl> wrote:
>>On another note, it looks like AMD dx2/66's don't like ghostscript - anybody
>>else see this?
>
>There have been reports of broken AMD DX2's.  It seems that recent chips
>don't have this problem.

Is successful compilation of ghostscript conclusive proof that one has one
of the good AMD DX2's?

--Tim Smith

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

From: Mitchum.DSouza@mrc-apu.cam.ac.uk (Mitchum DSouza)
Subject: Re: possible bug in libc 4.5.26 (__load_shared_libraries)?
Date: 3 Aug 1994 09:17:35 GMT

In article <Ctxr0A.6BF@raven.alaska.edu>, fxmlk@camelot.acf-lab.alaska.edu (Mike
L. Kienenberger) writes:
|> I'm running a program which unexpectedly dies at random intervals
|> with the message "statically linked" to stderr.  I've finally traced the
|> message back to __load.c in libc.  I can even see the exit() which kills
|> the program there.  I don't know for sure, but I assume I'm running
|> libc.4.5.26 since that's what shows up in /lib/lib*.   However,
|> I can't figure out where (or even why!) __load_shared_libraries() (the
|> source of the message) gets called.  Setting a breakpoint in the debugger
|> at exit(), _exit(), and __load_shared_libraries() shows an empty stack
|> except for __load_shared_libraries.
|> 
|> There's also no real pattern to the amount of time my program runs before
|> it dies.  It could happen as soon as 15 minutes or take as long as a day
|> or two before occurring.  I'd appreciate any information anyone could give
|> me.  My program fork()s a process and does a data checkpoint on the new
|> child (then exits) every 15 minutes.  The only pattern I've noticed is
|> that the death of the parent process seems to occur right before the data
|> is saved more often than not (but not always.)
|> 
|> If there's any further information I can supply, please let me know.
|> If I receive replies by email, and anyone else is interested, I'll post a
|> summary to usenet.

You can try getting the ld.so-1.4.4.tar.gz package which has a debugging version
of libldso.a. Link your program with that. You will then be able to debug
you program properly as control is not passed to ld.so.

Anyhow I think the problem probably is that you have some exec() calls with
incorrect arguments in your program.

Mitch

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

From: jmorriso@bogomips.ee.ubc.ca (John Paul Morrison)
Subject: Re: HOWTO: Change IRQ on EE16 netcard
Date: Wed, 3 Aug 1994 07:29:16 GMT

In article <Ctwq5C.FJ2@iceonline.com>,
Pat Richard <patr@icebox.iceonline.com> wrote:
>hi,
>    Having compiled in support for the EtherExpress 16 card, how do you
>change the IRQ that it defaults to? My card will always use IRQ 5, even
>if I reset it to something else before running Linux (it has a
>soft-settable IRQ).
>
Use softset (didn't it come with the ethercard??) to change the settings.
If you don't have softset.exe, ftp it from ftp.intel.com. (softset
is a DOS program)



-- 
===========================================================================
BogoMIPS Research Labs  --  bogosity research & simulation  --  VE7JPM  -- 
jmorriso@bogomips.ee.ubc.ca ve7jpm@ve7jpm.ampr.org jmorriso@rflab.ee.ubc.ca
===========================================================================

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

From: drew@kinglear.cs.colorado.edu (Drew Eckhardt)
Subject: Re: Interesting idea for lilo developers
Date: 3 Aug 1994 00:54:21 GMT

In article <kress.670.001066D0@kentrox.com>,
Bill Kress <kress@kentrox.com> wrote:
>lilo is a great system. The problem is obvious, there is
>no input that you can set when you turn your computer on
>so that you can go get a drink while your system boots
>to the operating system/configuration of your choice.

Wrong.  Lilo supports a -R flag, which lets you specify 
a boot image to be used the next time the system boots.

Ie, if I were to develop an uncontrolable compulsion to play
some DOS game, I could say

    lilo -R msdos

Go out for donuts, come back, settle down to blasting aliens,
and reboot into Linux.

>This way you could boot your OS/2, Linux 25x80,
>Linux 50x80, or Linux init level 6 (x-windows)
>just by repositioning your joystick.

Fortunately, some of us are touch typists, and it's quicker to 
do a lilo -R msdos or whatever before rebooting.

-- 
Drew Eckhardt drew@Colorado.EDU
1970 Landcruiser FJ40 w/350 Chevy power
1982 Yamaha XV920J Virago

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

From: N J Andrews <N.J.Andrews@durham.ac.uk>
Subject: Re: -= good programmer's editor for X?
Date: 4 Aug 1994 11:57:55 GMT

Andre April <aa@info.ucl.ac.be> wrote about xcoral:-

- Even if it is not perfect, it is more attractive for beginners than emacs or
- vi. It is easy to add functionalities with the 'small ansi C interpretor'.

I think I would say that for many people it is more attractive than emacs or vi.
For a start it looks better and speaking for myself I hardly used most of emacs
features.

Yep, it is easy to add functionality; however, we did find it lacking in
support for 'popen' and the like ( but we found a way around that problem ).


- The most usefull feature is the C/C++ browser.

It's a nice feature, however, most of my code has at least a few #ifdefs in,
which stop the browser from working on those files. A drawback, but livable with.

I am pleased to see some of the 'features' of the highlighting mechanism have
been addressed and I for one am just about to retrieve xcoral 2.1 and install it
on two different platforms ( another two to follow when our new disk gets mounted
and I find time ).

All in all, a nice editor, thanks Andre.

-- 
Nigel J. Andrews
Astronomical Instrumentation Group
Physics Department
University of Durham

BTW Andre, did we ever send you those fixes for the Alpha ( bit late now I guess
since it was a couple of versions ago )?

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

From: dave@ndeux.space.thiokol.com (David P. Boswell)
Subject: A/D drivers for Linux
Date: 4 Aug 1994 10:30:14 -0400
Reply-To: dave@ndeux.space.thiokol.com (David P. Boswell)

Over the past weeks I have seen several posts mentioning data acquisition
and realtime under Linux.  My next project is such a system and I feel
Linux is ready to take it on.  The only thing causing me to waver in
this decision is the driver for the A/D card.  The particular card I
am stuck with (unless there is a vendor out there that wants their
card first for Linux :)  is a Strawberry Tree APC-16.  I do have source
for a dos driver in C with some real mode inline assembly code and
some documentation.  However at this point I don't feel my protected
mode experience will allow me to port this in a reasonable amount of time.

Is anyone working on any A/D drivers under Linux ?

Would anyone like to help me with a driver for this card and further our
favorite cause ?

And, a final plug for my cause:

This could be good publicity for Linux as this system involves a very
political inspection in the Space Shuttle program.


I am  dave@ndeux.space.thiokol.com  should you prefer to speak in private.

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

Crossposted-To: comp.os.linux.admin
From: carlsonr@rnisd0.llnl.gov ()
Subject: Re: Enhanced IDE??
Reply-To: carlsonr@rnisd0.llnl.gov ()
Date: Thu, 4 Aug 1994 14:38:26 GMT

I have a WD caviar with 1063 cylinders and had a hard time getting
Linux to accept it with the autodetect setup mode in effect.  I selected
a user defined configuration, per WD telephone support, it worked like a
charm.  Apparently LILO uses BIOS a little to start the boot process
but afterward, Linux does its own I/O.  Therefore LILO needs to do its
reading from cylinders less than 1024.

When I partitioned the disk, I put Linux first, then a DOS partition up to
the 1024 cylinder mark and then another Linux partition for the swap
space after that.

Clay, did you go to Carleton?

Regards,
Robbin Carlson
Robbin.Carlson@roche.com

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

From: acg@kzin.cen.ufl.edu (Alexandra Griffin)
Subject: Re: dual monitor patches; 1.1.37 DOSEMU problem?
Date: 4 Aug 1994 08:10:28 GMT

Thanks for posting those!  Looks like a good justification for
upgrading to the 1.1.37 kernel release.  I've heard that Dosemu
doesn't work properly under 1.1.37, though-- is this true?  I
currently use 1.1.27 and Dosemu 0.52 works OK.   
-- alex

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

From: cmay@titan.ucs.umass.edu (Christopher M. May)
Subject: S3 support at the console
Date: 4 Aug 1994 14:28:34 GMT

Hi, I read in one of the kernel patches that some new support 
was added for the S3 cards.  Does this mean that svgalib will
be more likely to support the S3 soon?

I'm particularly interested in 16m color support for pov, etc.

--

-Chris May, Computer Science, University of MA, Amherst
-       Technical Assistant, P.C. Maintenance Lab


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

From: cmay@titan.ucs.umass.edu (Christopher M. May)
Subject: Re: S3 support at the console
Date: 4 Aug 1994 14:33:07 GMT

I'm also interested in finding register/programming info for
the S3 805.  Should I contact the manufacturer of my card or
S3?  Or should I just look at the XFree Accel server code?

--

-Chris May, Computer Science, University of MA, Amherst
-       Technical Assistant, P.C. Maintenance Lab


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

From: wieckows@deca.cs.umn.edu (Zbigniew Wieckowski)
Subject: Re: FYI -- context switching times
Date: Wed, 3 Aug 1994 02:16:41 GMT


Here is what I got from a QNX guy once. I must admit QNX context switch times
are quite impressive.

From danh@qnx.com Fri Mar 18 08:11:19 1994
Return-Path: <danh@qnx.com>
Received: from qnx.com by mail.cs.umn.edu (5.65c/)
        id AA09575; Fri, 18 Mar 1994 08:11:13 -0600
Received:  by qnx.com (5.67/25)
        id AA11366; Fri, 18 Mar 94 09:11:11 -0500
Message-Id: <9403181411.AA11366@qnx.com>
Subject: Re: Real-Time Linux and a/d device drivers
To: wieckows@mail.cs.umn.edu (Zbigniew Wieckowski)
Date: Fri, 18 Mar 1994 09:11:05 -0500 (EST)
From: "Dan Hildebrand" <danh@qnx.com>
In-Reply-To: <199403180235.AA07786@tera.cs.umn.edu> from "Zbigniew Wieckowski" at Mar 17, 94 08:35:52 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1953      
Status: RO

> > Most users in the realtime world don't take the Solaris realtime support
> > very seriously....  :-)
> 
> Can you elaborate on exactly why this is the case? I know of some problems with
> making Unix meet hard real time constraints, like the fact that the kernel
> cannot be preempted, on-demand paging, buffering disk transactions in buffer
> cache, but I know nothing about the RTS in Solaris, although I developed
> applications on Solaris.

The biggest problem tends to be the non-preemptable nature of the kernel, it
is possible for the system to be "locked up" for quite some duration in the
kernel, while realtime tasks don't get the service they need.  Also, the
interrupt latency and context switch times for Solaris are not terribly
good.  Here are some context switch numbers that compare various OS's,
including the QNX realtime OS:

  28     60 MHz ALR Pentium QNX 4.2
  34    100 MHz HP-747x HP-RT 1.1
  44     66 MHz 486DX2 QNX 4.2
  68    100 Mhz HP-735 HP-UX 9.01
  71     50 MHz HP-742 HP-RT 1.1
  80     33 MHz 486DX QNX 4.2
  93    150 MHz 21064 DEC OSF/1 v1.3
  98     40 MHz R3000 DEC 5000/240 Ultrix 4.2
  98     66 MHz 486DX2 Linux 0.99.10
 100    150 MHz Alpha DEC 3000/500
 102     62 MHz IBM-RS6000/580 AIX 3.2
 106     66 Mhz snake HP-UX 9.x
 127    150 MHz Alpha DEC 3000/400 21064
 128     40 Mhz viking SunOS 4.1.3
 154     25 MHz R3000 DEC 5000/200
 158     50 MHz R4000 SGI
 198     33 MHz Sparc SunOS 4.1.1
 198     40 MHz MIPS R3000 Ultrix 4.3
 210     33 Mhz 486 386BSD 0.1
 212     50 Mhz RIOS AIX 3.2
 281     20 MHz R3000 DEC 5000/120
 345     33 MHz R3000/3010 SGI Irix 4.0.5
 380     33 MHz 486 NetBSD
2603     16 MHz 386SX NetBSD

-- 
Dan Hildebrand                     email: danh@qnx.com
QNX Software Systems, Ltd.         QUICS: danh  (613) 591-0934 (data)
(613) 591-0931 x204 (voice)        mail:  175 Terence Matthews          
(613) 591-3579      (fax)                 Kanata, Ontario, Canada K2M 1W8

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

From: dwb@ITD.Sterling.COM (David Boyd)
Subject: Re: IDE patch won't work w/new kernels?
Date: 4 Aug 1994 05:57:32 GMT


In article <snickerCtx6D3.FLM@netcom.com>,
Brian A. Lind <snicker@netcom.com> wrote:
>>>
>>      These patches also used to work for me as well.  I thought it
>>might be another problem with my new Promise controller, but it looks like
>>something changed as I am having the exact same problems.  Will try an
>>older kernel tonight to verify. 
>>
>
>I had a Promise 4030VL controller for a while with 1Meg of cache on it.
>I ended up taking it back because I couldn't get more than my first
>2 drives to work under DOS and Linux. The card's setup seemed to
>recognize all 4 of my drives (2 West. Dig and 2 Maxtor), but the
>DOS device driver sure didn't and Linux secondary controller patches
>didn't, either. Ended up going back to my GSI-18 secondary controller.
>Also some of the tests I did with 'dd' under Linux showed the 4030VL
>card to be slightly slower than my old ISA based IDE card. 
>Maybe I didn't have enough cache RAM???
>Sped up windows noticably though.
>
        Well, I had about given up on seeing a response to my message.

I still can't get the promise to accept the multimode commands.  I tried
recompiling the hdmode program to no avail. I also verified that it was not
the physical I/O wait problem that was discussed earlier.

I hand hacked up an hd1.c driver from the 1.1.37 kernal hd.c.  I now get
to the point that the system gets hung in continous resets of the controller.
If I take the controller reset out, the driver hangs with the controller
always showing busy.

I am beginning to wish I had just bought a new DTC controller.
-- 
David W. Boyd                UUCP:     uunet!sparky!dwb
Sterling Software ITD        INTERNET: Dave_Boyd@Sterling.COM
1404 Ft. Crook Rd. South     Phone:    (402) 291-8300 
Bellevue, NE. 68005-2969     FAX:      (402) 291-4362
I survived - Seoul Sea of Fire Tour 94

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


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.development) via:

    Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Development Digest
******************************
