>- unit of disk space allocation for the kernel image file is > block. That is, optimizations like UFS fragments or reiserfs tails are > not applied, and > > - blocks that kernel image is stored into are real disk blocks (i.e., > there is a way to disable "delayed allocation"), and > > - kernel image file is not relocated, i.e., data are not moved into > another blocks on the fly.
It also has to implement the ioctl that tells you what blocks a file is in (that kind of implies much of the above). Except if the LILO installer makes special provisions as for Reiserfs, of course. To be really exact, it's OK for the blocks to move, as long as it doesn't do so so subtly that the user doesn't know to rerun the LILO installer. E.g. you can move the blocks of the kernel file if someone overwrites it. -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
