Hi,
> this of course is a problem if the ilist file is created by software
> outside the chroot.
This happens to be the case with amd64/i386, but not always a cure for
other combinations (not quite sure if there are other combinations).
That said, it is important to prevent the potential 64-bit i-node
problem (although it's not widespread enough to be a problem today).
> however, if the software is created *in* the chroot, i think there
> might still be potential problems if the inodes being referenced are
> actually 64bits on the real filesystem.
> the only potential issue is whether this may create a compatibility
> problem for pre-existing non-LFS versions...
'cowdancer --update' to this new version will fail on i386 arches.
I'd expect quite a few bug reports and angry users.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
