Subject: Linux-Development Digest #960
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:     Fri, 29 Jul 94 07:13:04 EDT

Linux-Development Digest #960, Volume #1         Fri, 29 Jul 94 07:13:04 EDT

Contents:
  Re: Dosemu won't work with >1.1.29 <1.1.35 and recompile won't help (Ross Boswell)
  Re: mouse error on 1.1.35 (Alan B. Evans)
  Re: 1.1.35 make problem: exhausted memory (Ugly)
  Interest in a new (up to date) LaTeX dist.? (Byron Faber)
  Threads design to follow soon (G Dinesh Dutt)
  Re: Found "talk" bug, fixing. (Harald Milz)
  Re: Panasonic CD-ROM broke under >1.1.31 (Olaf Flebbe)
  Re: shared Libs and X11 don't work in Linu (Mitchum DSouza)
  shared Libs and X11 don't work in Linux (Gerald Ehritz)
  Re: Panasonic CD-ROM broke under >1.1.31 (Olaf Flebbe)
  Energy star screen saver for X (Kim-Minh Kaplan)
  Multiple systems on multiple drives and LILO? (Yves Arrouye)
  Re: 1060 cyliders a problem? (Kevin Lentin)

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

From: drb@chem.canterbury.ac.nz (Ross Boswell)
Subject: Re: Dosemu won't work with >1.1.29 <1.1.35 and recompile won't help
Date: 26 Jul 1994 02:43:00 GMT

lcvanveen@et.tudelft.nl wrote:
: Last week I rebuild Linux to version 1.33 and noticed dosemu0.52 
: wouldn't work anymore. The screen went black and the only thing 
: I could do was shutdown with crtl-alt-del. This morning I went 
: over to Linux 1.1.35 and recompiled dosemu again. I still won't 
: work. 
Same problem here.
The last kernel that dosemu0.52 worked with was 1.1.31, I think.
At 1.1.33 it wouldn't compile because of a circular include-file
definition involving sigsegv.c and the definition of select_table.
At 1.1.35 it compiles but fails with a segmentation error; the last
output from -D+all is "put_video_ram called".  
Any wizards working on this?

--
| Ross Boswell                    | Email : drb@chmeds.ac.nz          |
| Department of Pathology         | FAX   : +64 3 364 0525            |
| Christchurch School of Medicine | Phone : +64 3 364 0590            |
| NEW ZEALAND                     | Post  : PO Box 4345, Christchurch |

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

From: aevans@kaiwan.com (Alan B. Evans)
Subject: Re: mouse error on 1.1.35
Date: 28 Jul 1994 19:28:43 -0700

Supat Faarungsang (supat@nuntana.animal.uiuc.edu) wuz sayin:
: Hi,

: I got following errors on mouse (psaux2)
: when compile kernel 1.1.36

: Could anyone fix it?

: THANKS,
: supat
: ==============
: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -m486 -c psaux.c
: /usr/src/linux/include/linux/timer.h: In function `init_timer':
: In file included from psaux.c:28:
: /usr/src/linux/include/linux/timer.h:85: `NULL' undeclared (first use this function)
: /usr/src/linux/include/linux/timer.h:85: (Each undeclared identifier is reported only once
: /usr/src/linux/include/linux/timer.h:85: for each function it appears in.)
: make[2]: *** [psaux.o] Error 1
: make[2]: Leaving directory `/usr/src/linux/drivers/char'
: make[1]: *** [driversubdirs] Error 1
: make[1]: Leaving directory `/usr/src/linux/drivers'
: make: *** [linuxsubdirs] Error 1



The macro name NULL is undefined when it is encountered in the heaer file
timer.h (at the end of the file). There are many different ways to do
this. You need something with a "#define NULL 0" or "#define NULL (void*)"
in it to resolve it.

alan
-- 
You can reach me at @ :
Internet : aevans@kaiwan.com, fa996@freenet-in-a.cwru.edu
ICBM     :   33 39'     North   Cruise  :   33 39' 37"  North
         :  117 59'     West            :  117 59' 54"  West

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

From: jpaz@herbie.unl.edu (Ugly)
Crossposted-To: comp.os.linux.admin
Subject: Re: 1.1.35 make problem: exhausted memory
Date: 28 Jul 1994 08:05:26 GMT

Dan Wilder (danw@connected.com) wrote:
: pcsigler@whale.st.usm.edu (Peter C. Sigler) writes:

: >Peter Schmitt (pete@geminga.dartmouth.edu) wrote:
: >: My 386 has 5M ram and 5M swap.  I am currently running 1.1.34 and got
: >: the following when trying to make 1.1.35:

: >I think this is a problem with the memory handling in 34.
: >I tried to compile 35, as well, under 34 and got the same
: >thing. My system is a 386/40 w/5Meg ram and 10meg swap.

: That isn't a lot of room.  Try running 'top' to see what the situation
: is.  I suspect with 5 meg RAM and 10 meg swap, you are nearing swap
: full compiling the kernel even with earlier kernels.  'Course it
: could be the memory handling.

I'm not so sure, because my system runs with 4 meg ram, and 8 meg swap, and
I've never run out of memory compiling the kernel.  It is painfully slow,
but doesn't ever complain about memory at all.  But to be safe, I would try
compiling again with another 10 megs swap and see what happens then.

Jorge
--
The opinions expressed above would annoy my employer, if I had one.
(c) 1994 Uglysoft, a division of Jorge Enterprises, Inc.
Jorge A Paz                 |      I protest, I am NOT a merry man!
jpaz@herbie.unl.edu         |        -Lieutenant Worf
 
                                 

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

From: btf57346@uxa.cso.uiuc.edu (Byron Faber)
Subject: Interest in a new (up to date) LaTeX dist.?
Date: 28 Jul 1994 16:27:04 GMT

I am curious whether there is enough interest in a new up to date LaTeX 
distribution?

If enough people want one, I can put together a LaTeX distribution based
on the June release standard of LaTeX 2e.

Byron
-- 
`Playing this disk at loud volume may permanently damage your speakers or
other sound components.'                                -LFO
                b-faber@uiuc.edu & http://www.cen.uiuc.edu/~bf11620/

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

From: G Dinesh Dutt <brat@htilbom.ernet.in>
Subject: Threads design to follow soon
Date: 29 Jul 1994 03:34:09 -0400
Reply-To: brat@htilbom.ernet.in

Hi everybody,

I shall post the design of the threads pacakge that we are implementing in a
while. There are a couple of issues that need tying up before we can consider
them viewable. But, one thing I can tell you is that "clone" is not the way we
are working. As some have already pointed out, Linus has been making the
task structure switchable into a LWP more easily. This has helped our progress
a lot better. Because of other work committments and other logistical problems,
progress had been a little slow. But, its picking up now and I should posting
the design when we thrashed out some of the little issues and present a
defendable design.

Thanks for all the interest. Will keep you posted,

Dinesh
----
P.S: To all of you who has personally written to me requesting details, I am
sorry for not having replied sooner. I have been extremely busy. Will let you
know as mentioned above.
---
There's more to life than just increasing its speed.
                                                - Mahatma Gandhi.
G. Dinesh Dutt,                                 email : brat@htilbom.ernet.in
Project Leader,                                 voice : 8321144/8349393/8391478
Hinditron Tektronix Instruments Ltd.,
SDF-2, Unit 63-A, SEEPZ, Andheri (east), Bombay - 400096.


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

From: hm@seneca.ix.de (Harald Milz)
Subject: Re: Found "talk" bug, fixing.
Date: Thu, 28 Jul 1994 20:31:27 GMT
Reply-To: hm@seneca.ix.de

Doug DeJulio (ddj@zardoz.elbows.org) wrote:

: > So, the "talk.FvK" patch has to be updated.  Given a remote address,
: > what's the quickest way to get the address of the local interface that
: > traffic to that address goes through?  I know I can do it by leafing
: > through /proc/net/route, but is there some more elegant or portable
: > way?  I'll start implementing the /proc/net/route method tonight, in
: > any event.

Shouldn't this be done by the proper routeing tables? 

-- 
Harald Milz                             office: hm@ix.de
iX Multiuser Multitasking Magazine      home:   hm@seneca.ix.de
Opinions are mine, not my employer's -- the answer is Forty-two
PS: I apologize for my bad return address - I hope this will be fixed soon.

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

From: flebbe@pluto.tat.physik.uni-tuebingen.de (Olaf Flebbe)
Subject: Re: Panasonic CD-ROM broke under >1.1.31
Date: 29 Jul 94 09:58:12 GMT

Eberhard_Moenkeberg@p27.rollo.central.de (Eberhard Moenkeberg) writes:

>All CDROM devices have to get mounted explicitely "read-only" now.

>Someone saw a bug within one driver, and so all drivers got changed.

That was me ;-) The problem was that one can fool the buffer cache
algorithm terribly, when you write to a R/O device.

>Let's hope that NFS mounts will not be the next (but, if someone
>is willing to restrict NFS mounts, too: -ENXIO would look nice,
>and probably really noone would understand the message. :-)

olaf--

-- 
  Olaf Flebbe,  Theoretische Astrophysik Tuebingen
  Internet:     flebbe@tat.physik.uni-tuebingen.de
  http://aorta.tat.physik.uni-tuebingen.de/~flebbe

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

From: Mitchum.DSouza@mrc-apu.cam.ac.uk (Mitchum DSouza)
Subject: Re: shared Libs and X11 don't work in Linu
Date: 29 Jul 1994 10:22:48 GMT

In article <317lbv$h5h@news.tuwien.ac.at>, ehritz@vexpert.dbai.tuwien.ac.at
(Gerald Ehritz) writes:
|> In article 28g@sun.cais.com, ericy@cais.cais.com (Eric Youngdale) writes:
|> In article <kaleb.775317458@kanga.x.org>, Kaleb KEITHLEY <kaleb@x.org>
|> wrote:
|> >ehritz@vexpert.dbai.tuwien.ac.at (Gerald Ehritz) writes:
|> >
|> >>I run into some strange problems trying to compile X11R6pl3 
|> >>I use Slackware 2.0 distribution ...
|> >
|> >Linux support in X11R6 is incomplete. You will either have to fix it
|> >yourself, wait for XFree86-3.1, or switch to FreeBSD/NetBSD, or wait
|> >until Linux has real SVR4-style shared libraries.
|> >
|> >    The problem in this case has nothing to do with linux support.  
|> >He was using an old version of "make" which did not understand the "export"
|>                ^^^^^^^^^^^^^^
|> >directive.
|> >
|> >-Eric
|> 
|> I use GNU make version 3.71. So you think this is old?
|> In the manual of version 3.70 i saw the "export" directive, so i asume, that
|> 3.71 understands it.

In any case unless you are in the XFree86 core team you will be unable to
compile shared libraries (DLL's) for linux as the standard X11 distribution
doesn't provide you with the associated jump.* files required for building
the DLL's. You can still however build the static archives by setting the
#define HasSharedLibraries in lnuxLib.rules to NO

Mitch

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

From: ehritz@vexpert.dbai.tuwien.ac.at (Gerald Ehritz)
Crossposted-To: comp.windows.x.i386unix
Subject: shared Libs and X11 don't work in Linux
Date: 27 Jul 1994 08:06:42 GMT
Reply-To: ehritz@vexpert.dbai.tuwien.ac.at

I run into some strange problems trying to compile X11R6pl3 and also compiling X11R5 applications. I traced it down to the entries for shared libraries in X11R6 and X11R5 config files. 
I use Slackware 2.0 distribution on 2 486 pc's. Everything works, except compiling X11R6pl3 or compiling X11 software, which generates libraries for its own. In the makefile-log i find the statement 

make: commands commence before first target. Stop

The referenced line in Makefile shows the statement : export JUMP_DIR JUMP_LIB

This happens in all of the library directories, which have some dependencies, like X11, Xt.
If i try to compile a X11 software with Xfree2.1.1, starting with xmkmf, i also get the shared library stuff in the Makefile, and if the software generates its own libraries, i also get the above error.

I tested this on 2 different ps's, and i also installed linux from scratch 3 times. Now i really wonder, if i have a broken distribution ( from univie.ac.at) or if there is something wrong with my two pc's, or one need special patches to make things work.

Many thanks

Gerald


---
________________________________________________________
Gerald Ehritz           ehritz@vexpert.dbai.tuwien.ac.at
Institut f. Informationssysteme
Technische Universitaet Wien
________________________________________________________


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

From: flebbe@pluto.tat.physik.uni-tuebingen.de (Olaf Flebbe)
Subject: Re: Panasonic CD-ROM broke under >1.1.31
Date: 29 Jul 94 10:22:07 GMT


>In comp.os.linux.development, article <1994Jul27.000944.4768@titan.westfalen.de>,
>  johannes@titan.westfalen.de (Johannes Stille) writes:
>> In article <312b26$1ao@smurf.noris.de> urlichs@smurf.noris.de (Matthias Urlichs) writes:

>> It is much better compareable to opening a device read-write where you
>> cannot write. I don't know any better approximation than EACCESS,
>> although this usually means that the action is not allowed (as opposed
>> to impossible).

>Exactly. So, since EACCES is somewhat misleading, we shouldn't use a
>legitimate error code for this, we should either invent our own or usurp
>one that's a reasonable approximation.

>Since other systems do reply with EROFS if you try this (just open /dev/fd0
>O_RDWR, with write protect on, on either a Sun or a SVR? machine -- I don't
>remember where I saw it) IMHO it's entirely reasonable.

The original patch for the CDROM code (with a horrible bug in it)
was by me. Linus (or someone else) invented the error code EACCES for
rejecting writes to a R/O floppy.

I tried writing to a R/O floppy on a silicon graphics indigo with
irix4 and it gave me EROFS. Please feel free to correct the error
code!

  olaf
-- 
  Olaf Flebbe,  Theoretische Astrophysik Tuebingen
  Internet:     flebbe@tat.physik.uni-tuebingen.de
  http://aorta.tat.physik.uni-tuebingen.de/~flebbe

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

From: kaplan@jussieu.fr (Kim-Minh Kaplan)
Subject: Energy star screen saver for X
Date: 27 Jul 1994 00:41:35 GMT

Subject: 

Here's the patch to use the power saving feature of your monitor.  It
works with my MAG 17 and cirrus logic 5428.  I don't know if it works
for you.

if you define DPMSVERTICAL or DPMSHORIZONTAL, it will turn off the
vertical or horizontal sync. to blank the screen.

Credit: this is nearly verbatim the patch from Christoph Rimek
chrimek@toppoint.de or chrimek@tpki.toppoint.de, adapted
to XFree86.

USE AT YOUR OWN RISKS: this can fry your monitor.

The file is in mit/server/ddx/x386/vga256/vga

My From line is probably wrong. use:

--
Kaplan Kim-Minh <kkaplan@cdfhp3.in2p3.fr>


*** 1.1 1994/07/21 15:24:51
--- vgaHW.c     1994/07/26 21:22:28
***************
*** 264,273 ****
--- 264,392 ----
       ScreenPtr     pScreen;
       Bool          on;
  {
+ #if defined (DPMSVERTICAL) || defined (DPMSHORIZONTAL)
+   static struct {
+     unsigned char     SeqCtrlIndex; /* Sequencer Index reg.   */
+     unsigned char     CrtCtrlIndex; /* CRT-Contr. Index reg.  */
+     unsigned char     CrtMiscIO; /* Miscellaneous register */
+     unsigned char     ModeControl; /* CRT-Controller:17h */
+     unsigned char     ClockingMode; /* Seq-Controller:01h */
+ #ifdef DPMSHORIZONTAL
+     unsigned char     HorizontalTotal; /* CRT-Controller:00h */
+     unsigned char     HorizDisplayEnd; /* CRT-Controller:01h */
+     unsigned char     StartHorizRetrace; /* CRT-Controller:04h */
+     unsigned char     EndHorizRetrace; /* CRT-Controller:05h */
+ #endif
+ #ifdef DPMSVERTICAL
+     unsigned char     Overflow; /* CRT-Controller:07h */
+     unsigned char     StartVertRetrace; /* CRT-Controller:10h */
+     unsigned char     EndVertRetrace; /* CRT-Controller:11h */
+ #endif
+   } vga;
+ #endif
+ 
    unsigned char   state;
  
    if (on)
      SetTimeSinceLastInputEvent();
+ 
+ #if defined (DPMSVERTICAL) || defined (DPMSHORIZONTAL)
+   if (x386VTSema) {
+     (*vgaSaveScreenFunc)(SS_START);
+     if (on) {
+       /* restore original values of VGA controller registers */
+       outb(0x3C2, vga.CrtMiscIO);
+ #ifdef DPMSHORIZONTAL
+       outb(0x3D4,0x00); /* HorizontalTotal */
+       outb(0x3D5,vga.HorizontalTotal);
+       outb(0x3D4,0x01); /* HorizDisplayEnd */
+       outb(0x3D5,vga.HorizDisplayEnd);
+       outb(0x3D4,0x04); /* StartHorizRetrace */
+       outb(0x3D5,vga.StartHorizRetrace);
+       outb(0x3D4,0x05); /* EndHorizRetrace */
+       outb(0x3D5,vga.EndHorizRetrace);
+ #endif
+ #ifdef DPMSVERTICAL
+       outb(0x3D4,0x07); /* Overflow */
+       outb(0x3D5,vga.Overflow);
+       outb(0x3D4,0x10); /* StartVertRetrace */
+       outb(0x3D5,vga.StartVertRetrace);
+       outb(0x3D4,0x11); /* EndVertRetrace */
+       outb(0x3D5,vga.EndVertRetrace);
+ #endif
+       outb(0x3D4,0x17); /* ModeControl */
+       outb(0x3D5,vga.ModeControl);
+       outb(0x3C4,0x01); /* ClockingMode */
+       outb(0x3C5,vga.ClockingMode);
+ 
+       /* restore index/control registers */
+       outb(0x3C4,vga.SeqCtrlIndex);
+       outb(0x3D4,vga.CrtCtrlIndex);
+     } else {
+       /* save original values of VGA controller registers */
+       vga.SeqCtrlIndex = inb(0x3C4);
+       vga.CrtCtrlIndex = inb(0x3D4);
+       vga.CrtMiscIO = inb(0x3CC);
+ #ifdef DPMSHORIZONTAL
+       outb(0x3D4,0x00); /* HorizontalTotal */
+       vga.HorizontalTotal = inb(0x3D5);
+       outb(0x3D4,0x01); /* HorizDisplayEnd */
+       vga.HorizDisplayEnd = inb(0x3D5);
+       outb(0x3D4,0x04); /* StartHorizRetrace */
+       vga.StartHorizRetrace = inb(0x3D5);
+       outb(0x3D4,0x05); /* EndHorizRetrace */
+       vga.EndHorizRetrace = inb(0x3D5);
+ #endif
+ #ifdef DPMSVERTICAL
+       outb(0x3D4,0x07); /* Overflow */
+       vga.Overflow = inb(0x3D5);
+       outb(0x3D4,0x10); /* StartVertRetrace */
+       vga.StartVertRetrace = inb(0x3D5);
+       outb(0x3D4,0x11); /* EndVertRetrace */
+       vga.EndVertRetrace = inb(0x3D5);
+ #endif
+       outb(0x3D4,0x17); /* ModeControl */
+       vga.ModeControl = inb(0x3D5);
+       outb(0x3C4,0x01); /* ClockingMode */
+       vga.ClockingMode = inb(0x3C5);
+ 
+       /* assure that video is enabled */
+       /* "0x20" is VIDEO_ENABLE_bit in register 01 of sequencer */
+       outb(0x3C4,0x01);
+       outb(0x3C5,vga.ClockingMode | 0x20);
+ 
+       /* test for vertical retrace in process.... */
+       if ((vga.CrtMiscIO & 0x80) == 0x80)
+       outb(0x3C2,vga.CrtMiscIO & 0xef);
+ 
+ #ifdef DPMSVERTICAL
+       /*  Set <End of vertical retrace> to minimum (0) and            *
+        *  <Start of vertical Retrace> to maximum (incl. overflow)     *
+        *  Result: turn off vertical sync (VSync) pulse                */
+       outb(0x3D4,0x10); /* StartVertRetrace */
+       outb(0x3D5,0xff); /* maximum value */
+       outb(0x3D4,0x11); /* EndVertRetrace */
+       outb(0x3D5,0x40); /* minimum (bits 0..3)  */
+       outb(0x3D4,0x07); /* Overflow */
+       outb(0x3D5,vga.Overflow | 0x84); /* bits 9,10 of  */
+       /* vert. retrace */
+ #endif
+ #ifdef DPMSHORIZONTAL
+       /*  Set <End of horizontal retrace> to minimum (0) and  *
+        *  <Start of horizontal Retrace> to maximum            *
+        *  Result: turn off horizontal sync (HSync) pulse      */
+       outb(0x3D4,0x04); /* StartHorizRetrace */
+       outb(0x3D5,0xff); /* maximum */
+       outb(0x3D4,0x05); /* EndHorizRetrace */
+       outb(0x3D5,0x00); /* minimum (0) */
+ #endif
+       /* restore both index registers */
+       outb(0x3C4,vga.SeqCtrlIndex);
+       outb(0x3D4,vga.CrtCtrlIndex);
+     }
+     (*vgaSaveScreenFunc)(SS_FINISH);
+   }
+ #else /* not DPMSVERTICAL, nor DPMSHORIZONTAL */
    if (x386VTSema) {
      outb(0x3C4,1);
      state = inb(0x3C5);
***************
*** 290,295 ****
--- 409,415 ----
      else
        ((vgaHWPtr)vgaNewVideoState)->Sequencer[1] |= 0x20;
    }
+ #endif /* not DPMSVERTICAL, nor DPMSHORIZONTAL */
  
    return(TRUE);
  }

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

Crossposted-To: comp.os.linux.help
From: arrouye@petole.imag.fr (Yves Arrouye)
Subject: Multiple systems on multiple drives and LILO?
Date: Fri, 29 Jul 1994 09:16:26 GMT

Hello,

I have two IDE drives on my system: the first one has DOS and Linux installed,
and I would like to install NEXTSTEP on the second one.
        I have tried installing NEXTSTEP on the second drive and everything is
fine until the installation procedure reboots before installing the system: my
PC then boots on the first drive, which has LILO (while the second should have
the NEXTSTEP loader), but I cannot make the second drive boot directly (or I
least I do not know how to do that).
        I tied to put an entry in lilo.conf for NEXTSTEP with /dev/hdb1 and
table=/dev/hdb, but when running /etc/lilo/install the program says it is not
able to get the magic for the second drive.

Any idea how I can obtain what I want?
Thanx,
Yves.

--
Advocates for the C++ school claim that a well designed           Yves Arrouye
    program does not need the extra flexibility (a lie),  Yves.Arrouye@imag.fr
while advocates for the Objective-C school claim that         (33) 76 57 48 64
    the errors are no problem in practice (another lie).             NeXT Mail

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

From: kevinl@bruce.cs.monash.edu.au (Kevin Lentin)
Subject: Re: 1060 cyliders a problem?
Date: 29 Jul 1994 07:52:41 GMT

Jeff Macdonald (jeff@zis.ziff.com) wrote:
> I have that exact drive and I'm using the UMSDOS file system. I dumped my old 
> hard drive to the maxtor and have had no problems. DOS's fdisk had no 
> problems. Don't you like how maxtor defines a megabyte as 1 million bytes? 

So do Western Digital. Their WD540 is a 516mb drive. There 212 is a 200mb
drive and so on. I once bought a 200mb drive and a week later got a 212mb
drive for the same price only to discover they had just changed their
definition.
-- 
[==================================================================]
[ Kevin Lentin                   |___/~\__/~\___/~~~~\__/~\__/~\_| ]
[ kevinl@bruce.cs.monash.edu.au  |___/~\/~\_____/~\______/~\/~\__| ]
[ Macintrash: 'Just say NO!'     |___/~\__/~\___/~~~~\____/~~\___| ]
[==================================================================]

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


** 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
******************************
