Subject: Linux-Development Digest #716
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:     Fri, 13 May 94 09:13:08 EDT

Linux-Development Digest #716, Volume #1         Fri, 13 May 94 09:13:08 EDT

Contents:
  Re: Linux 1.1.12...compile problem (Mark Evans)
  Re: Booting from CD-ROM, was: [Announcement] 386BSD Release 1.0 (Gordon William Matzigkeit)
  Re: Terminator-Power Question (na8520d00-Nichols)
  Re: CD-ROM's do all read and write now? (Gess Shankar)
  DIP Alternative patch (Whistler)
  Re: Linux 1.1.12...compile problem (Helmut Lichtenberg(m))
  HTML versions of 1.1 patches available (Sam Shen)
  Re: COMMODORE CALLS IT QUITS (Markus Wischerath)
  Re: kernel question, memory usage (Maarten Boekhold (Who'd you expect??))
  Re: COMMODORE CALLS IT QUITS (Maarten Boekhold (Who'd you expect??))
  Re: wt news--version 0.02 - port to MSDOS (J.C. Longley)
  Re: Apple filesystem and Appletalk (Archie Cobbs)
  SOME select() THANKS... (charles stigers)
  Kernel errors (bad inode) - leading to eventual failure (Christopher D. Gori)

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

From: evansmp@mb52112.aston.ac.uk (Mark Evans)
Subject: Re: Linux 1.1.12...compile problem
Date: Wed, 11 May 1994 20:43:04 GMT

Helmut Lichtenberg(m) (heli@tzv.fal.d400.de) wrote:
: Hey,
: I did it but still get:

: make[1]: Leaving directory `/usr/src/linux/lib'
: ld  -Ttext 100000 boot/head.o init/main.o tools/version.o \
:         kernel/kernel.o mm/mm.o fs/fs.o net/net.o ipc/ipc.o \
:         fs/filesystems.a \
:         drivers/block/block.a drivers/char/char.a drivers/net/net.a ibcs/ibcs.o \
:         lib/lib.a \
:         -o tools/zSystem
: net/net.o: Undefined symbol _rarp_ioctl referenced from text segment
: make: *** [tools/zSystem] Error 1


BTW this is comp.os.linux.development, it would be nice
if people using it knew at least the basics of c, the preprocessor
and Makefile rules
:-)

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

Crossposted-To: comp.os.minix,comp.os.mach,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.misc
From: gwmatzig@acs.ucalgary.ca (Gordon William Matzigkeit)
Subject: Re: Booting from CD-ROM, was: [Announcement] 386BSD Release 1.0
Date: Fri, 13 May 1994 01:28:55 GMT

It is my humble request to exclude comp.os.minix and comp.os.mach from
this thread.  Honestly, people!  :-)  I don't know anything about
booting from CD-ROM, and if I did, I know I'd subscribe to
*.development or *.hardware.misc

--Gordon Matzigkeit          "Let he who is without sin..." Ha! As if!
  gwmatzig@acs.ucalgary.ca   BANDWIDTH, bandwidth, bandwidth.

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

From: rnichols@ih4ehw.ih.att.com (na8520d00-Nichols)
Subject: Re: Terminator-Power Question
Reply-To: rnichols@ihlpm.ih.att.com
Date: Fri, 13 May 1994 01:19:06 GMT

In article <1994May12.203950.13241@kf8nh.wariat.org>,
Brandon S. Allbery <bsa@kf8nh.wariat.org> wrote:
>In article <1994May12.120014.17743@pe1chl.ampr.org>, pe1chl@rabo.nl says:
>+---------------
>| (if it is not that, I really cannot imagine how supplying terminator
>| power can interfere with anything)
>+------------->8
>
>Possibly by sourcing too much current?  In any case, the manuals for my
>Fujitsu hard drives say that no more than (some number, can't recall just now
>and I'm dialed in from work at the moment so can't check) should supply
>TERMPWR.  It doesn't say what dire effects will result if you have too many
>devices supplying TERMPWR.

The only "dire effect" is that, should the TERMPWR wire get shorted to
ground, there might be enough current available to burn out the wire
rather than the protective fuses in the devices supplying power.  Under
just the right conditions, it could even pose a fire hazard.

--
Bob Nichols
AT&T Bell Laboratories
rnichols@ihlpm.ih.att.com

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

From: Gess Shankar <gess@knex.mind.org>
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
Subject: Re: CD-ROM's do all read and write now?
Date: Tue, 10 May 1994 18:23:46 EST
Reply-To: gess@knex.mind.org (Gess Shankar)

rme81977@zach.fit.edu (Brian Fritz/ ADVISOR Russell (MAE)) writes:

> Can someone tell me if all CD drives read and write now?  Which ones
> are the "top of the line"?
> Thanks
> -BRian

All CD-ROM drives only READ. Hence the ROM moniker. CD-Recordables
are available, however. You use a recordable media (same form factor
as a CD-ROM) and premastered images can then be written (say in
ISO-9660 format) to the CD-R media. This can be read by all CD-ROM
drives.

While prices for CD-R recorders are coming down (Quad speed Yamaha
around $4000 e.g.), it is not a piece of equipment that you use for
reading and writing as in a WORM or hard disk. While they are good
for writing, you need to prestage everything and write a whole track
at-once. And the READ performance is abominable. Archiving and producing
CD-ROM masters/small production runs are primary applications.

I have not seen any support from any premastering software vendors for
OS/2. I am working on one.

GeSS
-- 
Gess Shankar      |<><>| Internet: gess@knex.mind.ORG                   |<><>|
CDPub List Admin. |<><>| uucp    : ..!emory!uumind!knex!gess            |<><>|
What's CDPub List?|<><>| Send email to: cdpub-info@knex.mind.org        |<><>|

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

From: slouken@cs.ucdavis.edu (Whistler)
Subject: DIP Alternative patch
Date: Tue, 10 May 1994 19:09:01 GMT


        Here is a patch to my expect script that shows how you
can set up a SLIP connection without even knowing the slip server's
IP address...  note the ifconfig and route commands. 
(Thanks to Johannes Stille for the tip on how to do it :)


Enjoy!

        -Sam


slip.patch --------------------------------------------------------
*** slip.exp    Tue May 10 11:11:26 1994
--- slip.exp.noserver   Tue May 10 11:14:58 1994
***************
*** 5,13 ****
  ##########################################################
  # Configuration
  #
- # The IP address of your slip server:
- set server 120.128.250.100
- #
  # If you have a static IP address, put it here:
  set local_ip  {}
  #
--- 5,10 ----
***************
*** 212,227 ****
  set timeout 2; expect
  
  # Get the SLIP parameters for this session and set it up!
! #regsub (\[0-9]+.\[0-9]+.\[0-9]+).\[0-9]+ $server {\1.0} network
! regsub (\[0-9]+.\[0-9]+.\[0-9]+).\[0-9]+ $server {\1.255} bcast
! system ifconfig $interface $local_ip pointopoint $server \
!                 mtu $MTU netmask 255.255.255.0 broadcast $bcast
! system route add $server
! system route add -net default gw $server metric 1
  
  # Run the SLIP startup script, if any.
  if { [file exists $sliprc] } {
        system $sliprc >/dev/null
  }
! send_user "SLIP connection established with $server.\n"
  exit 0
--- 209,221 ----
  set timeout 2; expect
  
  # Get the SLIP parameters for this session and set it up!
! system ifconfig $interface $local_ip pointopoint 0.0.0.0 \
!                 mtu $MTU netmask 255.255.255.0
! system route add default dev $interface
  
  # Run the SLIP startup script, if any.
  if { [file exists $sliprc] } {
        system $sliprc >/dev/null
  }
! send_user "SLIP connection established.\n"
  exit 0

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

From: heli@tzv.fal.d400.de (Helmut Lichtenberg(m))
Subject: Re: Linux 1.1.12...compile problem
Date: Fri, 13 May 1994 09:23:15 GMT

evansmp@mb52112.aston.ac.uk (Mark Evans) writes:
: Helmut Lichtenberg(m) (heli@tzv.fal.d400.de) wrote:
: : Hey,
: : I did it but still get:
: 
: : make[1]: Leaving directory `/usr/src/linux/lib'
: : ld  -Ttext 100000 boot/head.o init/main.o tools/version.o \
: :         kernel/kernel.o mm/mm.o fs/fs.o net/net.o ipc/ipc.o \
: :         fs/filesystems.a \
: :         drivers/block/block.a drivers/char/char.a drivers/net/net.a ibcs/ibcs.o \
: :         lib/lib.a \
: :         -o tools/zSystem
: : net/net.o: Undefined symbol _rarp_ioctl referenced from text segment
: : make: *** [tools/zSystem] Error 1
: 
: 
: BTW this is comp.os.linux.development, it would be nice
: if people using it knew at least the basics of c, the preprocessor
: and Makefile rules
: :-)

Thanks for your answer, it helped a lot :-)
I read comp.os.linux.help and got the following hint from lcvanveen@et.tudelft.nl:

> Any problems concerning 1.1.12 are due to a fault in the Makefile
> in linux/net/inet. How to solve it can be found in c.o.l.d.
> Goodluck,

So I read all the posts in c.o.l.h and c.o.l.d, followed all the 
"insert this ... in ..." and compiled the kernel although 
I'm no expert in c and Makefiles but want to get use of
kernel improvements. What's wrong with this?

Helmut
-- 
========================================================================
|                      Helmut Lichtenberg                              |
|           Institut fuer Tierzucht und Tierverhalten (FAL)            |
|                     heli@tzv.fal.d400.de                             |

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

From: sls@ux5.lbl.gov (Sam Shen)
Subject: HTML versions of 1.1 patches available
Date: 11 May 1994 09:10:02 GMT

I wrote this for myself but others may find it interesting.  Point
your favorite WWW browser at:

        http://www.lbl.gov/~sls/diffs_dir.cgi

That should bring up a list of patches to linux 1.1.  Each patch is a
link to a list of patched files.  Clicking on a file will bring up the
diff.  Basically it's a friendlier way to look at a patch.

The scripts are available in http://www.lbl.gov/~sls/html_diffs.shar.

Comments, questions, suggestions to slshen@lbl.gov.

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

Crossposted-To: comp.os.linux.misc
From: mw@spinfo.Uni-Koeln.DE (Markus Wischerath)
Subject: Re: COMMODORE CALLS IT QUITS
Reply-To: mw@spinfo.uni-koeln.de
Date: Fri, 13 May 1994 10:15:10 GMT


bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
> In article <1994May12.192514.12009@rosevax.rosemount.com>, grante@reddwarf.rosemount.com (Grant Edwards) says:
> +---------------
> | : 65C816, but that was an 8/16 bit microprocessor.  (The Apple IIGS
> | 
> | Yep, that's the one -- I mis-remembered the bus width.  Did the IIGS
> | even run the thing in 16 bit mode?
> +------------->8
> 
> If I remember correctly, one of the reaons the IIGS didn't take off was
> problems running 8-bit Apple II software.  I would suspect that means "yes".
> 
Huh? The GS runs 8-bit stuff just fine, except for a few old games. The 
65c816 can be switched into 6502 emulation mode. The reason that the GS
died was that Sculley rather wanted to sell Macintoys galore, and the GS
outperformed low-end Macs even though the standard GS CPU ran at a whopping 
2.8 MHz. The 16bit IIGS System resembles the one for the Mac, BTW.

Not that has anything to do with Linux, but... :) Any questions on the 
IIGS, drop me a line. 

--Markus               
mw@spinfo.uni-koeln.de            # rm -rf / and one was assaulted...peanut


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

Subject: Re: kernel question, memory usage
From: boekhold@morra.et.tudelft.nl (Maarten Boekhold (Who'd you expect??))
Date: 11 May 94 10:52:22 +0200

Klaus ZLOEBL (zloebl@piis10.joanneum.ac.at) wrote:
> Having following symptoms:
> program 27Mb size,
> PC 12Mb RAM, 16Mb swap, kernel 0.99pl14 .. 1.1   
> PC 8Mb RAM, 8Mb swap, kernel 0.99pl13 .. 1.1

> if i start the program on the first PC (12+16Mb) i get a seg.fault in libc_init

> starting it on the 2nd PC (8+8Mb) with kernel 0.99pl13 it runs (some 20Mb 
>  shared mem )
> starting it on the same (2nd) PC with any higher kernel i get the same 
> seg.fault as on the first PC.

> (sorry, i don't have the sources for pl13, and my compiled kernel does not
>  run on the 1st Pc, so i can not test it)


> after shrinking my program (to ~10Mb) it runs again on both PC's with all 
> kernels.

Well, it couldn't possibly have something to do with 12+16 being 28, 
which is only 1 mb above your 27 mb program? (which leaves you then only 
1 mb for system-tasks/resources). The second pc adds up to 8+8=16 Mb, 
which is definitely not enough for a 27 Mb program....

On the other hand.... 10 Mb fits in both

Maarten

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

Crossposted-To: comp.os.linux.misc
Subject: Re: COMMODORE CALLS IT QUITS
From: boekhold@morra.et.tudelft.nl (Maarten Boekhold (Who'd you expect??))
Date: 11 May 94 10:59:15 +0200

Alexandra Griffin (acg@kzin.cen.ufl.edu) wrote:
> In article <2q3q5a$8ht@clarknet.clark.net>, Ken Bass <kbass@clark.net> wrote:
> >: I guess this means that the market for PCs will be focused around the
> >: Intel, MIPS, Sparc and powerPC series of chips.
> >
> >  As opposed to what- the C64, Vic20, or Amiga chip?

> The 64 & vic were 6502-based-- no danger of that architecture
> re-emerging, I hope, even though they did manage to take it up to 32
> bits at one point (68C832?).  The Amigas were MC68K machines.  Quite

The 68000 (A1000, A500, A2000) work internally with 32 bits. But it has 
only a 24 bits adress-bus and a 16 bit data-bus. same for 68010. Since 
teh 68020 the microprocessors were completely 32 bit. The thing you 
mention is prbably the 68332, which is a microcontroller (notice the 
_controller_). It incorporates extra interfaces (serial etc. timers 
internally...) 

> ahead of their time in 1985 (I had an A1000), when CGA was still
> considered high resolution, but it's a pity Commodore kind of let them
> die out...

> It would be interesting if HP purchased rights to the Commodore
> product line... PA-RISC based Amigas would be quite nice!

It would be nice out of speedconsiderations, but you would loose binary 
compatibility (thought they could do something like apple with their new 
powermac).

Ok, enough talkabout this. Oh, one more thing, i've heard that 'a 
japanese company' was most likely to take over the amiga line. The 
company probably being sony. I'm not sure I like that :-(

Maarten

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

From: jcl1008@cus.cam.ac.uk (J.C. Longley)
Crossposted-To: rec.games.programmer,comp.windows.x
Subject: Re: wt news--version 0.02 - port to MSDOS
Date: 13 May 1994 10:31:03 GMT

In article <1994May11.145743.18853@cc.usu.edu>,  <sl859@cc.usu.edu> wrote:
>I ported 0.04 to Watcom C ... I'll post the appropriate files if you'd like.
>Joshua Jensen
PLEASE!  JEZZA


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

From: archie@qin.CS.Berkeley.EDU (Archie Cobbs)
Subject: Re: Apple filesystem and Appletalk
Date: 11 May 94 21:27:02 GMT

adamsvm@Dunx1.OCS.Drexel.Edu (Vince Adams) writes:

>       I have searched far and wide (short and narrow as well) for code to 
>mount an apple filesystem (hard drive or floppy) under Linux.  I have come to 
>the conclusion that there is nothing in the works.  

There is a program that will mount an Apple floppy (3.5" 1.4M only).
You can read but not write the disk. It's called "hfs" I think...
Check on sunsite (grep through the master index for string "hfs").

-Archie


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

From: stigers@mail.physics.utah.edu (charles stigers)
Subject: SOME select() THANKS...
Date: Thu, 12 May 1994 21:33:55 GMT

   To the _ONE_ person who responded to my questions
concerning the select() function - THANK YOU.  I'm
sorry, but I lost your Email address or I would have
sent this to you directly.

   To the rest... you were of no help, but that goes
without saying now doesn't it...  If your don't want
that hanging over you, giving you the "guilts" so badly
that you can't go to sleep at night - write me and ask
me what my questions WERE!

   Charles Stigers
   stigers@mail.physics.utah.edu

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

From: cgori@isengard.stanford.edu (Christopher D. Gori)
Subject: Kernel errors (bad inode) - leading to eventual failure
Date: 11 May 1994 00:59:26 GMT

[This is long because of the syslog entries at the end]

Hello all, I'm running 1.1.10 right now, getting a series of errors for bad
inode on my system (/dev/hdb1 is Linux ext2fs part'n, on a Maxtor 213 IDE).
I have 4MB system memory, 16MB swap on /dev/hdb2.  I wish I had more RAM,
but RAM=$$ now.

The crux of it all is that these errors don't drag the system down
completely, but they eventually pile up all over the place whenever I start
a process, crond runs, whatever.  Then it crashed today after spewing these
messages all day - unfortunately I thought that message had been logged, but
looking now it hasn't.  It ended of course in "kernel panic - trying to kill
swapper", but was preceded by some warnings about bad data structures on the
disk.

Also, some of these seem to be due to bad sectors (?) on my hd.  Is there a
way to explicity fsck my root partition to try to mark and relocate bad
sectors?  I looked at the man page for e2fsck and saw something about taking
sector file inputs but what generates this list for you?

Which of these should I nm zSystem on to find the addresses? I want to get
this cleaned up / debugged.  I did a couple and they were pretty useless to
me, 0010:00000003 follows 00000001 a CF_MASK, but it's so near the top,
00000009 follows 0000008 a EDX  and  00000008 a priority.
The dereference error leads me to believe there's a pointer arithmetic
problem here but...


        Thanks,

        Chris Gori
        cgori@leland.stanford.edu
        cgori@isengard.stanford.edu

(from syslog)
==================
May 10 02:42:00 isengard kernel: <2>EXT2-fs error (device 3/65): \
ext2_read_inode: bad inode number: 1672040
May 10 02:42:00 isengard kernel: <1>Unable to handle kernel NULL pointer \
dereference at kernel address 00000003
May 10 02:42:00 isengard kernel: <1>current->tss.cr3 = 00338000, $r3 = 00338000
May 10 02:42:00 isengard kernel: <1>*pde = 00102027
May 10 02:42:00 isengard kernel: <1>*pte = 00000027
May 10 02:42:00 isengard kernel: <6>Oops: 0000
May 10 02:42:00 isengard kernel: <6>EIP:    0010:00000003
May 10 02:42:00 isengard kernel: <6>EFLAGS: 00010246
May 10 02:42:00 isengard kernel: <6>eax: 002618c0   ebx: 00000083 \
  ecx: 001cf000   edx: 00263000
May 10 02:42:00 isengard kernel: <6>esi: 0000844d   edi: 00098ee0 \
  ebp: 00231e00   esp: 00231d90
May 10 02:42:00 isengard kernel: <6>ds: 0018   es: 0018   fs: 002b \
  gs: 002b   ss: 0018
May 10 02:42:00 isengard kernel: <6>Process crond (pid: 7882, process \
nr: 16, stackpage=00231000)
May 10 02:42:00 isengard kernel: <6>Stack: 0014a459 00198368 \ 
0000844d 00000001 00098ee0 
May 10 02:42:00 isengard kernel: <6>Code: 00 f4 06 70 00 16 00 8c 04 f4 06
May 10 02:46:00 isengard kernel: <2>EXT2-fs error (device 3/65): \
ext2_read_inode: bad inode number: 1672040
May 10 02:46:00 isengard kernel: <1>Unable to handle kernel paging\
 request at kernel address 009d2ec4
May 10 02:46:00 isengard kernel: <1>current->tss.cr3 = \
001bb000, ^Zr3 = 001bb000
May 10 02:46:00 isengard kernel: <1>*pde = 0009e027
May 10 02:46:00 isengard kernel: <1>*pte = 00000000
May 10 02:46:00 isengard kernel: <6>Oops: 0000
May 10 02:46:00 isengard kernel: <6>EIP:    0010:00000009
May 10 02:46:00 isengard kernel: <6>EFLAGS: 00010246
May 10 02:46:00 isengard kernel: <6>eax: 0004f8c0 ebx: 00000083 ecx: \
001cf000 edx: 003c6000
May 10 02:46:00 isengard kernel: <6>esi: 0000b2fd   edi: 00098ee0 \
  ebp: 00282f80   esp: 00282f10
May 10 02:46:00 isengard kernel: <6>ds: 0018   es: 0018   fs: 002b \
  gs: 002b   ss: 0018
May 10 02:46:00 isengard kernel: <6>Process crond (pid: 7896, process \
nr: 16, stackpage=00282000)
May 10 02:46:00 isengard kernel: <6>Stack: 00280018 00000018 \
0014a459 00198368 0000b2fd 
May 10 02:46:00 isengard kernel: <6>Code: 00 8c 04 f4 06 70 00 \
f4 06 70 00 54 ff 00 
May 10 04:03:00 isengard kernel: <2>EXT2-fs error (device 3/65): \
ext2_read_inode: bad inode number: 1672040
May 10 04:03:00 isengard kernel: <1>Unable to handle kernel paging request \
at kernel address 00d8ca9c
May 10 04:03:00 isengard kernel: <1>current->tss.cr3 = 003a2000,\
 ^Dr3 = 003a2000
May 10 04:03:00 isengard kernel: <1>*pde = 00000000
May 10 04:03:00 isengard kernel: <6>Oops: 0000
May 10 04:03:00 isengard kernel: <6>EIP:    0010:00000009
May 10 04:03:00 isengard kernel: <6>EFLAGS: 00010a82
May 10 04:03:00 isengard kernel: <6>eax: 002e8620   ebx: 00000083   \
ecx: 001cf000   edx: 00212000
May 10 04:03:00 isengard kernel: <6>esi: 0000844d   edi: 00098ee0   \
ebp: 003a3e00   esp: 003a3d88
May 10 04:03:00 isengard kernel: <6>ds: 0018   es: 0018   fs: 002b  \
 gs: 002b   ss: 0018
May 10 04:03:00 isengard kernel: <6>Process sh (pid: 8175, process \
nr: 17, stackpage=003a3000)
May 10 04:03:00 isengard kernel: <6>Stack: 003a0018 00000018 0014a459 \
00198368 0000844d 
May 10 04:03:00 isengard kernel: <6>Code: 00 8c 04 f4 06 70 00 f4 06 70 00\
54 ff 00 f0 43 eb 00 f0 eb 
May 10 04:04:00 isengard kernel: <2>EXT2-fs error (device 3/65): \
ext2_read_inode: bad inode number: 1672040
May 10 04:04:00 isengard kernel: <1>Unable to handle kernel paging request
\ at kernel address 00a39d7c
May 10 04:04:00 isengard kernel: <1>current->tss.cr3 \
= 0035d000, ^Zr3 = 0035d000
May 10 04:04:00 isengard kernel: <1>*pde = 0009e027
May 10 04:04:00 isengard kernel: <1>*pte = 00000000
May 10 04:04:00 isengard kernel: <6>Oops: 0000
May 10 04:04:00 isengard kernel: <6>EIP:    0010:00000009
May 10 04:04:00 isengard kernel: <6>EFLAGS: 00010283
May 10 04:04:00 isengard kernel: <6>eax: 0004c7e0   ebx: 00000083  \
 ecx: 001cf000   edx: 002ed000
May 10 04:04:00 isengard kernel: <6>esi: 000026ee   edi: 00098ee0 \
  ebp: 002ecf20   esp: 002ecea8
May 10 04:04:00 isengard kernel: <6>ds: 0018   es: 0018  \
 fs: 002b   gs: 002b   ss: 0018
May 10 04:04:00 isengard kernel: <6>Process touch (pid: 8178, \
process nr: 17, stackpage=002ec000)
May 10 04:04:00 isengard kernel: <6>Stack: 002e0018 00000018 \
0014a459 00198368 000026ee 
May 10 04:04:00 isengard kernel: <6>Code: 00 8c 04 f4 06 70 00 f4 06 \
70 00 54 ff 00 

etc.


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


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