NETLDISC

utzoo!decvax!ucbvax!william utzoo!decvax!ucbvax!william
Sat Nov 7 23:12:39 AEST 1981


That is not too far from the truth.

The problems we encountered with NETLDISC could be split in two
catagories:

	1)  Buffer syncronization/lockout
	2)  dz11 character lossage

The first was due to programming errors that we didn't have time to fix.
The total amount of time allotted to NETDISC was about 20 hours. We never
got around to even reducing our errors, since berknet was a important
resource not to be messed with.

The second was the failure to implement the silo code on the dz11. This
was down on a seperate machine, but never merged. The problems with NETLDISC
probably are more due to sheer negligence that to serious technical problems.

It turns out that one of the prime developement machines here didn't even 
have access to the berknet, so there was no interest in cleaning it up.

As far as the ioctl's go, I doubt this was the trouble, because NETDISC
is completely paranoid  about such. I suspect that the problems with it could
be solved in a day's worth of a programmers time....

	Bill Jolitz.



More information about the Comp.bugs.2bsd mailing list