Messages in this thread | | | From | Olaf Dietsche <olaf.dietsche#> | Subject | Re: Filesystem Capabilities in 2.6? | Date | Sat, 02 Nov 2002 19:18:10 +0100 |
| |
Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de> writes:
> "Theodore Ts'o" <tytso@mit.edu> writes: > >> HOWEVER, if we're going to do it, Olaf's patches is really not the way >> to do it. If we're going to do it at all, the right way to do it is >> via extended attributes. Using a sparse file to store capabilities >> indexed by inode numbers is a bad idea; it will break if the user uses >> resize2fs on an ext2/3 filesystem, for example. > > Dragging yet another one out of you. This is a pretty strong argument > against my implementation. Any other hints?
With dumping capabilities before resize and restoring them afterwards, you can solve this. See: <http://home.t-online.de/home/olaf.dietsche/linux/capability/dumpcaps.pl>
Regards, Olaf. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |