Path: utzoo!utgpu!watserv1!watmath!uunet!snorkelwacker!mit-eddie!andante!ulysses!dptg!mtune!jcm
From: jcm@mtune.ATT.COM (John McMillan)
Newsgroups: unix-pc.general
Subject: Re: HELP with *BLOCK* device driver
Message-ID: <293@mtune.ATT.COM>
Date: 5 Feb 90 22:25:01 GMT
References: <1990Feb5.074541.26335@stb.uucp>
Organization: AT&T BL Middletown/Lincroft NJ USA
Lines: 30

In article <1990Feb5.074541.26335@stb.uucp> michael@stb.uucp (Michael Gersten) writes:
>
>HELP! I'm getting bind errors with this.
>
>Repeat-by:
>masterupd -a block open close strategy release nfs
>cc -c nfs.c
>lddrv -av nfs
>
>lddrv complains: BIND error: Invalid parameter.

	I don't find that error in the sources.  Are you running 3.51 ?

>Note that if I say it is a char driver, with read instead of strategy,
>it works fine. Can block device drivers be loaded at all?

	I've never dealt with a BLOCK driver that lacked an
	underlying CHAR driver.  This presumption may be
	built into the code.  You can always FAKE the CHAR
	entries -- aborting an OPEN.

>(this is an attempt to write a driver whose data is supplied by another
>user program; in this case getting data from another machine by serial
>port).
:
	I didn't see -- in a 15 second intense scrutiny ;-) --
	WHY you were writing a BLOCK driver rather than a CHAR
	driver....  Nor shall I worry about it.

john mcmillan -- att!mtune!jcm -- muttering for SELF, not them