From owner-freebsd-current Mon Dec 11 18:10:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA27723 for current-outgoing; Mon, 11 Dec 1995 18:10:07 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA27718 Mon, 11 Dec 1995 18:10:03 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tPJRr-0000zeC; Mon, 11 Dec 95 19:24 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tPJLa-000DDbC; Mon, 11 Dec 95 19:17 WET Message-Id: Date: Mon, 11 Dec 95 19:17 WET To: sos@freebsd.org, current@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Mon Dec 11 1995, 19:17:33 CST Subject: WHAT is going on in -current ??????? Cc: jkh@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk [0]sos@freebsd.org writes: [0]On top of that the matcd driver no longer works, it read a couble [0]of block then hangs on "netio" :( [0] [0]Oh boy I thought I was getting back into business again, and [0]then this mess..... Uh, the changes made since 2.1.0-RELEASE to matcd in -current were NOT made by the author of the matcd driver. Other feet have trod on this rug. I have been busy adding support for some similar makes of drives and have not even studied the changes, although I guess I will have to when I try to bring my tree back in. I gather that some of the changes are in the name of devfs, or other 2.2-experimental work, or just bits of tidying. Try going back to the driver from 2.1.0-RELEASE. If it doesn't work, then some underlying kernel service has been broken or is in a transient state. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983