Hi Michael. Michael Schmitz - 29.06.18, 11:07: > > But it's up to the person (which is not Linux) formatting the disk > > to > > not try to use > > it on systems that cannot handle it, and may destroy it. > > > >>> Let me clarify: what exactly would the kernel option allow? When > >>> to use it?>> > >> Whether to use it if safe (on Linux). But whatever Linux does > >> (after > >> this patch), access will go to the right area of the disk (as > >> specified by the RDB) so Linux won't any longer stomp on anything > >> that would have mattered to 32 bit disk drivers. So it really > >> should be safe.> > > Personally, I see no reason to depend on a kernel option, if it is > > safe to use. Just use it. > > So to recap - someone partitions a disk on AmigaOS 4.x, taking > advantage of the large block device support there. > Using that disk on AmigaOS 3.1, data loss ensues. Whether or not Linux > (patched) ever touched the disk has no impact on that outcome. I am not even completely sure about that. Frankly I have no idea what would happen when using such a disk on AmigaOS 3.1 *without* NSDPatch or TD64 support (I think you could patch AmigaOS 3.1 with 64 Bit support already and some 3rd party harddisk controllers by Phase 5 hat TD64 support at that time already). Unless I try it, which I won´t at the moment, I´d say the behaviour is largely undefined. But hey, undefined means it may just overwrite start overwriting from the beginning of the disk beyond 32 bit. And I think that is quite likely. It could also crash, but if its an overflow I don´t think why it would crash. Anyway, I never tried this out. But in any way: This would happen or not happen no matter whether Linux parsed the RDB or not. I still think that the native OS warning really does not hurt… but I´d spare myself the kernel option. Having the warning without the kernel option would be a compromise between being cautious and being bold :). Thanks, -- Martin
