On Tue, 11 Dec 2001, Umesh Vaishampayan wrote:
On Tuesday, December 11, 2001, at 10:31 AM, Chris Bednar wrote:
I'm fooling with using UFS, and I notice that
I get in trouble at the 4-gig limit.
That's artificial limitation put in UFS few years ago when I implemented
UBC. At that time the VM did not support 64 bit data paths. Hence anything
above 4GB was not accessible. [Well, you could try to access it, but the
offset would wrap and lead to interesting :-) data corruption]. Hence the
following code was added:
Thanks for the clear answer! (and thanks to Louis for his, too) I feel better and better about this OS... I might even try building a kernel.
bsd/ufs/ffs/ffs_vfsops.c:
Yep, I had just found that.
Now that VM supports 64 bit data paths, the code above can be removed.
But will it work... well, I went through this with Linux; maybe I'll try it again.
Is the darwin
UFS implementation not 64-bit clean?
Yes it is.
Well, it is, in the sense that it won't (necessarily) crash if there's a file over 4GB on the platter, but truncating the file size this way doesn't seem all that clean to me...
3) LFS-ready
That you do not get without doing LOTS of work on it first...
Oh, don't be silly! There are only 15,364 lines of code in bsd/ufs/* , and that includes comments! how much work could it be ;) ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/