> This brings up another point: Repair is always possible with FreeBSD.
Quick tip for you guys -- create your own mtree file for /usr/local,
/usr/home, and /var via cron nightly. With that data and the ones provided
for the base system you can fix a machine that someone accidentally "chown
-R /" within minutes. The fact that Linux has nothing equivalent is
frightening. Mtree has saved me a lot of time when customers have broken
freebsd-stable@free... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@free..."