Date: Sun, 22 May 2011 21:57:02 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Adrian Chadd <adrian@FreeBSD.org>, src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, "Andrey V. Elsukov" <ae@FreeBSD.org>, Stefan Farfeleder <stefanf@FreeBSD.org>, svn-src-head@FreeBSD.org, Warner Losh <imp@bsdimp.com> Subject: Re: svn commit: r221972 - head/sys/geom/part Message-ID: <4779.1306101422@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 22 May 2011 13:28:35 MST." <6AE10D76-AC2F-4D7B-A985-EE072949ECC4@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <6AE10D76-AC2F-4D7B-A985-EE072949ECC4@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 phk@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4779.1306101422>