Subject: Linux-Development Digest #949
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, 26 Jul 94 18:13:11 EDT

Linux-Development Digest #949, Volume #1         Tue, 26 Jul 94 18:13:11 EDT

Contents:
  Re: PCI ethernet cards supported? (Donald Becker)
  Re: IDE patch won't work w/new kernels? (Mark Lord)
  ERROR: Not mounting SCSI cd-rom with 1.1.35 (Andre U Manoel)
  Re: ERROR: Not mounting SCSI cd-rom with 1.1.35 (Andre U Manoel)
  1.1.35 make problem: exhausted memory (Peter Schmitt)
  Re: NFS development?? (David Ferovick)
  Re: New kernel message at boot time? (David Holland)
  Re: 1.1.36 make problem: 'NULL' undeclared (James Smith)
  Re: Voice Mail cards. (Matt Womer)
  Re: DOES ANYONE KNOW ABOUT THE MAILINGLISTS? (hello, is anyone there?) (Frank Derichsweiler)
  Re: Xfree86: increase pallate? (Eberhard Moenkeberg)
  Re: buffer cache or isofs bug? (Eberhard Moenkeberg)
  Re: IDE patch won't work w/new kernels? (Mark Lord)
  Re: threads in kernel (Larry McVoy)
  Re: threads in kernel (Rob Janssen)
  Re: DOS EMU under 1.1.34 (Rob Janssen)

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

From: becker@cesdis.gsfc.nasa.gov (Donald Becker)
Subject: Re: PCI ethernet cards supported?
Date: 25 Jul 1994 13:24:26 -0400

In article <30s64d$ba7@usenet.rpi.edu>,
CesareMancini(KB2NOW) <mancic@rembrandt.its.rpi.edu> wrote:
>are there any PCI e-net cards that are supported (in any way)
>the ACM is putting together a Linux machine, and we're planing on getting 
>PCI with the NCR scsiany help is appreciated

There is a good chance that a PCI ethercard based on an AMD PCnet-PCI chip
(79C970, or 79C974 w/SCSI) will work if it's configured at one of the
standard I/O addresses: 0x300, 0x320, 0x340 or 0x360.

Note:   This is from reading the databook -- unfortunately I don't
have a PCI card to test with.  I'm currently working on updating the LANCE
driver to recognize the newer chips, and I'll probably write a special
PCnet32 device driver to support the 32 bit addressing mode available on
the new VLB and PCI chips.

-- 
Donald Becker                                     becker@cesdis1.gsfc.nasa.gov
USRA Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882         http://cesdis.gsfc.nasa.gov/pub/people/becker/whoiam.html

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

From: mlord@bnr.ca (Mark Lord)
Subject: Re: IDE patch won't work w/new kernels?
Date: 25 Jul 1994 17:09:08 GMT

In article <c9108932.775114211@peach.newcastle.edu.au> c9108932@peach.newcastle.edu.au writes:
>c9219517@sage.newcastle.edu.au (Scott Howard) writes:
>
>>Timo Kokkonen (tjko@tarzan.math.jyu.fi) wrote:
>
>>: IDE Performance Patch v2.0 [by Mark Lord] doesn't work with new 
>>: WD540 drives??? Or is it just my kernel 1.1.30 that causes the problem?
>
>>There's a very simple reason for this - they are already in the kernel!!

Ahh.. at last.  Caught me by suprise.  
>
>However I've been unable to find a hdparm program to dynamically set the
>ide options... is there one floating around that will work with the 
>ide patches that are now standard in the kernel or will I have to
>resort to changing the defines in hd.c ?

You should be able to just recompile the hdparm.c program from ide20.patch.gz
with the new kernel for now -- source included below for convenience.

I will upload a replacement file to tsx-11 shortly.  

USE AT YOUR OWN RISK -- READ linux/drivers/block/README.hd before trying!!
USE AT YOUR OWN RISK -- READ linux/drivers/block/README.hd before trying!!
USE AT YOUR OWN RISK -- READ linux/drivers/block/README.hd before trying!!

--- linux118/drivers/block/hdparm.c     Wed Dec 31 19:00:00 1969
+++ linux/drivers/block/hdparm.c        Tue Apr  5 21:09:27 1994
@@ -0,0 +1,48 @@
+/* make using:    cc -O -o /usr/bin/hdparm hdparm.c */
+
+#include <linux/hdreg.h>
+#include <sys/ioctl.h>
+#include <stdio.h>
+#include <sys/types.h>
+#include <unistd.h>
+#include <fcntl.h>
+
+/* extern int hd_ioctl(struct inode * inode, struct file * file,
+ *                     unsigned int cmd, unsigned long arg);
+ */
+
+
+void main (int argc, char *argv[])
+{
+       int fd, mrc, irc;
+       static long mcount, irqmode;
+
+       if (argc != 4 && argc != 2) {
+               fprintf(stderr,"Usage:  %s  <device>"
+                              " [<MultModeCount:0-64> <unmask:0/1>]\n", *argv);
+               exit (1);
+       }
+
+       fd = open (*++argv, O_RDONLY);
+       if (fd < 0) {
+               printf ("open failed - '%s' - %d\n", *argv, fd);
+               exit(1);
+       }
+        if (argc == 4) {
+               mcount = atoi(*++argv);
+               mrc = ioctl (fd, HDIO_SETMULTCOUNT, &mcount);
+               /* note that the new mcount does not take effect
+                  until the next disk I/O operation, so if we were
+                  to query it before then, the old value will show.
+                  Also, the drive may reject the new value, which will
+                  result in multiple mode being turned OFF completely! */
+               irqmode = atoi(*++argv);
+               irc = ioctl (fd, HDIO_SETUNMASKINTR, &irqmode);
+        }
+        else {
+               mrc = ioctl (fd, HDIO_GETMULTCOUNT, &mcount);
+               irc = ioctl (fd, HDIO_GETUNMASKINTR, &irqmode);
+        }
+       printf("MultModeCount=%d, rc=%d\n", mcount, mrc);
+       printf("unmask=%d, rc=%d\n", irqmode, irc);
+}
-- 
mlord@bnr.ca    Mark Lord       BNR Ottawa,Canada       613-763-7482

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

From: andre@futuro.usp.br (Andre U Manoel)
Subject: ERROR: Not mounting SCSI cd-rom with 1.1.35
Date: 25 Jul 1994 17:15:04 GMT

        Since I upgraded from kernel patchlevel 23 to 35 (due to SCSI
corruption problems I think were widely discussed) I cannot mount my SCSI
cd-rom. On boot-up, I get the message

============= cut here ================================================

Configuring Adaptec at IO:330, IRQ 12, DMA priority 5
scsi0 : Adaptec 1542
scsi : 1 hosts.
  Vendor: MAXTOR    Model: LXT-200S          Rev: 2.11
  Type:   Direct-Access                      ANSI SCSI revision: 01 CCS
Detected scsi disk sda at scsi0, id 0, lun 0
  Vendor: FUJITSU   Model: M2624F-512        Rev: 0405
  Type:   Direct-Access                      ANSI SCSI revision: 01 CCS
Detected scsi disk sdb at scsi0, id 1, lun 0
  Vendor: SONY      Model: CD-ROM CDU-8002   Rev: 1.8g
  Type:   CD-ROM                             ANSI SCSI revision: 01 CCS
Detected scsi CD-ROM sr0 at scsi0, id 2, lun 0
scsi : detected 2 SCSI disks 1 CD-ROM drive total.
Scd sectorsize = 2048 bytes

Linux version 1.1.35 (root@piaget) #1 Mon Jul 25 11:37:22 EST 1994
Partition check:
  sda: sda1
  sdb: sdb1 sdb2
  hda: WDC AC2200F (202MB IDE w/64KB Cache, MaxMult=8)
  hda: hda1 hda2 hda3
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 10284k swap-space

============== cut here ================================================

When trying to mount with, say "mount -t iso9660 /dev/sr0
/others/ftp/pub/cdrom", I get the followin error message:

mount: block device /dev/sr0 is not permitted on its filesystem


It didn't happen before and as I have not been followin the development of
the kernel, I have no idea of what could have caused that. Everything was
fine before. I'm sticking with 1.1.35 because everything else seems fine to
me, it is fast, too.

I'm running on a 486-DX2/66 with 16MB RAM. We had originally installed
Slackware 1.1.0 (I think), but much of it is now changed. The important part
of the configuration is, I think, already up there.


                                                Thanks,
                                                Andre


                                                ""
______________________________________________m_OO_m_________________________

Andre Uratsuka Manoel           Escola do Futuro - Universidade de Sao Paulo
andre@futuro.usp.br             Sao Paulo, Sao Paulo, Brazil
_____________________________________________________________________________






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

From: andre@futuro.usp.br (Andre U Manoel)
Subject: Re: ERROR: Not mounting SCSI cd-rom with 1.1.35
Date: 25 Jul 1994 17:29:37 GMT


        Please do forget about the above message. I just read a post on
comp.os.misc.development and found that all I have to do is to mount the
CD-ROM as readonly. Otherwise it won't. 

        I think now I got that all-right it's time to read once more
news.announce.newusers. Just to make sure I won't post so fast next time.


                                Sorry
                                Andre

                                             `'
___________________________________________m_oo_m____________________________

Andre Uratsuka Manoel           Escola do Futuro - Universidade de Sao Paulo
andre@futuro.usp.br             Sao Paulo, Sao Paulo, Brazil
_____________________________________________________________________________






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

From: pete@geminga.dartmouth.edu (Peter Schmitt)
Crossposted-To: comp.os.linux.admin
Subject: 1.1.35 make problem: exhausted memory
Date: 26 Jul 1994 11:14:36 GMT

My 386 has 5M ram and 5M swap.  I am currently running 1.1.34 and got
the following when trying to make 1.1.35:

make[2]: Entering directory `/usr/src/linux/drivers/char'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer -pipe -m386 -c tty_io.c
In file included from /usr/src/linux/include/linux/sched.h:87,
                 from tty_io.c:45:
/usr/src/linux/include/linux/mm.h:299: virtual memory exhausted
cpp: output pipe has been closed{standard input}: Assembler messages:
{standard input}:0: Fatal error:
virtual memory exceeded
make[2]: *** [tty_io.o] Error 1
--
peter.schmitt@dartmouth.edu             Computing Services
UNIX Systems Specialist                 Dartmouth College
Phn: 603-646-2085                       6028 Kiewit Computation Center
postmaster@dartmouth.edu                Hanover, NH  03755

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

From: davidf@austin.ibm.com (David Ferovick)
Subject: Re: NFS development??
Date: Mon, 25 Jul 1994 15:09:04 GMT

In article <310dnd$l2q@FERRARI.NMC.ED.RAY.COM> heiser@TDWR.ED.RAY.COM (Bill Heiser) writes:
>Hi - 
>
>After running LINUX on a home machine for a year or so, I have recently
>set up a machine at work running LINUX 1.1.x.  A number of other people
>I know at work are either running it or are interested in it.  However
>I have run into a major problem that will severely reduce the usefulness
>of a LINUX box in a business network environment: 
>
> I am seeing severe NFS corruption.
>
>For example I have my mail spool directory NFS-mounted from a SunOS 4.1.2
>system.  Almost daily my mailbox is getting corrupted.  We use NFS-mounted
>mail spools as a matter of routine on all kinds of platforms, without 
>serious problems, so I can only assume the LINUX NFS has problems.
>
>I'm wondering if NFS is something that is actively being worked on and
>debugged in the new LINUX kernels.  I really (really really really) 
>don't want to have to give up on LINUX now! :-)
>

Well, Linux NFS does not have NFS file locking, so using it to mount a mail
spool filesystems is a very bad idea.  The reason for this is that sun 
released the specification for their nfs file locking routines only a few 
months ago and nobody has picked up the specs and coded nfs file locking for
linux and other os'es.  

Dave


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

Subject: Re: New kernel message at boot time?
From: dholland@scws33.harvard.edu (David Holland)
Date: 26 Jul 1994 18:26:09 GMT


torvalds@cc.Helsinki.FI's message of 23 Jul 1994 00:54:10 +0300 said:

 > With 1.1.33 (and now 1.1.34 which cleans up some more and fixes ptrace,
 > for example), the kernel remembers which pages have been swapped out
 > even after thay are swapped in again so that the next time they are
 > swapped out they don't even need to be written to disk if they haven't
 > changed in the meantime.  

How does Linux handle swapping zeroed pages which haven't been
touched? (Does it swap them out, or just discard them?) Some
recent experience with some experimental stuff suggests that it makes
a big improvement in low memory conditions for programs with lots of
BSS. 

--
   - David A. Holland          | "The right to be heard does not automatically
     dholland@husc.harvard.edu |  include the right to be taken seriously."

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

From: smith@meishan.animal.uiuc.edu (James Smith)
Subject: Re: 1.1.36 make problem: 'NULL' undeclared
Date: 26 Jul 1994 19:29:09 GMT

aj@z2-db11.ms.DeTeMobil.de (Andreas Joppich) writes:

i got same problem.
the problem is using ps/2 mouse.
================================

>Today i got the new 1.1.36 version. After patching the 1.1.35 and
>running the various commands below I get the following error-message:

>make mrproper ; make config
>make dep ; make clean ; make

> 
>[..lots of stuff deleted..]

>/usr/src/linux/include/linux/timer.h: In function `init_timer':
>In file included from psaux.c:28:
>/usr/src/linux/include/linux/timer.h:85: `NULL' undeclared (first use this function)
>/usr/src/linux/include/linux/timer.h:85: (Each undeclared identifier is reported only once
>/usr/src/linux/include/linux/timer.h:85: for each function it appears in.)
>make[2]: *** [psaux.o] Error 1
>make[2]: Leaving directory `/usr/src/linux/drivers/char'
>make[1]: *** [driversubdirs] Error 1
>make[1]: Leaving directory `/usr/src/linux/drivers'
>make: *** [linuxsubdirs] Error 1


>Am I doing something wrong or is it a bug ? 
>-- 
>_______________________________________________________________
>Andreas Joppich                              aj@ms.DeTeMobil.de
>DeTeMobil GmbH                        
>D-48153 Muenster                         Phone +49-251-977-2943              
>Germany                                  Fax   +49-251-977-2949
>---------------------------------------------------------------
>   The above statements are my privat and personal opinions 
>       and not represantive for the DeTeMobil company !  

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

From: matt@csc.albany.edu (Matt Womer)
Subject: Re: Voice Mail cards.
Date: 25 Jul 1994 14:02:33 GMT

In article <3104sq$m2@brachio.zrz.TU-Berlin.DE> jorgagif@w250zrz (Joerg Mertin) writes:

> Well, under Linux you don't need a Voice-Mail-Card. I have an Old
> Galaxy-NX Card (Soundblaster Compatible) and installed on my system
> the metamail Package. Since the I'm using Voice mail for some Close
> Sites from home.
> By the Way, I also have an Phone-Answering System Working with a
> U-1496 E Zyxel and vgetty that mails me the incoming call to the Phone
> Administrator. So, why buy such special things ???

My original question was not clear enough, I wish to buy a voice mail card
that answers the phone and can store and retrieve messages stored on the
computer.

I don't wish to be able to send e-mail containing sound.  Sorry.

-Matt
--
matt@csc.albany.edu

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

From: i31ade@applsrv.rz.unibw-muenchen.de (Frank Derichsweiler)
Crossposted-To: comp.os.linux.admin
Subject: Re: DOES ANYONE KNOW ABOUT THE MAILINGLISTS? (hello, is anyone there?)
Date: 26 Jul 1994 19:05:15 GMT

kenb@qatrix.lonestar.org (ken brookner) writes:

>i'm having troubles also...  i subscribed to several, got the confirmations
>back, but for several days have received nothing.  i used to be on the ml
>from my work address and received many msgs daily...  

>anyone else still having problems?

>kenb@metronet.com
>kenb@qatrix.lonestar.org

mail an empty mail to linux-activists-request@niksula.hut.fi
and you will get the instruction set

Frank


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

Date: Sun, 24 Jul 1994 14:53:52 +0200
From: Eberhard_Moenkeberg@p27.rollo.central.de (Eberhard Moenkeberg)
Subject: Re: Xfree86: increase pallate?


Hello Eric Youngdale and all others,

on 23.07.94 Eric Youngdale wrote to All in USENET.COMP.OS.LINUX.DEVELOPMENT:

EY> : >I heard that millions of colors would arrive with XFree 3.1
EY> :
EY> : Perhaps you are joking, but someone out there will believe you.
EY> : XFree86[tm] 3.1 will not increase the colors available.
EY>
EY>    I heard that you will only get the additional colors if you are
EY> using FreeLSD or NetLSD :-).

Time for a joint venture. ;-)

Greetings ... Eberhard


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

Date: Sun, 24 Jul 1994 15:16:33 +0200
From: Eberhard_Moenkeberg@p27.rollo.central.de (Eberhard Moenkeberg)
Subject: Re: buffer cache or isofs bug?


Hello pe1chl and all others,

on 23.07.94 pe1chl wrote to All in USENET.COMP.OS.LINUX.DEVELOPMENT:

>> :   mount -t iso9660 -o ro,block=2048 /dev/sbpcd2 /CD1
p>
>> leads to my errors, and with the default "block=1024" everything runs fine.
p>
p> So we can consider this case closed? :-)

The new InfoMagic "Linux Developer's Resource" CD set seems globally ok
under "block=1024", but if you do a "cd live/usr/TeX/lib" on the second
CD and try to "cd ..", you can't ("du" needs it), and the isofs routines
tell something like "Backlink not properly set".

The weird things with "block=2048" are still there, and they do not
happen with other CDs (at least not the ones written with Eric Youngdale's
"mkisofs" program - Joel, any reason for not using it?). I still have
to verify if the reason lies only within sbpcd.c - I fear it is not.

Maybe someone can help me.

p> Actually, there really are problems in Linux when errors occur on the
p> disk devices, not only CD-ROM.
p> Any read error on the physical media will eventually result in the
p> wellknown "Weird  - unlocked, clean and not uptodate buffer on list..."
p> error for that sector.
p> Also, I think it sometimes can drive the system into an inconsistent state,
p> but I have no clear data on that.  Maybe it keeps the garbage data from
p> the failed read as the data for that sector??
p>
p> Sometimes one gets read errors on floppy disks, and I also have one CD-ROM
p> with many bad blocks on it.  This is not fun to use...

Does anyone have experiences using "block=2048", f.e. with SCSI CDROM drives?

Greetings ... Eberhard


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

From: mlord@bnr.ca (Mark Lord)
Subject: Re: IDE patch won't work w/new kernels?
Date: 25 Jul 1994 17:10:58 GMT

In article <CtI3Eo.J3v@cs690-3.erie.ge.com> teffta@cs690-3.erie.ge.com writes:
>In article 3Ip@seagoon.newcastle.edu.au, c9219517@sage.newcastle.edu.au (Scott Howard) writes:
>>Timo Kokkonen (tjko@tarzan.math.jyu.fi) wrote:
>>
>>: IDE Performance Patch v2.0 [by Mark Lord] doesn't work with new 
>>: WD540 drives??? Or is it just my kernel 1.1.30 that causes the problem?
>>
>>There's a very simple reason for this - they are already in the kernel!!
>
>I noticed this, when patch32 or so didn't patch cleanly into my
>kernel. I repatched cleanly from pl13 -> patch33, and now hdparm
>gives rc=-1, as if the patches are not in the kernel after all.
>Yet all the chunks fail if I try to apply the hd.diffs. So what's the
>secret?

Recompile hdparm.c and try again.  The ioctl codes must have changed..
-- 
mlord@bnr.ca    Mark Lord       BNR Ottawa,Canada       613-763-7482

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

From: lm@stanford.edu (Larry McVoy)
Subject: Re: threads in kernel
Date: 26 Jul 1994 17:52:26 GMT

Could you please explain what you mean by threads?  Are talking about
Sun like threads, where there are two sorts of processes, processes
that map 1:1 with an address space and processes (threads) that map
many:1 with an address space?  I personally think this is the wrong
approach.

SGI has a model which is like the clone() stuff discussed here recently.
A "thread" is simply a new process that happens to share (part of) the 
parent's address space.  That is easy to implement, easy to scale, and
simple.

The semantic problems with introducing a new programming model that goes 
along with Sun like threads is not worth it.


G Dinesh Dutt (brat@htilbom.ernet.in) wrote:
: Hi everybody,
: 
: I have been seeing a lot of messages with people interested in seeing threads
: in Linux kernel. Well, development for one has already started. We'll let you
: know as and when results come in.
: 
: Dinesh
: ----
: There's more to life than just increasing its speed.
:                                               - Mahatma Gandhi.
: G. Dinesh Dutt,                                       email : brat@htilbom.ernet.in
: Project Leader,                                       voice : 8321144/8349393/8391478
: Hinditron Tektronix Instruments Ltd.,
: SDF-2, Unit 63-A, SEEPZ, Andheri (east), Bombay - 400096.
: 

--
--
Larry McVoy                     lm@cs.stanford.edu               (415) 821-5758

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: threads in kernel
Reply-To: pe1chl@rabo.nl
Date: Tue, 26 Jul 1994 17:10:20 GMT

In <3128ql$mpe@senator-bedfellow.MIT.EDU> G Dinesh Dutt <brat@htilbom.ernet.in> writes:

>Hi everybody,

>I have been seeing a lot of messages with people interested in seeing threads
>in Linux kernel. Well, development for one has already started. We'll let you
>know as and when results come in.

I'm confused...  I think threads *already are* in the Linux kernel.
What are you developing?   Is it a library to make them more easily
usable from a C program?

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: DOS EMU under 1.1.34
Reply-To: pe1chl@rabo.nl
Date: Tue, 26 Jul 1994 17:15:17 GMT

In <312knd$ela@pheidippides.axion.bt.co.uk> stevebr@cherokee (Steve Brown) writes:

>Hi Folks,
>       I want to use Dosemu0.52, and the instructions tell me I need to
>upgrade my kernel ( I was on 1.0.8 ) so I did. Only snag is that Dosemu
>wont compile, it moans about too many things to mention ( and they
>fly off my screen at a rare rate of knots ), in sigsegv.c and its
>associated header files ( one of them is net.h! ).

I advise you to read some text about redirection of output in the UNIX
system, so that you can catch this output without problem.  I could post
some hints but it depends on the shell you are using, so running a "man"
for that shell is probably better (and also more educating)

>Does anyone else have this problem, or could someone tar the binaries
>up for me? Is my source tree corrupted ( the kernel compiled just fine! )
>Or is Dosemu0.52 not good with 1.1.34, in which case which source tree should
>I use?

Dosemu doesn't work with very recent kernels.  Try a slightly older version,
before 1.1.32 I think.

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

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


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