Just thinking about it fast, NILFS2 is a filesystem that wraps around the disk forever and LILO writes a bitmap of where the kernel image is. So if NILFS moves the image then LILO is at lost and will load some data which is not the kernel instead. A fast guess I would say using LILO on NILFS is impossible by design. Envoyà de mon appareil mobile. JÃrÃme Poulin Solutions G.A. On 2011-02-24, at 17:34, dexen deVries <dexen.devries@xxxxxxxxx> wrote: > Hello, > > as NILFS2 doesn't implement the FIBMAP ioctl, LILO cannot be used on it. > I've just learned about it the hard way -- after migrating computer's only > filesystem to NILFS2, running LILO returns: > ioctl FIBMAP: Invalid argument > > I see the FS_IOC_FIEMAP is implemented; perhaps some wrapper around could be > used to provide FIBMAP as well? > > > Regards, > -- > dexen deVries > > [[[â][â]]] > >> how does a C compiler get to be that big? what is all that code doing? > > iterators, string objects, and a full set of C macros that ensure > boundary conditions and improve interfaces. > > ron minnich, in response to Charles Forsyth > > http://9fans.net/archive/2011/02/90 > -- > To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
