Date: Tue, 4 Dec 2001 17:08:18 +0700 From: Eugene Grosbein <eugen@www.svzserv.kemerovo.su> To: Tony <tony@ubik.demon.co.uk> Cc: freebsd-fs@freebsd.org, Eugene Grosbein <eugen@grosbein.pp.ru> Subject: Re: [PATCH] msdosfs_vfsops.c: some kind of FAT32 incompatibility? Message-ID: <20011204170818.A57192@svzserv.kemerovo.su> In-Reply-To: <Usa06KAinID8IwoI@ubik.demon.co.uk>; from tony@ubik.demon.co.uk on Tue, Dec 04, 2001 at 08:31:30AM %2B0000 References: <20011203235203.A435@grosbein.pp.ru> <Usa06KAinID8IwoI@ubik.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 04, 2001 at 08:31:30AM +0000, Tony wrote: > >Once I decided to use some of this space for Windows95 residing > >at the beginning of drive but there was no standard tools to make it > >visible for Win95. So I used Norton Utilities 3.01 for Win95 and > >its Disk Editor to create new "Extended Partition" residing > >at the end of drive > I think you would have been better to create another Primary Partition. > Windows 9x and NT cannot create more than one Primary Partition on a > drive, but they are perfectly happy to use them. I tried to have another Primary but there are some problems. First, it is waste of last entry in MBR - this space really just does not need to be Primary. Second, there were some problems with disk checking tools I cannot remember now. Creating new Extended produced less troubles. > >and to link it to existing Extended Partition. > >Disk Editor has feature named 'Recalculate partition' that should > >guarantee correctness of new partition record. > This really sounds messy to your extended partition fragmented like > this. It will certainly cause problems with disk checking tools, as you > have found. At the other hand NDD worked just fine when that FAT32 needed fixes. > >The reason is that NDD changes the only byte in FAT32 signature: > >it changes BOOTSIG2 from 0 to 0x52. The filesystem is still usable > >by Windows but cannot be mounted by FreeBSD. > >Well, I can live with this, applying the following patch before each > >"buildworld". I just think that somebody else can hit this hole too. > > I think very few people will do anything similar to you with extended > partitions. > > On the other hand as NDD has a feature for tagging strange partitions > some other people may also find their FAT32 partitions ignored by > FreeBSD. I expect NDD is mostly right that the partition information > should be complained about, but if the user has been made aware and told > NDD to ignore it FreeBSD should ignore it too. > > >So I propose the patch that handles this situation. > >The patch is for RELENG_4 but that piece of code has not changed for > >long time so it should apply to CURRENT cleanly in spite of different > >file locations. > > > >diff -ur ./bootsect.h /usr/src/sys/msdosfs/bootsect.h > >--- ./bootsect.h Sat Aug 28 08:48:06 1999 > >+++ /usr/src/sys/msdosfs/bootsect.h Mon Dec 3 22:27:13 2001 > >@@ -69,6 +69,7 @@ > > #define BOOTSIG0 0x55 > > #define BOOTSIG1 0xaa > > #define BOOTSIG2 0 > >+#define BOOTSIG2_COMPAT 0x52 > > Please, please if this is committed comment clearly what this is for. I am not a committer but want people to say their pros and contras so it would be discussed if I find somebody to commit this. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011204170818.A57192>