Date: Thu, 7 May 1998 05:33:18 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: current@FreeBSD.ORG Cc: scsi@FreeBSD.ORG Subject: Re: SLICE broken Message-ID: <Pine.BSF.3.95.980507052845.28826A-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.3.95.980507031838.28597A-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
To reply to my own mail.. I've (I think) made this work (I'm typing on such a kernel) at least in the common case. If you are really worried about system integrety (then what are you doing on -current :-) then it might be an idea to not use SLICE/DEVFS for a few days till I manage to go through all the code paths again just to be sure. I think I've just added "fix SCSI code" back onto my list, at least till we see CAM more completely deployed. julian On Thu, 7 May 1998, Julian Elischer wrote: > > Because I origially wrote the scsi code I was under the mistaken > impression that I knew what was going on there and today's checkins > of sd.c have screwed up if SLICE/DEVFS is defined. > > backing down to 1.127 should make it work as well as before. > 1.128 is definitly bogus. I'm working on it but > some things happenned in the scsi code during my absence that are > definately done absolutly backwards. (right idea but backwards.) > for example one cannot get rid of all the devsw entrypoints > even of one doesn't need them any more :-] > > julian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980507052845.28826A-100000>