On Sun, Nov 04, 2001 at 07:14:18PM +1000, Anthony Towns wrote: > However this doesn't work quite frequently, since the umount fails > if there's any file in /usr that's been deleted (ie, was in a package > which has been updated), but is still being used (a /usr/lib/lib* that's > referenced by a long running program, or a /usr/bin/* program that's still > running, like apt-get or dselect). This is because the filesystem will > be modified when the file is closed, because the inode will be freed, > so it's obviously not read-only. isn't this a filesystem bug? it could delete the inode on-disk, but still keep it in-memory as long as it's being used by some process that would make it possible to remount,ro the fs i think the kernel-people are aware of this (i read about this problem some time ago...) but don't know if anyone is working on a fix -- CU, / Friedrich-Alexander University Erlangen, Germany Martin Waitz // [Tali on IRCnet] [tali.home.pages.de] _________ ______________/// - - - - - - - - - - - - - - - - - - - - /// dies ist eine manuell generierte mail, sie beinhaltet // tippfehler und ist auch ohne grossbuchstaben gueltig. /
Attachment:
pgpq978EhMIBG.pgp
Description: PGP signature