In message <6ae10d76-ac2f-4d7b-a985-ee072949e...@xcllnt.net>, Marcel Moolenaar writes:
>Rather than just calling it a bad idea, why not come up with something >constructive? One thing I would like to point out, is that the potential for damage is very different in R/O and R/W mode. I think it would be prefectly justified to refuse a R/W open of a provider if there is credible reason to think that might ruin data. But I have a very hard time seeing the point in preventing a R/O open which would allow people to examine if there is an actual problem. At the most basic level, not creating the slices prevents people from even running "fsck_msdosfs -n /dev/da0s1" to get an idea if things are totally bonkers... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ svn-src-head@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
