Re: FIBMAP ioctl missing

[dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

On Friday 25 of February 2011 01:21:53 you wrote:
> 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.

That's a good point, thanks.

A dirty hack comes to my mind, back from the days of DOS: files marked with 
`system' attribute were not moved during defrag (important for io.sys & 
msdos.sys). Perhaps using some sensible attribute (i? t? a new one?) would 
prevent nilfs_cleanerd from moving the file?

Would require implementing attributes on NILFS, thou.

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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html