Subject: Linux-Development Digest #729
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:     Wed, 18 May 94 02:13:06 EDT

Linux-Development Digest #729, Volume #1         Wed, 18 May 94 02:13:06 EDT

Contents:
  Re: Xfree86/mouse/IRQ/config problem (Douglas Donahue)
  Re: 1.0.9 kernel bug (+ partial fix): when using non-loopback address to send to localhost, "from" address should also be non-loopback. (Remco Treffkorn)
  Re: LAT support? (Nick Hilliard)
  Digiboard 8 port (was Digiboard Dump 8 port serial board) (Act of Treason)
  ADAPTEC 2740/2742 (Howie Grapek)
  Re: ET++ Application Framework (jean safar)
  Re: Proposal for Diskette Information Interchange (Jesus Monroy Jr)
  Re: [Announcement] 386BSD Release 1.0 (H. Peter Anvin)
  TCP lockups through Cisco box (Erik Olson)
  Z-Note Ethernet device driver status (pegettin@midway.uchicago.edu)
  Re: Appletalk support? (Eduardo Kaftanski)
  Keeping data structures in memory (Terence Davis)
  Re: TCP lockups through Cisco box (Alan Cox)
  Re: Appletalk support? (Bill Bogstad)
  Re: In defence of variety (was Re: Distributions considered harmful) (Daniel Quinlan)
  In defence of variety (was Re: Distributions considered harmful) (Jeff Epler)

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

From: odoncaoa@panix.com (Douglas Donahue)
Crossposted-To: comp.os.linux.admin,comp.windows.x.i386unix,comp.os.linux.misc,alt.uu.comp.os.linux.questions,aus.computers.linux,fr.comp.os.linux,maus.os.linux,de.comp.os.linux,fj.os.linux,no.linux
Subject: Re: Xfree86/mouse/IRQ/config problem
Date: 17 May 1994 19:12:21 -0400

Douglas Donahue (odoncaoa@panix.com) wrote: ...

I forgot to mention that the 'selection' executable seems to work just fine. 

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

From: remco@emc.rvt.com (Remco Treffkorn)
Subject: Re: 1.0.9 kernel bug (+ partial fix): when using non-loopback address to send to localhost, "from" address should also be non-loopback.
Date: Tue, 17 May 1994 00:38:27 GMT
Reply-To: remco@emc.rvt.com

Rob Janssen (rob@pe1chl.ampr.org) wrote:
: I think the original issue was only the existance of a bug and how it
: could be fixed.  When the bug is fixed in an alpha version and you don't
: want to upgrade to it, then so be it.  You still have your stable version
: with the bug.

: Rob

Do your emotions run away from you? 
What the heck is a "stable version with a bug"? An oxymoron?
If I remember correctly: The 1.0 version was supposed to be maintained
to be a "stable" version, meaning only bug fixes would be applied.
In fact nine bug fixes have been applied. This was ,inter alia, to acknolege
the fact, that there are really people out there runing Linux in a production
environment, not beeing interested in beein on 'the bleeding edge'.
V1.1 was supposed to be the hackers heaven again. 

If 1.0 has known bugs and they were not to be fixed, then to hell with it.
Just delete it from the ftp servers and force everybody to paricipate in
debugging the 'real' kernel. Anything else would at least be misleading.
No different from using 99.13 when 99.15 was out (well, worse!).

Just because a guy came on a bit strong does not justify to give everybody
depending on v1.0 the finger collectively! 

In review, maybe my emotions shine through a bit more than I would have liked
to, but I am too lazy to rewrite the drivel, so I let it go. No offense
intended.

Maybe I totally missunderstand the bit about v1.0 and v1.1, but so would
many other people I know. I think it is time for a clarification.
Or maybe we should just reread the old postings about the subject and
Linus announcement. Hope I still have the stuff around...

Remco

P.s.: If Alan feels it is too much to have to maintain the old 1.0.x stuff
ontop of the current development branch, then we should really get rid of
1.0.x, or maybe somebody is willing to fold back those fixes that would
applay under Alans supervision? BTW: that goes for all the developers.
I think the v1.0 branch only makes sense if the developers can support it.
If not, let's kiss it goodby if it is too much of a drain. I at least
consider the work on v1.1 more important, but then this is personal
opinion.
-- 

Remco Treffkorn, DC2XT
remco@emc.rvt.com
(408) 685-1201

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

From: nick@quay.ie (Nick Hilliard)
Subject: Re: LAT support?
Date: Tue, 17 May 1994 13:20:24 GMT

chris ulrich (insom@galaxy.ucr.edu) spoke thus:
: I have some old LAT based dec(obviously) terminal servers that
: I would like to connect to a linux box.  Is there any LAT support
: in linux?  Is there enough to run terminal servers?

No and no.  LAT is a proprietary communications protocol, and requires
licenses even if you reverse-engineer it.  Your best bet would be to set up
an account on another LAT compatible machine which would connect up to your
Linux box using telnet.

: chris
: insom@ac.ucr.edu                              Ecstatic peace
: insom@ucrvms                                  Savage conquest

Nick
-- 
| Nick Hilliard, Sys Admin,  | e-mail:   nick@quay.ie                    |
| Quay Financial Software,   | Phone:    [+353] 1 6612377                |
| 48-53, Lower Mount St,     |    The opinions expressed above do not    |
| Dublin 2, Ireland          | necessarily reflect those of my employers |

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

From: treason@gnu.ai.mit.edu (Act of Treason)
Subject: Digiboard 8 port (was Digiboard Dump 8 port serial board)
Date: 17 May 1994 20:01:16 GMT

Richard,

From the description of the card that you have given me, I am assuming that
the digiboard you have is a Digiboard PC-8 Non-intelligent board.  I acquired
my PC-4 in much the same way as you have the PC-8 and didn't have any 
documentation.  I called up Digiboard and asked them if they could send me
out any pertinent information on the baord, and believe it or not, they asked
me for what platform I wanted, and sent out the software and manuals FREE
of charge.  Since then I have modified my serial.c (in the kernel dist) to
support my digiboard, and have used it without error since.  If you need help
or for some reason, cant get ahold of digiboard, inc, write me personally and
we can talk.

Seeya,

treason@gnu

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

From: howie@fc.hp.com (Howie Grapek)
Subject: ADAPTEC 2740/2742
Date: 17 May 1994 01:02:43 GMT


Is the AHA 2740/2742 supported? Are the drivers available? 
I've seen mention of the 15xx/17xx (supported)
and the 28xx (not yet), but no mention of the 27xx.

Any clues would be helpful.

thanks, Howie

--
Howie Grapek, Contractor          __o          Hewlett Packard
Voice: (303) 229-2318           _ \<,_         3404 E. Harmony Road
FAX:   (303) 229-4977          (_)/ (_)        Fort Collins, Co  80525
                            howie@fc.hp.com

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

From: jsafar@lehman.com (jean safar)
Subject: Re: ET++ Application Framework
Reply-To: jsafar@lehman.com
Date: Mon, 16 May 1994 21:18:07 GMT

The only place where I have seen ET++ was with the distribution 
of sniff+ from takeFive. You can access the Sniff+ evaluation
distribution and then get ET++ with it (or just download ET++
of course), so it seems that ET++ is public domain.

From what the sniff+ guys say, their product seems to have been 
built with it which if it is true would really show that it is 
a nice and robust library. 

Sniff+ is not available on linux given the state of the distribution at
this site. 

the ftp site is: self.stanford.edu:/pub/sniff/SNIFF+-1.3

I hope this helped.

Have fun-

---
=======================================================

John Safar                           jsafar@lehman.com
                  I've seen things that you people ...

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

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.storage,comp.sys.ibm.ps2.hardware,comp.arch.storage
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Re: Proposal for Diskette Information Interchange
Date: Tue, 17 May 1994 00:52:50 GMT

 
 
                Below is a minor correction for proposal is below.
        An incorrect reference was made to the mapped sector numbers.
        The correction should read as below "sector 6-15".
 
 
====================================================================
 
        reserved
        ________
 
                TRACK ZERO  sector 6-15
 
                A "bad-sector" map area for 20 meg diskettes.
 
                These disk drives are scsi and have their own format to
        by pass bad sector problems. In either case, reserving track
        zero make it compatible with IBM/MS-DOS.
 
 
 

-- 
Jesus Monroy Jr                                          jmonroy@netcom.com
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________

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

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
From: hpa@ahab.eecs.nwu.edu (H. Peter Anvin)
Subject: Re: [Announcement] 386BSD Release 1.0
Reply-To: hpa@nwu.edu (H. Peter Anvin)
Date: Tue, 17 May 1994 01:09:19 GMT

Followup to:  <oyang.769000946@bruce.cs.monash.edu.au>
By author:    oyang@cs.monash.edu.au (Kai Shing O'Yang)
In newsgroup: comp.os.linux.development
>
> How about a scsi CDROM drive set at id=0? the SCSI Adaptor bios will
> treat the device as a hard drive and tries to read the boot sector from it. 
> if there is a way to fool the bios that the CD is actually a H/D, I can't see 
> why one can't boot from CD. If I'm wrong, pls correct me.

You are wrong.  SCSI devices announce the type of device; and the BIOS
will ignore devices not labelled as a hard drive (read/write mass
storage, nonremovable) or possibly a floppy (read/write mass storage,
removable).

There is no *technical* reason why it can't be done, the problem is
that with the standard PC hardware and BIOS there is no way of
transferring control to the CD without the aid of a program stored
elsewhere.  This program can be on hard disk, floppy, or in a ROM.

        /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
To the memory of Richard Nixon we will now dedicate 18 1/2 minutes of silence.

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

From: erik@hilo.phys.washington.edu (Erik Olson)
Crossposted-To: comp.os.linux.help
Subject: TCP lockups through Cisco box
Date: 17 May 1994 15:44:43 GMT

Okay, haven't seen anyone post about this yet, so I figured I'd spew.
I use my Linux system over the phone through a Cisco terminal server
that telnets to its hosts.  One major problem I have is that at random
the session will completely freeze and the only way to start it back again
is to send a BREAK signal, giving me back the cisco prompt, at which point I
hit return to resume the session.  Text then blasts by and the session resumes.

The criteria:

  * Happens on other tcp servers, not just telnet.  Therefore, I think it's
something in the kernel-level code, not telnetd.

  * Only happens on the Linux box.  Therefore, I think it's a Linux-specific
oddity.

  * Happens on dialin AND locally-connected lines.  Therefore, it's not
a modem handshake problem.

  * Only happens on Linux boxes, and has been happening since pl14.  I am
using 1.1.12 now.

  * Oh, and it happens on our Departmental cisco box, which has a SLIGHTLY
earlier software revision than the campus-wide cisco box, which doesn't
exhibit the problem.

Someone say they know what this means, please!

   - Erik
--
---
Erik D. Olson                                olson@phys.washington.edu
Grad Student                            erik@marge.phys.washington.edu

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

From: pegettin@midway.uchicago.edu
Subject: Z-Note Ethernet device driver status
Date: Tue, 17 May 1994 20:20:49 GMT

  I am considering putting Linux on my Z-Note 425Lnc and see no problems
(yet) except that I want to be able to use the built-in ethernet adaptor.
The latest Ethernet How-To said that a driver for the adaptor (which is
based on the Intel 82593 chip) should be done by mid-1994.  I was 
wondering if anyone knows what the status of the driver is?  Thanks.

Paul Gettings

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

From: ekaftan@ing.puc.cl (Eduardo Kaftanski)
Subject: Re: Appletalk support?
Date: Tue, 17 May 1994 01:29:27 GMT

In article <Cpx0Do.K2v@stortek.com>, Jeff Andre <andre@hoth.stortek.com> wrote:
>
>I've always been interested in doing this project.  Besides the "plenty
>of time" aspect, you need to program to the AppleTalk card.  I have both
>an old TOPS PC card and a (more?) current DL2000 from Dayna.  In order
>to support you'd have to get the vendors to release the specs for the
>cards in order to write the drivers.  They may, I don't know, haven't
>asked.

Ok. I have been working some on this. FIrst, what you are asking
is LocalTalk support. It will need two things: an AppleTalk implementation,
and drivers for the cards.
The first one is easier than the second. A fairly complete Appletalk
implementation can be found in either CAP or uar. CAP is free and reusable, uar
is alittle more protected (by his author an his university). Anyway,
djh (uar's author) suggested me I could use his code. I am no expert in
copyright, but we could release a patch and get the core code from him.
The second one costs money. I wrote Dayna a message asking for docs on their
cards and the response was to buy the developers kit. about 500 bucks, but
restricted to a Non disclosure agreement, so I could not release source
code for a driver.


>
>One of the real questions is how much of an interest is there in such
>a capability.  Beyond sharing printers, AppleTalk isn't a steller performer.
>
>I believe there is a way to attach Ethernet to old Macs; I believe there
>are SCSI devices.  If you're interested, I'll find the product.  I think
>we may have one or two here at work.

I suggest using Focus enhancments Etherlan miniSC. I resell them here (so
I AM biased) and get only good feedback from them. No one has failed so far.


>
>The other solution would be to get an IP <-> AppleTalk gateway.
>
        If you want TCP/IP for the macs on localtalk, and you have no 
money, get an old PC (free) an old WD8003e (cheap, if you can find one),
and an old Appletalk card (not so asy to find, about 300 if you buy it),
and use PCROUTE. It works fine, provided you reboot it once a week...


#disclaimer: I speak for myself. I don't speak for others for free ;-)

-- 
Eduardo Kaftanski

ekaftan@ing.puc.cl


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

Crossposted-To: comp.os.linux.misc
From: terence@soldev.tti.com (Terence Davis)
Subject: Keeping data structures in memory
Date: Tue, 17 May 1994 02:33:29 GMT


Hi,

  A student in a class of mine wants to be able to keep large data structures, 
i.e. 10 or more megabytes, in RAM.  He wants to force the objects into RAM and 
doesn't want them paged out.  Assuming he has enough real RAM, what's the 
algorithm Linux uses to page stuff out.  Is there a way to lock the memory for 
particular data structures in RAM?

Thanks,

Terry (terence@soldev.tti.com)


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

Crossposted-To: comp.os.linux.help
From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: TCP lockups through Cisco box
Date: Tue, 17 May 1994 19:01:15 GMT

In article <2raopb$bjh@news.u.washington.edu> erik@hilo.phys.washington.edu (Erik Olson) writes:
>  * Happens on other tcp servers, not just telnet.  Therefore, I think it's
>something in the kernel-level code, not telnetd.
Almost certainly the case.
>  * Only happens on the Linux box.  Therefore, I think it's a Linux-specific
>oddity.
No - one problem with TCP/IP is that most people use just the BSD net code
and don't test well with different net code. 
>  * Oh, and it happens on our Departmental cisco box, which has a SLIGHTLY
>earlier software revision than the campus-wide cisco box, which doesn't
>exhibit the problem.
>Someone say they know what this means, please!

I guess it means CISCO have just fixed the bug 8)

Alan

PS: If someone can verify this and email me versions it'll be valuable info
for future problems people may have.

Alan


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

From: bogstad@blaze.cs.jhu.edu (Bill Bogstad)
Subject: Re: Appletalk support?
Date: 16 May 1994 18:52:26 -0400

In article <1994May16.163133.24189@uk.ac.swan.pyr>,
Alan Cox <iiitac@uk.ac.swan.pyr> wrote:
>In article <2r4q4r$44a@nnrp.ucs.ubc.ca> pdivine@unixg.ubc.ca (Patrik J. Divine) writes:
>>
>>does anyone know if there is, or will be any Appletalk support for Linux?  I
>>want to network several Mac's to a Linux machine but most of the Mac's are
>>older and do not have ethernet capability (or can you hook up external
>>ethernet devices to Mac SE's?) .. any help would be apperciated.
>>
>There is nothing stopping anyone writing a kernel or usermode appletalk handler
>for Linux. The kernel has all the code needed to write it in user mode, or you
>could build it in the kernel as a protocol layer like IP, IPX or AX.25. Since
>appletalk is relatively simple its a viable job for someone with the specs
>and plenty of time.

        In case anyone is interested in doing this, they should look into the
CAP and netatalk packages which are free user mode and kernel mode AppleTalk
software packages for Unix systems.  CAP would probably be fairly easy to
port as long as the Linux kernel allowed raw ethernet packet access (which I
believe it does now (perhaps with a few patches)).

                                Bill Bogstad
                                bogstad@cs.jhu.edu

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

From: quinlan@pollux.cs.bucknell.edu (Daniel Quinlan)
Subject: Re: In defence of variety (was Re: Distributions considered harmful)
Date: 18 May 1994 01:46:33 GMT
Reply-To: quinlan@spectrum.cs.bucknell.edu


jepler@herbie.unl.edu (Jeff Epler) says:

>> using the TeX package from SLS because it didn't have its own.  The
>> differences are primarily cosmetic, and have probably lessened since
>> FSSTND.  Usually the procedure is:

Most Linux distributions *still* have an out-of-whack TeX directory
structure.  /usr/TeX is not standard, it's a relic from SLS.

bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:

> In any case, I'm no longer worrying about distributions that much
> because FSSTND (and Debian in particular) seem to be h*ll-bent on
> disenfranchising folks who need to be compatible with other systems
> for network mounting or use of iBCS software which wants iBCS
> standard paths.  (I brought this up once on FSSTND and was bluntly
> told that that was unimportant.  I haven't bothered to mention it
> since; it may not be important to them, but in my environment it's
> essential.)

If you haven't bothered to bring something up a second time, then
don't blame it on FSSTND.  In my FSSTND archives, I have a *single*
message from you (buried in over 6MB of other messages), mentioning
iBCS standard paths -- dated Dec 19.  And now, May is almost over.
The first public version wasn't even released until February.  You
are being somewhat unrealistic if a single message about it is going
to start a discussion.

Dan

--
Daniel Quinlan  <quinlan@spectrum.cs.bucknell.edu>

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

From: jepler@herbie.unl.edu (Jeff Epler)
Subject: In defence of variety (was Re: Distributions considered harmful)
Date: 17 May 1994 19:47:38 GMT

nelson@crynwr.crynwr.com (Russell Nelson) writes:

>I don't think the current state of Linux distributions is good.  Free
>software works because the users can be programmers, and everyone can
>cooperate.  But with the various distributions, we have
>noncooperation.  

I don't have that much of a problem with the fact that there are
different distributions.  Of course, I may not like some of them
much...

We've got MCC, the small system.  Slackware, the complete system.
SLS, the broken system with exactly one feature that might be nice to
have elsewhere.  Debian, the release that doesn't really exist yet.
Yggdrasil and the other CDrom distributions, for those with slow or
nonexistant linkage to the net..

They all have their place, and the fact that there are so many doesn't
really detract from them.

>Guys, that's what the SysV people do, not us.  They
>feel a need to differentiate their product from the base System V
>distribution from USL.  So when they fix a bug, or add a feature, they
>*don't* send it back to USL.

I don't know that this is really the case with the Linux
distributions.  The only thing I can think of that could be called
'truly innovative' is the SLS Modular Kernel.  I don't know if it's
not a part of the standard kernel because it is still quirky (I see
many posts about people trying to compile the SLS kernel, but I
haven't read any of them), because the SLS maintainer doesn't want the
mainstrean kernel to have these features (This would likely violate
the GPL), or because Linus just doesn't want those drivers there...

Are there other such situations you're thinking of?

>We've got at least four different package conventions (SLS, Slackware,
>Debian and Yggdrasil).  Why?  No good reason I can see.  FTP sites
>carry these different distributions, most of which differ only slightly.

It would be nice if there was a standardization that allowed
installation of a package from any distribution, even if you don't
have that distribution.  However, I don't think we're that far from
it.  On my MCC system I was able to effortlessly install the
Ghostscript and Ghostview binaries from Slackware.  Slackware easily
accepted tinyX and ran it admirably.  Slackware used to recommend
using the TeX package from SLS because it didn't have its own.  The
differences are primarily cosmetic, and have probably lessened since
FSSTND.  Usually the procedure is:
cd /
tar xzvf PACKAGE.tar.gz
<remove junk files particular to distribution PACKAGE comes from>

Three steps isn't very much at all...

>I feel that there is need, and room, for two Linux distributions, one
>conservative, and the other radical.  The conservative distribution is
>probably the harder, and potentially more money-making, distribution
>to do.  It is marketed at Linux "users".  People who don't want to
>have to fiddle.  People who are willing to pay for the software to
>"just work".  So the conservative distribution has its work (and
>profit) cut out for it.

If you're asking for this, why not just have one distribution with two
personalities?  Slackware and SLS come close to this with the concept
of 'disk sets', and with MCC it's easy to pick and choose which
packages you want since it is somewhat less than rigid in its disk
packing.  Perhaps the "users" version would be a stable libc, a 1.0.x
kernel, X 2.1.1 and formatted man pages, while the "radical"/"hacker"
version would include the necessities of GCC, 1.1.x kernel, one of the
unsupported X 3.0's floting around, etc.

>And there's plenty of money to be made on the radical distribution,
>because it's obvious that some people out there want the latest and
>greatest, and they're willing to pay for it.  "Who has the latest CD"
>is the subject of a recent Usenet message.

I don't think that keeping on the bleeding edge is something best done
by buying a new CD -- FTP is a much beter idea, for those who have it.
Installing new libc, gcc, kernel, or X is a pretty painless process..
The same for most software that will let me 'make install'.

>And multiple distributions are not good, because they tend to fragment
>the market.  The Linux market is small enough as it is -- we don't
>need to make it smaller!  If I'm running Slackware, I don't feel like
>I can purchase SLS's support package.  Or if I've bought Yggdrasil's
>CD-ROM, can I install an slackware package?  And not break everything?

Well, the answer to this is to take a chance that you might break
everything... 

>We should start with a merger between SLS and Slackware.  Send your
>requests for same to Peter and Patrick, imploring them to cooperate
>for the betterment of all.  Yes, they've had words, but they should
>still be able to work together.

I don't need The One True Distribution (But if I made my own, it would
be TOTDOLinux probably), and especially not as a union of SLS and
Slackware.  I'm sure someone does, but the fact that I don't want it
and can proceed to not have it but still have Linux is what makes the
idea of many distributions a good idea.

Of course, my views here are more of the hackerish sort, not ones
suitable for those who are going to use Linux in an atmosphere where
there are overworked admins and users who don't understand.  The vast
majority of the software I have here comes not from the MCC 0.99.10+ I
installed long ago, but from source code I found, liked, and compiled
myself.  Most of the rest is binary replacements of large packages,
such as libc, XFree86 or gcc, packaged independantly of any
distribution.  And while it has made a bit of a wilderness out of my
/usr, it has what I need 95% of the time.

The distribution isn't the be-all or end-all of Linux... They're a
base from which your personal Linux machine will grow.  Very few Linux
users can really say 'My computer is Slackware' or 'My computer is
MCC', because most everything gets taken out and replaced... But it's
still nice to start out with a Linux that is close to your particular
'personality'.  And the diversity of distrubutions is the best way to
get that right now.

Jeff
--
Jeff Epler       echo "kill -9 -1" | su         jepler@herbie.unl.edu 
____ "Nuke the unborn gay whales for Jesus" 
\bi/                                  -- Never seen on a protest sign
 \/  1.5<kinsey<2.5      Running Linux 1.1.11 -- DOS is to boot DOOM!

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


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