Don <[EMAIL PROTECTED]> wrote:
> Softupdates is definitely a viable solution however it does not
> address several issues and the license is not a BSD license so it
> makes me uncomfortable.
Well, Kirk's idea is to put them under a BSD-style license as soon as
possible, so in the long run, you might waste engergy...
What `several issues' are you referring to? Kirk mentioned us in a
comparision between various methods that there are exactly two
problems he's seeing on the downside for softupdates: code complexity,
and a large memory footprint. So unless you're working for machines
with little memory, what else do you have in mind? (For those
interested, for transaction logging, the downside is that it won't
help for occasional filesystem operations, since it doubles the disk
IO for this. It only helps the case `massive filesystem operations'
like "rm -rf" etc.)
--
cheers, J"org
[EMAIL PROTECTED] -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
