| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Aug 2009 14:18:50 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Jeff Shanab <jshanab@...thlink.net> CC: Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: Starting a grad project that may change kernel VFS. Early research Re: Starting a grad project that may change kernel VFS. Early research Jeff Shanab wrote: > Rik van Riel wrote: >> Hard links have been done like this in pretty much every >> Unix filesystem since the 1970's. [...] > There is no real way to handle this becasue the two files look the same > to the filesystem. See above; it has been state of the art since the 70's. With hardlinks or symlinks, a graph which represents the FS happens to contain loops. No rocket science involved. [...] > How would I display this information usefully to the user. Certain file managers display the overall size and the size on disk. The latter differs from the former due to - on-disk format overhead, - on-disk compression, - hardlinks and symlinks. If the user copies the directory to another filesystem, the size on disk will generally change. -- Stefan Richter -=====-==--= =--- ==-=- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists