>>>>> "mk" == mk <[EMAIL PROTECTED]> writes:
mk> My further tests with loop-mounting the hdimage appear to have exposed a
mk> problem - just as we were about to use this technique at a customer site.
mk> When i copy files from Linux to the loop-mounted image (no dosemu running),
mk> there is a significant chance that the fs layer starts to complain :
mk> end_request: I/O error, dev 07:00, sector 670
mk> loop: block 424 not present
mk> The hdimage will then automatically remount read-only. I had not seen
mk> these before because i was more concerned with copying from the hdimage
mk> then. Am i missing a mount option, do the mkdexe-generated hdimages have
mk> holes in them by default, or is this another case of 'don't do it' ?
I believe by default our hdimage files have holes in them.
Eric
