Subject: Linux-Development Digest #848
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, 21 Jun 94 03:13:10 EDT

Linux-Development Digest #848, Volume #1         Tue, 21 Jun 94 03:13:10 EDT

Contents:
  Beta testers wanted (David Miller)
  Re: Zilog SCSI controller chip used to drive my CDROM. (Alex Freed)
  Re: Disk-compression for Linux (Brett Coon)
  Re: assembly language & Linux (AlphaPC!) (Gerry Snyder)
  Solaris x86 disk = 82 = Linux swap (Tibor Polgar)
  Re: Novell NCP Documentation Available! (was Re: IPX Netware Protocol) (Brandon S. Allbery)
  Re: Solaris x86 disk = 82 = Linux swap (Brandon S. Allbery)
  Novell NCP Documentation Available! (was Re: IPX Netware Protocol) (Pete Kruckenberg)
  Re: problems with kernel-modules (Vassili Leonov)
  some rsh stuff broken with 1.1.20 (Ronald Ohst)
  Re: Linux and symmetrical multiprocessing (Rob Janssen)
  Re: DOSEMU and Novell (Rob Janssen)
  Re: anybody working on a MULTICAST kernel? (Rob Janssen)
  Problems with kernel 1.1.20 and UltraStor 24f EISA SCSI host adapter (Anders Hedborg)

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

From: davem@er4.rutgers.edu (David Miller)
Subject: Beta testers wanted
Date: 20 Jun 94 21:15:37 GMT

Hello, I recently embarked on a port of term118 to c++ code to teach
myself OO design. I have basically taken the basic data types of the
client packet modules and made them self sufficient classes. Upon
completion I would be interested if anyone in netland would like to
give my version a spin. I use term heavily but there are some features
that I don't use too often (such as share mode) and would be less
likely to catch bugs in these areas.
        I will also be writing a little paper on my design decisions
and the methodology I used to design the classes. Therefore, anyone
interested in seeing what I have right now and might want to offer
suggestions are more than welcome.

Please mail all responses to davem@eden.rutgers.edu

Thanks,
David S. Miller
davem@eden.rutgers.edu

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

From: freed@europa.mv.us.adobe.com (Alex Freed)
Subject: Re: Zilog SCSI controller chip used to drive my CDROM.
Date: Mon, 20 Jun 1994 21:03:49 GMT

In article <1994Jun20.160519.13815@se01.elk.miles.com> geis@se01.elk.miles.com (Jerry Geis) writes:

   Newsgroups: comp.os.linux.development
   From: geis@se01.elk.miles.com (Jerry Geis)
   Organization: Miles, Inc.
   Date: Mon, 20 Jun 1994 16:05:19 GMT

   I have a Media Vision MultiMedia16 sound card and CDROM. MEdia Vision
   told me the controller is a Zilog Z0538010VSC. All I need now is 
   someone who can translate this into one of the options used in the 
   make config so I can get my CDROM to work.

   Does anyone know what that would be?

   Thanks,
           jerry                        geis@se01.elk.miles.com

   PS. Please mail replies to me...

This is an NCR 5380 second-sources by Zilog. There is a "generic 5380" Linux
driver available.
-- 
 _______________________________________________________
| -Alex Freed (The opinions expressed are my own.       |                   
|               However everyone is entitled to them.)  |                   
| freed@adobe.com                                       |
 -------------------------------------------------------

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

From: brett@iit.com (Brett Coon)
Subject: Re: Disk-compression for Linux
Date: Mon, 20 Jun 1994 21:21:32 GMT

kevin@valis.worldgate.edmonton.ab.ca (Kevin B. Fluet) writes:

>I think  on-the-fly compression has been discussed by many people over the
>last year, but nothing has come of it.

I was under the impression that a compressed filesystem is currently
available.

> Basically, with hard drive prices
>dropping dramatically every week (almost), it may not be worth the trouble. 
>Prices are WELL under $1/MB these days.

Part of the attraction of disk compression is that the benefit increases
with hard disk size.  The more hard disks you buy, the more storage
you can gain by using compression.

> Also, with the PROVEN unreliability
>of compressed file systems, you would only have a few people willing to use
>it.  

Compressed file systems are not inherently unreliable.  By its very
nature, compression eliminates redundancy, which makes it harder to
recover from disk errors.  However, a well-designed system with error
control built-in could be more reliable than an uncompressed system.

-Brett

--
+------------------------------------------------------------+
| Brett Coon  -  brett@iit.com or brettc@leland.stanford.edu |
| Integrated Information Technology Inc. (408) 727-1885 x367 |
+------> finger brettc@leland.stanford.edu for PGP key <-----+

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

From: Gerald.C.Snyder@jpl.nasa.gov (Gerry Snyder)
Subject: Re: assembly language & Linux (AlphaPC!)
Date: 20 Jun 1994 21:48:37 GMT

In article <2tth03$43d@nyx10.cs.du.edu>, colin@nyx10.cs.du.edu (Colin Plumb) says:
>
>In article <2tmpm0$ejg@klaava.helsinki.fi>,
>Linus Torvalds <torvalds@cc.Helsinki.FI> wrote:
>> Any porters out there should feel happier knowing that DEC is shipping
>> me an AlphaPC that I intend to try getting linux running on: this will
>> definitely help flush out some of the most flagrant unportable stuff. 
>
>So, who at DEC do we thank for thus supporting free software?  They're
>probably not too altruistic, thinking that an AlphaPC is a very cheap
>way to get a working OS, but it's nice to know that there are people in
>authority that know that free software exists, and even occasionally
>sells machines, and I'd like to encourage them with praise if nothing
>else.
>-- 
>        -Colin

Agreed!!  Enlightened self interest may be self interest, 
but at least it is enlightened.

Gerry

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

From: tlp00@mtlyell.spg.amdahl.com (Tibor Polgar)
Subject: Solaris x86 disk = 82 = Linux swap
Date: Mon, 20 Jun 1994 21:04:23 GMT

This may be known, but in case it isn't.  Linux has defined filesystem type 82 as 
linux swap.  This same filesystem type is used by Solaris to define UFS.  Now since 
i assume Sun won't change their number, will Linux?  Do i report this problem as a 
kernel bug or what?

-- 
Tibor Polgar
tlp00@spg.amdahl.com, Amdahl Corp, ph.(408) 944-3500

-- all disclaimers apply  --

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

From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Novell NCP Documentation Available! (was Re: IPX Netware Protocol)
Date: Mon, 20 Jun 1994 23:48:35 GMT

In article <2u4tr4$3bq@magus.cs.utah.edu>, kruckenb@sal.cs.utah.edu (Pete Kruckenberg) says:
+---------------
| By any chance, has anyone tried to implement NCP using the information
| in Pawel Szczerbina's article in Dr. Dobbs on Novell's NCP
| ("Undocumented Corner: Novell's Netware Core Protocol", Dr. Dobbs,
+------------->8

Yes.  The information is reportedly buggy and incomplete, but I think it's
being used as a starting point to "black-box" a working NCP layer.

++Brandon
-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
Friends don't let friends load Windows NT.              Linux iBCS2 emulation

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

From: bsa@kf8nh.wariat.org (Brandon S. Allbery)
Subject: Re: Solaris x86 disk = 82 = Linux swap
Date: Mon, 20 Jun 1994 23:55:00 GMT

In article <TLP00.94Jun20140423@mtlyell.spg.amdahl.com>, tlp00@mtlyell.spg.amdahl.com (Tibor Polgar) says:
+---------------
| This may be known, but in case it isn't.  Linux has defined filesystem type 82 as 
| linux swap.  This same filesystem type is used by Solaris to define UFS.  Now since 
+------------->8

It doesn't matter, since *ixes don't use the partition type set in fdisk.  As
long as you stay away from DOS / Netware / OS/2 / NT partition types (those
operating systems *do* use the partition type) it doesn't matter what you use.
In particular, Linux is *not* going to suddenly start swapping in your Solaris
file system on its own just because its partition type is "Linux swap"; nor
will it stop you from doing a "mkswap"/"swapon" on a type 83 (Linux e2fs)
partition.

++Brandon
-- 
Brandon S. Allbery         kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
Friends don't let friends load Windows NT.              Linux iBCS2 emulation

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

From: kruckenb@sal.cs.utah.edu (Pete Kruckenberg)
Subject: Novell NCP Documentation Available! (was Re: IPX Netware Protocol)
Date: 20 Jun 1994 20:23:00 GMT

Byron A Jeff (byron@gemini.cc.gatech.edu) wrote:
: In article <perin.29.0034A6B9@mail.med.cornell.edu>,
: Lewis Perin <perin@mail.med.cornell.edu> wrote:
: -In article <Cro18F.Lq@pe1chl.ampr.org> rob@pe1chl.ampr.org (Rob Janssen) writes:
: ->From: rob@pe1chl.ampr.org (Rob Janssen)
: ->Subject: Re: IPX Netware Protocol
: ->Date: Sun, 19 Jun 1994 22:31:26 GMT
: -
: ->In <2u27qe$h5n@seralph0.essex.ac.uk> peddmv@sunlab40 (Peddlesden M J) writes:
: -
: ->>Can someone tell me if the IPX/SPX networking protocol has been
: ->>implemented in the networking support of Linux?
: -
: ->You can access Netware from dosemu, where you can load the usual
: ->Netware client software.
: ->IPX is in the Linux networking, but SPX and NCP aren't, so you can't
: ->do it directly from Linux.
: -
: -This granted, shouldn't it be possible to use IPX like UDP at the socket 
: -level, i.e. without DOSEMU in a "native" Linux program?  If so, can anyone 
:
: My understanding is that the upper level protocols of Netware are not
: pubclicly available. So while IPX can be put into the kernel (and in fact
: is) the code in netx cannot.

By any chance, has anyone tried to implement NCP using the information
in Pawel Szczerbina's article in Dr. Dobbs on Novell's NCP
("Undocumented Corner: Novell's Netware Core Protocol", Dr. Dobbs,
Nov. 1993, pp. 123-132). Pawel covers the packet contents and sizes of
NCP, including all the NCP function and sub-function codes. He also
has some sample code (for DOS) available via FTP at ftp.mv.com in
pub/ddj. The file should be something like NCPTEST (I haven't
checked--this is just what the article says).

I don't know much about Linux network drivers, but the article seems
to have enough information to talk NCP to a server from a client.
Maybe someone more familiar with the IPX stuff in Linux could take a
look at this article (I'd be glad to fax/mail copies of it if you
can't get ahold of the magazine).

Pete Kruckenberg
kruckenb@sal.cs.utah.edu


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

From: vassili@cs.sunysb.edu (Vassili Leonov)
Subject: Re: problems with kernel-modules
Date: 20 Jun 1994 16:17:41 GMT

luca@genova.world wrote:
: >it happend that insmod found some 'unresolved externels' when inserting
: >the driver, so i examined the kernel-symbol-table which is read by insmod.
: >i found out that some symbols, which are not in this list, may be used, while
: >others may not.

: This has happened also to me but then thanks to the author of this
: very useful package i found the problem.
: In the kernel directory of the kernel source files tree there is a
: file called "ksyms.c" where the symbol table for the kernel is
DONT'T DO THIS!!! Move to the kernel version at least 1.1.13 - all this stuff
is included there - and in a much cleaner way! Don't use modules on the
older versions of the kernel.
Vassili.

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

From: ohst@cogsci.ucsd.edu (Ronald Ohst)
Subject: some rsh stuff broken with 1.1.20
Date: 20 Jun 1994 23:02:32 GMT

Newsgroups: comp.os.linux.devel
Subject: 1.1.20 broke my rsh script
Summary: 
Followup-To: 
Distribution: world
Organization: University of California, San Diego
Keywords: 

I installed 1.1.20 this morning and one of my shell scripts died.
This shell script just does something like this
        
#! /bin/bash
rsh remote-computer remote-computer-sh-script

The remote-computer-sh-script among other things runs a program
that launches the rpc.nfsd  (there *is* a reason for doing this --
has to do with nfsd caching file handles and sharing an optical
disk via NFS and not being able to umount an optical disk because nfsd
things it is busy since a file handle is cached, even though it's
not busy, so I hafta kill rpc.nfsd umount, and restart nfsd...
it's a long story).

Anyway, this works fine with 1.1.18, but not with 1.1.20.  Now,
after I run this shell script, if I do a ps -ae | grep nfsd, I 
get something like

        97 con S    0:00 (rpc.nfsd)

but with 1.1.18 I get

        97 con s    0:00 /usr/sbin/rpc.nfsd

And if I run the remote-computer-sh-script on the remote-computer
I get what I used to get with 1.1.18.

Does anybody know what the parenthesis mean in ps?
Whatever they mean, rpc.nfsd isn't working properly when it says 
(rpc.nfsd).  But it does when ps gives the full path.

Any ideas?

(email preferred).
Ron Ohst                                rohst@ucsd.edu, (619) 534-2440
University of California, San Diego     Department of Cognitive Science

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Linux and symmetrical multiprocessing
Reply-To: pe1chl@rabo.nl
Date: Mon, 20 Jun 1994 21:51:27 GMT

In <HARE.94Jun20141500@zarquon.mathi.uni-heidelberg.de> hare@zarquon.mathi.uni-heidelberg.de (Hannes Reinecke) writes:

>In article <2ts1sk$hr9@sun.cais.com> ericy@cais.cais.com (Eric Youngdale) writes:

>   [Bunch of attributions deleted to satify my anal newsreader which 
>   complains about the ratio of new/old being too low]
>   >>>Now if we can just figure out the organization which lurks behind the 
>   >>>nom-de-compute "Eric Youngdale".
>   >
>   >>  I need to get a life.  Perhaps I should say that we need to get a 
>   >>life :-).
>   >
>   >You probably have to go on a world tour to show the folks that you really
>   >exist...

>          Well, I will be in Heidelberg.  Not being a student means that I 
>   cannot take off for weeks at a time like some people do :-).

>   -Eric

>Didn't impress me.
>I'll be in Heidelberg, too.

>Hannes

Ok.  So you are appointed to tell us all that Eric really exists.

(I can tell you that Linus exists.  I saw him at the NLUUG meeting in
the Netherlands :-)

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

Crossposted-To: comp.os.linux.help
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: DOSEMU and Novell
Reply-To: pe1chl@rabo.nl
Date: Mon, 20 Jun 1994 21:55:20 GMT

In <CrpEyr.7z@aston.ac.uk> evansmp@mb52112.aston.ac.uk (Mark Evans) writes:

>Alan Cox (iiitac@uk.ac.swan.pyr) wrote:
>: In article <2tuu3f$ght@blackbird.db.erau.edu> andersoa@news.db.erau.edu (Andrew Anderson) writes:
>: >Can you go into more detail on this?  Are you proposing to setup the Linux
>: >box with its own IPX network number?  Or are you referring to TCP/IP?

>: With its own IPX network number, and with each node address a magic number

>A nice trick would be to be able to assign an IPX network number "automagically",
>using the IP address might work in many cases.

>: so it appears the Linux box is a gateway to a (huge) network

>To undrestand this it helps to understand how IPX works. Try reading
>the "router" documentation on ftp.novell.com

I'll have a look at that.  I only hoped that NCP would be sophisticated
enough that it could maintain several associations between the same
server/client pair.  Alas, from the above thread it seems it isn't.

(but then, how does OS/2 do this.  do they use a network as well?)

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: anybody working on a MULTICAST kernel?
Reply-To: pe1chl@rabo.nl
Date: Mon, 20 Jun 1994 21:58:06 GMT

In <1994Jun20.163737.18247@ibr.cs.tu-bs.de> thuerman@ibr.cs.tu-bs.de (Urs Thuermann) writes:

>terjeve@ifi.uio.no (Terje Vernly) writes:

>>With a BIG smile, taylor@stimpy.eecis.udel.edu (Howard "the Duck" Taylor) wrote:

>>> has anyone stared work on a multicast kernel patch?  I know of
>>> sunos kernels with this ability, and sgi ships their systems
>>> with mutlicast support...

>>I started implementing the IP-Multicast extensions some time ago, and I
>>hope to have a working multicast-kernel ready by mid-July.

>What is IP-Multicast?

See RFC-1112

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: ahe@elixir.e.kth.se (Anders Hedborg)
Subject: Problems with kernel 1.1.20 and UltraStor 24f EISA SCSI host adapter
Date: 20 Jun 1994 23:40:35 GMT

Hi,

This is probably allready well known by now but as there are perhaps not so 
many of us using the UltraStor 24f EISA SCSI adapter - I thought I might 
as well post.

I'm having problems with v1.1.20 and my UltraStor 24f.

My machine is a IWILL 486 EI (Same as AIR :-) )
486DX2
16 Mb mem
UltraStor 24f EISA SCSI Host Adapter
2x Seagate 3390N Disks
SONY CD-ROM CDU-8003A
1x floppy drive 3 1/2" FDC version 0x9
Cirrus 5428 VLB video
wd8013 ethernet card

Writes to disk results in corrupted data. :-(


Regards...

Anders



sample messages in /var/adm/messages:

Jun 20 22:25:16 SL73-102 kernel: floppy 0: data CRC error: track 3, head 0, sector 18
Jun 20 22:25:29 SL73-102 last message repeated 11 times
Jun 20 22:25:29 SL73-102 kernel: Reset-floppy called
Jun 20 22:25:30 SL73-102 kernel: floppy 0: data CRC error: track 3, head 0, sector 18
Jun 20 22:25:30 SL73-102 kernel: Reset-floppy called
Jun 20 22:25:30 SL73-102 kernel: floppy 0: data CRC error: track 3, head 0, sector 18
Jun 20 22:25:30 SL73-102 kernel: Reset-floppy called
Jun 20 22:25:30 SL73-102 kernel: floppy 0: data CRC error: track 3, head 0, sector 18
Jun 20 22:25:30 SL73-102 kernel: Reset-floppy called
Jun 20 22:25:30 SL73-102 kernel: floppy 0: data CRC error: track 3, head 0, sector 18

Jun 20 22:25:47 SL73-102 kernel: dev 0200, sector 136
Jun 20 22:25:47 SL73-102 kernel: floppy I/O error
Jun 20 22:25:47 SL73-102 kernel: dev 0200, sector 138
Jun 20 22:26:17 SL73-102 kernel: VFS: Disk change detected on device 2/0
Jun 20 22:27:10 SL73-102 kernel: VFS: Disk change detected on device 2/0
Jun 20 22:27:19 SL73-102 kernel: VFS: Disk change detected on device 2/0
Jun 20 22:27:43 SL73-102 kernel: scsi0 : reseting for second half of retries.
Jun 20 22:27:43 SL73-102 kernel: US14F: reset: called
Jun 20 22:27:43 SL73-102 kernel: SCSI disk error : host 0 id 1 lun 0 return code = 27070000

Jun 20 23:41:28 SL73-102 kernel: scsidisk I/O error: dev 0815, sector 174376
Jun 20 23:42:18 SL73-102 kernel: scsi0 : reseting for second half of retries.
Jun 20 23:42:18 SL73-102 kernel: US14F: reset: called
Jun 20 23:42:18 SL73-102 kernel: scsi0 : reseting for second half of retries.
Jun 20 23:42:18 SL73-102 kernel: US14F: reset: called
Jun 20 23:42:18 SL73-102 kernel: SCSI disk error : host 0 id 0 lun 0 return code = 27070000
Jun 20 23:42:18 SL73-102 kernel: scsidisk I/O error: dev 0801, sector 442
Jun 20 23:42:18 SL73-102 kernel: SCSI disk error : host 0 id 0 lun 0 return code = 27070000
Jun 20 23:42:18 SL73-102 kernel: scsidisk I/O error: dev 0801, sector 726
Jun 20 23:42:18 SL73-102 kernel: scsi0 : reseting for second half of retries.
Jun 20 23:42:18 SL73-102 kernel: US14F: reset: called
Jun 20 23:42:18 SL73-102 kernel: SCSI disk error : host 0 id 0 lun 0 return code = 27070000
Jun 20 23:42:18 SL73-102 kernel: scsidisk I/O error: dev 0801, sector 728
Jun 20 23:42:18 SL73-102 kernel: scsi0 : reseting for second half of retries.
Jun 20 23:42:18 SL73-102 kernel: US14F: reset: called
Jun 20 23:42:18 SL73-102 kernel: SCSI disk error : host 0 id 0 lun 0 return code = 27070000
Jun 20 23:42:18 SL73-102 kernel: scsidisk I/O error: dev 0801, sector 730


. 
--
---
                                                     Anders Hedborg
                                                     e-mail: ahe@cadcam.kth.se

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


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