On Tue, 2 Jan 2001, Aaron J. Grier wrote:

> I have a NeXT-formatted floppy with an msdos filesystem [1], but
> mount_msdos doesn't grok it.  mtools has no problem.  the bootsector
> looks like this:
>
> 0000000 00e9 4e00 5845 2054 2020 0020 0102 0001
> 0000010 e002 4000 f00b 0009 0012 0002 0000 0000
> 0000020 0000 0000 0000 0000 0000 5500 544e 5449
> 0000030 454c 4444 5349 0000 0000 0000 0000 0000
> 0000040 0000 0000 0000 0000 0000 0000 0000 0000
>
> with nulls all the way up to 512 bytes.
>
> even file doesn't know what it is since it's missing the sequence 0xaa55
> at offset 0x01fe.  (I haven't tried modifying the disk yet...)
>
> seems like it would be trivial to update the code in the msdos mounting
> routines, if only I knew where to look.  :)
>
	sys/msdosfs/msdosfs_vfsops.c:msdosfs_mountfs() might be a good
	place to start. It has a comment of the form:
        /*
         * Read the boot sector of the filesystem, and then check the
         * boot signature.  If not a dos boot sector then error out.
         */

> fantastic news about SCSI, Darrin.  who should I pester about getting
> the non-512 byte per sector disks supported?  Almost all of Koji's PRs
> are still open!  :)
>
	I believe the situation may have changed now the Unified
	Buffer Cache has been committed, someone should probably try
	updating Koji's PRs to -current...


		David/absolute		-- www.netbsd.org: No hype required --