Subject: Linux-Misc Digest #457
From: Digestifier <Linux-Misc-Request@senator-bedfellow.MIT.EDU>
To: Linux-Misc@senator-bedfellow.MIT.EDU
Reply-To: Linux-Misc@senator-bedfellow.MIT.EDU
Date:     Tue, 21 Dec 93 09:13:09 EST

Linux-Misc Digest #457, Volume #1                Tue, 21 Dec 93 09:13:09 EST

Contents:
  Specialized XBoing sound driver for GUS/Linux? (Michael L. Murphy)
  Re: Debate: Time to Remove SLS From archive sites? (Vince Skahan)
  Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files (Hendrik G. Seliger)
  Re: Booting Linux Off Second HardDrive (Matt Welsh)
  Re: Specialized XBoing sound driver for GUS/Linux? (Jeff Randall)
  *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07) (Ian Jackson)
  Re: OPINION on Linux Counter: person lists? (Dr Eberhard W Lisse)
  Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files (Mr. Bassman)
  Re: Xwindows Terminal (Michael Elbel)
  Re: _Real_ hackers ... (Paul Tomblin)
  Re: Linux in a hospital? (Kai Petzke)
  Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files ( Karsten Ballueder)
  Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files (Peter Dalgaard SFE)

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

From: murphy@symcom.math.uiuc.edu (Michael L. Murphy)
Crossposted-To: uiuc.sw.linux
Subject: Specialized XBoing sound driver for GUS/Linux?
Date: 21 Dec 1993 06:25:47 GMT

XBoing 1.6 is cool!  But, I have the version 2.00 sounddrivers, and a
GUS, and the sound effects "queue" up (like, after I've died after a
particularly intense match, it sits there going "boing-boing-boing-
boom" for 20 seconds or so before "aw s**t" plays...) This is not
cool.  The audio.c file included for Linux looks good in theory (kill
the sound playing if there is one, and play the new sound) but it
doesn't work.  Why?  What's doing the buffering?  Does XBoing always
behave like this, even with older versions of the sound drivers?

The GUS is an ideal soundcard for the sound effects in a game like
XBoing.  Actually writing a specialized GUS driver should be trivial
(*smirk*) - load all the patches into the GUS's memory (should be plenty
of room even on a 256k GUS), and play the patch corresponding to the
name passed to the string passed in playSoundFile()'s argument in the
audio.c .  *There's no need to even deal with the DSP driver*.  Plus,
more that one sound (up to 32!) will be able to play at once, and
that'll sound great.  In fact, it's so trivial that someone out there
with a GUS must have done it already.  All right, fess up and share it
with the rest of us. :)

Well, I'm waiting... if no-one responds, I'll just have to delve through
glib & adagio and see how they do it, and write the sound driver
myself.  Well?  ("Get off your lazy butt and write it yourself!!!",
they shout.  Oh, OK...  sigh.)
-- 
+=And=the=Master=said=unto=the=silence,="In=the=path=of=our=happiness=shall=+
\ we find the learning for which we have chosen this lifetime." - R. Bach   /
+=send=e-mail=to=<murphy@symcom.math.uiuc.edu>==============================+

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

From: vince@victrola.wa.com (Vince Skahan)
Subject: Re: Debate: Time to Remove SLS From archive sites?
Date: 20 Dec 1993 17:51:14 -0800

I'd say give him 30 days to upload the current one or delete
the existing one.  If you don't want to delete it, move it
to a directory called "historical_archives" or something.

It's clearly out of date, buggy, and unsupported as a 
free downloadable product at this time and for the past
several months.

[...which is not to say that it hasn't been a great
        help to many, many people in the past...]

-- 
     ---------- Vince Skahan --------- vince@victrola.wa.com -------------
     "When you can get your customer to tatoo your name on their chest,
      it is unlikely that they will change brands"
             - Indiana Univ. of PA professor about Harley Davison owners

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

From: hank@Blimp.automat.uni-essen.de (Hendrik G. Seliger)
Subject: Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files
Date: Tue, 21 Dec 1993 08:11:52 GMT
Reply-To: hank@Blimp.automat.uni-essen.de

Jan Arne Fagertun (jafitv@termo.unit.no) wrote:


: I've made two small scripts for doing this :

Actually, you can even improve on that. Esp. international users quite
often have national characters in their texts, which also need
conversion from funny IBM-extended characterset to ISO-latin or
whatever you use on Mars. So, to add some noise to this newsgroup,
here's *my* solution (who else got s.th.? we might offer a prize for
the strangest solution=):

d2u:
#!/bin/sh
for i do
        tr -d '\r' < $i | tr '\204\224\201\216\231\232\341\240\205\203\202\212\210\241\215\214\242\225\223\243\227\226' '\344\366\374\304\326\334\337\341\340\342\351\350\352\355\354\356\363\362\364\372\371\373' > /tmp/d2u$$
        mv /tmp/d2u$$ $i
done


u2d:
#!/bin/sh
for i do
        tr '\344\366\374\304\326\334\337\341\340\342\351\350\352\355\354\356\363\362\364\372\371\373' '\204\224\201\216\231\232\341\240\205\203\202\212\210\241\215\214\242\225\223\243\227\226' < $i > /tmp/d2u$$
        mv /tmp/d2u$$ $i
done


(Actually, u2d doesn't put in the '\r', but I never had any DOS-stuff
complain about it.)

Hank



--
======================================================================
         Hendrik G. Seliger                  Universitaet Essen
     hank@automat.uni-essen.de                Schuetzenbahn 70
      Tel.: +49-201-183-2898                45117 Essen, Germany
======================================================================
             "Handling interrupts is simple." (G. Pajari)
             "Interrupts are an unpleasant fact of life." (A. Tanenbaum)

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

Crossposted-To: comp.os.linux.help
From: mdw@cs.cornell.edu (Matt Welsh)
Subject: Re: Booting Linux Off Second HardDrive
Date: Tue, 21 Dec 1993 08:16:13 GMT

In article <2f5no3$epi@orion.cc.andrews.edu> beaman@andrews.edu (Kendall Beaman) writes:
>    I'm about to do a followup article (by request) to my previous one about
>how I could boot Linux off my second drive using the OS/2 manager.  I have
>a question.  Does Linux Patch Level 12 support this.  At the end of the
>installation it told me that it couldn't install for boot off second hard
>drive and then asked if it could take over the first hard drives.  Of course
>I told it no.  This might be the problem.  Someone suggested that OS/2 couldn't
>read the Linux extended filesystem but I did have Linux running off my first
>hard drive being booted from the OS/2 Boot Manager.  Any help on this would
>be most appreciated.

All you need to do is install LILO on the Linux partition on the
second drive. NOT ON THE SECOND DRIVE ITSELF. You install LILO as a
second-stage boot loader for the Linux kernel on your Linux root
partition (such as /dev/hdb1). 

You then instruct OS/2's boot manager to boot Linux from this
partition. When booting, it should start LILO as the second-stage boot
loader, and all will be well.

As far as I know, booting from the second hard drive has nothing to do
with kernel support. As long as you have a boot loader installed for
your Linux kernel, and have some way of starting that boot loader
(e.g., from OS/2's BM, or from LILO installed on the MBR), it doesn't
matter where your Linux kernel or root filesystem is.

mdw
-- 
"Do you want to be Finnish? Sure, we all do!"

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

From: randall@ux1.cso.uiuc.edu (Jeff Randall)
Crossposted-To: uiuc.sw.linux
Subject: Re: Specialized XBoing sound driver for GUS/Linux?
Date: 21 Dec 1993 09:05:19 GMT
Reply-To: jrandall@uiuc.edu (Jeff Randall)

murphy@symcom.math.uiuc.edu (Michael L. Murphy) writes:
>XBoing 1.6 is cool!  But, I have the version 2.00 sounddrivers, and a
>GUS, and the sound effects "queue" up (like, after I've died after a
>particularly intense match, it sits there going "boing-boing-boing-
>boom" for 20 seconds or so before "aw s**t" plays...) This is not
>cool.  The audio.c file included for Linux looks good in theory (kill
>the sound playing if there is one, and play the new sound) but it
>doesn't work.  Why?  What's doing the buffering?  Does XBoing always
>behave like this, even with older versions of the sound drivers?

The key question is: 'What's doing the buffering?'


Short Answer: the kernel.

Long Answer: The kernel sounddrivers (even the old ones) has a buffer.
        If you think back, when you did 'make config' it asked you for
        what size buffer you wanted to use.  To test this theory, grab
        an .au file and cat it to /dev/audio.  Before it's finished, 
        ^C it and count how long you have to wait before the sound 
        actually stops...  To fix your immediate problem, decrease the
        size of the buffer, but this is not optimal.


>The GUS is an ideal soundcard for the sound effects in a game like
>XBoing.  Actually writing a specialized GUS driver should be trivial
>(*smirk*) - load all the patches into the GUS's memory (should be plenty
>of room even on a 256k GUS), and play the patch corresponding to the
>name passed to the string passed in playSoundFile()'s argument in the
>audio.c .  *There's no need to even deal with the DSP driver*.  Plus,
>more that one sound (up to 32!) will be able to play at once, and
>that'll sound great.  In fact, it's so trivial that someone out there
>with a GUS must have done it already.  All right, fess up and share it
>with the rest of us. :)

Well.. gimmie a break.. only had *MY* GUS for a week.. and spent most of
it playing DOOM and taking finals.. =)  Maybe if I get bored enough this
week.... I might give it a swing.


>Well, I'm waiting... if no-one responds, I'll just have to delve through
>glib & adagio and see how they do it, and write the sound driver
>myself.  Well?  ("Get off your lazy butt and write it yourself!!!",
>they shout.  Oh, OK...  sigh.)

Ah.. I see you *HAVE* learned the key to running a Linux system:  if it
doesn't currently exist, ask if someone's made their own, then if they
haven't, write it yourself..  =)

-- 
JRandall@uiuc.edu (MIME)                     THIS IS _NOT_ CCSO'S OPINION!!!
jar42733@sumter.cso.uiuc.edu (NeXT)           If It were, It would've had a
CP-SEL/MEL,IA, CFI-AI                          more important name on it. =)

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

From: ijackson@nyx.cs.du.edu (Ian Jackson)
Subject: *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07)
Date: Tue, 21 Dec 1993 11:03:01 GMT

Please do not post questions to comp.os.linux.misc - read on for details of
which groups you should read and post to.

Please do not crosspost anything between different groups of the comp.os.linux
hierarchy.  See Matt Welsh's introduction to the hierarchy, posted weekly.

If you have a question about Linux you should get and read the Linux Frequently
Asked Questions with Answers list from sunsite.unc.edu, in /pub/Linux/docs, or
from another Linux FTP site.  It is also posted periodically to c.o.l.announce.

In particular, read the question `You still haven't answered my question!'
The FAQ will refer you to the Linux HOWTOs (more detailed descriptions of
particular topics) found in the HOWTO directory in the same place.

Then you should consider posting to comp.os.linux.help - not
comp.os.linux.misc.

Note that X Windows related questions should go to comp.windows.x.i386unix, and
that non-Linux-specific Unix questions should go to comp.unix.questions.
Please read the FAQs for these groups before posting - look on rtfm.mit.edu in
/pub/usenet/news.answers/Intel-Unix-X-faq and .../unix-faq.

Only if you have a posting that is not more appropriate for one of the other
Linux groups - ie it is not a question, not about the future development of
Linux, not an announcement or bug report and not about system administration -
should you post to comp.os.linux.misc.


Comments on this posting are welcomed - please email me !
--
Ian Jackson  <ijackson@nyx.cs.du.edu>  (urgent email: iwj10@phx.cam.ac.uk)
2 Lexington Close, Cambridge, CB4 3LS, England;  phone: +44 223 64238

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

From: el@lisse.NA (Dr Eberhard W Lisse)
Subject: Re: OPINION on Linux Counter: person lists?
Date: Tue, 21 Dec 1993 07:28:42 GMT

hta@uninett.no (Harald T. Alvestrand) writes:

>Hello,
>I am now ready to publish a list of Linux users who have written to
>the counter and given permission for their names to be published.
>Is there anyone who objects to the posting of a list that looks like
>this:

>Denmark
>==============================================
>Henry Land                     luxd@dix.dk                  
>Mike Olsen                     mcexer@den.dk         

>2 persons listed

I you should present it in an awkable, perlable format, sometheting
like

Henry Land,denmark,luxd@dix.dk

>I have had a number of requests for this list in various formats; if
>anyone objects to me publishing it, either on this group or by anonymous
>FTP, I would like to hear of it rather quickly, so that I don't do anything
>that anyone would object to.

And I think you should have it available per FTP, for the people that
want it, makes for easier updates.

greetings, el
-- 
Dr. Eberhard W. Lisse   \         /                 Windhoek Central Hospital
<el@lisse.NA>            \ *      |  Department of Obstetrics and Gynaecology
Private Bag 13215         \      /  61 203 2106/7 (Bleeper)  61 224014 (home)
Windhoek, Namibia         ;____/

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

From: bassman@isoit034.bbn.hp.com (Mr. Bassman)
Subject: Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files
Date: Tue, 21 Dec 1993 12:23:51 GMT

In article <CIDLFs.Cx7@uni-essen.de>, hank@Blimp.automat.uni-essen.de (Hendrik G. Seliger) writes:
|> Jan Arne Fagertun (jafitv@termo.unit.no) wrote:
|> : I've made two small scripts for doing this :
[...]
|> So, to add some noise to this newsgroup,
|> here's *my* solution (who else got s.th.? we might offer a prize for
|> the strangest solution=):

Well, I can think of some silly ways of doing it, eg: using awk !
Here's the essential lines, ommitting the loop bits:

d2u:
        awk 'BEGIN{FS="\r"}{print $1}' < $infile > $outfile

u2d:
        awk '{printf "%s\r\n", $0}' < $infile > $outfile


Hey - here's an even more silly way: write a c program, which checks
every char, deleting it if it's \r (d2u) or changing it to \r\n (u2d),
and then writing it out. It'd probably run quicker, so why bother with
shell tools (and portablilty) at all ?


Mr. Bassman
Platform Services (UNIX)
Hewlett-Packard, Boeblingen, Germany
bassman@hpbbi30.bbn.hp.com

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

From: me@tartufo.pcs.com (Michael Elbel)
Subject: Re: Xwindows Terminal
Reply-To: me%dude.pcs.dec.com@inet-gw-2.pa.dec.com
Date: Tue, 21 Dec 1993 12:03:27 GMT

In <1993Dec20.180532.22113@taylor.wyvern.com> mark@taylor.wyvern.com (Mark A. Davis) writes:

>me@tartufo.pcs.com (Michael Elbel) writes:
[...]
>>However, you're making the assumption that there already exists a
>>working configuration for that class of X-terminals. This, at least in
>>my case here wasn't true. 

>?? The default one normally works just fine. 

Except for the network part (including font service, because, who
would set up the whole lot of X-fonts for e.g. NCDs if there are
already a couple of font servers running in the network. ;-) This, of
course, isn't a big deal if you know what you're doing, but it *has*
to be done nevertheless.

>Well, we are not talking about network configuration :)  That has to be
>done whether it is a workstation or an Xterminal.  In either case, it is
>unnecessary to set up NFS/RFS/NIS/YP/etc for Xterminals....

Except for, e.g. font service if the X-terminal isn't running R5 and
DNS/YP if you want it to know hosts' names.

>>Once you've done it, the next installation will take you almost no
>>time, but this first setup has to be done. In my experience, the
>>maintenance for X-terminals is only relatively cheap if you have a lot
>>of them and all are of the same kind (ever tried to maintain NCD *and*
>>DEC *and* HP X-terminals?)

>If you mean maintenance for the HARDWARE only, then I agree with you- but
>that applies to any hardware, such as printers, computers, drives, etc....
>consistancy is good.  As for the OS and software, there is really nothing
>to maintain on Xterminals, you plug it in and go to work :)

Depends on what you call software maintenance. You obviously *have*
experience with different kinds of X-terminals - try to generate a
setup on different brands that looks similar to the user for all of
them (e.g. the same fonts available, which is especially hard on DEC
and HP X-terminals that mainly seem to be designed to serve DEC and HP
hosts). Upgrading to a new software release also isn't *that* easy -
although easier than upgrading, like, a Workstation OS.

[..]

>Believe it or not, we [here] want users to use only remote resources, meaning
>the ultimate simplicity of maintenance, highest security, and often (as is here)
>lower cost.  If this is not your [reader's] goal, then Xterminals are not
>for you :)
'
I can understand this very well. I'd also rather not have the bulk of
our VAX-Cluster users use workstations or PCs. It *is* nice to be able
to just put a X-terminal on someone's desk, plug it in and not have to
worry about the local setup. Like several people (you including) have
already said, it all depends on your needs. I just wouldn't want to
underestimate the actual amount of work that goes into keeping a horde
of different X-terminals running consistently. If you have a some
hints about what to do/avoid in order to keep a net running with as
little work as possible, I'm sure other people would be interested too :-) 

Michael
Michael Elbel, Digital-PCS GmbH, Muenchen, Germany - me%pcs.dec.com@dec.com
Fermentation fault (coors dumped)

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

From: ab401@freenet.carleton.ca (Paul Tomblin)
Subject: Re: _Real_ hackers ...
Reply-To: ab401@freenet.carleton.ca
Date: Tue, 21 Dec 1993 12:46:03 GMT

armb@setanta.demon.co.uk (Alan Braggins) writes:

>In article <2en92b$j4n@senator-bedfellow.MIT.EDU> jmartin@opus.starlab.csc.com (John A. Martin) writes:
>>   A colleague, Dick Sites, once played "Happy Birthday" on a bank of tape
>>   drives for his girlfriend from the console of an IBM 709.  We all had 
>>   been very curious why he had signed up for computer time when we knew 
>>   he had a date!

>I used to work somewhere with an NC lathe that could play the British national
>anthem. (The milling machine played something else, but I forget what).

Not quite as hackish, but there used to be a word processor for the Commodore 
that if you hit the right 4 keys at once, it would play "Pomp and 
Circumstance March # 1".  Would freak people out if you were demoing your 
Word Porcessor and suddenly it started playin music.

-- 
Paul Tomblin.  In Vicki Robinson we trust.
"When viewed from the proper perspective, this thread is actually just a bunch
of people being silly." - Daniel Lottero

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

From: wpp@marie.physik.tu-berlin.de (Kai Petzke)
Subject: Re: Linux in a hospital?
Date: 21 Dec 1993 13:12:51 GMT

In <1993Dec20.203259.10095@ultb.isc.rit.edu> rxg3321@ultb.isc.rit.edu (R.X. Getter) writes:

>Linux is distributed expressly with no warranty. If someone decides
>to use it as a base for mission critical software in a hospital, he is
>taking complete responsibility for its behavior.

I know this.  But I am responsible for any decision I take.  In case
of SCO, I would have to trust.  In case of Linux, I can take a look
at the sources.  That is the difference.

>If, as a result of a
>failure, someone dies, the penalties could easily be criminal as well as
>civil. In the case of mission critical software which is sold as mission
>critical software, disclaiming liability is meaningless.

But there is no OS sold as "mission critical".  Any manufactorer of any
type of computer part will tell you something like: "1 read error in
10^10", or similiar.  No vendor of an OS guarentees you, that it won't
crash.  They would get bankrupt within days, if they did otherwise.

>Also, any product
>has an implied warranty of useability for its intended purpose. (If a word
>processor doesn't process words, you can get your money back no matter what
>the license says.) For mission critical, useability also means that the
>product won't fail, or at least won't cause irreparable harm. I would be
>very afraid of using Linux for this type of application. I would start with
>fault tolerant hardware, a fault tolerant OS, a fault tolerant database,
>and a very extensive period of testing.

If you know fault tolerant hardware, OS and database, I would be happy,
if you tell me them.  I do not know any.

I will print labels.  On that labels will be a blood group.  That blood
group must not be wrong.

This is the situation.

There is a fallback possibility.  If the system says: "Something is wrong
here, I can't print a label" this would annoy people, but would not cause
harm.  They could write the label by hand, as they do now.

So I will store a CRC of the blood group and the number of the donator
in a different place.  The change, that modified data produces the same
CRC is one in 2^32, or one in 4 billion.

If my software is faulty, or Linux is faulty, or the hardware is faulty,
we will see modified data.  With a change of 99,999999%, the CRC will
be wrong, and a message will be printed, saying: "Internal data error
-- the blood group may be corrupt", but no label will be printed.  If
this happens ten times in a row, we will know, that something is defunct,
and we must stop using this software.

>Anything less could easily be criminal
>negligence. I wouldn't touch Linux, and I wouldn't touch a conventional PC.

In the same hospital, in the same department, the machines for the
- AIDS test
- Hepatithis test
- Incubator
are all connected to conventional PC's, two running DOS, one running
SCO and Oracle.  I haven't seen computers, which aren't PC's.

A failed AIDS test is more dangerous than a wrong printed label.  In
the later case, a double check must be done by the stuff, in the
other, it won't.

I have read the ads of other companies, who supply software for blood
banks.  They end up using DOS or SCO, too, on conventional PC's.
--
Kai
wpp@marie.physik.tu-berlin.de
Advertisement by Microsoft in a well-known German magazine:
        If you don't like our programmes, then make your own ones.
However, they expect you to use Microsoft products for this -:)

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

From: karsten@lt6.cs.rhbnc.ac.uk ( Karsten Ballueder)
Subject: Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files
Date: 21 Dec 1993 12:29:30 GMT
Reply-To: karsten@lt6.cs.rhbnc.ac.uk ( Karsten Ballueder)


Nice scripts/solutions, but don't forget to remove the CTRL-D at the end of
DOS-files.  :-)

--


                                 _____..---========+^+=========---.._____
    ______________________ __,-='=====____  ================== _____=====`=
   (._____________________I__) - _-=_/    `--------=+=--------'
       /      /__...---===='---+---_'          
      '------'---.___ -  _ =   _.-'    
                     `--------'                
                                                 USS Enterprise, NCC-1701D 
  ------------------------------------------------------------------------------
         Karsten Ball"uder, Royal Holloway, c/o Physics Department,
             Egham Hill, Egham, Surrey TW20 0EX, United Kingdom
        charon.physik.uni-osnabrueck.de   jupiter.rz.uni-osnabrueck.de
                  --> LinuX - The better text adventure. <--

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

From: pd@kubism.ku.dk (Peter Dalgaard SFE)
Subject: Re: d2utxt-0.1.tar.gz -- tools for converting Unix and MS-DOS text files
Date: Tue, 21 Dec 1993 13:01:20 GMT

In <CIDx3s.Lro@hpwin052.uksr.hp.com> bassman@isoit034.bbn.hp.com (Mr. Bassman) writes:

>In article <CIDLFs.Cx7@uni-essen.de>, hank@Blimp.automat.uni-essen.de (Hendrik G. Seliger) writes:
>|> Jan Arne Fagertun (jafitv@termo.unit.no) wrote:
>|> here's *my* solution (who else got s.th.? we might offer a prize for
>|> the strangest solution=):

I've actually USED something like this:

sed `echo 's/$/X/' | tr X '\015'` < setup > /dev/lp1

to get a printout of the Slackware setup script. Well, to tell
the truth it was

echo sed 's/$/X/' | tr X '\015' > lp.filter
lp.filter < setup > /dev/lp1

(BTW: How do you insert a CR in your file with vi (alias elvis)??
^V^M doesn't seem to work)

--
   O_   ---- Peter Dalgaard
  c/ /'  --- Statistical Research Unit
 ( ) \( ) -- University of Copenhagen
~~~~~~~~~~ - (pd@kubism.ku.dk)

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


** 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-Misc-Request@NEWS-DIGESTS.MIT.EDU

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

    Internet: Linux-Misc@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-Misc Digest
******************************
