Linux-Development-Sys Digest #434, Volume #6 Fri, 26 Feb 99 22:14:40 EST
Contents:
Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?)
([EMAIL PROTECTED])
Re: Apache and persistent CGI programs????? (Max Welton)
896chipset (Donovan)
896chipset (Donovan)
dma_buffsize (Bob Nelson)
Re: Why I'm dumping Linux, going back to Windblows (finished!)
Re: Help!! Error compiling libstdc++ (Juergen Heinzl)
Re: Very odd getspent() behavior (RH 5.2) (Juergen Heinzl)
Re: /dev/zero (Juergen Heinzl)
Re: Kernel 2.2.2 installation (Aaron Faby)
TCP/IP, /proc/net, snmp (nospam)
Re: Kernel 2.2.2 installation (David T. Blake)
Re: Linux Threads use of SIGUSR1, SIGUSR2 (Peter Samuelson)
Re: Kernel 2.2.2 installation (Aaron Faby)
Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?) (BL)
Re: LINUX MERCED ("David A. Frantz")
Re: "RPM's harmful to Linux" harmful to Linux (Christopher B. Browne)
Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?) (Julian Robert Yon)
Re: "RPM's harmful to Linux" harmful to Linux (Todd Knarr)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux.slackware,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?)
Date: Fri, 26 Feb 1999 18:44:23 GMT
On Fri, 26 Feb 1999 13:36:11 -0500, GBP <[EMAIL PROTECTED]> wrote:
>
>Yeah point well taken. But is it true that overclocking can result in
>system instability? When netscape crashes how am i going to know it was
>a bug and not my CPU doing and instruction wrong or something? When
>people say instability what exactly do they mean? do these machines
>freeze?
>
>gbp
system freeze or kernel panic. my experience is page faults...
------------------------------
From: Max Welton <[EMAIL PROTECTED]>
Subject: Re: Apache and persistent CGI programs?????
Date: Fri, 26 Feb 1999 12:21:00 -0800
David Sisk wrote:
>
> Hi:
>
> Another quick question (I hope!). Is it possible for Apache (or any
> CGI-compliant web-server, for that matter) to launch a process in the normal
> CGI manner but NOT kill it until later? I understand that the CGI program
> would have to be written to not end immediately, but to sit and wait for
> further instructions (maybe via named pipes or something along those lines).
> If the process didn't die, is there a CGI-based method to send it further
> messages.
>
> For example:
>
> Hit1: launch the CGI program
> Hit2: do operation1
> Hit3: do operation2
> Hit4: exit the CGI program.
>
> Any ideas on how to point the instructions back to the right existing
> process?
>
> Is this possible with the current CGI specification? Any comments truly
> appreciated. Doubly thankful if you'd email as well as posting.
This sounds like a job for a servlet. Servlets operate much like ordinary
CGIs (even using the CGI protocol) but can remain 'up' and stateful.
max
--
The Feynman problem solving Algorithm
1) Write down the problem
2) Think real hard
3) Write down the answer
Murray Gel-mann in the NY Times
------------------------------
From: Donovan <[EMAIL PROTECTED]>
Subject: 896chipset
Date: Fri, 26 Feb 1999 16:21:39 -0800
Is there a kernal out for the Symbios53c896 chipset yet? anyone?
------------------------------
From: Donovan <[EMAIL PROTECTED]>
Subject: 896chipset
Date: Fri, 26 Feb 1999 16:20:51 -0800
Is there a kernal out for the Symbios53c896 chipset yet? anyone?
------------------------------
From: Bob Nelson <[EMAIL PROTECTED]>
Subject: dma_buffsize
Date: 26 Feb 1999 17:53:49 -0600
- Why was this tunable parameter revoked from the sound.o module
(somewhere between 2.0.36 and 2.2.1)?
- AFAIK, this is now strictly a hard-coded value in sound_config.h.
Right?
--
========================================================================
Bob Nelson -- Dallas, Texas, USA ([EMAIL PROTECTED])
http://www.oldradio.com/archives/nelson/open-computing.html
``Those who don't understand UNIX are condemned to reinvent it, poorly.''
------------------------------
From: [EMAIL PROTECTED] (finished!)
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: Fri, 26 Feb 1999 23:08:23 GMT
Are you crazy? MS Office is the industry standard and it's going to
stay that way. Bill won't let it happen any other way!
On Wed, 24 Feb 1999 09:12:26 +0000, chaz <[EMAIL PROTECTED]>
wrote:
>Hi,
>
>The reason office 97 file incorpiration is needed in linux is because companys
>like to send things in a MS format because it is what is supplied and has the
>vast majority of the market. However, as time progesses an MS slowly falls
>apart there will be a new standard in office file formats. I have seen many
>problems with companies having probs reading either newer versions of word than
>what they are using, I have also seen that the MS word for Mac has some slight
>differences to it.. So when MS goes down hill so will the obsession for MS
>office file formats.
>
>Matthew Isleb wrote:
>
>> In comp.os.linux.development.system Sniper <[EMAIL PROTECTED]> wrote:
>> >>Vmstat on both machines don't ever show 'swapped pages per second' above
>> >>zero for longer than a second (and it occurs rarely), so I notice no
>> >>sluggishness due to swapping.
>> >>
>> >>I don't even _want_ to say, try that with NT. I think I don't need to.
>>
>> > Can you export back to 97 format as well ? What about Excel 97 ?
>>
>> Can I ask what this obsession with the Office 97 file format is? I mean,
>> so you have to save files in an older format for portability, big deal.
>> Or do the hypothetical users you are talking about use 100% of the Office 97
>> features which would prevent the usage of another file format. Get real.
>>
>> Matt
>
>
>
>--
>Chaz
>
>Telephone: +44 1274 23 5981
>Mobile: +44 7788 422340
>Pager: +44 7666 782128
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Crossposted-To: comp.os.linux,comp.os.linux.development.apps
Subject: Re: Help!! Error compiling libstdc++
Date: Sat, 27 Feb 1999 00:42:24 GMT
In article <[EMAIL PROTECTED]>, Andrius Kaikaris wrote:
><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
[...]
So I snipped a lot ... *please* no HTML. Said that ... neither file.h
nor fcntl.h should be old; you simply must not mix glibc/libc6 and libc5
header files and that alone might be the cause for all the trouble
already.
Cheers,
Juergen
--
\ Real name : Jürgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
\ Phone Private : +44 181-332 0750 \ /
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Subject: Re: Very odd getspent() behavior (RH 5.2)
Date: Sat, 27 Feb 1999 00:42:22 GMT
In article <[EMAIL PROTECTED]>, Jonathan B Ellis wrote:
>For some reason getspent() returns NULL every single time it is called.
>Here is the code:
Minor question ... you *do* run that as root ? If not, no go since,
of course, only root is allowed to read the shadow file.
Cheers,
Juergen
--
\ Real name : Jürgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
\ Phone Private : +44 181-332 0750 \ /
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Subject: Re: /dev/zero
Date: Sat, 27 Feb 1999 00:42:23 GMT
In article <[EMAIL PROTECTED]>, Andreas Schwab wrote:
>[EMAIL PROTECTED] (Juergen Heinzl) writes:
[...]
>|> I always dreamt of that 8) ... nah, but serious again, /dev/zero
>|> is often used for memory mapped files for instance. Just remove it ... NO ...
>|> just kidding since without /dev/zero no loading of shared libraries anymore,
>|> at least with the libc5 loader (the libc6 one uses /dev/null (?)).
>
>No, libc6 used MAP_ANON, which does not require a file at all.
Thanks for the info,
Juergen
--
\ Real name : Jürgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
\ Phone Private : +44 181-332 0750 \ /
------------------------------
From: Aaron Faby <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.2.2 installation
Date: Thu, 25 Feb 1999 10:03:49 -0500
==============8BED1FC924CA70B6E0A1831E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
kingman cheung wrote:
> In article <[EMAIL PROTECTED]>,
> David D. Gitchell <[EMAIL PROTECTED]> wrote:
> >Aaron Faby wrote:
> >>
> >> Greetings...
> >>
> >> I compiled 2.2.2 fine but when i tried to run the mkinitrd it says
> >> "cannot find loopback device". Is there something else I need
> >> to configure? Thanks!
> >
> > Loopback device needs to be part of the kernel you are running at the
> >time that you execute mkinitrd. Check in your kernel config under
> >"Block devices" to see if you enabled it.
>
> My trick would be "insmod loop" before doing mkinitrd. Actually, I think
> mkinitrd is needed only if using SCSI adaptors and using it as a module.
> --
> kingman
I compiled the kernel per instructions located at the Red Hat website
(Im running Red Hat 5.2) http://www.redhat.com/errata/ and followed
their directions to the T. Maybe they added some steps that werent
necessary to my system? This is the first kernel that I have ever compiled
and Im wondering why I didnt get the same errors on my home machine.
--
Aaron Faby
[EMAIL PROTECTED]
System Administrator/Technical Support
Yourlink, Inc.
==============8BED1FC924CA70B6E0A1831E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
kingman cheung wrote:
<blockquote TYPE=CITE>In article <[EMAIL PROTECTED]>,
<br>David D. Gitchell <[EMAIL PROTECTED]> wrote:
<br>>Aaron Faby wrote:
<br>>>
<br>>> Greetings...
<br>>>
<br>>> I compiled 2.2.2 fine but when i tried to run the mkinitrd it says
<br>>> "cannot find loopback device". Is there something else I need
<br>>> to configure? Thanks!
<br>>
<br>> Loopback device needs to be part
of the kernel you are running at the
<br>>time that you execute mkinitrd. Check in your kernel config
under
<br>>"Block devices" to see if you enabled it.
<p>My trick would be "insmod loop" before doing mkinitrd. Actually,
I think
<br>mkinitrd is needed only if using SCSI adaptors and using it as a module.
<br>--
<br>kingman</blockquote>
I compiled the kernel per instructions located at the Red Hat website
<br>(Im running Red Hat 5.2) <A
HREF="http://www.redhat.com/errata/">http://www.redhat.com/errata/</A> and followed
<br>their directions to the T. Maybe they added some steps that werent
<br>necessary to my system? This is the first kernel that I have ever compiled
<br>and Im wondering why I didnt get the same errors on my home machine.
<pre>--
Aaron Faby
[EMAIL PROTECTED]
System Administrator/Technical Support
Yourlink, Inc.</pre>
</html>
==============8BED1FC924CA70B6E0A1831E==
------------------------------
From: [EMAIL PROTECTED] (nospam)
Subject: TCP/IP, /proc/net, snmp
Date: Sat, 27 Feb 1999 02:17:32 GMT
Can anyone point me to documentation - as detailed as possible -
on the following items. ( Online is best, but books, journals,
anything will be appreciated ).
1. The /proc directory - this is a view into the kernel, but
it is very difficult to find details of what the variables
are and how they work. I am particularly interested in the
tcp/ip variables in /proc/net and the SNMP variables.
2. From a tcp/ip standpoint - an exposition of the complete
accounting ( bean counting ) rules for packets flowing
into/out of a node - essentially a graph with the nodes
being the categories and the links showing the possible
paths and the rules which govern them. This is so that
one could construct a complete report of what happens
to all the packets at that node.
Thanks.
that node.
------------------------------
From: [EMAIL PROTECTED] (David T. Blake)
Subject: Re: Kernel 2.2.2 installation
Date: 25 Feb 1999 07:50:45 -0800
Aaron Faby <[EMAIL PROTECTED]> writes:
>kingman cheung wrote:
>>David D. Gitchell <[EMAIL PROTECTED]> wrote:
>>>Aaron Faby wrote:
>>>> Greetings...
>>>> I compiled 2.2.2 fine but when i tried to run the mkinitrd it
>>>> says "cannot find loopback device". Is there something else I
>>>> need to configure? Thanks!
>>> Loopback device needs to be part of the kernel you are
>>>running at the time that you execute mkinitrd. Check in your
>>>kernel config under "Block devices" to see if you enabled it.
>> My trick would be "insmod loop" before doing mkinitrd. Actually, I think
>> mkinitrd is needed only if using SCSI adaptors and using it as a module.
>I compiled the kernel per instructions located at the Red Hat website
>(Im running Red Hat 5.2) http://www.redhat.com/errata/ and followed
>their directions to the T. Maybe they added some steps that werent
>necessary to my system? This is the first kernel that I have ever compiled
>and Im wondering why I didnt get the same errors on my home machine.
Your first mistake was trusting Redhat's instructions. Don't
get me wrong, they do lots to help the linux community, but
a much better bet would be looking at the comments and readmes
in the kernel source.
I love the loopback device, and always build it in. Kinda funny,
but Dec included it (and mkisofs) in their latest True64Unix
release. Linux is trickling down to other Unices.
Just select it in a kernel rebuild and all will work fine.
--
Dave Blake
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: Linux Threads use of SIGUSR1, SIGUSR2
Date: 26 Feb 1999 20:00:59 -0600
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Rakesh Tiwari <[EMAIL PROTECTED]>]
> This relates to threads, may not relate to exactly what you folks are
> talking about (sorry for butting in).
So start your own thread. (No pun intended.) (Actually it was
intended, and I'm almost sorry.)
> I wrote a simple program in Solaris which allowed me to
> suspend/resume threads from keyboard within a process (kill
> SIGUSR1/SIGUSR2 pid).
> Same program will crash on Linux since pthread (I think) creates a
> process per thread.
Actually same program will do weird things on Linux since until fairly
recently, LinuxThreads (the standard pthreads implementation on Linux)
used SIGUSR1/SIGUSR2 internally. I believe the situation has been
resolved since the kernel now allows more signals than before.
Whether your program will work on Linux assuming it doesn't stomp on
the two pthreads-internal signals, I do not know. But a more accurate
way to put your statement is that Linux creates a thread for every
process, not a process for every thread. So each thread has a unique
PID (or TID, if you will) just like each process does. I haven't tried
it but you should be able to put a thread to sleep by sending it a
SIGSTOP, just like you can a single-threaded process. [If a Real
Threads Programmer reads this and frowns, please correct and ridicule
me to your heart's content....]
> My question is, what version of pthreads is likely to have decent
> implementation of threads which will allow me to suspend/resume
> threads arbitrarily ?(more like NT, basically I want to implement
> ResumeThread/ SuspendThread calls) and not created stupid processes ?
Hmmm, don't know if there are other threads implementations, but if I
remember correctly you might at least upgrade to a recent glibc (if you
haven't already) so it won't stomp on your SIGUSR1/USR2. (At least
there was talk of using different signals ... I don't actually know
that it took place.)
As to stupid processes, the processes will only be as stupid as the
code you wrote for them.... (:
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: Aaron Faby <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.2.2 installation
Date: Thu, 25 Feb 1999 11:17:34 -0500
"David T. Blake" wrote:
> Aaron Faby <[EMAIL PROTECTED]> writes:
>
> >kingman cheung wrote:
> >>David D. Gitchell <[EMAIL PROTECTED]> wrote:
> >>>Aaron Faby wrote:
> >>>> Greetings...
>
> >>>> I compiled 2.2.2 fine but when i tried to run the mkinitrd it
> >>>> says "cannot find loopback device". Is there something else I
> >>>> need to configure? Thanks!
>
> >>> Loopback device needs to be part of the kernel you are
> >>>running at the time that you execute mkinitrd. Check in your
> >>>kernel config under "Block devices" to see if you enabled it.
>
> >> My trick would be "insmod loop" before doing mkinitrd. Actually, I think
> >> mkinitrd is needed only if using SCSI adaptors and using it as a module.
>
> >I compiled the kernel per instructions located at the Red Hat website
> >(Im running Red Hat 5.2) http://www.redhat.com/errata/ and followed
> >their directions to the T. Maybe they added some steps that werent
> >necessary to my system? This is the first kernel that I have ever compiled
> >and Im wondering why I didnt get the same errors on my home machine.
>
> Your first mistake was trusting Redhat's instructions. Don't
> get me wrong, they do lots to help the linux community, but
> a much better bet would be looking at the comments and readmes
> in the kernel source.
>
> I love the loopback device, and always build it in. Kinda funny,
> but Dec included it (and mkisofs) in their latest True64Unix
> release. Linux is trickling down to other Unices.
>
> Just select it in a kernel rebuild and all will work fine.
>
> --
> Dave Blake
> [EMAIL PROTECTED]
I finally got the damn thing to compile and install! I didnt add the loopback
but since I dont have SCSI on my machine I didnt bother to run mkinitrd.
Compiled and installed like a charm this time! Even booted without error,
and as far as I can tell everything seems to be ok.
See if I ever listen to Red Hat anymore. :)
--
Aaron Faby
[EMAIL PROTECTED]
System Administrator/Technical Support
Yourlink, Inc.
------------------------------
From: BL <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.slackware,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?)
Date: 27 Feb 1999 02:18:36 GMT
In comp.os.linux.development.system GBP <[EMAIL PROTECTED]> wrote:
: Yeah point well taken. But is it true that overclocking can result in
: system instability? When netscape crashes how am i going to know it was
: a bug and not my CPU doing and instruction wrong or something? When
: people say instability what exactly do they mean? do these machines
: freeze?
easy to tell - run your system to-spec for a while to find out which bugs are
os- or app-related. then overclock and test again. the delta in bugs are
your local system.
------------------------------
From: "David A. Frantz" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: LINUX MERCED
Date: Fri, 26 Feb 1999 20:27:28 -0500
Christopher B. Browne wrote in message ...
>On 25 Feb 1999 22:44:48 GMT, bill davidsen <[EMAIL PROTECTED]> posted:
>>In article <[EMAIL PROTECTED]>,
>>Christopher B. Browne <[EMAIL PROTECTED]> wrote:
>>
>>| If the hardware is ridiculously expensive, as is entirely typical for
>>| latest generations of Intel hardware, then who will want to "swarm en
>>| masse" to it?
>>|
>>| Note the *lack* of swarming of Linux hackers to Xeon.
>>
>>What lack? Linus has a quad system, or so he posts.
>
>"Swarming" involves there being *huge* quantities of folks buying
>them.
>
>Linus may have one;I was not aware of that.
>
>There seems to be a whole lot more people "swarming" around Celeron
>300A and AMD K6-2-3D boxes that cost thousands of dollars less.
This is certainly the case. A well engineered SMP XEON machine can be as
costly as any UNIX workstation, for many of us It can not be justified.
For the average user a Dual processor P2 would be fine, but even at that few
swarm to them. Someone with a true need for 4 XEON processors should be
opened minded and look at the alternatives to i386.
>
>--
>Those who do not understand Unix are condemned to reinvent it, poorly.
>-- Henry Spencer <http://www.hex.net/~cbbrowne/lsf.html>
>[EMAIL PROTECTED] - "What have you contributed to free software today?..."
------------------------------
From: [EMAIL PROTECTED] (Christopher B. Browne)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: "RPM's harmful to Linux" harmful to Linux
Reply-To: [EMAIL PROTECTED]
Date: Thu, 25 Feb 1999 14:34:04 GMT
On 25 Feb 1999 06:08:49 GMT, Navindra Umanee <[EMAIL PROTECTED]>
posted:
>Christopher Browne <[EMAIL PROTECTED]> wrote:
>> Which "tarball format" do you suggest be used?
>>
>> a) Tarballs of pristine sources that must then be manually patched so
>> as to put them in the right places?
>
>Check. (debian basically does this)
>
>> c) Tarballs of the combination of sources and necessary patches and
>> other metadata?
>
>Do you have any argument against this or are you just listing the
>options? package.lnx.tar.gz could consist of:
I was trying to list all the options I could think of for completeness
sake, and to indicate that "You should use tarballs" is, without some
further context on what structure might be inside them, merely a
ludicrous screed against RPM.
--
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer <http://www.hex.net/~cbbrowne/lsf.html>
[EMAIL PROTECTED] - "What have you contributed to free software today?..."
------------------------------
From: Julian Robert Yon <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux.slackware,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Overclocking (was: Re: K6-2 and Linux, Are there any Bug?)
Date: Thu, 25 Feb 1999 17:18:09 +0000
BL wrote:
> you're partially correct.
>
> if you overclock by choosing nonstandard bus speeds (75, 83, 102, etc) then
> you are running pci at nonstandard data xfer speeds. but the intrinsic
> function of the board (unless they cut MAJOR corners in the design) derives
> timing locally, from a local clock source. ie, if you overclock, you should
> NOT be getting a "12megabit ethernet system", etc ;-) ;-)
I tried to overclock my 300A using a 83MHz bus and my i740 gfx card
didn't like it. It was, however, happy at 66 and 75MHz, and is labelled
as running at 100. This looks like a deliberate act on the part of Intel
(since some competitors' cpus run at 83), but maybe I'm just being
paranoid.
Of course, I'm having a few problems getting the card to work with linux
anyway, but that's another story...
Julian
~~~~~~~~~~~~~~~~~~~~
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: Todd Knarr <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: "RPM's harmful to Linux" harmful to Linux
Date: 27 Feb 1999 01:40:48 GMT
In comp.os.linux.development.system Villy Kruse <[EMAIL PROTECTED]>
wrote:
> But they don't. It appears to be stupid to re-download the entire
> source as part of a src.rpm if the only things changed are the patch
> files and the spec file. That would make a tremendously difference in
Laziness on the part of the packagers? It's simpler to just add the patch
files and let "rpm -ba" rebuild the complete source package than it is to
make a new spec file with the appropriate Nosource: and Nopatch: entries
in it. There's also no widely-accepted convention for what patches need
to be in the .nosrc.rpm, nor for how to build the base .src.rpm to
accomodate the later additions.
The complete .src.rpm has one advantage: you only need to download the
latest one if you don't already have it. The .nosrc.rpm requires you to
locate the base .src.rpm that goes along with it, either on your system
or an FTP site, and download and/or install it before installing the
.nosrc.rpm. No problem for me, but then I live by diff and patch. Big
problem for a lot of inexperienced people, though.
--
All I want out of the Universe is 10 minutes with the source code and
a quick recompile.
-- unknown
------------------------------
** 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: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
