[EMAIL PROTECTED] wrote:
> In fact, I think both LILO and ReserFS (and arguably Linux in general)
> have gone the wrong way with their blockmap/unpack code/ioctls.
>
> The Right Way to do this would be to make a program called "mkbootloader"
> or something that will take a filename and do 2 things with it: produce
> a blockmap in a well-known format, and communicate via a generic ioctl
> (NOT a filesystem-specific one) that it needs to be on hardware block
> boundaries and be in a fixed location.
OK, after thinking about this some more, it seems clear that ReiserFS
should *automatically* "unpack" files which have the Linux blockmap ioctl
made upon them.
Having to do filesystem-specific hacks when the filesystem already has
a clue about what's happening is just broken behavior.
I'm going to talk to the Reiser folks to see about this, probably tonight/
tomorrow sometime.
I think I'll also propose this on the Linux-Kernel email list as
the "defined" behavior of the FIBMAP ioctl, as well.
--
Erich Stefan Boleyn <[EMAIL PROTECTED]> http://www.uruk.org/
"Reality is truly stranger than fiction; Probably why fiction is so popular"
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
