Subject: Linux-Development Digest #321
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Mon, 17 Oct 94 00:13:16 EDT

Linux-Development Digest #321, Volume #2         Mon, 17 Oct 94 00:13:16 EDT

Contents:
  Problems compiling 1.1.54 (Huw Davies)
  Re: Telnet & ftp freeze! - AND UNFREEZE KLUDGE (For me to know.)
  Re: BUS MOUSE KERNEL DRIVER BUG (Hal N. Brooks)
  Re: How to add more space to Linux partition? (Jon Leonard)
  Re: NFS over TERM? (Patrick Reijnen)
  Re: Any plans for 'trace'? (Thomas Koenig)
  Re: We a FAQ: Linux vs. *BSD!!! (Jesus Monroy Jr)
  Re: [Q] What does MTU do in SLIP? (John Richardson)
  Re: NE2000+ and AHA1542CF problems (Darius Quenum)
  Re: We a FAQ: Linux vs. *BSD!!! (Jesus Monroy Jr)
  Magic mumber for a new fs (Ben Frank)
  IS anyone reading users' complaints? (Breakdown)
  Re: IS anyone reading users' complaints? (Bjorn Ekwall)
  Re: ext2fs vs. Berkeley FFS (Matthew Dillon)
  Kernel 1.1.53 - no BOOM (Mark A. Horton KA4YBR)
  Re: IS anyone reading users' complaints? (Matthew Dillon)
  Re: A badly missed feature in gcc (Erik Corry)
  SCSI detect.... (just me)

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

Crossposted-To: aus.computers.linux,latrobe.linux
Subject: Problems compiling 1.1.54
From: [email-masked] (Huw Davies)
Date: Mon, 17 Oct 1994 00:23:33 GMT

I've just applied the 1.1.54 patches to a (working) copy of 1.1.53, ran
make config choosing the usual group of options (although I added ISO9660
support which I must have accidentally turned off building 1.1.53) and
then ran make zImage. Sadly I get compile time errors (see below). I've
tried rebuilding the compiler with and without elf support but the errors
remain.

Given that noone else has complained, I assume that it's a problem with
my setup (most likely, I need a later version of something). Any pointers
appreciated.

Here is the section I'm having difficulties with....

make[2]: Entering directory `/usr/src/linux/fs'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-f
rame-pointer -pipe -m486 -DMODULE -c binfmt_elf.c
binfmt_elf.c:36: warning: function declaration isn't a prototype
binfmt_elf.c:825: redefinition of `padzero'
binfmt_elf.c:61: `padzero' previously defined here
binfmt_elf.c:841: redefinition of `create_elf_tables'
binfmt_elf.c:77: `create_elf_tables' previously defined here
binfmt_elf.c: In function `create_elf_tables':
binfmt_elf.c:857: structure has no member named `stk_vma'
binfmt_elf.c: At top level:
binfmt_elf.c:912: redefinition of `load_elf_interp'
binfmt_elf.c:159: `load_elf_interp' previously defined here
binfmt_elf.c:1000: redefinition of `load_aout_interp'
binfmt_elf.c:247: `load_aout_interp' previously defined here
binfmt_elf.c:1046: redefinition of `load_elf_binary'
binfmt_elf.c:295: `load_elf_binary' previously defined here
binfmt_elf.c: In function `load_elf_binary':
binfmt_elf.c:1291: structure has no member named `elf_executable'
binfmt_elf.c:1292: structure has no member named `executable'
{standard input}: Assembler messages:
{standard input}:1674: Fatal error:Symbol _padzero already defined.
binfmt_elf.c:1334: output pipe has been closed
gcc: Internal compiler error: program cc1 got fatal signal 13
make[2]: *** [binfmt_elf.o] Error 1
make[2]: Leaving directory `/usr/src/linux/fs'
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/src/linux/fs'
make: *** [linuxsubdirs] Error 1
kerberos:/usr/src/linux#

--
  Huw Davies           | [email-masked]
  Computing Services   | Phone: +61 3 479 1500   Fax: +61 3 479 1999
  La Trobe University  | I own an Alfa to keep me poor in a monetary
  Melbourne Australia  | sense, but rich in so many other ways

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

From: [email-masked] (For me to know.)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Re: Telnet & ftp freeze! - AND UNFREEZE KLUDGE
Date: 16 Oct 1994 04:35:02 -0600

In article <[email-masked]>,
Donald Becker <[email-masked]> wrote:
>In article <[email-masked]>,
>Steve Davies <[email-masked]> wrote:
>>The fix is to kill inetd and start a new one.

Agreed. This does seem to always fix the problem but is a very messy way 
of doing things. This is not a solution when it has to be done five to 
ten times in one day.

>>
>>The cause?  I have found that the problem is caused by people connecting
>>with SLIP and using the *wrong IP address* on their end.  In other words
>>they have configured their IP stack with an address different from that
>>in the diphosts file.

This is the cause on your computer but what about other people. I know 
that many people have the most problems with SLIP but it is definately 
not the only place an error occurs.

>This would explain a lot!
>The problem is unlikely to happen with other connection types.
>Most people that could track this problem down have correctly configured
>connections and never see the problem.

This may be the cause on your machine but it certainly is not the problem 
on mine. As has been found by many other people it is not even a problem 
in the inetd.

/-------------------------------+---------------------------------------------\
| Andrew Radke                  | Western Halls                               |
|   [email-masked]  | James Cook University                       |
|   [email-masked]     | Australia, 4811                             |
+-------------------------------+---------------------------------------------+
| 'Indeed, it is possible that the black hole could emit a television set or  |
| the works of Proust in 10 leather-bound volumes . . .' - Stephen W. Hawking |
\-----------------------------------------------------------------------------/

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

From: [email-masked] (Hal N. Brooks)
Subject: Re: BUS MOUSE KERNEL DRIVER BUG
Date: 16 Oct 1994 15:31:28 GMT
Reply-To: [email-masked] (Hal N. Brooks)

In article <[email-masked]> [email-masked] (Bob Wilson) writes:
>Possible BUG with BUSMOUSE Code ********************************************
>
>Linux Kernel Revision : 1.1.50
>Mouse in Question     : Logitech Bus Model No. P7-3F
>                        (Old Box like, 3 button Style)
>Mouse IRQ             : 5

For comparison, I don't seem to have much of a problem.

Linux Kernel Revision : 1.1.54
Mouse in Question     : MS brand busmouse (circa 1988, aka InPort)
Mouse IRQ             : 5

>Now watch procinfo    :
[snip]
>
>irq  1:      4651  irq  5:   9169730  irq  9:         0  irq 13:         0
[snip]
>
>**NOTICE IRQ 5** (Allowing a minute or two to pass) Here it is again :
>
[snip]
>
>irq  1:      5084  irq  5:  11187988  irq  9:         0  irq 13:         0
[snip]
>
>**NOTICE SHARP INCREASE!!**
>
[snip]
>
>         In general, I don't notice any mouse jumpy-ness in either
>         X Windows, or under Selection.  However, under selection,
>         I do notice severe problems controlling the mouse when I
>         am catting to /dev/dsp1.  It will ignore half of my
>         requests.

Do you take care to disable selection when using X11?  I was under
the impression that selection can't be enabled when using X11 and
a busmouse.  You did say X11 "or" selection, so I guess you're
aware of this problem.

At any rate, I don't compile selection into my kernels, since I'm
always in X11 anyway.

Also, I'm not seeing the poor performance that you seem to be experiencing.

>         Procinfo does not show any increase as long as nothing is
>         using the mouse.  ie, X isn't running, or selection isn't
>         running.  But the second they startup whether or not I move
>         the mouse, it climbs *fast*.

I don't have procinfo here, but I did

  cat /proc/interrupts; sleep 120; cat /proc/interrupts

and got:

 5:  1301090   MS Busmouse

 5:  1304723   MS Busmouse

while running X11.  I don't understand why any interrupts are necessary
as long as the mouse doesn't move, but this is considerably less
troubling than what you saw.  This is with a 386-33.

[snip]

======================================================================
 Hal N. Brooks     Voice: (706) 546-7792     Internet: [email-masked]
======================================================================

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

From: [email-masked] (Jon Leonard)
Subject: Re: How to add more space to Linux partition?
Date: Wed, 12 Oct 94 05:57:27 +0200

In <[email-masked]> [email-masked] (Philip Siming Zhan) writes:
>As the title, how to add more disk space to Linux partition?
>I have 200 MB for Linux mounted from /dev/hdb2. Now I need more
>space for Linux.

Anybody working on LVM for Linux?

-- 
========================================================================
  Jon Leonard       |
                    | Rock music doesn't have to be good to be good.
  [email-masked]  |
========================================================================

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

From: [email-masked] (Patrick Reijnen)
Subject: Re: NFS over TERM?
Date: Sun, 16 Oct 1994 10:21:50 GMT

In <[email-masked]> [email-masked] (Joel M. Hoffman) writes:

>I've asked this before, but I got no response.  I'll try one more time:

>Is there any way to remote NFS mount a directory via term?

Nope, at this moment this is not possible. Problem is the NFS server is only
 supposed to accept requests if the socket requesting the connection is bound
 to a port below 1024.

>-Joel
>([email-masked])

Patrick REijnen

--
************************* Patrick Reijnen *************************
* Department of Computer Science, Catholic University of Nijmegen * 
* Email:  patrickr@{sci,cs}.kun.nl                                *
* WWW:    http://{atlas,zeus}.cs.kun.nl:4080/homepage.html        *

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

From: [email-masked] (Thomas Koenig)
Subject: Re: Any plans for 'trace'?
Date: 16 Oct 1994 10:54:29 GMT
Reply-To: [email-masked]

Justin Beech ([email-masked]) wrote in comp.os.linux.development,
        article <[email-masked]>:

>Anybody else miss trace?

I don't, I use 'strace', which does the very same thing ;-)

(And yes, I'd miss it very much, if it wasn't there).
-- 
Thomas Koenig, [email-masked], [email-masked].
The joy of engineering is to find a straight line on a double
logarithmic diagram.

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

Crossposted-To: comp.os.386bsd.development,comp.unix.bsd
From: [email-masked] (Jesus Monroy Jr)
Subject: Re: We a FAQ: Linux vs. *BSD!!!
Date: Sat, 15 Oct 1994 03:54:07 GMT

Brandon S. Allbery ([email-masked]) wrote:
: In article <[email-masked]>, [email-masked] (Tony Porczyk) says:
: +---------------
: | [email-masked] (Jesus Monroy Jr) writes:
: | >   Can we get together and write a single FAQ on this?
: | Outstanding idea.
: +------------->

: My suggestion:

: Q: Which is better, Linux or FreeBSD?

: A: Neither is intrinsically "better".  The answer is the same as for any
:    operating systems X and Y:
:

        This is a good start. Can someone suggest some more ideas?

        Also, can someone track this thread?
        I don't have time to supervise this, or otherwise
        lend more of a hand.
-- 
Jesus Monroy Jr                                          [email-masked]
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________

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

From: [email-masked] (John Richardson)
Subject: Re: [Q] What does MTU do in SLIP?
Date: 11 Oct 1994 18:05:41 GMT

In article <[email-masked]>,
Andrew Robert Ellsworth <[email-masked]> wrote:
>

Maximum transfer unit.

The MTU is the maximum size of a "packet", you want this to be
as large as you can get it since datagrams would otherwise
fragment into multiple packets, increasing your overhead
per datagram because each packet has a seperate header.

On the other hand, if you make the MTU too big then you 
may have to have interactive traffic wait for a second or 
to for a large large batch (ftp) traffic to be sent.

--
John Richardson
[email-masked]

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

From: [email-masked] (Darius Quenum)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Re: NE2000+ and AHA1542CF problems
Date: 16 Oct 1994 01:50:06 GMT

I beleive IRQ 3 is reserved for tty01 under Linux. So you must put your
NE2000 card under IRQ 15 with port 340. I think is one of the best way.
But don't change your Adaptec's configuration because it's a good 
configuration. If you got a problem again then you must read your 
main-card's documentation for fixing the jumpers.

                friendly

darius quenum
email: [email-masked]

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

Crossposted-To: comp.os.386bsd.development
From: [email-masked] (Jesus Monroy Jr)
Subject: Re: We a FAQ: Linux vs. *BSD!!!
Date: Sun, 16 Oct 1994 06:54:54 GMT

R Vincent ([email-masked]) wrote:
: Ken Hughes ([email-masked]) wrote:

: : Normally I would agree, but in this case I doubt that ignoring the
: : questions will stop them from being asked.  New people come into these
: : groups all the time and so these questions are bound to keep coming up.
: : The problem is, as you point out, not the questions but the answers.  It's

: How about we just randomly assign a person to an operating system?

: *slinks back into his hole*
:
        How about I just cover this hole?

-- 
Jesus Monroy Jr                                          [email-masked]
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________

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

From: [email-masked] (Ben Frank)
Subject: Magic mumber for a new fs
Date: 16 Oct 1994 15:38:45 GMT
Reply-To: [email-masked]

Hi,
  I'm writing a new fs and I was wondering if there was any convention as 
regards magic numbers (for the super block). I read MAGIC in the kernel 
source but didn't see any other fs's in there. Can I just pick a number, any 
number? :)
Cheers

        Ben Frank

__
[email-masked]

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

From: [email-masked] (Breakdown)
Subject: IS anyone reading users' complaints?
Date: Sun, 16 Oct 1994 03:45:35 GMT

Is anyone who works in the Linux kernel development team 
reading all these problem reports and doing anything 
about them? Like sort through all the reports, and 
figure out which ones are bugs that probably deserve to
be paid attention to and be fixed in the next kernel
release? It seems to me as if they don't care, or they
just pay attention to what they want to. If I were deve-
loping the kernel, I'd probably make sure I went through 
all 200+ daily problem reports and figure out if there's
a real problem behind each and every one of them....
I dunno....I just get the feeling that no one is being
heard, and there are like sooo many complaints about how things
don't work... Mostly it is due users' lack of knowledge to 
set things up, but what about other probs/bugs? You know,
the serious ones? Just a thought.........

        Genie

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

From: [email-masked] (Bjorn Ekwall)
Subject: Re: IS anyone reading users' complaints?
Date: 16 Oct 94 21:50:22 GMT

Breakdown ([email-masked]) wrote:
 > Is anyone who works in the Linux kernel development team 
 > reading all these problem reports and doing anything 
 > about them? Like sort through all the reports, and 
 > figure out which ones are bugs that probably deserve to
 > be paid attention to and be fixed in the next kernel
 > release? It seems to me as if they don't care, or they
 > just pay attention to what they want to. If I were deve-
 > loping the kernel, I'd probably make sure I went through 
 > all 200+ daily problem reports and figure out if there's
 > a real problem behind each and every one of them....
 > I dunno....I just get the feeling that no one is being
 > heard, and there are like sooo many complaints about how things
 > don't work... Mostly it is due users' lack of knowledge to 
 > set things up, but what about other probs/bugs? You know,
 > the serious ones? Just a thought.........

 >      Genie

Excuse me, but aren't we _all_ members of "the Linux kernel development team"?
You included! If you find something that looks like a problem, fix it!
We are all in this together, really...

Or, if this only was a flame-bait, I fell for it...

Bjorn Ekwall == [email-masked]

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

From: [email-masked] (Matthew Dillon)
Subject: Re: ext2fs vs. Berkeley FFS
Date: 16 Oct 1994 15:02:14 -0700

:In article <[email-masked]> [email-masked] (Piers Cawley) writes:
:>
:>In article <[email-masked]>
:
:   Don't be influenced by the over-featurism that NT offers. There's no need
:   for this crud.
:
:Actually, my model for this sort of thing is the Mac filesystem. I wouldn't
:call it overfeatured, but it does a lot of stuff very well, and very easily,
:that is a royal PITA to accomplish with Unix.

    Frankly, I see nothing here that can't be EASILY implemented with
    directories and file extensions.  IMHO, Mac resource forks were the 
    second biggest mistake Apple made after the operating system.

    It sounds to me that you want a database, not a filesystem.

                                                -Matt

-- 

    Matthew Dillon              [email-masked]
    1005 Apollo Way             ham: KC6LVW (no mail drop)
    Incline Village, NV. 89451  Obvious Implementations Corporation
    USA                         Sandel-Avery Engineering
    [always include a portion of the original email in any response!]

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

From: [email-masked] (Mark A. Horton KA4YBR)
Subject: Kernel 1.1.53 - no BOOM
Date: Tue, 11 Oct 1994 17:17:49 GMT

After 3 consecutive hangs while posting news articles while 
processing news, I have punted on kernel 1.1.53 and gone back to
1.1.50.  No panic, no messages, no boom.... just a solid hang on
all VCs, telnet sessions, and dial-ups... no commands could be 
processed at all.  The only way out was a reset button reboot.  

System configuration information follows:

Console: colour EGA+ 132x44, 24 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
tty02 at 0x03e8 (irq = 4) is a 16550A
tty03 at 0x02e8 (irq = 3) is a 16550A
lp_init: lp1 exists, using polling driver

ATI Inport Bus mouse detected and installed.
Calibrating delay loop.. ok - 33.22 BogoMips
UltraStor driver version1.12.  Using 16 SG lists.
scsi0 : UltraStor 14F/24F/34F
BusLogic SCSI: Inquiry Bytes: 41 41 33 33
Configuring BusLogic ISA HA at port 0x330, IRQ 11, DMA 5, ID 7
BusLogic SCSI: Using extended bios translation.
scsi1 : BusLogic
scsi : 2 hosts.
  Vendor: QUANTUM   Model: PD1225S           Rev: 3142
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, id 1, lun 0
  Vendor: ARCHIVE   Model: VIPER 150  21247  Rev: -603
  Type:   Sequential-Access                  ANSI SCSI revision: 01
Detected scsi tape st0 at scsi0, id 3, lun 0
scsi : detected 1 SCSI tape 1 SCSI disk total.
  Vendor: QUANTUM   Model: PD1225S           Rev: 3110
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdb at scsi1, id 0, lun 0
  Vendor: NEC       Model: CD-ROM DRIVE:841  Rev: 1.0 
  Type:   CD-ROM                             ANSI SCSI revision: 01
Detected scsi CD-ROM sr0 at scsi1, id 2, lun 0
  Vendor: SONY      Model: CD-ROM CDU-541    Rev: 4.3a
  Type:   CD-ROM                             ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi1, id 5, lun 0
  Vendor: QUANTUM   Model: PD1225S           Rev: 3110
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdc at scsi1, id 6, lun 0
scsi : detected 1 SCSI tape 2 SCSI cdroms 3 SCSI disks total.
Scd sectorsize = 2048 bytes
Scd sectorsize = 2048 bytes
Memory: 26944k/32768k available (728k kernel code, 384k reserved, 4712k data)
This processor honours the WP bit even when in supervisor mode. Good.
Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
FDC 0 is a 8272A
Swansea University Computer Society NET3.016
NET3 TCP/IP protocols stack v016
IP Protocols: ICMP, UDP, TCP
PPP: version 0.2.7 (4 channels) NEW_TTY_DRIVERS OPTIMIZE_FLAGS
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
eth0: WD80x3 at 0x280,  00 00 C0 C3 82 66 WD8013, IRQ 10, shared memory at 0xd0000-0xd3fff.
wd.c:v1.10 9/23/94 Donald Becker ([email-masked])
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Linux version 1.1.53 (root@ka4ybr) (gcc version 2.5.8) #1 Mon Oct 10 13:28:43 EDT 1994
Partition check:
  sda: sda1 sda2 sda3 sda4
  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
  sdc: sdc1 sdc2 sdc3 sdc4
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 17396k swap-space
Adding Swap: 17392k swap-space
Adding Swap: 17404k swap-space
Adding Swap: 17404k swap-space
Max size:326341   Log zone size:2048
First datazone:72   Root inode number 73728
ISO9660 Extensions: RRIP_1991A
Max size:331019   Log zone size:2048
First datazone:120   Root inode number 122880
ISO9660 Extensions: RRIP_1991A
ppp: channel ppp0 mtu = 1500, mru = 1500
ppp: channel ppp0 open

--
"No boom today.  Boom tomorrow, there's ALWAYS a boom tomorrow."
                                         -- Ivanova (Babylon 5)
============================================================
Mark A. Horton       ka4ybr           [email-masked]
P.O. Box 747 Decatur GA US 30031-0747   [email-masked]
+1.404.371.0291 : 33 45 31 N / 084 16 59 W    [email-masked]

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

From: [email-masked] (Matthew Dillon)
Subject: Re: IS anyone reading users' complaints?
Date: 16 Oct 1994 15:19:51 -0700

:In article <[email-masked]> [email-masked] (Breakdown) writes:
:>Is anyone who works in the Linux kernel development team 
:>reading all these problem reports and doing anything 
:>about them? Like sort through all the reports, and 
:>figure out which ones are bugs that probably deserve to
:>be paid attention to and be fixed in the next kernel
:>release? It seems to me as if they don't care, or they
:>just pay attention to what they want to. If I were deve-
:>loping the kernel, I'd probably make sure I went through 
:>all 200+ daily problem reports and figure out if there's
:>a real problem behind each and every one of them....
:>I dunno....I just get the feeling that no one is being
:>heard, and there are like sooo many complaints about how things
:>don't work... Mostly it is due users' lack of knowledge to 
:>set things up, but what about other probs/bugs? You know,
:>the serious ones? Just a thought.........
:>
:>      Genie

    Well, I listen to anything related to those parts of the operating
    system that I work on, and I'm sure others do as well.  But you 
    have to realize that bugs aren't necessarily easy to find... for
    example, it took me 6 hours to track down a timing window in some
    scheduling code that I was working on.  It only took 10 minutes
    to introduce the bug in the first place :-)

                                                -Matt

-- 

    Matthew Dillon              [email-masked]
    1005 Apollo Way             ham: KC6LVW (no mail drop)
    Incline Village, NV. 89451  Obvious Implementations Corporation
    USA                         Sandel-Avery Engineering
    [always include a portion of the original email in any response!]

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

From: [email-masked] (Erik Corry)
Subject: Re: A badly missed feature in gcc
Date: Sun, 16 Oct 1994 21:36:21 GMT

How about a new comment start sequence for C:

/// This is a comment.

Using /// to start a comment will:

a) Not break any legal C program
b) Not break any legal C++ program

Too simple?

The only thing I am worried about is:

/* This is a comment with a // in it */

or

/* This is a comment with a /// in it */

What does C++ do about this?

-- 
Erik Corry, Freiburg, Germany, +49 761 406637 [email-masked]

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

From: [email-masked] (just me)
Subject: SCSI detect....
Date: Tue, 11 Oct 1994 17:01:15 GMT

Where is the code that detects what devices are on the SCSI bus during
boot?

I'm using an Adaptec 1522a, hard drive, and a CDROM. The boot kernel only
recognizes the hard drive, not the CDROM.

I looked in ~/linux/drivers/scsi/aha152x.c and sr.c, but I'm braindead
and don't see where the detection is done. Probably looking in the wrong
place to begin with.

Any help is appreciated,
Alan

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

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

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

    Internet: [email-masked]

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