Subject: Linux-Development Digest #866
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:     Tue, 28 Jun 94 12:13:10 EDT

Linux-Development Digest #866, Volume #1         Tue, 28 Jun 94 12:13:10 EDT

Contents:
  System lock ups: NCR 53c810 driver problem? (Lutz Pressler)
  Re: TCP socket help (John F. Davis)
  Re: Quirky idea: Remote V (Brian Stoler)
  #9GXE 64 X server! (Paul Quinn)
  Re: computer science (Wayne Schlitt)
  Re: computer science (Steven Buytaert)
  Re: tcsh bug: more information (Mika Liljeberg)
  Re: Vesa Local Bus IDE support (Bradley Schatz)
  Re: Disk-compression for Linux (H. Peter Anvin)
  Re: Major device number clash (iCS) (H. Peter Anvin)

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

From: Lutz.Pressler@Unix.Med-Stat.GWDG.DE (Lutz Pressler)
Subject: System lock ups: NCR 53c810 driver problem?
Reply-To: Lutz Pressler <Lutz.Pressler@Med-Stat.GWDG.DE>
Date: Tue, 28 Jun 1994 11:50:59 GMT

Hello,

first of all many thanks to Drew Eckhardt for writing the NCR PCI driver.
I'm afraid I have to report some kind of (disturbing) bug though:
with the NCR chip enabled and that driver, the system sometimes (quite
often :() locks up totally. That does not happen with an Adaptec 1542B.

Details:

Hardware:  DELL Omniplex 4100 system
           - i486DX4-100, 256 kB cache
           - PCI mainboard with NCR 53c810
           - 32 MB RAM
           UltraVision (?) graphics (Mach64 (or 32?), 2 MB VRAM
           3com 3c509 Ethernet card
           DEC DSP3107LS  1 GB SCSI disk

Software/Installation:

Partition 1, 260 MB made with DOS fdisk and NCR controller.
DOS/MS-Windows and local software installed.

Linux installed with EISA Adaptec 1542B (NCR disabled)
  [it's not possible to boot DOS (C:) when using the Adaptec 
  (No operating system present..); DOS 6.2 fdisk shows 1 MB more total
  capacity with NCR then with Adaptec]:

/dev/sda2: 100 MB ext2   (/)
/dev/sda3: 201 MB ext2   (/usr)
/dev/sda4 extended
/dev/sda5: 201 MB ext2   (/usr/local)
/dev/sda6:  65 MB swap
/dev/sda7: 193 MB ext2   unused

No problems (of that kind) with this system (Slackware-1.2-based,
different kernel versions) when using Adaptec controller.


Included ncr_src.2.tar.gz into the kernel source tree and made new
kernel (1.1.19 first, then smaller one, 1.1.21, 1.1.22.. not much of
a difference concerning lock ups). 

Kernel boot messages of 1.1.22 (dmesg output) follow:
=====
bios32_init : BIOS32 Service Directory structure at 0xffe80
bios32_init : BIOS32 Service Directory entry at 0xffe90
pcibios_init : PCI BIOS revision 2.00 entry at 0xfcae1
Console: colour EGA+ 80x25, 8 virtual consoles
Serial driver version 4.00 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
lp_init: lp1 exists, using polling driver
PS/2 auxiliary pointing device detected -- driver installed.
Calibrating delay loop.. ok - 50.08 BogoMips
scsi1 : at PCI bus 0, device 15,  function 0
scsi1 : NCR53c810 at memory 0x3effff00, io 0xff00, irq 15
scsi0 : using io mapped access
scsi0 : using initiator ID 7
scsi0 ; burst length 8
scsi0 : using 40MHz SCSI clock
scsi0 : m_to_n = 0x90, n_to_m = 0xa0, n_to_n = 0xb0
scsi0 : NCR code relocated to 0x1b7fac
scsi0 : testing
scsi0 : tests complete.
scsi0 : NCR53c{7,8}xx
scsi : 1 hosts.
  Vendor: DEC       Model: DSP3107LS         Rev: 441C
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, id 0, lun 0
scsi : detected 1 SCSI disk total.
scsi : 32 buffers total 16388 bytes
Memory: 31620k/32768k available (532k kernel code, 384k reserved, 232k data)
This processor honours the WP bit even when in supervisor mode. Good.
Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
floppy: FDC version 0x90
Swansea University Computer Society NET3.016
NET3 TCP/IP protocols stack v016
IP Protocols: ICMP, UDP, TCP
eth0: 3c509 at 0x300 tag 1, BNC port, address  00 60 8c cd af fc, IRQ 5.
3c509.c:pl15k 3/5/94 becker@super.org
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Linux version 1.1.22 (root@cortex) #6 Sat Jun 25 14:08:09 MET DST 1994
Partition check:
  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 66552k swap-space
module `iBCS' (17 pages @ 0x02820000) created
initializing module `iBCS', 68208 (0x10a70) bytes
  init entry @ 0x02822144, cleanup entry @ 0x028221b4
iBCS: socksys registered on character major 30
=====


Symptoms:

When working under X (haven't able to reproduce it without someone using
X on console, it's started anyway (xdm), sometimes the system totally locks
up: no keyboard reaction (incl. alt-cntrl-del) , no login via IP,
mouse cursor is garbage.
The only "cure" is pressing reset button or using power switch, hoping that
the file systems are usable afterwards...
That (mostly) happens when starting a program, sometimes that's the first
xterm to start, sometimes it's under load >5 (gcc compiling kernel, 2 emacs
running haoin, gnuchess playing machine-machine, etc... that was a test..)
Because of the 32 MB RAM even in the latter situation swapspace (almost)
wasn't touched.

Things I tried to make it work better...:

- different kernel versions 
- set jumper marked "SYN" on disk; I don't know if this is "synchronous mode
  negatiation on/off", we don't have documentation on the DSP3107LS, I'm
  afraid .. but it had no effect anyway
- disable video BIOS shadowing/caching
 
... all with no effect.

The only setting I wasn't able to hang the system yet was with processor
cache disabled. Then even load 7 was no problem, but of course the whole
thing was a couple a times slower (factor 9 for "BogoMips"), so that's no
solution.



The follwing SCSI related entries I found in syslog (I think it was a
1.1.19 kernel then and the SYN drive-jumper was set, but I'm not sure):

=====
Jun 25 21:21:55 cortex kernel: scsi0 : impossible phase mismatch in data
transfer.
Jun 25 21:21:56 cortex kernel: scsi0 : DANGER : abort_connected() called 
Jun 25 21:21:56 cortex kernel: scsi : aborting command due to timeout :
pid 8712, scsi0, id 0, lun 0 Write (6) 0c 48 1a 02 00
Jun 25 21:21:56 cortex kernel: 
Jun 25 21:21:56 cortex kernel: scsi0 : DANGER : command in running list,
can't abort.
Jun 25 21:21:56 cortex kernel: scsi : aborting command due to timeout :
pid 8712, scsi0, id 0, lun 0 Write (6) 0c 48 1a 02 00
Jun 25 21:21:56 cortex kernel: 
Jun 25 21:21:56 cortex kernel: scsi0 : DANGER : command in running list,
can't abort.
Jun 25 21:21:56 cortex kernel: SCSI host 0 abort() timed out - reseting
Jun 25 21:21:56 cortex kernel: scsi0 : DANGER : NCR53c7xx_reset is NOP
Jun 25 21:21:56 cortex kernel: Unable to reset scsi host 0 - probably a
SCSI bus hang.
Jun 25 21:21:56 cortex kernel: scsi0 : target 0 lun 0 unexpected disconnect
Jun 25 21:21:56 cortex kernel: SCSI disk error : host 0 id 0 lun 0 return
code = 25040000
Jun 25 21:21:56 cortex kernel: scsidisk I/O error: dev 0803, sector 65562
Jun 25 21:21:56 cortex kernel: scsi0 : target 0 lun 0 unexpected disconnect
Jun 25 21:21:56 cortex kernel: scsi : aborting command due to timeout :
pid 8713
, scsi0, id 0, lun 0 Write (6) 0c 48 1e 02 00
Jun 25 21:21:56 cortex kernel: 
Jun 25 21:21:57 cortex kernel: scsi0 : DANGER : command in running list,
can't abort.
Jun 25 21:21:57 cortex kernel: SCSI disk error : host 0 id 0 lun 0 return
code = 28000000
Jun 25 21:21:57 cortex kernel: extra data not valid Current error sd803:
sense key Unit Attention
Jun 25 21:21:57 cortex kernel: scsidisk I/O error: dev 0803, sector 65566
=====

That was the only time syslog entries appeared.



I haven't been able to use LILO (with disktab) either.

dparam 0x80 on DOS yields:  62 33 1022

Output of linux fdisk /dev/sda, after setting sectors, heads and cylinders
to values above, "print the partion table":

=====
Disk /dev/sda: 33 heads, 62 sectors, 1022 cylinders
Units = cylinders of 2046 * 512 bytes

   Device Boot  Begin   Start     End  Blocks   Id  System
/dev/sda1   *       1       1     261  266972    6  DOS 16-bit >=32M
/dev/sda2         262     262     362  102661   83  Linux native
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(260, 47, 23) logical=(261, 0, 1)
Partition 2 has different physical/logical endings:
     phys=(360, 63, 32) logical=(361, 11, 40)
Partition 2 does not start on cylinder boundary:
     phys=(260, 47, 23) should be (260, 0, 1)
Partition 2 does not end on cylinder boundary:
     phys=(360, 63, 32) should be (360, 32, 62)
/dev/sda3         362     362     563  205824   83  Linux native
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(361, 0, 1) logical=(361, 11, 41)
Partition 3 has different physical/logical endings:
     phys=(561, 63, 32) logical=(562, 18, 8)
Partition 3 does not end on cylinder boundary:
     phys=(561, 63, 32) should be (561, 32, 62)
/dev/sda4         563     563    1022  470016    5  Extended
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(562, 0, 1) logical=(562, 18, 9)
Partition 4 has different physical/logical endings:
     phys=(1020, 63, 32) logical=(1021, 32, 58)
Partition 4 does not end on cylinder boundary:
     phys=(1020, 63, 32) should be (1020, 32, 62)
/dev/sda5         563     563     764  205823+  83  Linux native
/dev/sda6         764     764     829   66559+  82  Linux swap
/dev/sda7         829     829    1022  197631+  83  Linux native
=====


/etc/disktab
=====
0x800   0x80    62      11      1022    0
0x801   0x80    62      11      1022    0
0x802   0x80    62      11      1022    0
0x803   0x80    62      11      1022    0
0x804   0x80    62      11      1022    0
0x805   0x80    62      11      1022    0
0x806   0x80    62      11      1022    0
0x807   0x80    62      11      1022    0
=====

Output of lilo (inst. on  /dev/fd0):
Added Linux
Device 0x0800: Invalid partition table, 2nd entry
  3D address:     23/47/260 (180256)
  Linear address: 1/0/783 (534006)


Anyway, that's not as important (maybe disktab isn't correct? I'm not
sure). 

Any idea if this is a bug in the NCR driver? Maybe the DX4-100 system
is "too fast"? Or should I install from scratch, as the partition table
doesn't seem to be "perfect" at all.. Btw, the system did NOT hang when
I backed up all linux filesystems via NFS yesterday, but when I came back
and logged in under X ...

Thank you very much in advance for any solutions/patches/hints,...
we have 10 of these systems and HAVE to use them quite soon under Linux, too.
We don't have 9 spare 1542s though or want to buy them. To be exact,
the other 9 have 350 (approx) MB Maxtor disks. I haven't installed Linux on
these at all, and won't be able to do that before the Heidelberg conference
(Thursday). 

If anyone of you is interested in talking to me about these problems
(or anything :)) personally in Heidelberg (maybe even Drew? :)), I probably
will read e-mail before leaving Thursday around 5 am. 


Have a nice day,

   Lutz

IMPORTANT: Please reply by e-mail (or Cc:), since our news feed is more or
less unusable at the moment (I hope that will change next week..). I'll post
a summary if appropriate. Thanks.



--
Abteilung Medizinische Statistik            Lutz Pre"sler
Universit"at G"ottingen                     privat:
Humboldtallee 32                            Kreuzburger Str. 11
D-37073 G"ottingen                          D-37085 G"ottingen
Tel.: (+49[0]551) 39-4956   FAX: -4995      Tel.: (+49[0]551) 7700178
----> E-mail: Lutz.Pressler@Med-Stat.GWDG.DE / lpressl1@GWDG.DE <----

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

From: davis@clark.net (John F. Davis)
Subject: Re: TCP socket help
Date: 28 Jun 1994 12:57:16 GMT

I've seen the light.  Thanks for the help.

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

From: sto2@netaxs.com (Brian Stoler)
Subject: Re: Quirky idea: Remote V
Date: 28 Jun 1994 12:49:58 GMT

John Will (john.will@dscmail.com) wrote:
: BR>I meant for it to support multiple VC's. In fact if it worked properly
: BR>it would look and act exactly like the Linux console.

: Sounds like SCREEN...

Try doing anything color in screen, much less GRAPHICS.


--

- Brian Stoler
- sto2@netaxs.com

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

Crossposted-To: comp.os.linux.misc
From: p_quinn@ECE.Concordia.CA (Paul Quinn)
Subject: #9GXE 64 X server!
Date: Tue, 28 Jun 1994 01:28:32 GMT


Is there any possibility of getting an X server for the #9GXE 64?  Can you
use the S3 server with this card?  Can you use the SVGA server with this card?

Is anyone about to start developing a server for it?


--
________
Paul Quinn
p_quinn@ece.concordia.ca
Computer Science: Systems Architecture
Concordia University
Montreal, QC, CANADA
========

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

From: wayne@backbone.uucp (Wayne Schlitt)
Subject: Re: computer science
Date: Tue, 28 Jun 1994 14:02:53 GMT
Reply-To: wayne@cse.unl.edu

In article <1994Jun28.025344.29840@rosevax.rosemount.com> grante@reddwarf.rosemount.com (Grant Edwards) writes:
> : I would like to know what some of the Linux developers think of their
> : jobs.  I am considering switching my major from electrical engineering
> : to computer science.  What would be important to learn?  What might I
> : end up doing?
> 
> If you want to do embedded or real-time software developement stick
> with EE.  [ ... ]
> 
>               Most of it is written by people with engineering
> degrees.  At all of the companies that I'm familiar with, you are
> better of with an engineering degree than with a CS degree.
>
> The people with CS degrees are "programmers" or "systems analysts" and
> are on the same pay structure as the drafters, technicians, and others
> without 4 year degrees.  The people who write software but have
> engineering degrees are "Design Engineers" and are on the engineering
> pay structure.


I think you haven't seen all companies.  Your background is probably
selecting which companies you see.


If you go to work for a company that was founded by EEs, and has only
gotten into programming in the last 5-10 years (like many of the jobs
you listed), then being an EE is probably a big advantage.

But, if you go to work for a company that was founded by CS people,
and has only gotten into hardware in the last 5-10 years, then being a
CS grad is probably a big advantage.

The same thing can be said for graduating from the right school.
(Stanford vs UCB vs MIT, etc)

In large companies, it depends on the department, but often they are
well mixed and your abilities will count more than having the
appropriate label.  Small companies who need to bring in new knowledge
may go to the opposite extreme.  That is, if the are an EE shop, the
will only look for CS people and vis versa if they think that they
really need more knowledge in the opposite area.  


The 'new grad pay scale' reports that I have seen show EEs getting
slightly more money than CS grads, but not that much.  Maybe a 5%
difference at tops.



Some schools are now offering "Computer Engineering" degrees that are
kind of a cross between CS and EE.  You get less of the highly
specialized database, image processing, compiler theory type CS
courses, and you get less of the power supply, analog, antenna theory
type EE classes.  If you are really interested in mixing hardware and
software, this is probably the way to go.  (These schools say that
grads with CE degrees have a high pay than either CS or EEs, but this
might be biased :-)


-wayne


-- 
Our reasoning goes something like this:  "If I want it, I need it.  If
I need it, it's my right.  If it's my right, someone should give it to
me.  Or else I'll sue."     -- Newsweek June 27, 1994

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

From: buytaert@imec.be (Steven Buytaert)
Subject: Re: computer science
Date: Tue, 28 Jun 1994 13:12:33 GMT

Bob Phillips (bobp@syl.nj.nec.com) wrote:
: In article <1994Jun28.025344.29840@rosevax.rosemount.com>, grante@reddwarf.rosemount.com (Grant Edwards) writes:
: |> At all of the companies that I'm familiar with, you are
: |> better of with an engineering degree than with a CS degree.  
[ Some things of Bob appreciated and snipped ... ]

: But, his perspective provides a valuable lesson:  if you have a software degree,
: you are better off working for a company that appreciates software.  
: Companies that manufacture chips spend so much on the bloody things that 
: they think the only thing the software types can do is screw things up by
: writing slow code. :^) :^) :^) :^) :^) :^) :^) :^)

 Hi Bob,

 I appreciate the smileys, but, I'm one of the guys that makes chips
 (and that writes software too for another company, see my previous
 follow up). But, in fact, when I use the software for making chips
 (simulator, poly pusher, extraction, DRC, ERC, LVS, synthesizer, ...)
 speed isn't my biggest gripe, it's *obvious flaws* in the software
 itself. Mostly in the interfacing between the SW components. I do
 know that the frameworks are a huge system, but I have the general
 feeling that the people that have analysed the system requirements
 didn't do a 100% good job. It's my feeling that they didn't listen
 to us designers long enough...

 Anyway, maybe this thread should move to comp.lsi.cad ?

 Stef

--
Steven Buytaert 

WORK buytaert@imec.be
HOME buytaert@innet.be

        'Imagination is more important than knowledge.'
                        (A. Einstein)

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

From: liljeber@karhu.Helsinki.FI (Mika Liljeberg)
Subject: Re: tcsh bug: more information
Date: 28 Jun 1994 14:06:13 GMT

In article <2unqdj$cf9@harbinger.cc.monash.edu.au> shcun1@aurora.cc.monash.edu.au (Stuart Cunningham) wrote:
>   I've now realised that there is an important difference between csh
> and tcsh from the point of view of someone who writes alot of scripts.
> Under csh the single quote chracter ' quotes all characters, including
> the backslash \, (except for ! which must be escaped with a \).  Under
> tcsh the single quote does not quote the backslash - an important
> difference when you have many scripts written for the csh which won't
> run under the tcsh. I thought the tcsh was designed to support all csh
> scripts.

In truth, there are probably some subtle differences between csh and
tcsh that crop up with complex enough scripts. However, what you're
observing here is not one of those differences. If you write a lot of
scripts, you should be aware that the surrounding operating system
introduces a lot of "features" which have to be taken into account.
One of those features is that the echo command (a builtin in tcsh, but
not in csh, by the way) behaves differently in SYSV and BSD
environments. The SYSV-version supports a bunch of nice
escape-commands for controlling the output. The BSD version on the
other hand understands none of these, but instead has a command line
option -n that suppresses the trailing newline.

Linux, being a kind of a hybrid, comes with GNU echo and tcsh (with a
builtin echo), both of which support both the BSD and SYSV styles.
With tcsh you control the behaviour with the shell variable
echo_style:

set echo_style=bsd
set echo_style=sysv
set echo_style=both     # This is the default under Linux

With GNU echo you can try the following:

echo -e '\a'    # Output BEL-character
echo -E '\a'    # Output \a

The default depends on how it's been compiled.

>   Anyway, putting the difference between csh and tcsh aside, I still say
> there is a bug in tcsh. I believe that it should not be possible to put
> an ASCII zero (the character 0x00) in a file by the following echo
> command:
>  echo '\' > test

You're right. Echo shouldn't produce a NUL-character in this case.
Check out the patch I posted in a previous article.

> (under csh this puts a single quote in the file)
> under tcsh I would expect a Unmatched ' error, but no error is reported
> and the 0x00 character in put in the file.  This needs to be fixed!
> 
>   Stuart Cunningham

        Mika
--
Mika Liljeberg                  Email:  liljeber@cs.Helsinki.FI
Helsinki University                     Mika.Liljeberg@Helsinki.FI
Dept. of Computer Science

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

From: cs323423@dingo.cc.uq.oz.au (Bradley Schatz)
Subject: Re: Vesa Local Bus IDE support
Date: 29 Jun 1994 00:22:39 +1000

john@cs.vu.nl (John Romein) writes:

>Friday I bought a new Vesa Local Bus IDE controller to replace my old
>ISA bus controller (which ran at 16.5 MHz)  With the supplied VLB driver
>installed under DOS, my WD-340 caviar is able to read at 3900 Kb/s, instead
>of merely 2400 Kb/s with the ISA-bus controller.
>Under Linux, I see absolutely no difference.

>that there is no Vesa Local Bus support for IDE harddisks ?
>If not, is it easy to do so ?
>BTW, I use the IDE performance enhancement patches.

>John Romein

John,

It depends what make of local bus I/O card you are using. I have patches 
for the Promise variety of cards if you need...

Brad


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

From: hpa@solo.eecs.nwu.edu (H. Peter Anvin)
Subject: Re: Disk-compression for Linux
Reply-To: hpa@nwu.edu (H. Peter Anvin)
Date: Mon, 27 Jun 1994 18:19:53 GMT

Followup to:  <Crwtz8.Br1@pe1chl.ampr.org>
By author:    pe1chl@rabo.nl
In newsgroup: comp.os.linux.development
> 
> >3rd point:
> >     Would it be possible to modify /bin/ld to produce a
> >self-uncompressing executable?  (Of course, I know it's possible --
> >with computers, everything is virtually possible! :-))  Perhaps
> >someone who is looking for a summer project my consider this.  This
> >could be an alternative to the reportedly unreliable gzexe approach.
> 
> Please note that Linux uses demand paging.  That means an executable
> is not first read in memory where it can be conveniently uncompressed,
> like under some other operating system.
> The gzexe approach first uncompresses the executable into file from where
> it can be paged in.
> (I don't know about unreliability with this)
> 

A compressed executable under Linux should of course be uncompressed
into *swap*, not into a file.  This might require kernel support,
however.

        /hpa

-- 
INTERNET: hpa@nwu.edu               FINGER/TALK: hpa@ahab.eecs.nwu.edu
IBM MAIL: I0050052 at IBMMAIL       HAM RADIO:   N9ITP or SM4TKN
FIDONET:  1:115/511 or 1:115/512    STORMNET:    181:294/101
#include <stdquote.h>

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

From: hpa@solo.eecs.nwu.edu (H. Peter Anvin)
Subject: Re: Major device number clash (iCS)
Reply-To: hpa@nwu.edu (H. Peter Anvin)
Date: Mon, 27 Jun 1994 18:24:23 GMT

Followup to:  <1994Jun24.121813.28051@kf8nh.wariat.org>
By author:    bsa@kf8nh.wariat.org (Brandon S. Allbery)
In newsgroup: comp.os.linux.development

> 
> Huh?  Then why is it distributed with such a low limit?  Seems
> pretty silly to me...
> 

No need to bump the major device number count until you really need
it.  Remember, you have to have drivers that *use* those numbers
installed, and since for most people the drivers are distributed with
the kernel...

        /hpa
-- 
INTERNET: hpa@nwu.edu               FINGER/TALK: hpa@ahab.eecs.nwu.edu
IBM MAIL: I0050052 at IBMMAIL       HAM RADIO:   N9ITP or SM4TKN
FIDONET:  1:115/511 or 1:115/512    STORMNET:    181:294/101
"Conserve energy"... like I have a choice!!  -- David Guidry

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


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