Date: Wed, 09 Sep 1998 11:38:47 +0100 From: Mark Blackman <tmb@rcru.rl.ac.uk> To: dag-erli@ifi.uio.no (Dag-Erling =?iso-8859-1?Q?Co=EFdan?= =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: Bruce Evans <bde@zeta.org.au>, freebsd-current@FreeBSD.ORG Subject: Re: [LONG PATCH] Re: 2048-byte sector support for DOS filesystem. Message-ID: <199809091038.LAA07810@bird.te.rl.ac.uk> In-Reply-To: Your message of "09 Sep 1998 10:18:41 %2B0200." <xzphfyhzoke.fsf@hrotti.ifi.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> Bruce Evans <bde@zeta.org.au> writes: > > > Such is my understanding. Somebody in the CAM team will have to > > > confirm it. > > CAM should have no affect on this, since the driver already supports > > 2048-byte sectors. msdosfs doesn't support them. It begins by > > attempting to read a 512-byte boot sector... > > Ah. I was thinking of the inability of the od driver to handle media > with >512 byte sectors. Then this is a different problem altogether, > which the second patch in kern-7210 addresses: [patch omitted] Thanks for clearing that up for me. So in summary, the od/scsi-related patches in kern-7210 are superceded by the CAM work, but the msdosfs-related patches are still meant to be applied if you want this 2048-byte block functionality in msdosfs. This then would imply (questions of labour aside) that the msdosfs-related patches are appropriate for inclusion in CURRENT at some convenient point, no? I do understand that there literally hundreds of more important things for the kernel gods to address, but I just want to add my (possibly irrelevant) vote for increasing it's priority somewhat. Cheers, Mark Blackman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809091038.LAA07810>